Topic starter
23/06/2026 9:18 pm
TL;DR: Enterprises are moving AI agents into load-bearing workflows where a binary kill switch can create a second incident by breaking regulated processes, according to Cerbos. The real governance problem is runtime authorization and scoped revocation, because agent drift can happen inside the same operational window that legacy IAM review cycles assume.
Editorial analysis by NHI Mgmt Group, based on content published by Cerbos: “It's a dimmer switch, not a kill switch. How CISOs are rethinking AI agent governance”.
Key questions
Q: What breaks when organisations use a kill switch for AI agent governance?
A: A kill switch can stop the agent, but it also stops the workflow, drops context, and can create a new operational or compliance incident.
Q: Why does AI agent drift create risk even when the agent was authorised at the start?
A: Because the security problem is not just entry approval.
Q: How do organizations prove AI agent controls are actually working?
A: Organizations prove control effectiveness by showing which agents accessed which data, what actions they executed, and whether those actions stayed within approved task boundaries.
Practitioner guidance
- Implement scoped revocation for agents Define policy states that can reduce an agent from full task execution to read-only, limited-tool, or no-access modes without stopping dependent systems.
- Enforce runtime policy decisions Place a policy decision point in the request path for every sensitive agent action so access is checked against current context, not just initial approval.
- Record policy state at the moment of action Keep time-stamped logs of the policy version, context attributes, and decision outcome for each agent action so investigators can reconstruct what governance was in force.
Bottom line: AI agents introduce a governance problem that binary shutdown models handle poorly when the agent is embedded in an active business process.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 2:32 am
The kill-switch model is structurally wrong for AI agents that sit inside business operations. A binary off switch assumes shutdown is the safest containment action, but regulated workflows often continue to generate risk if they are interrupted midstream. The real issue is not whether an agent can be stopped. It is whether the governance model can reduce privilege without breaking the operation. Practitioners should treat AI agent control as live authorization, not emergency deactivation.
A few things that frame the scale:
- Only 44% of organisations have implemented any policies to manage their AI agents, despite 92% agreeing that governing AI agents is critical to enterprise security, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: What is the difference between kill-switch governance and a dimmer-switch model for AI agents?
A: A kill switch ends access entirely, while a dimmer switch reduces it in stages so the agent can keep working under tighter limits. The difference matters in regulated operations, where the goal is to contain drift without stopping the business process that depends on the agent.
👉 Read our full editorial: AI agent governance needs a dimmer switch, not a kill switch