Definitions
Terms used in this paper
These definitions establish how the paper uses its core terms before the argument begins.
- Accumulation risk
- The possibility that one event or correlated set of events produces losses across many policies or insureds at the same time.
- Systemic dependency
- A shared technology, service, provider, or failure mode that can create correlated impact across otherwise separate insureds.
- Treaty
- Reinsurance covering a defined portfolio or class of business under agreed terms rather than a single individually negotiated risk.
- Facultative reinsurance
- Reinsurance negotiated for a specific individual risk rather than an entire treaty portfolio.
1. Individual scores do not explain portfolio accumulation
A reinsurer can hold a book in which every individual insured appears acceptable and still face material accumulation risk. The reason is dependency. Multiple insureds may rely on the same cloud provider, identity platform, remote-access product, managed service provider, software supply chain, or other shared technology.
Accumulation risk is therefore not the arithmetic sum of individual cyber scores. It is the possibility that one event or correlated set of events produces loss across many policies at once. Reinsurance analysis has to ask which dependencies can couple otherwise separate risks.
2. Evidence quality affects what the portfolio view means
A portfolio distribution is only as useful as the evidence underneath it. If one insured is represented by current technical observations and another by a twelve-month-old questionnaire, the apparent comparability can be misleading.
Evidence quality should therefore be visible alongside any aggregate cyber view. Freshness, source coverage, unresolved unknowns, and evidence continuity help a reinsurer distinguish a genuinely observed portfolio pattern from a pattern created by uneven reporting.
Aggregate insight should carry aggregate uncertainty. A clean chart is not a substitute for knowing how well the underlying risks are observed.
4. Treaty and facultative views ask different questions
Treaty reinsurance covers a defined portfolio or class of business under agreed terms. Facultative reinsurance is negotiated for an individual risk. The evidence needed to support those decisions can overlap, but the unit of analysis is different.
At treaty level, concentration and dependency patterns dominate. At facultative level, a reinsurer may need deeper evidence about the individual insured's controls, exposures, and change history. A common evidence architecture can support both views without pretending they are the same underwriting problem.
5. Operational evidence should improve catastrophe modeling without becoming the model
Operational telemetry should give catastrophe and accumulation models better observations about the underlying book while model ownership, assumptions, event definitions, and uncertainty remain explicit.
That separation creates a disciplined way to test whether evidence quality, shared dependencies, and measured changes explain later portfolio outcomes. The goal is better inputs and clearer uncertainty, not forcing an operational security measure to behave like a catastrophe-loss distribution.
Evidence base
Sources and notes
External foundations are kept distinct from VitalSec implementation notes so readers can see what supports the argument independently and what documents the platform implementation.
External foundations and sources
VitalSec implementation notes
These links document how the argument is implemented or described inside VitalSec. They are not offered as independent validation of the paper's thesis.
