Actuarial topic · Property and casualty and emerging risks

Cyber risk and cyber insurance

Ransomware that shuts down a plant in Querétaro, an exposed customer database or a faulty update that knocks out millions of computers on the same day. Cyber risk combines high frequency, heavy-tailed severity and an accumulation potential few lines of business share. This guide covers its typology, coverages, accumulations, war exclusions, actuarial modeling and the Mexican framework.

≈ US$15 bn
global cyber premiums 2025
Jul 19, 2024
CrowdStrike outage
2023
first 144A cyber cat bond
IntroductionTypologyCoveragesAccumulationsWar exclusionsFrequency and severityScenarios and dataPricingReinsurance and bondsCalculatorWorked exampleIn MexicoCommon mistakesFAQFurther reading
01

Introduction

Cyber risk refers to losses arising from the failure, misuse or attack of information systems and the data they hold. It can be malicious (a criminal group that encrypts servers and demands a ransom) or accidental (a configuration error, a faulty update). What sets it apart from other property and casualty risks is that its cause ignores geography: the same code can hit an insurer in Monterrey, a hospital in Mérida and a bank in Madrid within minutes.

Cyber insurance is still a young market. In April 2026 Munich Re estimated that global premiums totaled about 15 billion dollars in 2025 and could reach some 28 billion by 2030. The volume is small next to auto or fire, but the insurable exposure is enormous and nearly the whole economy now depends on a handful of cloud, operating system and security software providers.

For the actuary, this line packs several hard problems into a single portfolio: a short and shifting history, an adversary that adapts, severities with tails that look more like those of a catastrophe risk than those of auto insurance, and dependence between insureds that invalidates the independence assumption on which classic pricing rests.

02

Typology: first party, third party and what lies in between

The most useful split for the actuary separates the insured's own costs (first party) from its liability to others (third party). First party resembles property insurance with business interruption; third party resembles liability insurance with long development and litigation. A single intrusion often triggers both: ransomware halts operations (first party) and also exposes customer data, whose owners then file claims (third party).

Recent experience points to ransomware as the main source of losses. According to Munich Re's 2025 report, business interruption accounted for 51% of the costs of ransomware events, and manufacturing had the largest share of such claims, followed by healthcare. The average cost of a data breach reached a record 4.9 million dollars.

FIRST PARTY

Ransomware and extortion

Encryption of systems or theft of information with a threat to publish it. It generates ransom (where legal and insurable), forensics, restoration and downtime. It is the scenario that dominates severity in small and midsize business portfolios.

FIRST PARTY

Business interruption

Lost profit and extra expense from the outage of the insured's own systems or a supplier's (contingent business interruption). It is measured in hours and depends on recovery time, not on the value of assets.

FIRST PARTY

Data restoration and response

Forensic experts, lawyers, notification of data subjects, call center, credit monitoring and public relations. These costs are frequent and relatively predictable.

THIRD PARTY

Data and privacy liability

Claims by customers, partners or authorities over the exposure of personal or confidential data, including defense in administrative proceedings. Development is long, and severity depends on the number of records and the jurisdiction.

THIRD PARTY

Network security and media

Damage to third parties from transmitting malware, from failing to stop an attack that spreads, or from content published on the company's digital media.

GRAY AREA

Fraud and system failure

Fraudulent transfers through social engineering and non-malicious outages (human error, faulty updates). Many policies cover them with sublimits or as an optional extension.

03

Coverages in a cyber policy

A stand-alone cyber policy bundles sections with their own limits and deductibles, almost always under an annual aggregate limit. To model it, one must understand that each section has a different distribution: incident response is frequent and moderate, business interruption depends on a time threshold, and third-party liability arrives years after the event.

Cyber coverage also shows up, sometimes unintentionally, in traditional fire, liability or surety policies that do not expressly exclude cyber events. That silent cyber risk is a source of unpriced accumulation, which is why the market has been adopting clauses that affirm or exclude cyber coverage across all lines.

