Skip to content

Commercial · Cyber Risk

Cyber liability insurance, aligned to CMMC and NIST CSF 2.0

Your security controls and your cyber policy describe the same company. When they disagree, the policy loses. We align the two — control by control — so coverage holds when it's tested.

Schedule a Cyber Coverage Review
$4.99MGlobal average cost of a data breach in 2026, a record high.Source: IBM, Cost of a Data Breach Report 2026
$11.5MAverage cost of a breach for U.S. organizations — more than double the global figure.Source: IBM, Cost of a Data Breach Report 2026
247 daysAverage time to identify and contain a breach.Source: IBM, Cost of a Data Breach Report 2026

Breach cost estimator

What would a cyber incident cost your business?

National averages describe other companies. This estimate is built from your revenue, headcount and the data you hold, one cost at a time, so you can see where the money goes.

1. Choose a scenario
2. Describe your business
$
Customers, patients and current and former employees. Count each person once.
Adjust the assumptions
%
Revenue lost to downtime is counted at gross margin, not full revenue.
%
Share of next year's revenue that leaves after the incident.
$
$
$
Set to $0 if you would not pay.
$

Estimated cost of this incident

$0

0%of annual revenue
0days of revenue

    An estimate shows the exposure. Your policy decides how much of it you carry. We'll compare this number to your limits, retentions and sublimits, line by line.

    Schedule a Cyber Coverage Review

    How the estimate is built. Each line is a separate cost, added together. Response and restoration scale with headcount, since forensics and rebuilds scale with the number of devices and accounts. Downtime is daily revenue, times days disrupted, times the share of operations stopped, times gross margin. Notification and legal costs scale with the number of records exposed, with higher legal costs in regulated industries. The range applies lower and higher assumptions to the uncertain lines: downtime, response, per-record costs and customer loss.

    Reference points. IBM's Cost of a Data Breach Report 2026 puts the U.S. average breach at $11.5 million. NetDiligence's 2026 Cyber Claims Study finds that small and midsize company incidents involving business interruption cost more than five times as much, on average, as those without it. Ransomware outages commonly run three to four weeks.

    This is an illustration, not a prediction. Actual costs depend on facts no calculator can know. The "typically addressed by" notes describe common cyber policy sections. Whether any loss is covered depends on the terms, limits, retentions and exclusions of an actual policy. This tool does not provide coverage, a quote, or legal advice.

    What is the difference between affirmative cyber and “silent cyber”?

    “Silent cyber” is cyber risk that a property, liability or crime policy neither clearly covers nor clearly excludes, leaving the outcome of a cyber-caused loss to argument after the fact. Affirmative cyber coverage states, in defined terms, which cyber events are covered, with what limits and under what conditions. Since Lloyd’s required its market to state cyber cover explicitly beginning in 2020, most traditional policies have moved toward exclusions — which means cyber losses that were once arguable are now plainly uninsured unless a dedicated policy picks them up.

    A manuscripted or heavily endorsed cyber policy lets the definitions match how your company actually operates. The definitions we negotiate most often:

    Definition Why it matters
    Computer system Must include operational technology (PLCs, HMIs, robot controllers), cloud services and, ideally, systems run by your IT providers
    Business interruption trigger Whether a voluntary shutdown to contain an attack counts, and whether non-malicious system failure is covered
    Waiting period Hours before income loss is paid; 8–12 hours vs. 24 hours changes recoveries materially
    Dependent business interruption Income lost when a vendor you depend on (MSP, ERP host, payroll provider) is attacked
    Social engineering / funds transfer fraud Wire fraud and invoice manipulation, often sublimited or placed on the crime policy instead
    Bricking Replacement of hardware rendered unusable by an attack
    War / state-backed exclusion Recent market wordings vary widely; the definition of attribution matters
    Regulatory fines and penalties Covered only “where insurable by law”; contractual penalties are usually excluded

    What are the CMMC requirements, and what is their status in 2026?

    The Cybersecurity Maturity Model Certification (CMMC) program sets three levels for Department of Defense contractors: Level 1 (15 basic safeguarding requirements for Federal Contract Information, self-assessed annually), Level 2 (the 110 requirements of NIST SP 800-171 for Controlled Unclassified Information), and Level 3 (additional requirements from NIST SP 800-172, assessed by the government). Phase 1, which allows CMMC self-assessments in new contracts, took effect November 10, 2025. Phase 2 — mandatory third-party (C3PAO) certification for most Level 2 contracts, scheduled for November 10, 2026 — was suspended on July 13, 2026 while the Department reviews the program (status as of October 2026).

    Status as of October 2026. The suspension has continued past its original 60-day review period. What did not change: DFARS 252.204-7012 still requires NIST SP 800-171 controls and 72-hour cyber incident reporting; SPRS self-assessment scores and annual affirmations remain in effect where contracts require them; and primes may still flow down third-party certification in their own subcontracts. We update this page as the Department issues guidance.

    CMMC level Information protected Requirements Assessment (current)
    Level 1 Federal Contract Information (FCI) 15 requirements (FAR 52.204-21) Annual self-assessment and affirmation
    Level 2 Controlled Unclassified Information (CUI) 110 requirements (NIST SP 800-171 Rev. 2) Self-assessment; third-party certification paused at the Department level but may be required by primes
    Level 3 Higher-sensitivity CUI Level 2 plus selected NIST SP 800-172 requirements Government-led assessment (implementation milestone suspended)

    How does CMMC compliance affect cyber insurance?

    Insurers do not price CMMC certification directly, but nearly every control CMMC Level 2 requires — multi-factor authentication, access control, logging, incident response, backups, encryption of CUI — appears on cyber insurance applications and drives both premium and coverage terms. A contractor with a strong, documented NIST SP 800-171 implementation is generally a better-controlled risk. The larger issue is consistency: your SPRS score, your System Security Plan and your insurance application are three statements about the same network, and contradictions between them create misrepresentation risk.

    The insurance consequences of compliance gaps are concrete:

    • Rescission risk. Insurers have sought to void policies after a loss when the application overstated controls such as MFA. A rescinded policy pays nothing.
    • False Claims Act exposure. The Department of Justice’s Civil Cyber-Fraud Initiative pursues contractors that misrepresent cybersecurity compliance to the government. Defense costs may be covered under some management liability or cyber policies; FCA damages and penalties generally are not insurable.
    • Contractual liability. A CUI breach can trigger indemnity claims from your prime. Many cyber policies exclude liability assumed by contract unless it would exist without the contract — review this wording before signing flow-downs.
    • Incident reporting overlap. DFARS requires reporting to the Department within 72 hours; your policy requires prompt notice to the insurer and use of approved vendors. One incident response plan must satisfy both clocks.

    How does the NIST Cybersecurity Framework 2.0 map to cyber insurance underwriting?

    NIST CSF 2.0, released in February 2024, organizes cybersecurity into six functions — Govern, Identify, Protect, Detect, Respond and Recover — and the questions on a modern cyber insurance application follow almost the same structure. Mapping your program to CSF 2.0 lets you see which controls an underwriter will ask about, which gaps will raise premium or trigger exclusions, and which investments improve both security and insurability. We use it as the shared language between your IT team, your leadership and the insurer.

    CSF 2.0 function Underwriting question Coverage consequence of a gap
    Govern Who owns cyber risk? Is there a policy, a budget and board-level reporting? Higher retentions; management liability concerns after an incident
    Identify Do you have an asset inventory, including OT and end-of-life systems? End-of-life or unsupported software exclusions; sublimits for legacy systems
    Protect MFA on email, remote access and privileged accounts? EDR? Privileged access management? Patching cadence? Declination, ransomware sublimits or coinsurance, or rescission if misstated
    Detect 24/7 monitoring (MDR/SOC)? Centralized logging? Higher premium; longer dwell time increases covered loss and insurer scrutiny
    Respond Written, tested incident response plan? Pre-approved breach counsel and forensics? Slower response; disputes over use of non-panel vendors
    Recover Offline or immutable backups, tested restores, defined recovery time objectives? Reduced business interruption recovery; extortion becomes the only option

    What does a cyber insurance policy cover?

    A comprehensive cyber policy combines first-party coverage for your own losses with third-party coverage for claims brought against you. First-party coverage typically includes incident response (forensics, legal, notification, credit monitoring), business interruption, data restoration and cyber extortion. Third-party coverage typically includes privacy and network security liability, regulatory defense and penalties where insurable, and media liability.

    First-party: breach response and forensics · business interruption and extra expense · dependent business interruption · data and system restoration · cyber extortion and ransom negotiation · bricking · social engineering and funds transfer fraud (where included)

    Third-party: network security and privacy liability · regulatory defense and fines where insurable · PCI fines and assessments · media and content liability · technology errors and omissions (for firms providing technology services)

    What should be in place before applying for cyber insurance?

    Insurers now treat a short list of controls as minimum conditions of coverage, and lacking them can mean declination, significantly higher retentions, or restricted ransomware coverage. The core set is multi-factor authentication on email, remote access and privileged accounts; endpoint detection and response on all endpoints; offline or immutable, tested backups; a patching program for critical vulnerabilities; and a tested incident response plan. Each answer on the application should be accurate as of the day you sign it.

    Our process before any cyber submission:

    1. Control inventory against the application questions, with your IT provider in the room.
    2. Evidence file — screenshots and reports that support each “yes,” kept with the application.
    3. Gap plan — controls you can complete before binding versus those you disclose and remediate.
    4. Definitions review — the clauses in the table above, negotiated before price is discussed.

    Schedule a Cyber Coverage Review

    Related: Aerospace & Defense · Advanced Manufacturing · Contractors (incl. IT firms)

    This page is educational and does not alter any policy or constitute legal advice on CMMC or DFARS compliance. Coverage is determined by the actual policy forms, endorsements and declarations issued by the insurer.

    What triggers it. What’s excluded. What you pay first. We go over it with you, in the policy’s own words.

    Schedule a Cyber Coverage Review