What Cyber Insurance Does Not Cover

What Cyber Insurance Does Not Cover

Photo by RDNE Stock project on Pexels

Just as important as knowing what's covered is understanding the gaps. Cyber insurance is not a blank check — policies contain specific exclusions that can leave you exposed if you don't read carefully. Here's what most standard policies exclude.

1. Losses From Known Vulnerabilities

If your insurer discovers you knew about an unpatched vulnerability for 60+ days and did nothing, they may deny coverage for any incident exploiting that vulnerability. This is called the "known vulnerability exclusion." Insurers increasingly require vulnerability scanning as a precondition for coverage.

2. Reputational Harm and Lost Business Value

A breach damages your reputation, and customers may leave. However, most policies do not cover:

• Long-term customer attrition beyond the immediate business interruption period
• Damage to brand value or goodwill
• Lost future revenue from deals that fall through due to breach publicity

Some premium policies offer limited "reputational harm" coverage, but caps are typically $25,000–$50,000 — a fraction of actual reputational losses.

3. Costs of Upgrading Systems After a Breach

If a breach reveals your systems were outdated, the cost of purchasing new security software, upgrading hardware, or implementing new policies is generally not covered. Insurance pays to restore you to your pre-breach state — not to improve it. Budget separately for ongoing security improvements.

4. Bodily Injury and Property Damage

If a cyberattack on a manufacturing system causes physical injury or property damage (e.g., disabling safety controls at a factory), cyber insurance typically excludes this. It falls under general liability or specialized industrial policies. The boundary between cyber and physical risk is a growing gray area — discuss with your broker if you operate physical infrastructure.

5. War, Terrorism, and Nation-State Attacks

Following the NotPetya attack in 2017, many insurers added "war exclusion" clauses. If an attack is attributed to a nation-state actor, your claim may be denied. This is a contentious issue — some policies have narrowed the exclusion to only declared wars, while others maintain broad nation-state exclusions.

6. Prior Acts and Pre-existing Conditions

If a breach occurred before your policy's effective date — even if you didn't discover it until later — most policies won't cover it. This is why insurers require a security questionnaire before binding coverage. They want to confirm you don't already have a lurking problem.

How to Protect Yourself Against Gaps

1. Read the exclusions section carefully — It's often the most important part of the policy.
2. Ask your broker to explain each exclusion in plain language — A good broker should translate legalese to real scenarios.
3. Consider endorsements — Some exclusions can be removed or narrowed for additional premium.
4. Maintain documentation — Prove you're actively patching and improving security, which strengthens your position if a claim dispute arises.

Key Takeaways

• Known vulnerabilities, reputational harm, system upgrades, and nation-state attacks are commonly excluded
• Insurance restores you to pre-breach state — it doesn't fund improvements
• Read exclusions as carefully as coverage descriptions
• Consider buying endorsements to close critical gaps

Deep Dive: Practical Implementation Details

Understanding the theory behind cyber insurance readiness is important, but putting it into practice is where most organizations struggle. Let's break down the concrete steps you need to take to move from awareness to action. Many businesses treat cyber insurance as a checkbox exercise — they purchase a policy and assume they're protected. In reality, the policy is only as good as your organization's actual security posture and documentation. Insurers are becoming increasingly stringent, requiring evidence of implemented controls before issuing or renewing policies.

Real-World Scenario

Consider a mid-sized manufacturing company that held a cyber insurance policy for three years without ever reviewing its coverage. When they suffered a ransomware attack that encrypted their production systems, they discovered their policy excluded coverage for acts of war — and the insurer argued the attack was state-sponsored. The company spent over $2 million in recovery costs out of pocket. This situation is increasingly common as insurers refine their exclusions. The lesson: review your policy annually with a qualified broker who understands cyber risk, and document every security control you implement to strengthen your position during claims.

Free and Low-Cost Tools to Support This Step

You don't need an enterprise budget to build cyber insurance readiness. The following free or low-cost tools can help you implement and document the controls discussed in this lesson:

• NIST Cybersecurity Framework (CSF) — A free framework that provides a structured approach to managing cybersecurity risk. Use it as your baseline for organizing your security program. Download the framework and its companion documents from the NIST website at no cost.
• CIS Controls — The Center for Internet Security offers a free set of 18 prioritized security controls. Their free implementation guides walk you through each control with specific, actionable steps.
• CISA Cyber Hygiene — The U.S. Cybersecurity and Infrastructure Security Agency offers free vulnerability scanning for public-facing IPs and domains. This is an excellent way to demonstrate proactive risk management to your insurer.
• SecurityScorecard Free Tier — Provides a free security rating for your organization's external posture, which insurers increasingly use as part of their underwriting process.

What Happens If You Skip This Step

Organizations that neglect this area face several serious consequences. First, you may be unable to obtain cyber insurance at all — many insurers now require evidence of specific controls before offering coverage. Second, if you do obtain coverage but haven't implemented the required controls, your claim may be denied when you need it most. Third, without proper documentation, you'll struggle to demonstrate compliance during the underwriting process, potentially resulting in higher premiums or reduced coverage limits. Finally, in the event of an audit or breach investigation, the absence of documented controls can expose your organization to regulatory fines and legal liability that insurance may not cover.

Common Questions (FAQ)

Q: How often should we review this aspect of our cyber insurance readiness?
A: At minimum, conduct a review annually before your policy renewal. However, any significant change in your IT environment, business operations, or regulatory requirements should trigger an immediate review. Many organizations benefit from quarterly check-ins to ensure their documentation stays current.

Q: What if we don't have dedicated security staff?
A: This is a common challenge for small and mid-sized organizations. Consider engaging a managed security service provider (MSSP) for monitoring and incident response, and use frameworks like NIST CSF or CIS Controls as your roadmap. Many insurance brokers also offer risk assessment services as part of their offering. The key is to document what you do have in place, even if it's basic controls like antivirus, firewalls, and employee training.

Q: Will implementing these steps actually reduce our premiums?
A: While there's no guarantee, insurers increasingly offer premium discounts for organizations that can demonstrate strong security postures. Documented implementation of recognized frameworks like NIST CSF, regular employee training, and tested incident response plans are among the factors that can positively influence underwriting decisions. Some insurers offer discounts of 5-15% for verifiable security controls.

Q: How do we document our controls for the insurer?
A: Create a security documentation binder (digital or physical) that includes: your security policies, risk assessment results, training records, incident response plan, backup and recovery procedures, and evidence of control implementation (screenshots, configuration exports, scan reports). Update this binder regularly and have it ready before renewal discussions.