Incident response. Forensics, legal advice, notification, crisis center and data restoration. It usually responds from the first peso with a low deductible and is the gateway to the insurer's services.
Business interruption. Gross profit lost during the indemnity period. Instead of a monetary deductible it uses a waiting period measured in hours: if the outage is shorter, there is no payment. It can be extended to outages at IT service providers.
Cyber extortion. Negotiator fees and, where the law allows, payment of the ransom. It requires notifying the insurer and complying with restrictions on international sanctions.
Privacy and network security liability. Defense and damages to third parties and, to the extent insurable, the costs of regulatory proceedings.
Typical exclusions. War and cyber operations attributable to a State, infrastructure failure (power, telecommunications), bodily injury or property damage unless agreed, system upgrades, and willful acts of executives.
Payment under a section with a waiting period
\[Y_{BI} = \min\left\{\, b \cdot \max(0,\; D - w),\; L_{BI} \right\}\]

D is the duration of the interruption in hours, w the waiting period, b the lost profit per hour and LBI the section limit. The waiting period acts as a deductible on time, not on money: that is why small changes in w greatly alter payment frequency.

04

Accumulations and systemic risk: CrowdStrike and NotPetya

A cyber accumulation occurs when a single cause affects many insureds at once. Typical sources are a common vulnerability in widely used software, a cloud provider outage, malware that spreads uncontrollably and the technology supply chain. Unlike an earthquake, the accumulation has no epicenter: exposure is defined by technology dependencies, which almost never appear in underwriting information.

CrowdStrike, July 19, 2024. A faulty content update to CrowdStrike's security software left Windows computers inoperable around the world. Microsoft estimated about 8.5 million affected devices, less than 1% of Windows machines, but concentrated in airlines, banks, hospitals and services. It was not an attack: it was a system failure. Insured loss estimates varied by model: Guy Carpenter put it between 300 million and 1,000 million dollars, CyberCube between 400 million and 1,500 million for the stand-alone cyber market, and Parametrix calculated that US Fortune 500 companies (excluding Microsoft) would suffer direct losses of about 5,400 million, of which only 10% to 20% would be insured because of high retentions and low limits.

NotPetya, 2017. Destructive malware that the White House attributed to Russian action against Ukraine and that spread far beyond its target. Merck claimed about 1,400 million dollars from its property insurers (all risks policies) for more than 40,000 disabled machines. The insurers invoked the hostile or warlike action exclusion; on May 1, 2023, the New Jersey appellate court ruled that the exclusion did not apply because it requires the involvement of military action, and the parties reached a confidential settlement in early 2024. Mondelez, which sued Zurich for about 100 million over the same event, also settled in 2022.

The two cases teach different lessons. CrowdStrike showed that a non-malicious failure can produce the largest event of the year and that the business interruption waiting period determines how much the market pays. NotPetya showed that policies that do not mention cyber risk can end up paying for it and that the wording of war exclusions matters as much as the model.

Common shock model for claim counts
\[N_i = N_i^{\,ind} + I_E \cdot B_i, \qquad N_i^{\,ind} \sim \text{Poisson}(\lambda), \quad I_E \sim \text{Bernoulli}(p_E), \quad B_i \sim \text{Bernoulli}(f)\]

Each policy i has idiosyncratic claims and, with probability pE per year, a systemic event occurs that hits a fraction f of the portfolio. The covariance between two policies is \(p_E(1-p_E)f^2\): small for each pair, but across a portfolio of n policies it adds up to something of order n2 and dominates the tail. This is the model used by the calculator in this guide.

05

War exclusions and State cyber operations

Traditional war exclusions were written with armies and bombings in mind. The Merck case made clear that, without specific wording, a court may refuse to extend them to a cyberattack attributed to a State. The Lloyd's market responded in two steps.

On November 25, 2021, the Lloyd's Market Association (LMA) published four model clauses, LMA5564 through LMA5567. Number 1 is titled war, cyber war and cyber operation, and it is the simplest: it excludes loss arising directly or indirectly from a war or a cyber operation. Numbers 2 to 4 introduce the term limited cyber operation and offer different levels of coverage for State operations that fall short of war. All of them share the concept of a major detrimental impact on an essential service of a State.

