Map the affected chain
- AI application, agent or copilot and its deployed version
- Model provider, orchestration layer and hosting environment
- Retrieval sources, persistent memory and ingestion routes
- Human and service identities, tokens and connected tools
- Business systems where actions or disclosures may have occurred
Record operational constraints
Identify business-critical services, permitted maintenance windows, third-party owners and actions requiring executive or legal approval. Include existing responders and supplier incident channels so work does not conflict.
Agree the deliverable and evidence boundary
Specify the questions to answer, accessible records, retention periods and reporting audience. Lack of trace data may limit reconstruction. A bounded investigation should explain those limits rather than imply a complete forensic history.
Resolve these boundaries before collecting evidence
| Boundary | Scoping decision |
|---|---|
| Time | First known observation, relevant look-back and record retention |
| Identity | Initiating user, delegated principal and shared credentials |
| System | Application, provider, retrieval stores, tools and destination systems |
| Authority | Who may approve collection, restriction and restoration |
| Output | Question to answer, reporting audience and limits of available evidence |
Change the scope when the evidence warrants it
If a new identity, destination or earlier event is implicated, document the reason for expanding the investigation. Confirm permission, access and commercial effects with the owner. Include existing responders to prevent duplicate collection and conflicting changes. Use the cost guide to frame the estimate and the brief builder for the first non-sensitive request.
