Topic starter
18/08/2026 2:13 pm
TL;DR: AI is turning vulnerability discovery into a continuous, machine-speed process, widening the gap between how quickly weaknesses surface and how slowly most teams remediate them, according to Ory. The practical implication is that patch-cycle thinking is no longer sufficient when discovery accelerates faster than human response.
Editorial analysis by NHI Mgmt Group, based on content published by Ory: “The New Arms Race: AI Just Picked a Side... Both Sides”.
Key questions
Q: What breaks when vulnerability discovery is faster than patch cycles?
A: Patch-centric programmes break because they assume security teams have days or weeks to assess, approve, and deploy fixes.
Q: Why does faster vulnerability discovery create more risk for security programmes?
A: Because discovery speed amplifies the gap between identifying a weakness and proving it is fixed.
Q: How do security teams know whether Teams remediation is working?
A: They should measure dwell time, removal latency, and the percentage of malicious messages removed before any user interaction.
Practitioner guidance
- Prioritise continuous remediation triage Replace quarterly vulnerability review with a continuously updated queue that ranks exposed assets by exploitability, reachability, and business criticality.
- Inventory service accounts tied to vulnerable systems Map service accounts, tokens, and API credentials to the applications and workloads they support so compromise impact can be assessed quickly.
- Shorten exception lifetimes for known flaws Set expiry dates on compensating controls and accepted-risk decisions so unresolved vulnerabilities do not become permanent fixtures.
Bottom line: AI-assisted discovery compresses the time between defect discovery and exploitation, which makes periodic patching too slow to manage exposure effectively.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
18/08/2026 3:05 pm
Patch-cycle defense is now a lagging control. The article describes a shift from occasional vulnerability discovery to continuous machine-speed finding, and that breaks the assumption that periodic remediation is enough. In governance terms, the control failure is not patching itself but the belief that patch cadence can remain slower than discovery cadence. Practitioners should treat remediation latency as a first-class risk signal.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: How should teams govern privileged non-human identities in agentic systems?
A: Treat the agent as a non-human identity with scoped authority, provenance controls, and explicit action authorization. Separate content reading from execution, require authenticated control channels for task changes, and remove any standing privilege the agent does not need. That governance model matters because prompt injection becomes far more dangerous once it can steer a privileged runtime.
👉 Read our full editorial: AI speeds up zero-day discovery and breaks patch-cycle defense