Category Summary
Detection Profiles
Each profile activates a different set of engines, which determines which signatures run:MITRE ATLAS Technique Coverage
All 100 signatures map to one or more MITRE ATLAS techniques. The table below lists every covered technique, its name, and the number of signatures mapped to it.
InferenceWall implements these ATLAS mitigations across all signatures:
- AML.M0015 Adversarial Input Detection
- AML.M0020 Generative AI Guardrails
- AML.M0006 Ensemble Methods
Full Catalog
Prompt Injection (67 signatures)
Direct Injection — INJ-D (30 signatures)
Indirect Injection — INJ-I (10 signatures)
Obfuscation — INJ-O (17 signatures)
Semantic — INJ-S (10 signatures)
Semantic signatures use FAISS + MiniLM embeddings to catch paraphrased attacks that bypass keyword and regex detection. They require the Standard or Full profile.Content Safety (9 signatures)
Toxicity — CS-T (7 signatures)
Bias — CS-B (2 signatures)
Data Leakage (14 signatures)
All data leakage signatures run on output (LLM responses).PII — DL-P (8 signatures)
Secrets — DL-S (6 signatures)
System Prompt (4 signatures)
Agentic (6 signatures)
Signature Fields Reference
Every signature YAML file declares the following fields:Severity and Confidence Levels
Severity reflects the risk if the threat is real:
Confidence reflects how certain the engine is that a true positive was detected. Low-confidence matches contribute fewer effective points due to confidence-weighted scoring.
Licenses
- Engine code (Rust, Python, CLI, API): Apache-2.0
- Community signatures (
catalog/): CC BY-SA 4.0 — modifications must be shared back under the same license
To add your own signatures or override built-in ones, see the Custom Signatures guide.