Skip to content

Detection Coverage

The runtime combines fast pattern-based detectors with optional semantic and multi-turn analysis. Inspectors run independently, so one detector failing does not suppress the rest of the chain.

Threat Categories

CategoryPrimary detectorDefault action
Prompt injectionRegex injection inspectorblock
PII and PCIPresidio NER inspectorredact
Jailbreak heuristicsRule-based jailbreak detectorblock
Jailbreak MLML-backed jailbreak detectorblock
Deception and social engineeringConversation-turn inspectorblock
Semantic policy violationsSemantic content policyblock
SQL injectionSQL injection inspectorredact
Shell injectionShell injection inspectorredact
Template injectionTemplate injection pathredact

Detection-to-Decision Flow

Behavior Notes

  • Pattern-based inspectors remain the fastest path and cover canonical prompt injection, SQL, and shell payloads.
  • Presidio handles common PII and PCI entities, while semantic extras add intent-level reasoning when installed.
  • Jailbreak detection can run as both heuristic and ML-backed layers; they are additive rather than mutually exclusive.
  • Multi-turn deception scoring runs in its own stage, separate from single-turn inspectors.

Known Boundaries

  • Encoded or heavily obfuscated prompt-injection content is harder for heuristic detectors than direct override language.
  • Paraphrased or indirect PII forms are weaker matches for standard NER models.
  • Scope matters: the pipeline is designed around guarded request content, not arbitrary upstream storage or system-prompt sources.

Open source but Use responsibly 🛡️