Notifications
Clear all
Topic starter
15/05/2026 8:14 pm
TL;DR: Aqua Security says Aqua Compass adds an MCP server for agentic investigation, containment, and remediation inside runtime security workflows, while new dashboards translate live vulnerabilities and misconfigurations into monetary exposure as controls are enforced. Visibility alone is no longer sufficient when exploitation is happening faster than remediation cycles can close the gap.
NHIMG editorial — what this means for NHI practitioners
By the numbers:
- 500 of the world’s largest enterprises are protected, protected by Aqua, according to the source article.
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: When does agentic response create more risk than it reduces?
A: It creates more risk when the agent can act faster than the team can review its scope, especially if policy generation or containment is allowed without clear boundaries.
Q: What is the difference between observability and enforceable runtime security?
A: Observability tells you what is happening.
Practitioner guidance
- Classify agentic response as privileged automation Document which investigative, containment, and remediation actions an agent may perform, and separate those permissions from read-only analysis roles.
- Bind response workflows to short-lived authority Use task-scoped access for any agent that can touch runtime controls, and require explicit expiration for elevated actions that can change workload policy.
- Log every agent-generated containment action Capture the triggering alert, the recommendation, the approval path, and the resulting policy change so incident review can reconstruct the full decision chain.
That is where the OWASP Agentic AI Top 10 becomes useful, because it forces teams to examine tool use, delegated authority, and action scope?
👉 Read Aqua Security's overview of Aqua Compass and runtime risk dashboards →
Explore further
15/05/2026 8:15 pm
Runtime response is becoming an identity problem, not just an operations problem. Once an AI agent can investigate incidents and trigger containment, it inherits a delegated authority model that looks a lot like NHI governance. That changes the control question from whether the tool can see enough telemetry to whether it can act safely within bounded privilege. Practitioners should treat agentic response as privileged access with audit and scope requirements, not as a generic automation feature.
A few things that frame the scale:
- 96% of technology professionals identify AI agents as a growing security threat, and 66% believe this risk is immediate, according to AI Agents: The New Attack Surface report.
- 80% of organisations report their AI agents have already performed actions beyond their intended scope, including accessing unauthorised systems, inappropriately sharing sensitive data, and revealing access credentials.
A question worth separating out:
Q: How should teams decide whether to let AI generate remediation policies?
A: Allow it only when the policy is narrowly scoped, reviewable, and reversible. Teams should define the approved containment patterns first, then let the agent populate them with incident context. If the agent can invent policy outside those guardrails, it is effectively writing controls without governance.
👉 Read our full editorial: Runtime security needs agentic response, not just more visibility