On August 16, 2022, Lloyd's issued market bulletin Y5381, which requires its syndicates to ensure that stand-alone cyber policies exclude losses from State-backed cyberattacks and have a robust basis for attributing them, applicable to every policy incepting or renewing on or after March 31, 2023. In January 2023 the LMA replaced the original clauses with eight versions (LMA5564A and B through LMA5567A and B). The A versions include an agreed method for attributing the operation to a State and comply with the bulletin; the B versions omit attribution and require prior approval from Lloyd's. The new wording defines war as an armed conflict between States involving the use of physical force.

ElementWhat it addressesActuarial effect
War exclusion between StatesRemoves losses from armed conflicts involving physical force.Cuts off the extreme tail that no private capital can bear.
State cyber operationExcludes attacks attributed to a State with a major impact on essential services.Reduces accumulation but introduces basis risk: it depends on attribution happening and on how it is proven.
Attribution clause (A version)Defines who determines, and how, that the attack comes from a State.Provides contractual certainty; without it the claim can stay in litigation for years.
Limited coverage (numbers 2 to 4)Restores coverage for operations that do not reach the major damage threshold.Requires separate estimates of the frequency and severity of these events and their sublimit.
For the model: a poorly drafted exclusion does not remove the risk, it moves it to the legal arena. The actuary must document which events are assumed excluded and stress the scenario in which a court does not exclude them.
06

Frequency and severity modeling

The starting point is the collective model: a random number of claims per year and a random severity for each. In cyber, frequency usually shows overdispersion (the variance exceeds the mean) because of heterogeneity among insureds and waves of attack campaigns, so the Poisson is a starting point and the negative binomial a natural improvement. Severity needs heavy tails: the lognormal works well in the body of the distribution and the Pareto better describes claims above a high threshold.

The quantities that matter for the premium are not those of the gross loss but those of the layer the policy pays: the amount above the deductible and up to the limit. For that we use the limited expected value, which has a closed form for the lognormal. The same tool appears in loss functions and in reinsurance layer analysis.

Collective model: mean and variance of aggregate loss
\[S=\sum_{j=1}^{N} Y_j,\qquad E[S]=E[N]\,E[Y],\qquad \operatorname{Var}(S)=E[N]\operatorname{Var}(Y)+\operatorname{Var}(N)\,E[Y]^2\]

With Poisson, Var(N) = λ. With a negative binomial of mean λ and parameter r, Var(N) = λ(1 + λ/r): the second term grows and fattens the tail of S even though the pure premium does not change.

Lognormal from the mean and coefficient of variation
\[\sigma^2=\ln\!\left(1+CV^2\right),\qquad \mu=\ln m-\tfrac{1}{2}\sigma^2\]

m is the mean severity and CV the coefficient of variation. With CV = 3, σ² = ln 10 = 2.3026: the median is only 32% of the mean, a sign that a few large claims explain almost all of the cost.

Limited expected value of the lognormal
\[E[X\wedge u]=e^{\mu+\sigma^2/2}\,\Phi\!\left(\frac{\ln u-\mu-\sigma^2}{\sigma}\right)+u\left[1-\Phi\!\left(\frac{\ln u-\mu}{\sigma}\right)\right]\]

Φ is the standard normal distribution function. The first term is the contribution of claims below u and the second that of claims capped at u.

Expected layer payment per claim and pure premium
\[E[Y]=E[X\wedge(d+L)]-E[X\wedge d],\qquad PP=\lambda\,E[Y],\qquad P_{rate}=\frac{PP}{1-g}\]

d is the per-claim deductible, L the per-claim limit, λ the annual frequency and g the share of premium allocated to expenses and profit. The formula was validated against 2 million simulations with a relative error below 0.15%.

Pareto tail for large claims
\[P(X>x)=\left(\frac{\theta}{x+\theta}\right)^{\alpha},\qquad E[X]=\frac{\theta}{\alpha-1}\ \ (\alpha>1)\]

With α between 1 and 2 the mean exists but the variance is infinite: the sample average converges very slowly and a single claim can change the estimate. α is fitted to the excesses over a high threshold (extreme value theory) and used for the upper layers.

