AI-Assisted Secure Coding (Appendix C) · Compromise Containment & Automated Remediation
A playbook for AI pipeline compromise
Verify that an incident-response playbook exists for AI-in-pipeline compromise. At minimum it covers: revoking AI-agent credentials, rotating every secret that touched the compromised workflow run, quarantining the compromised artifacts, notifying downstream consumers, notifying regulators where applicable, and preserving prompts, responses, and audit logs for forensics.
OWASP AISVS v1.01, requirement AC.14.1
In plain English
Have an incident response playbook for a compromise involving AI in your pipeline. It must cover revoking AI agent credentials, rotating every secret the compromised run touched, quarantining the artifacts it produced, telling downstream consumers and, where required, regulators, and preserving prompts, responses and audit logs for the investigation.
What good looks like
- The playbook exists and covers each of the six steps.
- Each step has a named owner and says how it is done.
- It is linked from the main incident process and people know it exists.
- Evidence preservation comes before clean-up in the order of steps.
How teams usually do it
- Extending the existing incident playbooks with an AI-in-pipeline scenario.
- A list of where prompts, responses and agent session records are stored, so they can be preserved quickly.
- Notification templates for downstream consumers, and the regulatory deadlines that apply to you.
Suggested evidence
- The playbook and its last review date.
- A tabletop or real incident record that used it.
Common mistakes
- Rotating and cleaning up before preserving prompts and responses, which destroys the evidence.
- A playbook that says "rotate affected secrets" without a way to find which ones the run could reach.
- Nobody owning notification of downstream users.
Not sure which requirements apply to your system? Take the assessment, or browse every guide in this chapter.
Requirement text from the OWASP AI Security Verification Standard, licensed under CC BY-SA 4.0. This guidance is shared under the same licence.