When an AI dependency is compromised: a containment sequence (illustrative)

When an AI dependency is compromised: a containment sequence (illustrative) A workflow diagram generated by Archify. 01 / Security team 02 / Platform team 03 / Service owners Detect and scope Contain Recover and learn Advisory received · package or image · Security team › Detect and scope Advisory received package or image Identify exposure · versions, hosts, keys · Security team › Detect and scope Identify exposure versions, hosts, keys Preserve evidence · logs, digests, images · Security team › Contain · before rebuild Preserve evidence logs, digests, images before rebuild Incident record · decisions, residual risk · Security team › Recover and learn Incident record decisions, residual risk Isolate · egress off, scale to zero · Platform team › Contain Isolate egress off, scale to zero Rotate secrets · provider keys, tokens · Platform team › Contain Rotate secrets provider keys, tokens Verify and rebuild · pinned, known-good digest · Platform team › Recover and learn Verify and rebuild pinned, known-good digest Monitor · usage, egress, spend · Service owners › Recover and learn Monitor usage, egress, spend scope affected capture close redeploy Legend Agent logic Policy Context / trace Cloud service External system