TL;DR: Roughly 20% of enterprise devices are running degraded, non-compliant, or absent security controls, according to Absolute Security. That leaves policy and reality out of sync, so recovery has to be tested as a security outcome, not left as an afterthought.
Editorial analysis by NHI Mgmt Group, based on content published by Absolute Security: “Beyond the Breach: A Recap of the Resilient CISO Summit at RSAC 2026”.
By the numbers:
- roughly 20% of enterprise devices have security controls that are degraded, non-compliant, or simply not running
Key questions
Q: Why do AI-enabled environments make resilience harder to prove?
A: Because the environment is no longer defined by one workload or database.
Q: How do security teams know if backup recovery is actually working?
A: They know by testing restorations under realistic conditions and checking whether identity services come back in the right order.
Q: What breaks when security controls silently degrade across enterprise devices?
A: When controls degrade silently, policy and reality diverge.
Practitioner guidance
- Audit control continuity across endpoints Track whether security controls remain active, compliant, and healthy after updates, agent collisions, and AI-related software changes.
- Define a trusted recovery state Document the baseline state devices and services must return to after disruption, including access policy, security agents, and compliance settings.
- Add AI-mediated action to governance reviews Require teams to record when automation, agents, or delegated workflows initiate changes on behalf of users.
Bottom line: The article argues that AI is widening the gap between intended and actual control coverage across enterprise environments.
Glossary terms: Control Continuity, Rapid Rehydration, AI-Mediated Action
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Control continuity is now a first-order security governance problem. The summit's central message is that prevention-only security models no longer match how modern environments fail. If endpoint controls silently degrade, then governance has to cover the operational state of those controls, not just their intended deployment. Practitioners should treat control continuity as a measurable assurance domain.
A question worth separating out:
Q: What is the difference between normal endpoint protection and resilience architecture?
A: Endpoint protection tries to stop compromise before it spreads. Resilience architecture assumes some failure will happen and focuses on restoring trusted state fast enough that the breach has limited operational value. The distinction is not philosophical. It changes where the control lives, how it is measured, and how quickly recovery must occur.
👉 Read our full editorial: Why resilience is overtaking prevention in AI-native security