Verizon DBIR 2025 signals a reset in breach and identity risk

At a glance

What this is: NHI Mgmt Group's analysis, drawing on ColorTokens's blog post: Verizon's 2025 DBIR shows breach risk shifting toward third parties, rapid vulnerability exploitation, and unmanaged GenAI use inside enterprises.

Why it matters: Identity, IAM, and security teams need to treat supply chain trust, edge exposure, and employee AI access as governance problems, not just technical exceptions.

By the numbers:

• Third-party involvement was a factor in 30% of all breaches this year, according to Verizon.
• The exploitation of vulnerabilities accounted for 20% of all breaches, overtaking phishing at 15%, according to Verizon.
• Of employees using GenAI on corporate devices, 72% used a personal email for their account, according to Verizon.
• Another 17% used a corporate email address not integrated with company authentication systems, according to Verizon.

Context

Verizon's 2025 DBIR is presented here as a signal of where defensive models are failing rather than a simple year-end summary. The article argues that the most important changes are not isolated incidents, but structural shifts in how breaches begin, spread, and intersect with identity governance.

The security implication is that organisations can no longer treat third-party access, edge exposure, and unsanctioned AI use as separate issues. Each one creates a pathway where trust assumptions outlive the controls that were supposed to bound them, which makes access governance and exposure reduction central to resilience.

Key questions

Q: What breaks when third-party access is not governed as part of identity lifecycle management?

A: Access can outlive the business relationship that justified it, which leaves external identities active after need has ended. In healthcare, that failure can expose claims systems, patient data, and connected devices. The practical problem is not just excessive access, but access that no longer has an accountable owner.

Q: Why do edge vulnerabilities create such a different risk profile from ordinary patchable flaws?

A: Internet-facing assets can be exploited before normal patch windows close, so the issue becomes how much reachable surface remains after disclosure. That is why segmentation, isolation, and compensating controls matter as much as patch speed when critical flaws appear on VPNs and similar systems.

Q: What are the signs that employee GenAI use has moved outside governance?

A: Look for personal email registrations, corporate accounts that are not tied to enterprise authentication, and shadow usage of public AI platforms on managed devices. Those patterns show that identity, policy enforcement, and data handling controls are no longer aligned with actual user behaviour.

Q: Should organisations prioritise patching or containment for high-risk device fleets?

A: For patchable systems, patching remains necessary, but for fleets with long patch cycles or no patch path, containment should come first. The right priority depends on whether the device can be remediated in time. If not, reduce reachable services and enforce network-level least privilege.

Technical breakdown

Why third-party involvement now changes breach calculus

Third-party involvement becomes a governance issue when external software, cloud services, and partner credentials sit inside an organisation's trust boundary but outside its direct control. The article points to supply chain compromise, stolen partner credentials, and service-provider outages as different expressions of the same problem: inherited exposure. In practice, a breach can begin without a direct attack on the enterprise, yet still end inside its environment because identity, dependency, and recovery assumptions were never designed for shared risk.

Practical implication: map partner access, software dependencies, and delegated trust paths as part of your control boundary, not as exceptions.

Why edge vulnerability exploitation compresses response windows

Edge devices such as VPNs and other internet-facing systems collapse the time available for traditional scan-and-patch cycles. When a critical flaw is public, attackers can mass-exploit it before many defenders have even completed triage. That changes the control problem from routine remediation to exposure reduction, because the real question is no longer how quickly a patch can be scheduled, but how much blast radius remains while a flaw is still reachable.

Practical implication: prioritise compensating controls, segmentation, and exposure management for internet-facing assets that cannot rely on patch cadence alone.

How unsanctioned GenAI use creates an identity and data control gap

The article's GenAI findings show that the main issue is not advanced attacker use of AI, but employee access to public AI platforms outside corporate authentication and governance. Personal email accounts and unintegrated corporate accounts break visibility, policy enforcement, and data handling controls. That makes sanctioned access a governance requirement, because once users can reach external AI services without managed identity, the organisation loses both oversight and the ability to define acceptable data paths.

Practical implication: require managed identities and approved access paths for employee AI use before sensitive data is exposed to public services.

Threat narrative

Attacker objective: The attacker or intruder aims to turn trusted external exposure into internal compromise, disruption, or data theft without needing to defeat the organisation's perimeter directly.

1. Entry begins through third-party software flaws, inherited partner access, or exposed edge systems rather than a direct attack on the enterprise perimeter.
2. Credential and access abuse follows when stolen partner credentials or weakly governed delegated access are used to enter trusted environments.
3. Impact occurs when these pathways enable internal disruption, broad service interruption, or data exposure that the victim organisation experiences as its own breach.

Breaches seen in the wild

