TL;DR: The CSA CISO Community, SANS and OWASP GenAI Security Project paper shows mean time-to-exploit collapsing to about 20 hours, according to PipeLab's analysis. Runtime containment has to absorb damage while patch cycles catch up, because prevention alone no longer covers the window.
Editorial analysis by NHI Mgmt Group, based on content published by PipeLab: “What CSA, SANS, and OWASP Just Told Every CISO About Runtime Agent Security”.
By the numbers:
- Mean time-to-exploit went from 2.3 years in 2018 to approximately 20 hours in 2026.
Key questions
Q: Why do identity and runtime controls matter so much for cyber-capable AI?
A: Because cyber-capable AI can use identity state as an input to planning.
Q: What are the signs that an agent harness is failing in practice?
A: Common signs include plausible but wrong outputs after truncation, repeated loss of earlier constraints, bloated token counts from always loaded tool schemas, and debugging that feels like archaeology because step level telemetry is missing.
Q: What breaks when patching cannot keep up with AI-speed exploitation?
A: Patch-first programmes assume defenders have enough time to validate, approve, and deploy fixes before attackers operationalise a flaw.
Practitioner guidance
- Define runtime containment as a control objective Map which workloads, agents and integrations must be constrained even if they are already compromised, then set explicit blast-radius limits for each class of runtime.
- Audit the agent harness as a privileged surface Review prompts, tool definitions, retrieval pipelines and escalation logic together, because the security boundary sits in the whole harness rather than any one component.
- Enforce outbound controls for AI and NHI traffic Block or tightly segment external requests from agents, service accounts and workloads so exfiltration paths are reduced before human review can occur.
Bottom line: AI-driven exploit speed changes the control model from prevention-only to containment-first, because patch cycles can no longer be assumed to arrive in time.
Glossary terms: Runtime containment, Agent Harness, Blast Radius, Machine-speed response
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Blast-radius control is now the decisive security variable. When exploit windows shrink to hours, the old assumption that there will be enough time to patch, investigate and then contain no longer holds. Security programmes have to assume some compromise will arrive before remediation, which makes containment the governing design principle. Practitioners should measure whether their runtime controls can still limit impact after initial compromise.
A few things that frame the scale:
- Gartner predicts that more than 50% of successful cyberattacks against AI agents through 2029 will exploit access control weaknesses.
A question worth separating out:
A: They should do both, but identity hardening often limits the fastest spread while patching addresses the root entry point. If the exploit path already includes SSO, tokens, or privileged credentials, revocation and containment can reduce impact before the patch cycle completes.
👉 Read our full editorial: Runtime controls for agents are now a security boundary