Topic starter
14/09/2026 10:10 am
TL;DR: AI agents for cybersecurity are moving into production, with security teams using them for alert triage, detection tuning, hunting, and vulnerability prioritisation, according to WitnessAI. The central issue is that machine-speed execution, privileged non-human identities, and shadow MCP-connected agents turn policy-only governance into a runtime control problem.
Editorial analysis by NHI Mgmt Group, based on content published by WitnessAI: “AI agents for cybersecurity: use cases and risks”.
Key questions
Q: What breaks when AI agents are not governed at runtime?
A: Without runtime governance, an agent can shift behaviour after provisioning and still execute actions that were never reviewed in context.
A: Standing privilege expands the blast radius of every compromised credential, misrouted tool call, or overbroad automation.
Q: How do security teams know if AI governance is working?
A: Look for evidence that access decisions are reviewable, permissions are revocable, and exceptions are not becoming permanent.
Practitioner guidance
- Map every acting agent to a distinct identity Assign each security agent a unique non-human identity, not a borrowed human credential, and bind it to a named human sponsor for accountability and revocation.
- Move enforcement to tool-call time Block or allow agent actions in the enforcement path before execution, especially for tool use that can change data, permissions, or production systems.
- Tier approvals by action risk Permit read-only and low-impact investigations to proceed autonomously, but require explicit human approval before any irreversible remediation, deletion, or access expansion.
Bottom line: AI agents used in security operations create a governance problem because they can act, not just recommend, and the action path now matters as much as the model output.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
14/09/2026 10:11 am
Runtime governance, not policy governance, is the control boundary that matters for AI agents. Policy documents can describe what an agent should do, but they do not stop a tool call once the agent is already executing. This is why approval language without execution enforcement fails in practice. For practitioners, the decisive question is whether policy is translated into controls that operate at decision time.
A few things that frame the scale:
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
- 19% of organisations give AI systems dramatically more access than human employees, nearly one in five granting unrestricted privilege, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: Should organisations separate read-only agent tasks from irreversible actions?
A: Yes. Read-only enrichment, triage, and detection tuning can often run with lower risk, but any action that changes data, access, or production state should sit behind a stronger approval path. The point is to keep autonomy where the blast radius is low and slow down anything that cannot be easily reversed.
👉 Read our full editorial: AI agents for cybersecurity expose gaps in runtime governance