Tail measures for capital
\[\operatorname{VaR}_{p}(S)=\inf\{s:\,F_S(s)\ge p\},\qquad \operatorname{TVaR}_{p}(S)=E\left[S \mid S\ge \operatorname{VaR}_{p}(S)\right]\]

With p = 99.5%, VaR matches the calibration of the solvency capital requirement (see solvency). In cyber, TVaR is more informative because the tail keeps growing beyond the quantile.

07

Scenarios, vendor models and scarce history

Cyber claims data cover few years, mix very different policy wordings and reflect technology that has already changed. A 2019 claim says little about today's double extortion ransomware, and observed frequency depends on the maturity of the insured's controls, which have also changed. Fitting a distribution to that history and extrapolating to a 200-year return period is, at best, an informed guess.

That is why practice combines three sources. First, exposure models that estimate frequency and severity from insured characteristics (revenue, sector, number of records, vendor dependencies). Second, deterministic accumulation scenarios: a cloud provider outage lasting a certain number of hours, mass ransomware on an operating system, a security software failure. Third, probabilistic models from specialist vendors such as CyberCube, whose estimates were used for the CrowdStrike event and as the risk model for Beazley's Cairney bond. For market indices, PERILS publishes US cyber industry insured losses that already serve as a bond trigger.

With scarce data, credibility theory makes it possible to blend own experience with market assumptions transparently. And parameter uncertainty is best treated as one more risk: two reasonable models can differ by a factor of five in the 200-year return period loss, as the ranges published after CrowdStrike showed.

01

Cloud scenario

Outage of a regional cloud provider for a given number of hours. The duration is crossed with each policy's waiting period and its declared dependence on the provider.

02

Mass malware

Code that spreads through a common vulnerability. The fraction of the portfolio affected depends on patching and segmentation practices, which underwriting can observe.

03

Cascading data breach

Compromise of a vendor that processes data for many insureds. It triggers third-party liability with long development and simultaneous notification costs.

08

Pricing based on security controls

A cyber rate starts from a base premium by size (revenue) and sector, and adjusts it with factors that reflect the insured's security hygiene. What is new compared with other lines is that those factors can be verified from the outside: external scans reveal exposed ports, expired certificates or unpatched software, and the insurer can require minimum controls as a condition of underwriting.

Controls act on different components. Multifactor authentication and patch management reduce frequency; tested offline backups reduce ransomware severity because they shorten the interruption and weaken extortion; a rehearsed response plan reduces first-party costs. Separating the effect on frequency and severity makes it possible to price with GLM relativities rather than arbitrary discounts.

The pricing cycle also matters. After the 2020 to 2022 increases, Howden reported that global cyber rates were 22% below their mid-2022 peak and that market revenue growth slowed to 6% a year between 2022 and 2024. A soft market with better controls can be profitable; a soft market that relaxes requirements repeats the mistake of the previous cycle.

Premium with multiplicative relativities
\[P = B(\text{revenue}, \text{sector}) \times \prod_{k} r_k \times \frac{1}{1-g}, \qquad \ln E[N\mid \mathbf{x}] = \beta_0+\sum_k \beta_k x_k + \ln(\text{exposure})\]

B is the base risk premium, rk = eβk the relativity for control k (MFA, backups, endpoint detection and response, privileged access management, training) estimated with a Poisson frequency GLM, and g the loading for expenses and profit. An analogous model with a gamma distribution estimates the effects on severity.

MFA on email and remote accessTested offline backupsEDRCritical patching within daysPrivileged accessResponse planVendor management
09

Reinsurance and cyber catastrophe bonds

Cyber insurance relies heavily on reinsurance. The dominant form has been quota share, which shares premiums and losses proportionally and allows the cedent to grow without consuming as much capital. Accumulation protection is bought through per event or aggregate excess of loss covers, whose weak point is the event definition: when are two intrusions with the same malware a single event?

