← All tags · All resources · All guides

#incident-response

4 guides tagged #incident-response on ChangeGamer.

Guides

• How to Build an Incident Response Runbook for AI Agent Failures · guide
  An operator playbook for the moment an AI agent fails in production: a triage step to classify the failure fast, trace freezing before rollback destroys the evidence, first-response depth on the four failure classes, and a blameless post-mortem that feeds back into guardrails and eval.
• How to Secure AI Agents in Production · pillar guide
  Credential hygiene, prompt-injection defense in depth, sandboxing choices for code execution, supply-chain provenance, least privilege, audit trails, incident response, and rate/abuse controls — eight operator-side defenses against an adversarial actor or a compromised dependency, not against ordinary load or failure.
• How to Respond When an AI Agent Takes a Harmful Action · guide
  Why the pillar's cut-credential, stop-instance, export-evidence order is structurally forced rather than a tidy convention, a concrete answer for who holds standing revocation authority, a pre-incident drill for the evidence-export path, and what changes when the compromised credential belongs to a third-party tool server instead of the agent itself.
• What to Do When an AI Support Agent Gives a Customer a Wrong Answer · guide
  What to do when an AI support agent gives a customer a wrong answer: classify the error, contain one intent, find every affected conversation in traces, correct the customer, weigh honouring or reversing the commitment, and add a fixture.