Notifications
Clear all
Topic starter
25/08/2026 9:13 am
TL;DR: Agentic AI creates a new security window between prompt and action, and Impart says Optro closed that gap with inline inspection, response visibility, and same-day virtual patching that reached 100% mitigation on a live zero-day within 24 hours. The broader lesson is that AI governance now depends on request-path enforcement, not log-only detection or slow patch cycles.
NHIMG editorial — based on content published by Impart: How Optro Reached 100% Mitigation in Hours with Impart
By the numbers:
- Reached 100% mitigation on a live zero-day within 24 hours.
- Replaced 90-day and 30-day patch SLAs with same-day virtual patching.
Questions worth separating out
Q: How should security teams govern AI agents that can choose tools at runtime?
A: Security teams should govern runtime agent choice as an access event, not as a simple application action.
Q: Why do AI agents create a different access-risk profile than traditional applications?
A: AI agents can chain actions, call multiple tools, and change behaviour based on context, so one credential can enable more than one operational path.
Q: What breaks when AI security only relies on logging and alerting?
A: Logging and alerting fail when the risky action finishes before a human can intervene.
Practitioner guidance
- Enforce inline agent policy checks Inspect prompt, tool call, and response together so a policy can block unsafe actions before the agent reaches the backend.
- Map agent permissions to delegated task scope Review which data sources, APIs, and write actions each agent can reach, then reduce permissions to the narrowest task scope possible.
- Use virtual patching for exposed AI workflows Create temporary runtime rules for vulnerable endpoints, prompt paths, and agent-connected APIs while permanent fixes are developed.
What's in the full article
Impart's full post covers the operational detail this analysis intentionally leaves for the source:
- Inline enforcement mechanics for request-path inspection and blocking across agentic workflows
- How Optro converted detections into same-day rules and validated them before deployment
- The telemetry model for recording what the agent attempted, what policy fired, and what was stopped
- Practical examples of virtual patching against live vulnerabilities and AI-specific threats
👉 Read Impart's analysis of agentic AI runtime control and same-day mitigation →
AI agent request paths: are your controls keeping up?
Explore further
25/08/2026 9:14 am
AI agent governance is becoming a runtime control problem, not a policy document problem. Once an agent can choose tools and act on behalf of a user, static approvals and periodic reviews no longer describe the risk accurately. The control point has to move to the moment of decision and execution, where scope, data access, and response handling can still be constrained. For practitioners, the lesson is to treat agent runtime as a governed identity surface.
A question worth separating out:
Q: How do identity and privilege controls apply to agentic AI workflows?
A: They should define what the agent may access, what it may change, and which actions require stronger telemetry or approval. The useful question is not whether the user was authenticated, but whether the delegated authority given to the agent was proportional to the task and visible at the point of execution.
👉 Read our full editorial: Agent request visibility and runtime control close AI security gaps
