Before changing the system
Record observed symptoms, the time first noticed and current service impact. Identify an authorised incident lead. If immediate containment is necessary, document the action and its time; do not delay protection solely to complete this list.
AI application and orchestration
- Application, workflow, prompt-template and model configuration versions
- Run and session identifiers, timestamps and timezone
- Relevant inputs, outputs and references, collected under agreed privacy controls
- Tool requests, arguments, responses, approvals, retries and errors
Sources, identities and destinations
- Retrieved document identifiers, source versions and ingestion history
- Agent permissions, service identities and credential changes
- Destination-system audit records confirming actual actions
- Known recipients or data-transfer records where available
- Deployment, connector, memory and index changes
Handle evidence deliberately
Preserve originals and record collection time, source and transformations. Restrict access and use an agreed secure transfer channel. Do not paste confidential prompts or log bundles into the public enquiry. The checklist is preparation guidance, not a finding that your system is compromised.
A collection register that supports later review
| Record | Capture alongside it |
|---|---|
| Run or session export | System, identifier, collector, query window and export time |
| Source document | Version, provenance, access permissions and ingestion reference |
| Tool execution | Arguments, result, approval, principal and correlation ID |
| Destination event | Object or job identifier, event time and resulting state |
| Configuration | Deployment/version identifier and effective time |
| Provider response | Request reference, scope, supplied records and stated limitations |
Preserve only what you are authorised to handle
Use original exports where available and keep transformations documented. Restrict access and record integrity checks appropriate to the agreed process. Collecting every prompt or file without a defined purpose can unnecessarily expose sensitive information. The forensics guide explains how the records support conclusions, while the response plan assigns their owners.
