TL;DR: Mandiant’s M-Trends 2026 reports the average vulnerability is exploited seven days before a fix exists, while CrowdStrike’s 2026 Global Threat Report says 42% of exploited vulnerabilities were attacked before public disclosure. Illumio argues the useful control is containment, not patch velocity, because disclosure now doubles as attacker reconnaissance.
At a glance
What this is: AI-assisted exploit generation is shrinking the window between disclosure and exploitation, making patch speed alone an inadequate defence.
Why it matters: Security teams need to assume some exposure will exist before remediation completes and design containment, segmentation, and reachability controls accordingly.
By the numbers:
- 42% of exploited vulnerabilities were attacked before they were publicly disclosed.
Context
Patch management breaks down when the time between disclosure and exploitation becomes shorter than the time needed to validate and deploy a fix. In that environment, the primary governance problem is no longer how quickly teams can patch, but how much access an attacker gains during the unavoidable exposure window.
This article sits at the intersection of vulnerability management, segmentation, and identity-aware reachability. Illumio’s core argument is that once AI compresses exploit development, defenders need controls that limit blast radius even when remediation is still in progress.
Key questions
Q: What fails when organisations rely on patching speed alone after disclosure?
A: Patching speed fails when exploit generation is faster than validation, deployment, and rollback. At that point, the issue is not whether a fix exists, but how much of the environment an attacker can reach before the fix lands. Containment, segmentation, and tight access scoping become the controls that decide whether a vulnerability becomes a broad incident or a limited event.
Q: Why do publicly exposed vulnerabilities create such a short decision window for defenders?
A: Once a vulnerability is disclosed and remains unpatched, attackers can begin working immediately while defenders are still validating scope and impact. In a large attack surface, that delay matters because exposures multiply across applications, integrations, cloud services, and business units. The practical consequence is a race against time, where speed of assessment often determines whether an issue becomes a breach.
Q: How do security teams know if segmentation is actually reducing risk?
A: Teams know segmentation is working when unnecessary workload communications disappear, exception volume falls, and policy changes are validated continuously rather than assumed. A good signal is that one compromised workload cannot reach adjacent systems without hitting an explicit control. If internal traffic remains widely open, the organisation still has a propagation problem, not a containment strategy.
Q: What should teams do when a critical flaw is disclosed before remediation is available?
A: Contain the reachable surface first. That means restricting access, isolating the affected service, and removing unnecessary administrative paths before the exploit window is closed with a patch. When a service is both exposed and high value, compensating controls are the only safe bridge between disclosure and full remediation.
Technical breakdown
Why disclosure now accelerates exploit creation
Public vulnerability disclosure has changed from a defensive transparency mechanism into an attacker input. Once a CVE or advisory is published, attackers can diff the patched and unpatched code, infer the vulnerable logic, and automate exploit creation. AI systems make that process cheaper and faster by generating proof-of-concept code and iterating on failure modes at scale. The consequence is a negative time-to-exploit, where defenders may still be validating a patch while adversaries are already testing weaponisation. Practical implication: treat disclosure as the start of containment posture, not the start of a comfortable remediation window.
Practical implication: Move vulnerability response from patch-only tracking to exposure-window containment.
Why segmentation changes the attack economics
Segmentation works by constraining reachability, which changes the attacker’s economics even when a vulnerability remains unpatched. If an exposed service can be reached by thousands of users and devices, the exploit surface is broad and the probability of successful misuse is high. If that same service is only reachable by a tightly bounded set of identities and systems, the attacker’s usable blast radius collapses. This is why containment is not a substitute for patching, but a compensating control when the patch cycle cannot keep up with disclosure velocity. Practical implication: prioritise limiting who and what can reach high-value assets before the next disclosure event.
Practical implication: Reduce reachable paths to crown-jewel systems so exploitable flaws cannot spread widely.
Why machine-readable identity data matters to containment
Segmentation policy is only as good as the inventory that feeds it. To enforce useful boundaries, teams need machine-readable data about workloads, applications, and the identities that are allowed to talk to them. Without that mapping, policy becomes either too broad to protect anything or too brittle to operate. The identity angle matters because modern containment is not just network zoning, but access scoping across users, devices, and workloads. Practical implication: align workload and identity inventories before trying to automate segmentation policy at scale.
Practical implication: Tie segmentation rules to identity and workload inventory before automating policy enforcement.
Threat narrative
Attacker objective: Exploit newly disclosed vulnerabilities fast enough to gain access before defenders can validate and deploy containment or patches.
- Entry begins when an AI-generated exploit is built from a public disclosure or advisory rather than from original flaw discovery.
- Credential access is not the main stage here; the attacker instead uses a working exploit to reach the vulnerable service before the patch lands.
- Impact occurs when the exposed asset is reached through overly broad network access, allowing the flaw to be used at enterprise scale.
Breaches seen in the wild
- Gainsight Salesforce breach 2025: Stolen OAuth tokens for Gainsight's Salesforce app, some eight years old, were used against customer orgs; Google saw 200+ instances at risk.
Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.
NHI Mgmt Group analysis
Containment is now the primary control variable when exploit generation outpaces remediation. Patch velocity still matters, but it no longer defines whether an environment remains defensible during disclosure-driven exploitation. The security programme that survives this shift assumes compromise during the patch window and limits what that compromise can reach. Practitioners should treat blast-radius reduction as a first-class control objective.
Disclosure has become an attacker research feed, not just a defender notification channel. Once vulnerable code becomes visible through advisories or diffs, AI can compress exploit development to a trivial cost. That changes the governance assumption behind patch prioritisation because exposure now has an automated adversary sitting on top of it. Security teams need to reframe vulnerability management around reachable impact, not publication date.
Identity-aware segmentation is where cyber resilience and identity governance meet. The article is not only about networks, but about which users, systems, and workloads are permitted to reach a vulnerable asset in the first place. That makes reachability policy a governance issue for IAM, PAM, and workload identity teams as much as for network security. The practitioner conclusion is clear: controls that limit access paths are now core resilience controls.
Patch-tsunami readiness is a useful named concept for this risk pattern. The volume and speed of AI-assisted vulnerability discovery will keep compressing the time defenders have to respond. Teams that still rely on manual validation and flat reachability will fall behind fastest. The practical response is to design programmes that absorb high disclosure volume without allowing every new flaw to become a broad incident.
From our research library:
- The median time to fully patch a vulnerability in CISA's Known Exploited Vulnerabilities catalog rose to 43 days, according to Verizon's 2026 Data Breach Investigations Report.
What this signals
Patch-tsunami readiness: AI will continue to compress the interval between vulnerability publication and usable exploit code, which means patch programmes that depend on calm, predictable queues will struggle. The practical shift is to govern for continuous exposure, not occasional emergency response.
Security leaders should expect segmentation, reachability, and identity scoping to absorb more of the risk that patching used to carry alone. That changes the operating model for IAM, PAM, and workload identity teams because the question is no longer only who can authenticate, but who can reach a vulnerable asset when the next disclosure lands.
For practitioners
- Prioritise segmentation around high-value systems Start with the applications and data stores whose compromise would create the largest business impact, then restrict reachability to the smallest viable identity set.
- Build an accurate workload and identity inventory Map which users, devices, workloads, and service identities actually need access before translating policy into network or host enforcement.
- Treat disclosure as a containment trigger When a vulnerability becomes public, immediately review whether the affected asset sits behind meaningful reachability limits or is exposed to the full environment.
- Put legacy systems on a mandatory refresh cycle Require periodic review or rebuild of older systems so segmentation rules and access assumptions do not drift far beyond what the environment can support.
Key takeaways
- The article’s central warning is that exploit creation now moves faster than patch validation in many real-world cases.
- The evidence it cites shows both pre-fix exploitation and pre-disclosure exploitation are already common enough to change programme design.
- The practical answer is to reduce reachability and blast radius so disclosure does not automatically become enterprise-scale compromise.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST CSF 2.0, CIS Controls v8, NIST Zero Trust (SP 800-207) and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | PR.AA-05 — Access Permissions, Entitlements and Authorizations | Segmentation and containment depend on limiting reachability through enforced access permissions. |
| Recommendation — Use PR.AA-05 to reduce who and what can reach vulnerable assets. | ||
| MITRE ATT&CK | TA0001; TA0006; TA0040 — Initial Access; Credential Access; Impact | The article describes disclosure-led exploitation that leads from entry to impact. |
| Recommendation — Map disclosure-driven exploitation to TA0001, TA0006, and TA0040 to prioritise containment. | ||
| CIS Controls v8 | CIS-5 — Account Management | Accurate identity and access inventories are necessary to make segmentation policy enforceable. |
| Recommendation — Maintain current account and service access inventories so reachability rules stay accurate. | ||
| NIST Zero Trust (SP 800-207) | Policy Engine — Policy Engine and Continuous Verification | Continuous verification is the logic behind limiting access during the disclosure-to-exploit window. |
| Recommendation — Apply continuous verification before granting access to high-value resources. | ||
| NIST SP 800-53 Rev 5 | SC-7 — Boundary Protection | Segmentation is a direct boundary protection control for limiting exploit spread. |
| Recommendation — Enforce boundary protection around crown-jewel systems to constrain exploitation paths. | ||
Key terms
- Exposure Window: The period in which a credential, session, or privilege grant can be exploited before it is revoked or expires. Shorter windows help, but they do not solve the deeper question of whether the access remains justified for the full time it is active.
- Segmentation: The practice of dividing an audience into groups so that messages, offers or experiences can be tailored. In identity terms, segmentation depends on reliable attributes, and it fails quickly when the source data is stale, duplicated or poorly governed.
- Blast Radius: The potential scope of damage if a specific credential or identity is compromised. Identities with broad permissions have a larger blast radius and represent a higher priority for least-privilege enforcement and security controls.
- Disclosure-Driven Exploitation: Disclosure-driven exploitation is attack activity that accelerates after a vulnerability becomes public, because advisories and code diffs help attackers build working exploits. AI tools make this pattern more scalable by reducing the time and skill needed to weaponise a flaw.
Deepen your knowledge
NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, workload identity, secrets management, and agentic AI identity. It is a fit for practitioners who need to connect identity controls to broader security design and operational resilience.
Published by the NHIMG editorial team on July 22, 2026.
Updated on October 13, 2026.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org