Attack scenarios
A scenario describes an adversary persona, the technique they exercise, and the assertion that decides whether the defense held.
Key points
- Saved custom templates record `updated_at`; each run preserves the concrete request it executed for later review.
- Built-in LLM probes retain stable category and technique attribution where the corpus defines it.
- Selected built-in LLM scenario families include versioned paraphrase variants for scoped robustness checks.
- Custom scenarios can be added via the scenario authoring API.
01
Built-in scenario families
- Prompt injection / jailbreak (LLM01).
- Sensitive information disclosure (LLM02).
- System-prompt leak (LLM07).
02
Custom scenarios
- Save a title, category, optional tags, and a schema-valid RunRequest template through the scenario API.
- Tenant and plan boundaries are enforced before the template is stored.
- The engine evaluates the saved template through the normal evidence pipeline; executable grader uploads are not supported.