Since 2023 cyber risk has reached the capital markets. In January 2023 Beazley placed Cairney, a 45 million dollar private bond with an indemnity trigger that protects above a 300 million event. AXIS sponsored Long Walk Re 2023-1, described as the first cyber catastrophe bond placed under Rule 144A, for 75 million dollars, with a per occurrence indemnity trigger and a 510 million attachment point. In December 2023 Swiss Re issued Matterhorn Re 2023-1 for 50 million, the first with an industry loss trigger based on PERILS data. In January 2024 Beazley closed PoleStar Re 2024-1, at 140 million, its first 144A bond.

For an investor, the appeal is a high premium for a risk with little correlation to earthquakes and hurricanes. For the actuary, each structure raises a different question: with indemnity, how much of the cedent's underwriting risk does the investor take on; with an industry index, how much basis risk does the cedent take on.

INDEMNITY

Pays the cedent's actual loss

No basis risk for the insurer, but the investor depends on the quality of its underwriting and the wording of its policies, including war exclusions.

INDUSTRY INDEX

Pays according to the market loss

Transparent and hard to manipulate. The cedent bears the risk that its portfolio fares worse or better than the market in a specific event.

10

Interactive calculator

Lab

Pure premium of a cyber layer and VaR of a portfolio with accumulation

Poisson frequency per policy, lognormal severity with editable mean and CV, per-claim deductible and limit. The pure premium uses the closed-form limited expected value formula; the portfolio's 99.5% VaR and TVaR are obtained by Monte Carlo with a fixed seed, with and without a systemic event that hits a fraction of the policies.

·
Expected layer payment per claim E[Y]
·
Pure premium per policy
·
Gross rate premium per policy
·
Expected portfolio loss (formula)
·
Simulated mean loss (validation)
·
Portfolio 99.5% VaR with accumulation
·
99.5% VaR without accumulation
·
99.5% TVaR with accumulation
·
Implied capital: VaR minus mean / gross premiums

11

Worked example: pure premium of a cyber policy for a midsize company

A pharmaceutical distributor in Guadalajara applies for a cyber policy with a $500,000 deductible and a $15,000,000 limit per claim. Based on its sector, size and controls, the technical team estimates a frequency of 0.2 claims per year and a lognormal gross severity with a mean of $3,000,000 and a coefficient of variation of 3. The loading for acquisition and administrative expenses and profit is 35% of premium.

  1. Lognormal parameters: σ² = ln(1 + 3²) = ln 10 = 2.3026, so σ = 1.5174 and μ = ln 3,000,000 − 2.3026 / 2 = 14.9141 − 1.1513 = 13.7628. The median is e13.7628 ≈ $948,700, less than a third of the mean.
  2. Limited expected value at the deductible: for u = 500,000, the arguments are (ln u − μ − σ²)/σ = −1.9395 and (ln u − μ)/σ = −0.4221. Then E[X ∧ 500,000] = 3,000,000 × Φ(−1.9395) + 500,000 × [1 − Φ(−0.4221)] = 3,000,000 × 0.02622 + 500,000 × 0.66351 = $410,418.
  3. Limited expected value at the top of the layer: for u = d + L = 15,500,000, the arguments are 0.3235 and 1.8410, with Φ(0.3235) = 0.62685 and 1 − Φ(1.8410) = 0.03281. Then E[X ∧ 15,500,000] = 3,000,000 × 0.62685 + 15,500,000 × 0.03281 = $2,389,175.
  4. Expected policy payment per claim: E[Y] = 2,389,175 − 410,418 = $1,978,757. Without a limit, the excess over the deductible would be worth 3,000,000 − 410,418 = $2,589,582; the limit cuts 24% of the expected cost because 3.3% of claims exceed $15.5 million.
  5. Pure premium: 0.2 × 1,978,757 = $395,751. The expected number of claims that pay something is 0.2 × P(X > 500,000) = 0.2 × 0.6635 = 0.1327 per year.
  6. Gross rate premium: 395,751 / (1 − 0.35) = $608,848. The probability that the insured has no claim in the year is e−0.2 = 81.9%, and the probability of two or more is 1.75%.
