Skip to content
TapPass Internal

Check pack

Check pack

Section titled “Check pack”

A Check pack is a named bundle of pipeline steps that solve one functional concern.

"PII redaction" is a check pack. "Secret detection" is a check pack. "Prompt-injection defense" is a check pack. Operators attach packs to pipelines instead of authoring every step from scratch.

Check pack ≠ Compliance pack. A check pack is function-shaped (what risk does it address?). A Compliance pack is regulation-shaped (what ISO/NIST control does it satisfy?). A compliance pack is typically a curated combination of check packs.

At a glance

Section titled “At a glance”
Composed ofpipeline steps (one to many) with sensible default config
Attached toa Pipeline
Authored byTapPass platform (first-party packs) or customer (custom packs)
Versionedyes — packs follow semver; pipelines pin pack versions
Statuslater

First-party packs (planned set)

Section titled “First-party packs (planned set)”
PackWhat it does
pii-redactionDetect + redact PII in prompts and responses (names, emails, SSNs, addresses)
secret-detectionDetect + block API keys, passwords, tokens leaking into LLM input/output
prompt-injection-defenseHeuristic + classifier-based prompt-injection scanning before the LLM call
code-reviewStatic-analysis-style checks for code the agent generates (secret strings, dangerous functions)
sql-injection-defenseSQL injection pattern detection on tool calls that hit databases
exfiltration-detectionOutbound-data-volume + pattern checks (e.g., dumping a customer table to an LLM)
cost-budgetPer-session / per-agent / per-org token budget enforcement
loop-guardSliding-window detection of runaway destructive operations

Why this concept exists

Section titled “Why this concept exists”

Pipeline steps are the atomic unit; check packs are the composable unit. An operator authoring a pipeline shouldn't be choosing 8 individual PII detector steps and configuring each — they should attach pii-redaction and tune one setting.

Packs also let TapPass (and the community) ship updates to a category of protection without each customer rewriting their pipeline. When prompt-injection-defense v1.4 adds a new classifier, customers pinned to the major version pick it up.

What's in a pack

Section titled “What's in a pack”
pii-redaction.pack.yaml
id: pii-redaction
version: 1.2.0
steps:
  - id: detect.pii.names
    config: {confidence_threshold: 0.85}
  - id: detect.pii.contact
    config: {include: [email, phone]}
  - id: redact.pii.findings
    config: {strategy: replace, replacement_marker: "[REDACTED]"}
compliance_tags: [gdpr.art-32, ccpa.de-identification]

The compliance_tags are how check packs feed into Compliance packs — a compliance pack maps a regulation control (e.g., GDPR Art. 32) to the check packs that satisfy it.

Surfaces

Section titled “Surfaces”
PersonaSurfaceWhat they do
OperatorAdmin UI → Pipeline editor → Add packAttach a pack with one click
Operatortappass pipeline attach-pack <pipe> <pack>CLI equivalent
Pack authorPack SDK + specAuthor a custom pack
Section titled “Related concepts”