Most organizations spend considerable time trying to determine whether their cybersecurity controls are effective. They conduct assessments, review vulnerabilities, test recovery procedures and measure compliance against established frameworks. These activities provide useful information about the security environment, but they don't necessarily tell management how the organization will perform when a serious incident disrupts its operations. That difference becomes important because most companies have relatively limited experience recovering from major cyber incidents. They may conduct tabletop exercises and periodically test their incident response plans, but those activities are generally built around assumptions about how an event might unfold. Fortunately, most organizations don't experience enough major incidents to develop a meaningful body of evidence about how their business actually performs under those conditions.

The cyber insurance industry has a very different perspective because insurers participate in the aftermath of thousands of incidents across organizations of different sizes and industries. They see how events develop and what happens when established controls fail. They also have visibility into the financial consequences of decisions made during response and recovery, including the effects of delays that may have little to do with the technical complexity of the original incident. A recent development involving the cyber insurance industry suggests that this collective experience may become increasingly important in how organizations approach cyber resilience.

The Insurance Industry Has an Information Advantage

On September 29, CYGNVS announced that CyberAcuView had selected its Cyber Incident Response Management platform to support coordinated incident response among the consortium's members. The announcement received additional attention in an October 11 Cybersecurity Insiders article examining how insurers could use their collective incident experience to improve cyber resilience. CyberAcuView was established in 2021 by seven cyber insurers and has grown to 25 members that, according to the organizations' announcement, represent approximately two-thirds of the global cyber insurance market. Its work includes aggregating anonymized claims information, analyzing emerging threats and developing industry practices intended to improve risk management.

The partnership introduces a common environment where participating insurers can coordinate incident response outside potentially compromised corporate networks. The platform supports controlled workflows and maintains records of response activities, which becomes particularly important when multiple insurers and external specialists need to collaborate during a significant event. The announcement also provides some indication of the scale involved. CYGNVS reports that its platform is used by more than 3,000 organizations across 71 countries and supports more than 50 new business-critical incidents each week. The details are available in the CYGNVS partnership announcement and the subsequent Cybersecurity Insiders analysis.

What interests me about this development isn't the platform itself. It is the opportunity to bring evidence from actual incidents into the decisions organizations make about cybersecurity and recovery. There is an important distinction between knowing that a control should reduce risk and having evidence that it actually changed the outcome of an incident. The insurance industry is in a position to contribute to that understanding because it sees the consequences of failures across a much broader population than any individual organization.

What Claims Experience Can Tell Us About Cybersecurity

Most cybersecurity programs measure effectiveness through the condition of the controls they operate. A vulnerability has been remediated, an endpoint protection system is deployed or a backup process has completed successfully. These measurements are necessary because they provide evidence that an activity occurred or that a particular technical condition exists. The problem is that they don't always establish whether the business can depend on the control when circumstances become difficult.

Consider backup and recovery. An organization may have years of successful backup reports and still discover during a ransomware incident that restoring its most important applications takes considerably longer than expected. The backup system may have performed exactly as designed while the broader recovery process fails to meet the needs of the business. That failure may involve dependencies that weren't understood when recovery objectives were established, or it may involve organizational decisions that nobody anticipated needing to make under pressure. From a traditional cybersecurity perspective, the backup control may be considered effective. From a Business Survivability perspective, the organization may still be poorly prepared.

Claims experience provides an opportunity to examine that difference because it captures consequences that technical assessments often don't measure. The insurance industry's ability to analyze these outcomes is also becoming more sophisticated. CyberAcuView's description of its industry data collection and analysis services explains that aggregated and anonymized claims information can help identify causes of loss and provide insurers with a better understanding of the conditions affecting claims.

That is meaningful because it introduces a different basis for evaluating cybersecurity investments. Instead of relying exclusively on whether a control aligns with a framework or accepted industry practice, organizations may increasingly be able to consider evidence showing how particular capabilities influence actual loss outcomes. Claims information has limitations because it doesn't capture every incident, and circumstances vary considerably between organizations. A control associated with lower losses isn't automatically the reason those losses were lower. Even with those limitations, the opportunity is significant because cybersecurity has spent decades developing increasingly sophisticated ways to measure technical exposure while remaining less successful at connecting those measurements to the ability of the business to continue operating when something goes wrong.

The Difference Between Control Validation and Operational Assurance

This is one of the central problems I have been addressing through Integrated Assurance. Organizations have become reasonably good at evaluating individual controls and producing evidence that those controls exist. What remains more difficult is establishing whether the combination of controls, operating processes and management decisions produces the outcome the business actually needs. That difference becomes particularly important during an incident because a technically correct response can still create operational consequences the organization isn't prepared to manage.