Lesson: for this policy on its own, the 99.5% VaR is exactly the $15 million limit, because the probability of two large claims in the same year is very low. Capital is driven by the portfolio, not the policy, and there accumulation rules: with 50 independent policies the tail diversifies, but a single systemic event with a 2% annual probability is enough for the portfolio VaR to grow far more than the pure premium. You can check it in the calculator.
12

Cyber risk in Mexico

The Ley de Instituciones de Seguros y de Fianzas (LISF, Insurance and Surety Institutions Law) has no cyber line: its article 25 lists the lines within the property and casualty operation (liability and professional risks, fire, miscellaneous, among others), and cyber insurance is structured as a product within that operation, supported, like any product, by a technical note, contractual documentation and a consistency opinion (article 201). Because industry statistics are organized by those lines, cyber-specific information is scarce and hard to compare across companies, unlike auto or medical expense. Whoever builds the technical note depends on the company's own experience, reinsurance and international benchmarks adjusted to the local market.

The data protection framework changed in 2025. On March 20, 2025, a new Ley Federal de Protección de Datos Personales en Posesión de los Particulares (LFPDPPP, Federal Law on the Protection of Personal Data Held by Private Parties) was published in the DOF (Official Gazette), in force from the following day, replacing the 2010 law and transferring the functions of the defunct INAI to the Secretaría Anticorrupción y Buen Gobierno (Ministry of Anti-Corruption and Good Governance). The law requires every data controller to maintain administrative, technical and physical security measures (article 18) and to inform data subjects immediately of security breaches that significantly affect their property or moral rights (article 19). Fines under article 59 range from 100 to 160,000 or from 200 to 320,000 times the UMA (Unidad de Medida y Actualización, the official reference unit) depending on the violation, and may be doubled for sensitive data. These obligations define a large part of the response costs and third-party liability that a policy covers.

Insurers themselves must manage their technology risk. The Circular Única de Seguros y Fianzas (CUSF, Single Insurance and Surety Circular) requires the internal control system to preserve the security of the information generated, received, transmitted, processed or stored in their systems (Provision 3.3.3, section VI) and requires policies for outsourcing services to third parties to maintain the confidentiality and security of information and to provide for continuity plans (Provision 3.6.3). For transactions through electronic means, Chapter 4.10 calls for mechanisms to detect and prevent events that affect the confidentiality, integrity and availability of information, for reporting incidents to the audit committee and for response procedures under the responsibility of the chief executive officer (Provisions 4.10.23 to 4.10.26). No regulator is immune: on January 30, 2026, the CNSF (National Insurance and Surety Commission) itself reported an information security incident that exposed data from intermediaries' license records.

LISF, article 25

Authorized operations and lines. Cyber insurance is sold within the property and casualty operation; its reserves and capital requirement follow the general rules of the line in which it is registered.

LFPDPPP 2025, articles 18, 19 and 59

Security measures, immediate notice of breaches to data subjects and fines in UMA; the authority is the Secretaría Anticorrupción y Buen Gobierno.

CUSF, Provisions 3.3.3 and 3.6.3

Information security in internal control and in outsourcing to third parties, including continuity plans.

CUSF, Chapter 4.10

IT security controls, incident reporting to the audit committee and response procedures for transactions through electronic means.

13

Common mistakes

Pricing as if policies were independent

The pure premium barely changes when an accumulation is introduced, so the error goes unnoticed in the rate and shows up in capital. Measure the portfolio tail with scenarios and a common shock model.

Using a light-tailed severity

A gamma, or a lognormal with a low CV, understates the high layers. Fit the tail with a Pareto above a threshold and check how much of the premium comes from claims you have never observed.

Ignoring the waiting period and sublimits

Business interruption responds to hours, not pesos. In an event lasting a few hours, like CrowdStrike, moving from an 8-hour to a 12-hour waiting period can leave a large part of the portfolio without payment.

Forgetting silent risk

Fire, liability or surety policies that do not mention cyber events may end up paying for them. Inventory those coverages and add them to the accumulation, as NotPetya taught.

14

Frequently asked questions

