PatientLock
Research & white papers
PatientLock Research · 2026 Edition

Cyber Portfolio Concentration Beyond Industry Codes

Cyber accumulation is driven by shared technology and correlated failure paths as well as industry and geography. Reinsurance portfolio analysis improves when common dependencies can be observed beneath the insured and carrier hierarchy.

Paper context

Author
PatientLock Research
Edition
2026
Audience
Reinsurance accumulation teams, treaty underwriters, carrier portfolio managers, and cyber modelers
Sections
5

Central argument

Cyber concentration is driven by shared digital dependencies as well as industry and geography. Portfolio analysis improves when common providers, technologies, and failure paths are visible beneath the insured hierarchy.

Definitions

Terms used in this paper

These definitions establish how the paper uses its core terms before the argument begins.

Portfolio concentration
Exposure clustering that can produce correlated loss across multiple insureds or policies.
Shared dependency
A provider, platform, software component, service, or failure mode common to multiple insureds.
Dependency confidence
The degree to which shared-dependency data is directly observed, reported, inferred, or unknown.
Scenario exposure
The portion of a portfolio potentially affected under a defined systemic cyber event.
01

1. Cyber concentration does not respect traditional segmentation

Industry codes and geography remain useful portfolio dimensions, but digital dependencies can connect organizations that otherwise appear unrelated. Two insureds in different sectors may depend on the same cloud platform, identity provider, managed service provider, payment processor, or widely deployed software component.

That creates a cyber accumulation problem: one event can generate correlated loss across policies that a traditional segmentation view might treat as diversified. Reinsurers therefore need a view of shared dependencies in addition to conventional portfolio dimensions.

Different sectors can share the same failure path.
Traditional segmentation
Industry and geography describe useful business categories, but may suggest separation between digitally connected risks.
Dependency view
Shared cloud, identity, software, or service providers can connect those risks through a common cyber event.

Use both views. Known, inferred, and missing dependency information should remain distinguishable.

02

2. Dependency data is incomplete by nature

No insurer has a perfect map of every technology dependency across every insured. Vendor inventories change, fourth parties are opaque, SaaS dependencies are layered, and many relationships are not material enough to justify deep collection.

The analytical goal should therefore be graded confidence rather than false completeness. A reinsurer can identify known shared dependencies, distinguish observed data from inferred or reported data, and show where concentration estimates are limited by missing information.

03

3. Control state changes the meaning of a shared dependency

Two insureds can rely on the same technology while presenting different loss pathways. One may have strong segmentation, tested recovery, constrained administrative access, and current evidence. Another may have broad dependency and weak recovery controls.

Accumulation analysis becomes richer when the shared dependency is combined with operational state rather than treated as a binary yes-or-no attribute. That does not turn operational telemetry into a catastrophe model; it provides additional explanatory variables for scenario design and portfolio review.

04

4. Scenario analysis should preserve the event definition

A cloud outage, ransomware campaign, software supply-chain compromise, and identity-provider disruption have different propagation mechanisms. Reinsurance scenarios should state the event being modeled, affected dependencies, duration assumptions, loss pathways, and policy response assumptions.

Operational evidence can then help identify which insureds appear exposed and which resilience controls may affect severity. The catastrophe or accumulation model remains responsible for translating the scenario into loss estimates.

05

5. Better dependency visibility improves questions before it improves answers

The near-term value of richer portfolio evidence may be better inquiry rather than a perfect accumulation number. Reinsurers can identify where an apparently diversified book contains a common dependency, where evidence quality is low, and where a material change deserves deeper review.

That helps treaty underwriters and accumulation teams prioritize investigation and design more realistic stress scenarios without pretending the underlying data is complete.

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.

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.

  1. 01VitalSec research — Cyber Accumulation and Evidence Quality in Reinsurance
  2. 02VitalSec for Reinsurance