Adversarial testing
AI Red Team & Adversarial Testing Packet
A findings register with executive summary, evidence, and a remediation + retest plan.
The first deliverable is a decision package: what is in scope, what is required, what is blocked, and what can proceed.
No production testing, adversarial activity, access to secrets, or customer-data processing happens without explicit authorization and the right agreement path. Do not enter secrets or credentials here.
What to gather for this packet
Needed: In-scope AI systems · Authorized techniques · Test window & contacts · Access model
Helpful: RAG corpus · Agent tools · Known guardrails
Bring names and high-level descriptions only — exact targets, accounts, and credentials are shared later through a secure channel.
Engagement
Readiness inputs
Deliverables you want
Packet modules
- Scope Brief — What is in scope, what decision is being made, and what success looks like.
- Authorization Statement — Confirmation the org owns, controls, or is authorized to assess the targets.
- Evidence Handling Plan — Where evidence is stored, redaction, retention, and deletion.
- Contract Requirements — The required and conditional agreements for this engagement.
- Draft SOW Inputs — Scope, window, deliverables, and acceptance inputs for the SOW.
- Open Questions — What is still required before a scoping call or private offer.
- Follow-On Recommendations — Natural next services once this engagement completes.
- Target Inventory — The named systems, endpoints, repos, accounts, or surfaces in scope.
- Rules of Engagement — Authorized targets, techniques, window, and stop conditions for active testing.
- Allowed / Prohibited Techniques — Which techniques are authorized and which are prohibited by default.
- Access Plan — How access and test accounts are provisioned through a secure channel.
- Emergency Contacts — Stop-testing and escalation contacts reachable during the window.
- Data Handling Plan — Data sensitivity, masking, sample-only, retention, and deletion rules.
- Deliverables Plan — The artifacts the buyer will receive and in what format.
- Retest Plan — How remediation is confirmed after fixes land.
AI Red Team & Adversarial Testing Packet — preview
Adversarial testing
Scope Brief
- Organization: To be specified during scoping
- Decision: A findings register with executive summary, evidence, and a remediation + retest plan.
- Driver: We need adversarial validation of prompt injection, RAG exposure, tool abuse, tenant leakage, and unsafe autonomy.
Authorization Statement
- Not yet confirmed — required before any access or testing.
Evidence Handling Plan
- Evidence stored in an access-controlled encrypted store; redaction; agreed retention + deletion.
Contract Requirements
- Mutual NDA — Required for this engagement.
- Evidence Handling Policy — Required for this engagement.
- Statement of Work Template — Required for this engagement.
- Assessment Terms Addendum — Required for this engagement.
- AI Red Team Rules of Engagement — Required for this engagement.
- No-Cost Scoping Retainer (conditional) — Scope before any paid work or active testing.
Draft SOW Inputs
- Engagement: AI Red Team & Adversarial Testing Packet
- Deliverables: 7 selected
- Budget category: Red team / adversarial testing / AI security budget
Open Questions
- Authorization (own / control / explicitly authorized to assess the targets)
- Target inventory (named systems/endpoints in scope)
- Access plan (how access and test accounts are provisioned securely)
Follow-On Recommendations
- ai product security assessment
- agentic workflow security
- claim readiness evidence
Target Inventory
- No named targets yet — required before testing.
Rules of Engagement
- No active adversarial testing requested.
Allowed / Prohibited Techniques
- Which techniques are authorized and which are prohibited by default.
Access Plan
- Access plan needed — secure-channel provisioning, no public credentials.
Emergency Contacts
- Stop-testing and escalation contacts reachable during the window.
Data Handling Plan
- Sensitive data in scope: No
- Standard handling; secrets masked; minimum-necessary access.
Deliverables Plan
- Red Team Scope Document
- Findings Register
- Executive Summary
- RAG Security Test Plan
- Remediation Roadmap
- Abuse-Path Findings
- Retest Plan
Retest Plan
- How remediation is confirmed after fixes land.
Onboarding
Move four tracks in parallel
We put legal, finance, procurement, and technical scoping on parallel rails so the work can start without waiting on every internal process sequentially.
Technical Scoping
Output: Draft Launch Review Plan
- architecture
- demo/staging
- prompts
- RAG
- agents/tools
- authz
- logs/evals
- test boundaries
Legal
Output: NDA + Scoping Authorization
- mutual NDA
- data handling
- authorized testing boundaries
- confidentiality
- work-product terms
Finance / Procurement
Output: Procurement Packet
- vendor profile
- tax/payment details
- budget category
- fixed-fee quote path
- invoice terms
- onboarding answers
Internal Approval
Output: Approval Memo
- why now
- business pressure
- risk if delayed
- expected deliverables
- timeline
- decision needed
Output
Your output: a clear, measurable prescription.
SCOPE delivers a one-page engagement plan you can share and act on immediately.
- Situation & core problem
- Desired outcome & success criteria
- Key risks & assumptions
- Recommended path(s)
- Effort, timing & impact
- Open questions & next step
SCOPE Prescription
Situation
Criteria
Recommended path
Next step
Export as markdown ↗