A security team may identify a compromised system and correctly determine that it needs to be isolated. The technical decision may be straightforward, but isolating that system could interrupt an important business process. Someone then needs to determine whether the operational consequences are acceptable and whether the organization has an alternative way to continue providing the affected service. In that situation, the security control may be functioning correctly while the business struggles with the consequences of using it.

The same issue appears during recovery. Technical teams can restore systems according to an established sequence, but that sequence may not reflect the actual dependencies of the business. Management may have approved recovery objectives years earlier without understanding how the operating environment has changed. The problem in these situations isn't necessarily a failed security control. It may be a failure to validate the assumptions connecting the control to the business outcome.

Integrated Assurance is intended to address that gap by connecting visibility into the operating environment with validation of the capabilities management depends upon. The objective is to give decision-makers a more reliable understanding of whether the organization can achieve its intended outcomes under the conditions that matter. Claims experience can contribute to that process because it provides evidence about where assumptions that appeared reasonable before an incident proved unreliable during recovery.

Recovery Delays Often Begin Before the Incident

One of the more interesting opportunities in examining actual incidents is understanding the effect of organizational decisions on recovery time. When a business experiences a major cyber event, its technical responders may know what needs to happen but still be unable to proceed immediately. The organization may need to establish who has authority to approve a particular action or determine how a decision affects contractual and regulatory obligations. Those delays can become expensive because the financial consequences of an interruption continue to accumulate while the organization works through decisions that could have been anticipated.

This is where decision debt becomes particularly relevant. Organizations routinely defer decisions because the immediate consequences of doing so appear manageable. An incident response plan may identify responsibilities without resolving who has final authority when those responsibilities overlap. Recovery priorities may be documented without being reconciled against current business dependencies. An insurance policy may provide access to incident response specialists without the organization fully understanding how those resources will be engaged. None of these omissions necessarily creates an immediate operational problem, so the unresolved decisions remain largely invisible.

During a serious incident, those decisions can suddenly become prerequisites for recovery. The organization discovers that it cannot move forward until someone resolves questions that should have been addressed before the event occurred. The resulting interruption can have relatively little to do with the sophistication of the attack and much more to do with how the organization prepared to make decisions under pressure.

A shared incident response environment such as the one CyberAcuView is implementing can help preserve records of decisions and improve coordination among participants. The greater opportunity comes from using the evidence generated during actual incidents to understand where governance and operating processes need to change. The platform itself doesn't eliminate decision debt, but the experience captured through real incidents can expose the decisions that repeatedly slow organizations down.

Insurance Claims Are Becoming a Source of Business Intelligence

There is another important development in how the insurance industry is beginning to use claims information. The 2026 Breach Impact Study developed by Verizon Business and CyberAcuView examined approximately 70,000 U.S. cyber insurance claims from January 2019 through October 2025. The study provides a much broader view of financial consequences than the individual incidents that typically receive public attention.

Among its findings, the study reported that the median financial impact of a breach increased from approximately $60,000 in 2019 to $110,000 in 2025. It also examined how losses differed across business sizes and incident types. The research is available in the 2026 Verizon Breach Impact Study.

What I find particularly useful about this research is its potential to connect the financial consequences of incidents with the conditions that contributed to those losses. A business owner generally doesn't need another explanation of why ransomware is dangerous. The more useful information concerns which investments are likely to reduce the financial and operational consequences when an incident occurs.

That requires looking beyond the initial compromise because organizations experiencing similar attacks can have very different outcomes. Differences in operating dependencies and recovery capabilities can influence the eventual loss, while the quality of decisions made during the incident can materially affect how quickly the organization returns to normal operations. Those are the relationships I would like to see the insurance industry help organizations understand more clearly.

The objective shouldn't be limited to identifying which security controls reduce the likelihood of a claim. It should also include understanding which organizational capabilities reduce the consequences when a claim becomes necessary. That distinction would move claims information from being primarily an insurance resource toward becoming a meaningful source of business intelligence about cyber resilience.

Cyber Insurance Readiness Should Benefit From This Evidence

The growing availability of claims information also has implications for how organizations prepare for cyber insurance underwriting. Historically, much of the application process has focused on whether particular controls exist. Insurers ask about multifactor authentication, endpoint protection, vulnerability management, backups and incident response capabilities because these controls are associated with important sources of cyber risk. The challenge is that an affirmative answer doesn't necessarily establish how well the control operates or whether the business can actually depend upon it.

CyberAcuView and the Center for Internet Security have already begun addressing part of this problem through Control Assist, which connects foundational CIS security safeguards with common cyber insurance underwriting questions. The Verizon study discusses the initiative as a way to help smaller businesses understand which controls matter and provide more consistent evidence of their implementation. That is useful progress because it makes the relationship between cybersecurity practices and insurance expectations easier to understand.