Why isn't a frequency and severity model with independent policies enough?
Because cyber risk has common causes: a software vulnerability, a cloud provider outage or spreading malware affect many insureds on the same day. Under independence, the law of large numbers dilutes the portfolio tail; with a common shock, the tail grows with portfolio size. The pure premium changes little, but the capital needed changes a lot.
Does a cyber policy cover an attack attributed to a State?
It depends on its exclusion. In the Lloyd's market, since March 31, 2023, stand-alone cyber policies must exclude State-backed attacks with an attribution mechanism, and clauses LMA5564 to LMA5567 offer different levels of coverage for cyber operations that do not amount to war. Outside Lloyd's, wordings vary, so the specific policy must be read.
What is the difference between a deductible and a waiting period?
A deductible subtracts an amount of money from each claim. A waiting period, specific to business interruption, subtracts time: the policy pays only the lost profit that occurs after a certain number of hours of interruption. In a short, widespread event, the waiting period can decide whether the market pays little or a lot.
Why are the lognormal and the Pareto used for severity?
Because cyber claims have heavy tails: most are moderate and a few are enormous. The lognormal describes the body well and has closed-form formulas for layers; the Pareto better describes excesses over a high threshold and, with a shape parameter between 1 and 2, has a finite mean and infinite variance, which calls for caution with sample averages.
What should a company in Mexico do if it suffers a personal data breach?
The 2025 Ley Federal de Protección de Datos Personales en Posesión de los Particulares requires data subjects to be informed immediately when the breach significantly affects their property or moral rights, so they can protect themselves. The competent authority is the Secretaría Anticorrupción y Buen Gobierno (Ministry of Anti-Corruption and Good Governance), which can impose fines of up to 320,000 times the UMA, and up to twice that for sensitive data.
15

Further reading

In December 2024, as part of its Actuarial Monitoring Scheme, the Institute and Faculty of Actuaries published the thematic review Actuaries managing cyber risk, which describes how actuaries take part in managing operational cyber risk and in designing coverages, with examples of collaboration with security specialists. It is useful reading for understanding the professional role beyond the model.

Sources consulted
  1. Munich Re: Global Cyber Risk and Insurance Survey 2026 (2025 market size and 2030 projection)
  2. Business Insurance: Munich Re on ransomware and business interruption in 2024 (April 2025)
  3. Microsoft: Helping our customers through the CrowdStrike outage (July 20, 2024)
  4. Reinsurance News: Guy Carpenter and CyberCube estimates for the CrowdStrike event
  5. Parametrix: CrowdStrike to cost Fortune 500 $5.4 billion
  6. Simpson Thacher: Merck v. ACE, New Jersey appellate court (May 1, 2023)
  7. Insurance Business: Merck settles US$1.4 billion cyber case against insurers
  8. Reinsurance News: Zurich settles NotPetya lawsuit with Mondelez
  9. DAC Beachcroft: LMA publishes updated war and cyber operation exclusions
  10. Lloyd's Market Association: cyber war and cyber operation clauses updated
  11. Artemis: Beazley cyber cat bond (Cairney)
  12. Reinsurance News: AXIS sponsors first ever 144A cyber catastrophe bond (Long Walk Re)
  13. Artemis: Matterhorn Re Ltd. (Series 2023-1), first cyber bond with an industry index trigger
  14. Beazley: Beazley closes $140m cyber catastrophe bond (PoleStar Re)
  15. Howden: Cyber Report 2025, executive summary in Spanish
  16. Ley Federal de Protección de Datos Personales en Posesión de los Particulares, DOF March 20, 2025 (Chamber of Deputies)
  17. EY Mexico: the new Ley Federal de Protección de Datos Personales en Posesión de los Particulares
  18. Ley de Instituciones de Seguros y de Fianzas, current text (Chamber of Deputies)
  19. CUSF, Chapter 3.3: internal control (CNSF)
  20. CUSF, Chapter 3.6: outsourcing of services to third parties (CNSF)
  21. CUSF, Chapter 4.10: use of electronic means (CNSF)
  22. La Razón: the CNSF suffers a security incident (February 2026)
  23. IFoA: Actuaries managing cyber risk, thematic review report (December 2024)
PreviousCatastrophe riskNextHealth and medical costs