Partial degradation trigger threshold
The gap between a policy or service contract that only pays out on total outage and the reality of modern incidents, which are often a performance degradation rather than a complete service interruption.
The partial degradation trigger threshold refers to the difficulty in matching the clauses of a service contract or business interruption policy, historically built around the binary notion of total outage, to the reality of modern IT incidents, which most often show up as a performance degradation, abnormal latency or intermittent errors rather than a complete and clearly observable service stoppage. The difference is not merely semantic: a service that answers only one request in three, or answers correctly but ten times slower than usual, can interrupt a client's business just as much as a total outage without triggering a contract clause written around complete unavailability. For insurers and cloud providers alike, the challenge is to define a measurable, objective threshold, an error rate, response time or percentage of failed requests, precise enough to avoid disputes over what actually counts as a compensable outage. This gray zone structurally favors the provider or insurer, since the absence of a clear threshold shifts the burden of proving damage onto the client, who is often ill-equipped to demonstrate a diffuse degradation rather than a clean stoppage.
On July 2, 2019, a faulty regular expression in one of Cloudflare's web application firewall rules exhausted the processors across its global network for twenty-seven minutes, severely degrading millions of client sites without producing a total stoppage that every standard monitoring tool would register.
Follow the research
One letter a week. First, the week's underwriting note, when one is published: a dated, argued decision, signed by Paul Bernardski. Then what the observatory published on cyber risk, political risk and insurance. No account, no tracking.
No spam, one-click unsubscribe, no data ever sold.