I would argue that the next opportunity is to extend that thinking toward recovery outcomes. If insurers can identify which combinations of controls and operating capabilities are associated with better recovery results, businesses can begin evaluating readiness against something more meaningful than the ability to complete an application. This connects directly to the argument behind Can We Insure This? because an insurance application is a representation of how the business manages risk. The organization should be able to support those representations with evidence, but it should also understand what the evidence actually demonstrates.

A successful backup report establishes something important about the backup process, but it doesn't establish how long the company can continue operating without the systems being backed up. Understanding that requires a different kind of assessment that connects technical recovery capability to the operating requirements of the business. Claims intelligence has the potential to help organizations understand which of those distinctions matter most because it shows what happens when theoretical controls encounter real operating conditions.

Business Survivability Requires More Than Successful Recovery

There is a larger issue underneath this discussion that deserves more attention. Cybersecurity has traditionally approached recovery as the process of restoring affected technology. That is necessary, but it doesn't fully address what happens to the organization while recovery is underway. A company can restore every affected system and still suffer consequences that extend well beyond the technical incident because customers may have moved elsewhere, contractual obligations may have been missed or the organization may have experienced financial pressure that continues long after its systems are functioning again.

Business Survivability requires understanding how the organization will operate during the disruption, including the minimum capabilities it needs to preserve while normal operations are unavailable. This is where I think the collective experience of cyber insurers could become particularly valuable because insurers see the financial consequences of incidents alongside many of the circumstances surrounding those losses. They can observe how organizations respond to interruptions and how recovery decisions influence the eventual cost of an event.

If that experience can be translated into better guidance about operating dependencies and recovery assumptions, it could help organizations make more informed decisions about resilience investments. There is an important difference between knowing how to restore a system and understanding how to preserve a business while that system is unavailable. The first is primarily a technical capability, while the second depends on how well the organization understands its operations and whether management has made the decisions necessary to continue functioning under difficult conditions. Both matter, but they shouldn't be treated as interchangeable.

What We Should Expect From the Insurance Industry

The CyberAcuView and CYGNVS partnership is an interesting step toward better coordination and the potential use of collective incident experience. It doesn't establish that insurers have already solved the problem of identifying which recovery practices consistently produce better outcomes. Claims information needs to be sufficiently consistent to support meaningful analysis, and organizations need to distinguish between controls that correlate with lower losses and those that materially contribute to better outcomes.

There are also legitimate limitations on how much information insurers can share because claims involve confidential business information and circumstances that may be difficult to compare across industries. Nevertheless, the opportunity is worth pursuing because the industry has access to experience that individual businesses generally cannot reproduce. More of that experience should be translated into practical guidance that helps management understand which assumptions are most likely to fail during a serious incident and which capabilities have demonstrated value in reducing operational consequences.

That would represent a meaningful evolution in the relationship between cybersecurity and cyber insurance. Insurance would remain a mechanism for transferring some of the financial consequences of cyber events, while the evidence accumulated through claims could help organizations make better decisions about how to reduce those consequences before an event occurs. The value would extend beyond improving underwriting because the same evidence could help management understand where investments in resilience are most likely to affect actual business outcomes.

The Value of Knowing What Actually Works

I have spent much of my career working with organizations that have invested heavily in cybersecurity controls and developed increasingly sophisticated approaches to measuring risk. The challenge has rarely been a complete absence of security activity. More often, it has been the difficulty of establishing whether the activities being performed are producing the level of protection and operational confidence management believes it has purchased.

That is why I find the growing connection between cyber insurance claims intelligence and incident response so interesting. The insurance industry has an opportunity to contribute evidence about what happens when organizations are forced to depend on their controls and recovery capabilities under real conditions. That experience can challenge assumptions that might otherwise remain embedded in cybersecurity programs for years, particularly when an organization has never experienced the type of disruption those assumptions were intended to address.

For business leaders, the value of that evidence should ultimately be measured by whether it changes decisions. A company that learns from claims experience that a particular recovery dependency routinely causes extended interruption should be able to evaluate whether the same condition exists in its own environment. An organization that discovers its response process depends on decisions that frequently delay other companies should have an opportunity to resolve those questions before experiencing a similar event. This is the kind of learning that can make assurance more meaningful because it connects evidence from actual outcomes to decisions about how the organization operates.

Cyber insurance tells us something about the financial risk an insurer is prepared to accept, while claims experience can provide evidence about the consequences of failures and the conditions that influence recovery. Business Survivability requires using that understanding to make the organization more capable of continuing to operate when its normal assumptions no longer hold. The real opportunity in this development isn't simply that insurers may become better at responding to incidents. It is that their collective experience could help businesses become better prepared to survive them.