// products
Attack scenarios
Each attack scenario focuses a Red Teaming report on one security question. Browse 49 built-in scenarios to see what they check and what a finding can tell you. Each page links to related OWASP, CWE, or vendor guidance.
Applications · Agents · Repositories
Choose a scenario
Choose Attack scenario in red-team settings or when creating a report. General assessment is the default and keeps the full methodology. Search the dropdown by name, objective, or ID to select a focused scenario for your target category.
A selected scenario focuses the assessment on that objective. Unselected scenarios are outside the assessment and must not be treated as tested. For Agents, unrelated framework entries are marked outside_selected_assessment.
Supply the prerequisites
Review the scenario’s required capabilities and setup. Supply authorized identities, expected policy, and disposable fixtures needed to exercise the objective. Keep passwords and tokens in the encrypted credential fields. Use the specific prompt for non-secret fixture references and expected policy.
Missing prerequisites are reported as blocked. Unsupported capabilities require a not applicable explanation. Selecting a scenario does not provide missing capabilities or expand the authorized scope.
Create and manage custom scenarios
Organization owners can choose Add new scenario in the dropdown or Edit scenario for a selected custom scenario. The modal requires only a Name and What should we test? in plain language. Selecting a preset first prefills the instructions with its objective. Superagent discovers the relevant capabilities and determines the testing approach, evidence, and finding classification; missing required setup remains blocked.
The Custom scenarios section in the Red teaming tab lists reusable scenarios for the target category. Owners can add, edit, or delete them there. Each save creates a revision. Settings apply the selected revision to manual and scheduled runs; existing reports and reruns preserve their resolved definition. Deleting removes a scenario from the library, while existing reports and saved run settings retain their pinned version.
Interpret scenario coverage
The report labels the selected scenario and tracks coverage separately from findings:
| Coverage | Meaning |
|---|---|
| Verified vulnerability | A linked finding passed the existing verification gates. |
| Blocked | Required setup or prerequisites were unavailable. |
| Not applicable | The target does not support a capability required by the scenario; the report explains why. |
| Inconclusive | The available evidence does not establish a verified outcome. |
| Not tested | The scenario has not been exercised. |
Runner-reported negative results remain inconclusive until independently verified outside the target environment, even when baseline, denied-control, and attack-variant evidence is supplied. Zero findings alone is not a pass. Scope, verification, peer review, and remediation requirements still apply. Proposed control relationships are scoped evidence references and do not establish certification or full compliance.
Applications
- BOLA testing for web applications
- Resource ownership in web applications
- Tenant isolation in web applications
- Administrative permissions in web applications
- Account takeover and recovery
- MFA and reauthentication checks
- Session and access revocation testing
- Approval and workflow stages
- Business transaction integrity
- Webhook authentication and replay protection
- Permissions for exports and shared data
- Cross-site scripting (XSS) testing for web applications
- SSRF testing for web applications
- File upload and import safety
- Input injection in web applications
- OPTIMJACK and third-party JavaScript
- NGINX2Root and NGINX worker isolation
- Ruby2Shell testing for web applications
Agents
- Private data in AI agents
- Tenant isolation for AI agents
- Privileged actions in AI agents
- Connected account isolation for AI agents
- Access revocation for AI agents
- Human approval for AI agent actions
- Approval reuse in AI agents
- Sensitive data sent through agent tools
- Indirect prompt injection testing for AI agents
- AI agent memory poisoning
- AI agent knowledge base poisoning
- Authentication for AI agent handoffs
- Trust boundaries for AI agent tools
- Untrusted repository content in coding agents
- AI agent execution isolation
Repositories
- Object-level authorization checks in source code
- Tenant isolation in backend code
- Privileged operations in backend code
- Credential validation and identity binding
- Revoked permissions in backend code
- Approval and state transitions in code
- Interpreter injection in source code
- Outbound request boundaries in code
- Path traversal and file access boundaries
- Parser and native code safety
- Authentication for internal messages
- Execution sandbox isolation in code
- CI and release permissions
- Reachable dependency vulnerabilities
- Secrets in artifacts and diagnostics
- Ruby2Shell testing for repositories