• Sisense breach 2024: A credential in Sisense's GitLab reportedly opened S3 buckets of customer tokens, passwords and certificates; CISA urged a full reset.
• CISA Private-CISA GitHub leak 2026: A CISA contractor's public GitHub repo exposed AWS GovCloud admin keys, Artifactory credentials and plaintext passwords for six months.

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

Third-party breach exposure is now an identity governance problem, not just a supply chain concern. When 30% of breaches involve third parties, the old assumption that risk sits cleanly outside the enterprise no longer holds. The governance failure is not only vendor risk review, but the lack of continuous control over delegated trust, shared credentials, and cross-boundary access. Practitioners should treat partner identity as part of the identity estate, with lifecycle, scope, and revocation discipline.

Exposure time is the new control variable: the article shows that edge vulnerability exploitation has become fast enough to outpace ordinary remediation rhythms. That means security programmes need to stop measuring themselves by patch completion alone and start measuring how much reachable surface remains when a flaw is disclosed. The practical consequence is a shift toward containment-first design, where segmentation and exposure reduction buy time when prevention fails.

Unmanaged GenAI use exposes a verification trust gap: employee access to public AI platforms through personal or unintegrated accounts creates a blind spot between usage and governance. The problem is not only data leakage, but the absence of authoritative identity context at the point of access, which leaves policy unenforceable. NHI and IAM teams should recognise that sanctioned AI use is now an identity control issue as much as a data policy issue.

ColourTokens' framing is a reminder that resilience is increasingly about blast-radius control. As breach paths multiply across suppliers, edge assets, and internal AI use, organisations need controls that assume prevention will fail somewhere. The decisive question is which systems can still be isolated, contained, and governed when trust boundaries are crossed. Practitioners should align controls to containment outcomes, not just prevention aspirations.

What this signals

Third-party trust now belongs in the identity programme: once suppliers, cloud services, and shared platforms can trigger internal compromise, the boundary between vendor risk and access governance disappears. Security leaders should expect delegated identities and partner credentials to sit alongside human accounts and NHIs in review processes, because the breach path increasingly runs through both.

Containment has become the practical measure of resilience: the article's edge-device discussion shows that exposure can outpace remediation, which leaves less room for heroic patching and more need for isolation. Teams should assess whether their critical services can be segmented quickly enough to keep a disclosed flaw from becoming an enterprise-wide event.

Sanctioned AI use is now an identity enforcement problem: if employees can reach public GenAI tools through unmanaged accounts, the organisation has lost its ability to bind usage to policy. The control question is no longer whether staff will use AI, but whether that use can be tied to governed identities before sensitive data moves outside the enterprise.

For practitioners

• Define the third-party identity boundary Inventory vendor, partner, and platform accounts that can reach internal systems, then assign ownership, review cadence, and offboarding triggers to each one.
• Build exposure controls for edge devices Use segmentation, restriction of inbound paths, and tighter monitoring around internet-facing systems so a disclosed flaw does not become a full-environment entry point.
• Approve one sanctioned path for employee AI use Require managed identities and approved authentication for any GenAI service that may receive corporate data, and remove business reliance on personal email registrations.
• Treat partner credentials as revocable assets Shorten review and revocation cycles for external credentials, especially where a supplier or service provider can reach production or sensitive data.
• Measure containment, not just prevention Track how quickly suspicious third-party access or exposed services can be isolated, revoked, or segmented after discovery.

Key takeaways

• Third-party involvement is no longer a peripheral issue, because external dependencies can now become the shortest route into internal environments.
• Edge exposure and rapid exploitation have reduced the value of calendar-based remediation for internet-facing systems.
• Managed identities and containment controls matter more when employees use public GenAI tools outside corporate authentication.

Key terms

• Third-party breach exposure: Third-party breach exposure is the risk that an organization is harmed because a supplier, contractor, partner, or other external party is compromised. It includes stolen data, unauthorized access, malware spread, and operational disruption. The exposure arises when external access, shared data, integrations, or trust relationships extend the attack surface beyond direct control.
• Blast Radius Control: Blast radius control is the practice of limiting how far damage can spread when an identity, system, or workload is compromised. It uses segmentation, least privilege, isolation, and scoped credentials to contain impact. In identity security, it reduces lateral movement, privilege escalation, and data exposure after a breach or misuse.
• Sanctioned AI: Sanctioned AI is an AI system that has gone through procurement, legal, and security review and is governed by defined controls. The term matters because approved status should reflect real access scoping, ownership, and data handling rules, not just a business decision to use the tool.
• Edge Exposure: The condition where internet-facing applications, devices, or control planes are reachable from outside the organisation. It matters because attackers can discover and exploit those systems without needing an internal foothold, especially when patching or asset ownership is inconsistent.

Deepen your knowledge

NHI Foundation Level course covers NHI governance, secrets management, and workload identity in a way that helps security teams connect access control to real-world operational risk. It is designed for practitioners who need to align identity governance with the broader security programme.