RESEARCH DOSSIER
Commercial Cyber Property and Liability Program Integration
Abstract. A single enterprise cyber event may disable information systems, impair industrial equipment, interrupt production, expose personal information, generate claims against the enterprise, and cause contractual losses throughout a supply chain. Commercial insurance responds to these consequences through several distinct insuring agreements, not through the technical classification of the initiating event alone. This monograph investigates the coordination of standalone cyber, commercial property, general liability, business interruption, crime, professional liability, and excess insurance when one initiating cyber event produces simultaneous first-party and third-party losses. Its evidence base combines insurance supervisory statements, market requirements, incident-response standards, legislation, original judicial decisions, official market statistics, and peer-reviewed cyber-risk research. The analysis distinguishes cyber causation, contractually defined insured loss, loss measurement, and recoverability; differentiates damaged tangible equipment from corrupted information and unavailable services; and traces the changing relation between occurrence-based property and liability insurance and event-, discovery-, or claims-made cyber protection. The research finds that integration turns principally on the coordination of definitions, temporal triggers, allocation clauses, aggregation provisions, and limits across policies. It also finds that historical judgments about electronic data and war exclusions are intensely wording- and jurisdiction-dependent; that incident response and regulatory notification create expense obligations before many liability outcomes are resolved; and that an enterprise’s insured recovery can be substantially less than its total economic harm even when several policies respond. A transparent illustrative loss ledger demonstrates these interactions without representing a market loss estimate. Market evidence from the National Association of Insurance Commissioners documents growing claim counts alongside changing premium levels, but cannot establish enterprise-level protection without insured-value, contract, and population denominators. The conclusions provide an evidence-based research agenda for cross-line contract comparison, incident accounting, accumulation assessment, and insurance governance. No new insurance theory or proprietary actuarial model is asserted.
Keywords: commercial cyber insurance; property insurance; liability insurance; cyber-physical loss; non-affirmative cyber; silent cyber; business interruption; privacy liability; contingent business interruption; insurance contract interpretation; aggregation risk; insurance program integration; insurance coverage gap; insurance claims; operational resilience; reinsurance
Introduction
Commercial cyber exposure is a compound financial and legal phenomenon. The same malicious code, erroneous software update, credential compromise, or unauthorized network instruction may cause a server to fail, a production line to stop, orders to be delayed, confidential records to become accessible, and customers to demand compensation. Each consequence has its own factual chain, duration, claimant, and possible contractual response. The central question is therefore: under what evidentiary and contractual conditions can an enterprise reconcile one cyber-origin incident across several insurance policies without mistaking an economic loss for an insured indemnity?
The distinction matters because a portfolio of apparently comprehensive policies can contain incompatible definitions of property, damage, interruption, computer systems, unauthorized access, third-party injury, and occurrence. A retained loss can sit below several policy attachments. The same payment may be presented to more than one insurer without becoming recoverable twice. A privacy claim can arise long after initial business interruption has been adjusted. A computer-induced physical event can be covered under a specifically drafted cyber-property extension while ordinary cyber coverage excludes tangible damage. Lloyd’s CY and CZ risk-code distinction explicitly differentiated cyber business without physical-property damage from coverage involving physical damage in its historical market guidance.
The research object is enterprise program coordination at the intersection of cyber, property, and liability insurance. The unit of causal analysis is an incident or linked incident sequence; the unit of indemnity is a contractually eligible loss component; the units of market inference are defined policy, claim, insurer, and exposure populations. These units must remain distinct. A security event is a technical occurrence; a data breach is a legally and operationally specific exposure; a claim is a demand or procedure defined by applicable wording; and payment is an executed contractual or negotiated outcome. The analytical value of integration lies in making these transitions visible.
Three questions govern the investigation. First, how do cyber triggers translate into property damage, system impairment, or interruption, and what observations can distinguish those outcomes? Second, how do incident costs and third-party claims pass through different coverage terms, legal duties, and enterprise decisions? Third, what do market evidence and cross-country supervisory practices establish about uncovered exposures, event concentration, and the limitations of enterprise protection?
The evidence is documentary and comparative rather than an original claims census. It draws on PRA cyber underwriting expectations, EIOPA’s non-affirmative cyber statement, NAIC market reporting, NIST technical guidance, European legislation, and identified United States decisions. Peer-reviewed studies inform insurability and sample-selection limitations. An illustrative numerical exercise discloses all assumptions. The study neither infers an insurer’s actual coverage decision from generic policy labels nor treats a judicial holding as universal law.
Scientific Foundations and Comparative History
Object of the inquiry and methodological commitments
An enterprise insurance program is the set of policies, endorsements, insured entities, covered locations, limits, retentions, reporting duties, and inter-policy provisions through which specified financial consequences may be transferred. The program may be administered centrally while different entities and territories remain subject to distinct local policies. The object investigated here is narrower than enterprise risk management as a whole: it is the interaction of cyber-origin consequences with commercial property, liability, and affiliated expense insurance.
There are four necessary levels of description. An initiating mechanism is the unauthorized, malicious, accidental, or dependent-system condition that changes operations. An economic consequence is the measurable cost, lost margin, asset impairment, or obligation attributable to that condition. An insurance characterization applies contractual grants, definitions, conditions, exclusions, and legal rules to a consequence. A recovery is the amount ultimately paid, net of retentions, limits, allocation, and settlement terms. An incident can be certain at the first level while coverage remains disputed at the third; paid recovery should never be inferred simply from an alleged amount of loss.
The methodological priority is source-to-claim matching. Statutes establish the duties they actually impose on defined entities and territories. A regulatory expectation governs the institutions within its remit, subject to its effective date. An insurance case establishes the particular court’s interpretation of identified policy terms and pleaded or proven facts. A market statistic measures the reporting population and accounting concept stated by its producer. A scholarly article contributes the design and findings of its sampled research, with its limitations retained. No one of these kinds of source substitutes for the others.
A core program integration exercise can be expressed as an accounting sequence: incident observations; itemized losses and obligations; candidate insurance grants; exclusions and conditions; allocation and attachment; insurer payments; and residual enterprise loss. This is an analytical procedure for applying existing contract and accounting concepts, not a proposed new theoretical model. Its purpose is to prevent an event label, such as ransomware, from concealing the different contractual paths of revenue interruption, corrupted records, replacement equipment, personal injury, and third-party privacy actions.
The historical formation of separate insurance responses
Commercial property and liability insurance developed around physical property interests, interruption following specified covered damage, legal responsibility to third parties, and the defense of covered claims. Businessowners packages later combined selected property, business income, and liability protections, but a package label alone says little about the treatment of digital loss. Modern cyber insurance added affirmative grants for incident response, privacy breach services, computer restoration, cyber extortion, network security liability, and selected nonphysical interruption losses. Coverage language then had to respond to events capable of crossing those historically separated categories.
This history explains the concept of non-affirmative or silent cyber exposure. Cyber causation can activate a traditional policy even when the policy was originally designed and priced around other causes. The Prudential Regulation Authority’s cyber insurance underwriting statement includes malicious and nonmalicious acts involving tangible and intangible assets and places non-affirmative exposure, risk appetite, and expertise within its supervisory concerns. The Bank of England’s page identifies a current version published November 15, 2024, effective December 31, 2024; reliance on the initial July 2017 edition alone would miss that version history.
EIOPA’s 2022 supervisory statement asks national supervisors to focus attention on undertakings with significant non-affirmative exposure and inadequate identification or management plans. Lloyd’s current war and coverage guidance similarly emphasizes express wording rather than a silent assumption that an omission equals the intended cover. These positions concern underwriting certainty and supervisory discipline. They do not determine the outcome of a policyholder’s disputed claim in a particular jurisdiction.
Lloyd’s earlier classification of cyber-property coverage is useful precisely because it does not collapse first-party and third-party loss into a single property category. Its CY code described security and privacy loss without physical property damage; CZ included damage to physical property. The codes are market classification tools, not universally controlling policy clauses. Their institutional value is evidence that insurers recognized a meaningful coverage boundary before the later consolidation of cyber products.
The resulting historical direction is toward express grants and express exclusions, cyber-specific provisions added to existing lines, and more detailed attention to loss accumulation. It is an imperfect transition. Legacy language persists, endorsements interact with base forms, and national interpretive doctrines vary. A corporate program must therefore be evaluated against the actual policy editions in force at the loss date rather than inferred from the trajectory of the market.
The literature on insurability and evidentiary selection
Cyber insurance research has long identified intertwined problems of correlated loss, limited usable experience, and informational asymmetry. Biener, Eling, and Wirfs (2015) examined 994 operational-risk cyber-loss cases and assessed insurability criteria. Their sample illuminates the structure of recorded cyber losses, but reported operational events are not equivalent to a population of insured claims or to global economic cyber damage.
In a structured review of 209 papers, Eling and Schnell (2016) identified data, modeling, dynamic exposures, and accumulation as persistent barriers to conventional underwriting. The review’s evidence is historical to its search horizon; its continuing value lies in the identified research problems, not in an assertion that the 2016 market volumes describe conditions in 2026.
Romanosky (2016) investigated reported cyber incidents, their causes, and recorded costs. The study illustrates heavy-tailed costs and a profound selection issue: many incidents have no observed financial consequence in the dataset, while publicly reported events and costs depend on reporting incentives and available records. The paper’s descriptive comparisons should not be repurposed as a current insurance rate, a universal cyber-loss frequency, or a forecast for an individual enterprise.
These contributions establish a methodological constraint: incident datasets, security surveys, insurer claims statistics, and economic-loss estimates are related but different objects. The present inquiry uses their conceptual findings to construct and audit contract comparisons; it does not convert their heterogeneous observations into a pooled global actuarial distribution.
Cyber Triggers and Property Damage
Technical events and contractual causes of loss
A causal investigation begins with the actual incident sequence. Relevant mechanisms include credential compromise, malicious remote instruction, ransomware encryption, destructive code, unauthorized changes to operational technology, software or configuration error, and failure of an external service provider. An outage can follow an intentional attack or an accidental update. These pathways may have different exclusions, attribution requirements, and reporting obligations even where their financial consequences overlap.
NIST’s guide to operational technology security defines a domain in which programmable systems monitor or control physical environments, including industrial controls and building systems. It emphasizes safety, reliability, and physical-process effects. That technical account supports the possibility of cyber-origin physical harm but does not, by itself, establish that any insurance contract covers such harm. A manufacturing failure requires evidence concerning commands, process histories, equipment conditions, alarms, preventive interlocks, mechanical condition, and the relationship between digital changes and physical damage.
Incident reconstruction also has a temporal dimension. Initial intrusion, execution of malicious instructions, loss of functionality, discovery, reporting, restoration, and subsequent claims may occur on different dates. Event aggregation terms may combine them; claims-made liability cover can respond by a claim first made or reported within a period; occurrence-based property protection may turn on when damage occurred. Every temporal finding must therefore be mapped to a particular clause. The insurer and insured may agree on the existence of an attack and disagree about which policy period or retention applies.
The NIST Cybersecurity Framework 2.0 provides a common operational vocabulary for governing, identifying, protecting, detecting, responding, and recovering. Its outcomes can help organize evidence of controls and recovery readiness. They should be treated as cybersecurity risk-management guidance, not as substitute policy warranties or automatic coverage conditions. Whether a specific security failure affects indemnity depends on the contract, applicable law, and any material representation or condition.
Tangible assets, electronic data, and unavailable services
Three forms of loss should be separated in technical records and insurance analysis. First, tangible damage may involve a burned drive, destroyed controller, impaired industrial motor, or damaged manufacturing equipment. Second, electronic data or software may be corrupted, encrypted, erased, or made unusable while physical equipment remains intact. Third, a service may become unavailable despite preserved hardware and data integrity, producing financial interruption. Some policies expressly deem selected electronic data impairments physical loss for defined purposes; others exclude electronic data, limit restoration cost, or require tangible damage.
The boundaries matter because asset replacement, data restoration, reconfiguration, and lost income are different economic consequences. A claim file should identify which items existed before the event, which were changed, and the feasible repair or restoration alternatives. Replacing a whole server may be economically rational while the policy limits payment to the cost of restoring insured property. Conversely, a technology-focused insuring agreement may cover system failure without showing traditional tangible damage. Neither result follows from the word cyber in the declaration.
Lloyd’s CY/CZ market distinction demonstrates the underwriting relevance of physical damage. The question for a particular insured is more precise: does a cyber exclusion in a conventional property policy remove this cause, does a resulting-damage exception restore part of the loss, and does a cyber policy extend to physically damaged assets? A casualty policy may also be implicated if a system failure injures a third party or damages that party’s property. Those are separate insuring-agreement questions even when one electronic command causes all of them.
The technical evidence sequence should preserve contemporaneous logs, images of affected systems, OT historian records, equipment inspections, expert findings, business records, and custody histories. Loss quantification is strongest when the technical counterfactual is stated: what would the equipment and operations have done absent the incident, given maintenance, demand, and other preexisting constraints? That question determines both causation and the appropriate baseline for interruption accounting.
Judicial interpretation of cyber-induced property loss
The 2023 New Jersey appellate opinion in Merck v. ACE provides unusually concrete evidence of contract structure. Merck sought coverage under twenty-six all-risk property policies after the June 2017 NotPetya event. The opinion described three property layers with an aggregate program limit of $1.75 billion above a $150 million deductible; approximately $699.475 million was disputed by the remaining appellants. These are litigation and program figures, not a verified final aggregate claims payment. Crucially, the quoted property wording included computer-data destruction, distortion, or corruption within defined physical loss or damage and also contained a computer-systems nonphysical-damage extension. The appellate court affirmed that the particular hostile or warlike action exclusion had not been shown to apply to the circumstances presented.
The decision supports two narrow propositions. First, the historical all-risk wording in that litigation expressly connected physical and electronic forms of loss. Second, the appellate court interpreted a longstanding war exclusion in its context rather than treating alleged state involvement as automatically dispositive. The court explicitly declined to define every cyberattack that might fall within a war exclusion. Its holding cannot determine a differently drafted exclusion, another state’s insurance law, or a policy issued after the industry’s later state-backed cyber provisions.
National Ink and Stitch v. State Auto provides a different contractual fact pattern. A Maryland federal district court considered a businessowners policy whose computer coverage endorsement defined covered electronic media and records to include stored data. In the ransomware dispute, it granted the policyholder’s summary-judgment motion concerning direct physical loss or damage. The endorsement’s treatment of electronic records and the alleged persistent impairment mattered to that reasoning. This district court decision is persuasive evidence of an interpretive possibility under its policy and jurisdiction, not a nationwide rule that any corrupted file is physically damaged property.
Placed together, these decisions show why abstract statements about whether data are physical property are inadequate. In Merck, express coverage language and the scope of a war exclusion were central. In National Ink, specific endorsement definitions and system impairment were central. The proper research unit is the combination of wording, proof, forum, and time. A contract comparison that omits one of those four elements risks producing a false universal conclusion.
Interruption, dependencies, and time conditions
Business interruption creates a second boundary around the same event. Under a traditional property policy, lost business income commonly depends on a covered cause of physical loss or damage, together with specified waiting periods and periods of restoration. Cyber forms may provide network business interruption after a defined system security failure or system failure, sometimes without physical damage. Extensions may address dependent or contingent business interruption, cloud-service outages, vendor failures, and outages of utilities, often with narrower triggers or sublimits.
An enterprise can incur interruption from its own damaged equipment and from a third party’s service disruption at the same time. The relevant evidence includes separate outage intervals, affected revenue streams, alternative production, extra expense, saved variable costs, demand displacement, and recovery constraints. Treating every day of depressed revenue as a covered day ignores the contractually defined start and end of the period of restoration. Treating lost sales as lost profit can overstate a business-income claim. A covered loss calculation must reconcile accounting records with operational causation and the specific basis of indemnity.
A crucial distinction is between loss of functionality and physical destruction of a dependency. The business may be unable to receive cloud services although the supplier’s equipment is unharmed; the supplier may be impaired by a software failure rather than a malicious security breach; or the supplier may have an actual physical incident. A dependent-business interruption grant may cover only some of these combinations. The contract and the supplier incident record, rather than the generic phrase supply-chain cyber incident, settle the response analysis.
NIST’s 2025 incident response recommendations connect preparation, detection, response, and recovery to enterprise risk governance. For insurance purposes, good incident records simultaneously support prompt recovery, notice under the policy, proof of covered downtime, mitigation expense, and later claims reconstruction. The practical insight is that response design and insurance evidence design should be coordinated before a loss, because records lost during restoration cannot reliably be recreated afterward.
Incident Cost and Third-Party Claims
Incident accounting and first-party expense categories
Incident cost is a portfolio of distinguishable obligations rather than a single invoice category. First-party costs may include forensic investigation, external incident managers, systems rebuilding, specialized legal advice, notification and credit monitoring, public communications, extortion response, equipment replacement, extra expense, and loss of business income. Third-party costs may include defense, settlements, judgments, contractual indemnities, privacy actions, and injury or property damage claims. Financial reporting may recognize further liabilities or impairments that are not insured, and some direct business costs may be excluded or too remote for indemnification.
The NAIC cybersecurity overview lists diverse possible consequences including interruption, reputational harm, data repair, hardware and software cost, and litigation. It also warns that commercial property and general liability policies commonly do not provide broad cyber protection and that cyber policies are customized. This supports checking actual contracts rather than assigning standard coverage to each cost label. It does not mean that every listed expense is included in every policy, nor that reputational loss is normally measurable or payable on the same basis as invoiced restoration.
Claims accounting should maintain a loss-component ledger with unique identifiers, service period, payee, claimant, affected legal entity, causation description, original invoice or revenue evidence, candidate policy, adjustment status, and ultimately paid amounts. An insurer’s panel-vendor requirement, consent-to-incur-expense provision, sublimit, hourly waiting period, or betterment restriction can materially alter the amount recoverable. The same legal firm may perform both breach-response advice and defense of a civil action, and its work should be allocated by what it actually did rather than pooled into a single legal-cost category.
The ledger must also preserve the chronology of cash. Crisis vendors are often paid well before claims are adjusted, class actions settle, or the business resumes normal operations. Liquidity exposure therefore can exceed the eventual uncovered loss, because the insured advances costs during investigation and recovery. This timing problem is especially important for smaller enterprises and groups with centralized cash management. Insurance limit adequacy should be tested against both net indemnity and interim funding requirements.
Liability, defense, and regulatory obligations
Third-party cyber liability takes several forms. Data subjects may allege privacy injury, customers may seek recovery for their own system damage or interruption, consumers may claim injury from an automated system failure, and business partners may assert contractual indemnities. Each theory raises distinct duty, causation, damage, jurisdiction, and exclusion questions. Network-security liability often addresses liability from failure to prevent unauthorized access or attack propagation; privacy liability addresses disclosure and misuse of information; general liability may respond to defined bodily injury or property damage; professional liability may respond to negligent services. The existence of a technical intrusion does not establish any of those legal liabilities.
The unpublished Fourth Circuit decision in Travelers v. Portal Healthcare affirmed a duty to defend under specified liability policies where a complaint alleged that medical records had been publicly accessible online. The duty-to-defend decision concerned allegations and the policy language governing publication of private information. It was expressly unpublished and nonprecedential in the circuit, and it was not an adjudication of final liability or a generalized holding that all cyber privacy claims fall within commercial general liability. The example nonetheless establishes that CGL cyber interfaces are legally real and historically contested.
Coverage analysis should distinguish defense duty, reimbursement of defense cost, and indemnity for an established liability. Some policies impose a duty to defend; others reimburse approved costs. Defense spending can erode the policy limit in one form while sitting outside it in another. Regulatory investigations may be included or excluded by a definition of claim or proceeding. Fines and penalties may be subject to express restrictions and to rules concerning their legal insurability in the relevant jurisdiction. A program cannot assume that paying for legal advice entails paying a regulator’s financial sanction.
Legal duties add time-sensitive expenses but do not create an insurance grant. Under GDPR Article 33, a controller generally must notify the competent supervisory authority without undue delay and where feasible within 72 hours of becoming aware of a personal-data breach unless the stipulated risk threshold exception applies; processors notify controllers without undue delay. Article 34 separately addresses communication to affected people under its higher-risk threshold and exceptions. These are distinct duties; neither converts every security incident into a reportable personal-data breach.
For essential and important entities within the relevant framework, NIS2 Article 23 establishes staged significant-incident reporting: an early warning generally within 24 hours, an incident notification within 72 hours, and later reporting as specified. Implementation is through member-state law and applicable implementing measures. The United States SEC disclosure guide explains that domestic Exchange Act registrants generally file Item 1.05 Form 8-K within four business days after determining a cybersecurity incident is material, not four days after discovering it, subject to its stated framework. These obligations have different triggers and populations. An enterprise needs a jurisdictional calendar, not a single universal cyber deadline.
Program coordination across policy families
Cross-policy reconciliation begins with an insuring-agreement inventory. Dedicated cyber insurance may be most relevant to response cost, electronic data restoration, cyber business interruption, network security, and privacy liability. Property and equipment coverage may be relevant to physical damage caused by a cyber event if the applicable form grants and exclusions permit it. Commercial general liability may respond to bodily injury or property damage suffered by others if the trigger, injury definition, and cyber or electronic-data exclusions permit it. Professional liability may address a covered negligent professional service. Crime coverage may address specified fraudulent transfer or social engineering, often subject to distinct authorization, verification, and discovery wording. None of these descriptions represents an automatic payment promise.
Four points govern coordination. First, definitions identify insured persons, entities, assets, locations, systems, and third parties. Second, temporal terms establish what happened and when, when a claim is considered made, and whether circumstances were notified in the required period. Third, exclusions and affirmative carvebacks establish which consequences remain in scope, including physical damage, electronic records, failure of utilities, infrastructure, and war or state-backed attacks. Fourth, limits and allocation provisions determine which eligible costs can be funded, including shared aggregates, specific sublimits, deductibles, retentions, and excess attachment.
Other-insurance clauses are particularly sensitive. Two policies may each appear to grant a form of defense or indemnification while making their relation to other coverage contingent, excess, or otherwise allocable. Coordination must use actual other-insurance text and applicable law. The economic principle against double recovery is distinct from the legal order in which insurers contribute. An insured may pursue more than one potentially responsive policy, but the consolidated recoveries and expenditures must reconcile to the loss and governing obligations.
An enterprise group also faces named-insured and territorial issues. A cyber event involving a parent and subsidiaries may cross countries and locations that are not identically scheduled. Local compulsory insurance, admitted-market restrictions, sanctions, and tax considerations can constrain the master program’s response. An affiliate’s legal obligation may be excluded even when the parent incurs business loss from that same event. This is a case for precise legal-entity mapping and policy schedules; the label global program cannot replace such evidence.
Illustrative loss allocation and sensitivity
The following example is entirely hypothetical. It demonstrates accounting and attachment logic for specified assumptions. It is not an observed loss, insurer quotation, market forecast, or new actuarial model. Assume one connected cyber incident causes the following gross enterprise economic losses, measured in millions of US dollars. Each item is separate and there is no duplicate billing.
| Loss component | Gross loss, USD millions | Assumed program response |
|---|---|---|
| Forensics and system restoration | 1.20 | Cyber first-party |
| Privacy response and third-party defense | 1.80 | Cyber liability/response |
| Own-network business interruption | 5.00 | Cyber business interruption |
| Dependent cloud-provider interruption | 2.50 | Excluded in base case |
| Physical industrial equipment damage | 3.00 | Property |
| Third-party bodily-injury liability | 4.00 | General liability |
| Deceptive funds-transfer loss | 0.50 | Crime |
| Total | 18.00 | Subject to clauses below |
Assume the three eligible cyber items total USD 8.00 million, a single USD 1.00 million cyber retention, and a USD 6.00 million shared primary cyber aggregate. The cyber payment is the smaller of USD 6.00 million and USD 8.00 million less the USD 1.00 million retention: USD 6.00 million. Assume separately that the property policy pays USD 3.00 million less a USD 0.50 million retention, or USD 2.50 million; the liability policy pays USD 4.00 million less USD 0.25 million, or USD 3.75 million; and the crime policy pays USD 0.50 million less USD 0.10 million, or USD 0.40 million. All four hypothetical grants are assumed to apply; no costs overlap and no separate sublimits or coinsurance apply.
The base-case program pays USD 12.65 million, leaving USD 5.35 million economically unrecovered. That residual comprises USD 2.00 million from the cyber grant after the retention and cap, USD 2.50 million of excluded dependent interruption, and USD 0.85 million of property, liability, and crime retentions. The exercise deliberately distinguishes a gap caused by an exclusion from a gap caused by an exhausted aggregate. Both are uncovered in the base-case accounting, but their contractual remedies differ.
Now suppose a follow-form cyber excess layer supplies USD 3.00 million after the exhausted primary, with unchanged eligible gross cyber loss. One additional USD 1.00 million of cyber eligible net loss is payable, raising total program recovery to USD 13.65 million and reducing residual loss to USD 4.35 million. If, in addition, a valid contingent interruption extension covers the USD 2.50 million cloud interruption within the same cyber limit structure, net eligible cyber loss after the USD 1.00 million retention becomes USD 9.50 million. The combined USD 9.00 million primary-plus-excess cyber capacity pays USD 9.00 million. Total program payment becomes USD 15.65 million, leaving USD 2.35 million unrecovered. The increment is constrained by the shared limit; the extension does not generate an additional independent limit.
| Sensitivity | Cyber paid | Other lines paid | Total paid | Residual gross loss |
|---|---|---|---|---|
| Base: cloud interruption excluded, no excess | 6.00 | 6.65 | 12.65 | 5.35 |
| USD 3m cyber excess, cloud excluded | 7.00 | 6.65 | 13.65 | 4.35 |
| USD 3m excess plus eligible cloud interruption | 9.00 | 6.65 | 15.65 | 2.35 |
All values are USD millions, with identical gross loss of USD 18.00 million. This sensitivity has no probabilistic calibration and no assumed premiums or insurer solvency effects. Real contracts could reverse several assumed responses, apply multiple event retentions, impose hourly waiting periods, treat defense expenses inside limits, reduce limits for earlier claims, or allocate payments among entities. Its reproducibility consists of the stated arithmetic and assumptions, not of an extrapolation to insurance-market losses.
The finding is structural: adding a covered peril can have zero immediate payment effect when a shared limit is already exhausted, while raising an attachment layer can matter only when a covered and allocated amount remains above the underlying limit. Effective program comparison therefore requires the interaction of wording and limits rather than a count of purchased policies.
Coverage Gap and Concentration
Market denominators and the difference between premium and protection
The most recent NAIC report located for this research, its 2026 cyber insurance market report, covers the 2025 reporting year. It reports approximately USD 9.46 billion in United States cyber direct written premium including alien surplus lines, compared with approximately USD 9.14 billion in 2024, a rise of 3.5 percent. Domestic direct written premium is reported at about USD 7.46 billion in 2025, compared with USD 7.08 billion in 2024. The report distinguishes primary, excess, and endorsement reporting and states that domestic insurers reported 56,323 claims in 2025. These observations describe reporting scope and market activity; they are neither an estimate of global insured limits nor a measure of the share of a particular enterprise’s loss that insurers will pay.
The direct-premium figures cannot be divided into a universal protection-gap rate because premium is the price of contractual risk transfer, not the value of uninsured damage. Likewise, claims count cannot be converted to cyber-incident incidence without a consistent exposure population and reporting definition. A claim may involve a small loss, a multi-year dispute, or multiple claims arising from one event. Insured limits can remain unused even as claims counts rise. The number of policies can differ from the number of covered organizations because entities purchase multiple layers and insurers issue endorsements and grouped contracts.
The NAIC’s 2026 report discussion of accumulation recognizes that one cloud outage, vendor incident, or widely used software vulnerability can affect many policyholders. It also notes that economic cyber losses are largely uninsured. The report’s approximation that about one percent of global economic cyber losses are insured is useful as an institutional indication of a broad gap, but its global economic-loss denominator is methodologically distinct from the US policy and premium tables; the estimate should not be interpreted as a mechanically derived audited international ratio. In particular, reported cybercrime economic costs, operational disruption valuations, and claims payments can count different kinds of effects.
To measure an enterprise protection gap, the more credible denominator is the specified loss scenario or observed loss ledger, and the numerator is payment under the actual policies after coverage adjustment. To measure an industry gap, researchers need aligned populations, insured locations, dates, loss definitions, actual insured payments, and consistent gross losses. Where these are absent, the intellectually sound conclusion is that the coverage gap is material but not precisely identified by the public premium series alone.
Comparative supervisory and legal environments
The United Kingdom’s PRA addresses both affirmative and non-affirmative cyber underwriting through Supervisory Statement SS4/17. The version history matters for evaluating insurer governance and prudential practices at a particular date. In the European Union, EIOPA’s non-affirmative exposure guidance concentrates on supervisor attention, underwriting identification, and line-of-business exposure. Both focus on insurer underwriting and resilience; neither provides a standardized worldwide policy to insured enterprises.
EU operational and data-protection law creates additional obligations for enterprises, with a different legal purpose from insurance contracts. The Digital Operational Resilience Act applies from January 17, 2025, within its defined financial-sector scope. Its ICT-risk management, incident management, testing, and third-party risk provisions should be mapped by entity type and applicable regulatory acts; it is not a general insurance coverage statute. The GDPR breach-notification framework and NIS2 incident-reporting framework likewise apply according to their own scope and thresholds. Compliance cost can become an insured expense only where relevant wording supplies the grant and conditions.
In the United States, the federal SEC disclosure framework applies to specified public-company registrants, while general insurance coverage interpretation and insurer regulation remain strongly shaped by state law and the specific policy. Portal Healthcare, National Ink, and Merck demonstrate multiple policy forms and procedural postures even within one country. They should be compared as contract-specific evidence, not combined into an imaginary uniform American cyber-insurance rule.
International comparisons must also record currency, claims inflation, insurance penetration, enforcement environment, legal process, and reporting incentives. The same incident can produce different regulatory notifications, defense costs, and recoverable liabilities across countries. This makes a global cyber policy economically appealing but contractually intricate: different local entities can face divergent compulsory terms, sanctions exposure, admissibility issues, or public-policy limits on insuring particular liabilities.
Aggregation, exclusions, and reinsurance interfaces
Cyber accumulation arises when a common vulnerability, vendor, platform, or malicious campaign produces dependent losses across many insureds and lines. One supplier outage can trigger many customers’ contingent interruption claims. A compromised software distribution system can generate business interruption, data restoration, liability, and property claims in separate companies. Dependence defeats an assumption that independent enterprise locations necessarily imply independent cyber exposures. Aggregate loss may rise together with the number of shared dependencies and the concentration of insured limits.
The 2022 Lloyd’s Bulletin Y5381 set requirements, effective for relevant inceptions or renewals from March 31, 2023, for suitable state-backed cyberattack exclusion clauses in standalone CY and CZ cyber-attack policies unless otherwise agreed by Lloyd’s. The bulletin addressed severe impairment of state functioning or security capabilities, out-of-territory effects, attribution, and defined terms. It also called attention to legally reviewed wording and back-to-back reinsurance terms. It is a market requirement directed to the specified Lloyd’s business, not a statement that every state-associated incident is excluded from every property or cyber policy.
This issuance must be interpreted alongside the earlier Merck appellate decision. Merck involved 2017–2018 property policy wording and a historically worded hostile/warlike action exclusion; Y5381 concerned later standalone cyber wording and specified more express state-backed exclusion requirements. The apparent tension disappears when policy class, contract edition, and applicable legal forum are made explicit. It would be an error either to use Merck to promise recovery under every later cyber policy or to use Y5381 to recast the wording that the court actually reviewed.
For an insurer or reinsurer, non-affirmative exposures challenge accumulation estimates because cyber triggers may be embedded in property, liability, and specialty books outside standalone cyber premiums. For an insured enterprise, the parallel issue is whether aggregate limits, incident definitions, retentions, and reinstatements coincide. Reinsurance can affect insurer capacity and pricing, but the policyholder’s contractual entitlement is ordinarily determined by the policy and governing law rather than by a general assumption that reinsurers will reimburse the insurer. Specific direct insurance or cut-through provisions require separate examination.
A credible accumulation assessment therefore reports the shared technology dependencies, the enterprises and lines exposed, event definitions, loss correlation assumptions, policy exclusions, aggregate caps, and the basis for allocating a common catastrophe among insurers. Models that assume independent incidents while overlooking shared software or cloud providers understate tail dependence. Models that assume all insureds incur maximum limits simultaneously can overstate plausible response unless that stress is explicitly labeled as an extreme scenario.
Enterprise residual risk and recovery governance
Residual loss after insurance includes uninsured categories, exhausted limits, retentions, timing gaps, uncollectible or disputed amounts, and indirect effects that policy terms do not indemnify. A firm may also face costs of rebuilding trust, changing systems, or strengthening controls that serve future benefit rather than restitution for the insured event. Those costs should be distinguished from a covered reasonable mitigation or recovery expense. The financial statement and cash flow of the insured enterprise are not identical to the claims-adjusted loss.
Program coordination is strongest before the loss. Risk and insurance managers can reconcile schedules of insured entities, policy periods, cyber and data definitions, dependent service providers, waiting periods, liability defense provisions, and common aggregate limits. They can simulate one initiating incident with physical, nonphysical, privacy, and bodily-injury consequences and require each insurer or broker to identify the relevant insuring provision and exclusion. A properly documented comparison can reveal uncovered segments before the incident has occurred.
During an incident, enterprises need coordinated incident command, legal privilege assessment, preservation of forensic material, timely insurer notice, approved panel engagement, and transparent cost allocation. Coverage preservation is part of disciplined incident management, but operational safety, data-protection duties, and prompt recovery remain governed by their own requirements. An enterprise should not delay necessary safety action merely because coverage allocation is unresolved.
After the incident, claims and finance teams should reconcile gross costs, policy payments, subrogation proceeds, third-party recoveries, and residual loss. Multiple responsive insurance contracts demand allocation accuracy, particularly when excess towers, local policies, and group insurance arrangements overlap. Without a consolidated audit trail, apparent coverage breadth can obscure actual recovery or produce inconsistent positions across insurers.
Evidence Validation and Uncertainty
Source hierarchy, comparability, and adjudicated facts
The evidence used here consists of official standards and supervisory material, original legislation, reported judicial opinions, regulator market statistics, and scholarly publications. Each has a defined claim domain. Technical NIST standards describe systems and response practices; they do not decide property-insurance coverage. Judicial opinions interpret pleadings, facts, and contracts within procedural limits; they do not measure market incidence. NAIC data describe a specified US reporting population; they do not supply a complete international cyber-loss series. Academic research contributes methods and sample findings; it does not supersede primary contract text or legislation.
The strongest empirical claims in this dossier are intentionally few and precisely dated: the NAIC’s 2025 reporting-year premium and claims figures; dates and scope stated in official supervision and regulation; and the program terms, litigation amounts, and outcomes expressly recited by courts. The analysis does not rely on undocumented private loss databases. The evidence ledger accompanying the manuscript records each checked source, its URL, material claim, and limitation. The source claims are tied to visible links in the chapters and full bibliographic entries.
A court’s statements need procedural qualification. The appellate judgment in Merck affirmed a particular ruling on an exclusion; the underlying factual narrative contains litigated assertions and judicially described policy language, not an audited worldwide NotPetya loss total. National Ink was a federal district court’s summary-judgment determination about one businessowners endorsement. Portal Healthcare was an unpublished appellate affirmance of a duty-to-defend ruling based on alleged publication of private records. The contract particulars explain the results more reliably than generalized slogans about cyber coverage.
The survey literature creates separate limits. Biener and coauthors’ sample does not identify all incidents, all uninsured losses, or contemporary cross-policy claims. Eling and Schnell’s literature review has a 2016 publication horizon. Romanosky’s reported-event analysis acknowledges missing cost observations and selection constraints. The work uses them for critical interpretation, not direct calibration of 2026 contract prices or expected claims.
Contractual, legal, and empirical uncertainty
Contractual uncertainty is created by different policy wordings, endorsement priorities, manuscript clauses, definitions of systems and events, temporal conditions, aggregation provisions, and allocation rules. Legal uncertainty arises from jurisdiction-specific interpretation, statutory requirements, insurability of penalties, procedural posture, and subsequent appellate or regulatory developments. Empirical uncertainty arises from incomplete loss reporting, changing cyber technology, varying denominators, unknown insured values, and confidential settlement records. These dimensions should be reported separately because more historical incident data cannot resolve an ambiguous exclusion, and more detailed contract wording cannot by itself identify the frequency of future correlated loss.
Potential confounding factors include preexisting hardware condition, maintenance and backup quality, demand changes during downtime, unrelated outages, restoration betterment, third-party supply interruptions, and post-event legal claims whose origin may differ from the initial technical incident. In business interruption, failing to deduct saved costs and account for replacement sales can distort indemnity. In privacy liability, assuming that record access occurred merely because data became publicly reachable can obscure distinct legal and factual issues. In state-backed attack exclusions, treating technical attribution, political attribution, and the contract’s attribution procedure as interchangeable can create serious errors.
The 2026 NAIC figures offer a specific uncertainty example. USD 9.46 billion of direct written premium is measured under a defined US reporting approach including alien surplus lines. USD 7.46 billion of domestic premium uses a narrower population. Treating either as global premium, or combining either with worldwide economic cybercrime losses to derive a precise percentage of insured harm, would mix inconsistent denominators. The report’s own methodology and insurance class distinctions must travel with any reuse of the figures.
Audit trail, measurement design, and robustness
A reproducible claims study should preserve versioned policy wordings, declarations, endorsements, entity schedules, renewal dates, actual coverage correspondence, incident technical timeline, loss accounting, legal filings, and insurer payment records. Researchers should define the population before estimating incident or claims frequency and identify whether every record represents a security event, one policy claim, one insured group, or one litigated dispute. Cost data should state currency, price year, inclusion of defense and business interruption, treatment of uninsured amounts, and known censoring.
For contract comparisons, a practical cross-check tests each loss component against at least two plausible characterizations: physical property damage versus intangible data impairment; own versus dependent interruption; first-party expense versus third-party defense; malicious act versus nonmalicious system failure; and occurrence versus first-made claim. For each characterization the study should ask what changed in the wording, what records support it, and what payment implication follows. This is a robustness exercise because the result is sensitive to defined assumptions, not an invitation to select whatever policy yields the largest hypothetical indemnity.
The numerical example in the preceding chapter is arithmetically reproducible from seven loss rows and four retentions. Repeating it with an additional excess layer and extended dependent-interruption grant isolates the effects of capacity and eligibility. It does not simulate claims frequency, vendor failure dependence, premium costs, credit risk, court uncertainty, or settlement behavior. Those would require separate data and models. Its scientific function is to expose where an unqualified statement such as insured for cyber business interruption conceals multiple independent requirements.
The technical controls for this research package are distinct from scientific judgment. Manuscript identity, bibliographic URLs, source-to-claim mapping, exact source SHA-256, and the editorial review record can be inspected mechanically. The mandatory site-local source-link command must be executed against the authoritative repository before release approval. A successful structural check cannot demonstrate that an insurer will pay a real claim, and a scientific interpretation cannot certify a technical test that was never run.
Integrated Analysis and Research Agenda
Synthesis of cross-line mechanisms
The central finding is that commercial cyber-property-liability integration is a coordination problem across contractual objects rather than a search for one comprehensive cyber label. One event creates several causal and legal pathways. Tangible equipment damage, loss of access to data, nonphysical system outage, privacy notification, third-party bodily injury, contract indemnification, and fraud transfer can all follow from a connected event while remaining distinguishable for insurance purposes.
Three relationships recur in the evidence. The technical cause of loss does not determine a uniform insurance trigger; the detailed text of the grant and exclusions matters. Loss timing is plural; immediate forensic costs, periods of interruption, later lawsuits, and regulatory proceedings can attach to different policies or policy years. Aggregate payment is constrained by capacity and allocation; eligibility for an additional cost category has limited economic value when the relevant shared aggregate is exhausted.
The case law offers a concentrated demonstration. Merck shows that express data and computer coverage provisions materially shaped a property-insurance dispute and that a historical war exclusion had a particular legal scope. National Ink shows that an electronic media endorsement can be decisive to interpretation of physical loss. Portal Healthcare shows that allegations of public exposure of private information can engage a liability duty to defend under particular wording. Together they justify contract-by-contract analysis while resisting a false rule that every cyber event is either entirely property or entirely liability.
The supervisory material adds a portfolio perspective. The PRA, EIOPA, and Lloyd’s have emphasized non-affirmative exposure identification and clear specification of cover. These concerns are compatible with the enterprise need for clarity: an insurer should understand correlated exposure before pricing and accumulating risk, while an enterprise should understand precisely which classes of loss can be financed. Clarity can improve decision making even where it produces an express exclusion that reveals an uninsured exposure.
Underwriting, claims, and enterprise implications
Underwriters should examine how a single technology dependency can generate claims across books as well as within cyber products. Risk selection based only on a business’s individual security rating omits supplier concentration, systemic vulnerabilities, and physical process dependencies. Claims observations should distinguish incurred, paid, reported, and economically estimated losses. Policy-level attachment and reinsurance accumulation should be assessed with the actual clauses and exposures, rather than a single generic severity assumption.
Claims professionals should keep separate, reconcilable records of first-party expense, tangible asset loss, electronic restoration, business income, third-party defense, and bodily injury. Policy notices should be synchronized with actual reporting obligations but evaluated contract by contract. A coherent causal timeline and ledger can reduce duplicative adjustment and support fairer allocation among policies, while preserving reservations and dispute procedures that applicable law permits.
Enterprise managers should conduct scenario analyses using both coverage and cash-flow measures. One assessment asks how much of a defined loss is eligible under the current program. A second asks how quickly funds become available and whether the firm can maintain operations while adjustment is pending. A third asks whether one vendor or platform failure could exhaust multiple entities’ shared limits. These are existing risk-management questions; the contribution of this study is to connect them explicitly to the primary technical, contractual, legal, and supervisory record.
Research priorities
The highest-value empirical research would join anonymized incident-level causal records with full policy terms and ultimate claims payments across cyber, property, and liability lines. This would permit estimation of the distribution of losses genuinely recovered under multiple policies and reveal whether certain endorsements close measurable gaps. Such work requires careful control of confidentiality, sampling, reporting delays, insurer selection, and legal jurisdiction.
A second priority is to compare standardized cyber-origin physical-loss hypotheticals against actual wordings from different policy years and jurisdictions, especially the effect of electronic-data definitions, ensuing-loss exceptions, and state-backed cyber exclusions. Historical court decisions should be tied to policy edition and procedural status. The objective is comparable interpretation evidence, not a misleading global coverage opinion.
A third priority is to align cyber-loss accumulation scenarios with insured supply-chain graphs and cloud or operational technology dependencies, while preserving uncertainty around correlated adoption and event reach. A fourth is to examine how reporting laws influence observed incident counts and insurance claims without conflating regulatory notification with coverage-triggered loss. A fifth is to measure liquidity gaps between paid crisis response and ultimate claim recovery at the enterprise level.
These priorities follow from the evidence limitations documented in this study. They do not require inventing new doctrines or assuming that one analytical framework will solve legal, data, and actuarial problems simultaneously. Better primary data and explicit contract terms are the necessary conditions for stronger inference.
Conclusion
Commercial Cyber Property and Liability Program Integration establishes a source-grounded account of how cyber-origin losses move through commercial insurance contracts. An initiating event can be technically unified while its financial and legal consequences require distinct proof of physical damage, electronic impairment, interruption, response expense, privacy harm, bodily injury, fraud, and liability. Each consequence becomes potentially insurable through an identified grant, subject to exclusions, conditions, jurisdiction, attachment, allocation, and limits. The governing object of insurance analysis is therefore the specific insured loss component under the relevant contract, tied to the same incident through documentary evidence.
Primary court decisions confirm that wordings matter. Merck’s historical property program, National Ink’s electronic records endorsement, and Portal Healthcare’s liability publication allegations produced distinct interpretive questions; none supplies a universal rule for later cyber policies. Lloyd’s CY/CZ classification and state-backed attack bulletin, together with PRA and EIOPA supervisory positions, document an institutional demand to make cross-line cyber exposure express and assessable. NIST guidance establishes the technical basis for incident reconstruction and operational recovery. GDPR, NIS2, DORA, and SEC rules establish differing legal duties for defined entities and circumstances, which must be mapped without mistaking legal compliance for automatic indemnification.
The NAIC’s 2025 reporting-year figures show an active and changing insurance market, but premium and claims counts are insufficient to calculate the protection available against every enterprise’s economic cyber loss. A transparent USD 18.00 million illustrative scenario demonstrates why program effectiveness depends jointly on eligibility, retentions, shared limits, and excess capacity. A coverage extension does not independently create a second limit; a larger limit cannot compensate for an excluded category; and total program recoveries remain distinguishable from gross economic harm and timing-related liquidity needs.
The research concludes that rigorous integration requires versioned policy records, incident-level evidence, a loss-component ledger, jurisdiction-aware legal interpretation, and explicit aggregate and dependency analysis. It supplies an original analytical synthesis of these relationships and a bounded agenda for future empirical study. The analysis asserts no new authorial insurance theory and makes no claim of independent external peer review. The resulting manuscript is intended for scientific editorial intake and later separately authorized batch publication, with any final release decision conditioned on the documented source and technical checks.
References
Biener, Christian, Martin Eling, and Jan Hendrik Wirfs. 2015. “Insurability of Cyber Risk: An Empirical Analysis.” The Geneva Papers on Risk and Insurance—Issues and Practice 40 (1): 131–158. DOI: 10.1057/gpp.2014.19. https://alexandria.unisg.ch/entities/publication/9054bc0d-f4a7-4f46-a961-b804eef06f4d
Eling, Martin, and Werner Schnell. 2016. “What Do We Know About Cyber Risk and Cyber Risk Insurance?” The Journal of Risk Finance 17 (5): 474–491. DOI: 10.1108/JRF-09-2016-0122. https://www.sciencedirect.com/org/science/article/abs/pii/S1526594316000090
European Insurance and Occupational Pensions Authority (EIOPA). 2022. “Supervisory Statement on the Management of Non-Affirmative Cyber Exposures.” Published September 22, 2022. https://www.eiopa.europa.eu/publications/supervisory-statement-management-non-affirmative-cyber-exposures_en
European Parliament and Council of the European Union. 2016. Regulation (EU) 2016/679 (General Data Protection Regulation), especially Articles 33–34. Official Journal of the European Union. https://eur-lex.europa.eu/eli/reg/2016/679/ojv
European Parliament and Council of the European Union. 2022a. Regulation (EU) 2022/2554 on Digital Operational Resilience for the Financial Sector (DORA), especially Articles 2 and 64. Official Journal of the European Union. https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1713857248180&uri=CELEX%3A32022R2554
European Parliament and Council of the European Union. 2022b. Directive (EU) 2022/2555 on Measures for a High Common Level of Cybersecurity Across the Union (NIS2), especially Article 23. Official Journal of the European Union. https://eur-lex.europa.eu/eli/dir/2022/2555/oj/eng?uri=CELEX%3A32022L2555
Lloyd’s. 2017. “Global Policies and Cyber Insurance.” Market regulatory communication, including CY/CZ cyber risk-code definitions. https://www.lloyds.com/news-and-insights/market-communications/regulatory-communications/news-articles/global-policies-and-cyber-insurance
Lloyd’s. 2022. “State Backed Cyber-Attack Exclusions.” Market Bulletin Y5381, August 16, 2022. https://assets.lloyds.com/media/35926dc8-c885-497b-aed8-6d2f87c1415d/Y5381%20Market%20Bulletin%20-%20Cyber-attack%20exclusions.pdf
Lloyd’s. n.d. “War & NCBR Exposures.” Requirements and Standards, coverage wording guidance. Accessed November 16, 2026. https://www.lloyds.com/market-resources/requirements-and-standards/lloyds-requirements-of-the-council/operating-at-lloyds/performance-management/wr-nbbr-exposures
National Association of Insurance Commissioners (NAIC). 2024. “Cybersecurity.” Insurance Topics; page last updated May 9, 2024. https://content.naic.org/insurance-topics/cybersecurity
National Association of Insurance Commissioners (NAIC). 2026. “2026 Report on the Cybersecurity Insurance Market.” Reporting year 2025; includes primary, excess, endorsement, and alien surplus lines data. https://content.naic.org/resource-center/2026-report-cybersecurity-insurance-market
National Institute of Standards and Technology (NIST). 2023. Stouffer, Keith, et al. “Guide to Operational Technology (OT) Security.” Special Publication 800-82, Revision 3, September 2023. DOI: 10.6028/NIST.SP.800-82r3. https://csrc.nist.gov/pubs/sp/800/82/r3/final
National Institute of Standards and Technology (NIST). 2024. Pascoe, Cherilyn, Stephen Quinn, and Karen Scarfone. “The NIST Cybersecurity Framework (CSF) 2.0.” CSWP 29, February 26, 2024. DOI: 10.6028/NIST.CSWP.29. https://csrc.nist.gov/pubs/cswp/29/the-nist-cybersecurity-framework-csf-20/final
National Institute of Standards and Technology (NIST). 2025. Nelson, Alexander, Sanjay Rekhi, Murugiah Souppaya, and Karen Scarfone. “Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile.” Special Publication 800-61, Revision 3, April 2025. DOI: 10.6028/NIST.SP.800-61r3. https://csrc.nist.gov/pubs/sp/800/61/r3/final
Prudential Regulation Authority (PRA), Bank of England. 2024. “Cyber Insurance Underwriting Risk.” Supervisory Statement SS4/17, current version published November 15, 2024, effective December 31, 2024; initial version July 2017. https://www.bankofengland.co.uk/prudential-regulation/publication/2017/cyber-insurance-underwriting-risk-ss
Romanosky, Sasha. 2016. “Examining the Costs and Causes of Cyber Incidents.” Journal of Cybersecurity 2 (2): 121–135. DOI: 10.1093/cybsec/tyw001. https://academic.oup.com/cybersecurity/article/2/2/121/2525524
U.S. Court of Appeals for the Fourth Circuit. 2016. Travelers Indemnity Company of America v. Portal Healthcare Solutions, LLC, No. 14-1944, unpublished per curiam opinion, April 11, 2016. https://law.justia.com/cases/federal/appellate-courts/ca4/14-1944/14-1944-2016-04-11.html
U.S. District Court for the District of Maryland. 2020. National Ink and Stitch, LLC v. State Auto Property and Casualty Insurance Company, Civil Action No. SAG-18-2138, memorandum opinion, January 23, 2020. https://law.justia.com/cases/federal/district-courts/maryland/mddce/1%3A2018cv02138/427038/39/
U.S. Securities and Exchange Commission (SEC). 2023. “Cybersecurity Risk Management, Strategy, Governance, and Incident Disclosure.” Small Entity Compliance Guide, August 30, 2023. https://www.sec.gov/resources-small-businesses/small-business-compliance-guides/cybersecurity-risk-management-strategy-governance-incident-disclosure
Superior Court of New Jersey, Appellate Division. 2023. Merck & Co., Inc., et al. v. ACE American Insurance Company, et al., A-1879-21, opinion, May 1, 2023. https://law.justia.com/cases/new-jersey/appellate-division-published/2023/a-1879-21.html