Notifications
Clear all
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.
NHIMG editorial — based on content published by WitnessAI: AI agents for cybersecurity and the runtime controls needed to govern them
By the numbers:
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes.
- The ratio reaches 144 to 1 in cloud-native environments.
Questions worth separating out
Q: How should security teams govern AI agents that can take runtime response actions?
A: Treat them as privileged NHI workloads with explicit scope, short-lived authority, and full action logging.
Q: Why do AI agents create more risk than traditional automation?
A: AI agents create more risk because they can interpret context, choose actions, and invoke tools autonomously.
Q: What are the signs that AI governance is failing in the enterprise?
A: Common warning signs include rapid growth in AI use without matching policy coverage, sensitive files being copied into personal accounts, and a large share of AI apps carrying high or critical risk.
Practitioner guidance
- Assign unique identities to every security agent Use a dedicated non-human identity for each agent, with task-scoped permissions, named human sponsorship, and revocation tied to the workflow owner.
- Enforce tool allow-lists before execution Place approval and policy checks in the execution path so the agent cannot call unapproved tools, MCP servers, or data sources before the action runs.
- Classify irreversible actions for human approval Separate read-only work from any action that can change detections, access, or infrastructure, and require a human gate for the latter.
What's in the full article
WitnessAI's full analysis covers the operational detail this post intentionally leaves for the source:
- How its visibility layer identifies agents and MCP servers across IDEs, terminals, applications, and local frameworks.
- How its agentic control path allow-lists tools and blocks unauthorised tool calls before execution.
- How its prompt protection scans inbound instructions and outbound responses to reduce injection risk at runtime.
- How the article maps captured agent actions back to the initiating human identity for accountability.
👉 Read WitnessAI's analysis of AI agents for cybersecurity and runtime controls →
AI agents for cybersecurity: are your runtime controls keeping up?
Explore further
14/09/2026 10:11 am
Runtime policy, not static policy, is the governance boundary for AI agents: security teams are no longer dealing with tools that wait for approval at each step. When an agent can choose and sequence actions inside a security workflow, the decisive control is whether enforcement exists at the moment of execution. That shifts the governance question from documentation to runtime proof, which is where most identity programmes are still thin. Practitioners need to treat every action as a live authorisation event.
A few things that frame the scale:
- Only 52% of companies can track and audit the data their AI agents access, leaving 48% with a complete blind spot for compliance and breach investigation, according to AI Agents: The New Attack Surface report.
- The ratio reaches 144 to 1 in cloud-native environments, according to Ultimate Guide to NHIs , Key Challenges and Risks.
A question worth separating out:
Q: When should organisations require human approval for an AI agent action?
A: Require human approval when the action could change infrastructure, expose sensitive data, move laterally across systems, or trigger a business-critical workflow that is hard to reverse. Approval is also warranted when the agent’s decision depends on ambiguous input or external data that cannot be trusted at face value. High-consequence actions need a human stop point.
👉 Read our full editorial: AI agents for cybersecurity expose gaps in runtime governance
