BlueprintPage 40
40OPERATIONS
Kill Switch, Quarantine & Containment
Security should always be able to answer: “Can we stop it right now?”
- Priority
- P0
- Phase
- MVP
- Primary owner
- Security / Platform
- Status
- Blueprint
Objective
Customers need confidence that they can stop an agent immediately. The kill switch must be fast, scoped and resilient, with options ranging from one session to an entire agent class or tool integration.
What to build
- Terminate active agent sessions and queued protected actions.
- Revoke agent/session tokens and brokered credentials.
- Disable specific tools or destinations.
- Force approval-only mode for an agent/team.
- Global emergency policy for an incident class.
Implementation decisions
- Distribute revocation state to gateways with very low propagation delay.
- Require strong admin authentication and reason for large-scope kill actions.
- Allow preconfigured emergency groups and playbooks.
- Ensure containment preserves forensic evidence.
Definition of done
- A test agent loses protected access within the defined kill-switch SLA.
- Global containment is protected against accidental single-click activation.
- Restoration requires explicit review and leaves a full audit trail.
Success metrics
- Revocation propagation time
- Containment scope
- Emergency activations
- Restore-after-review compliance
PROMISE
Security should always be able to answer: “Can we stop it right now?”