Quantum-safe insurance, for data that outlives the policy

Life, health and liability files have to stay confidential for decades, far longer than the encryption protecting them today. We find every use of quantum-vulnerable cryptography across policy, claims and partner systems, and plan its replacement around your longest-lived data first.

EU date for moving high-risk use cases
End-2030 EU date for moving high-risk use cases
DORA has applied to insurers and reinsurers
Since 2025 DORA has applied to insurers and reinsurers
how long life and health files can stay sensitive
Decades how long life and health files can stay sensitive

Why it matters now

Looking up through a clear umbrella covered in rain drops
01

The longest-lived data in finance

Life policies, medical underwriting and claims files stay sensitive for decades. Anything sent today under RSA or elliptic curves can be recorded now and read later.

02

Signatures that have to last

Contracts and consents signed electronically must stay verifiable for the life of the policy. That needs a plan for long-term validation with quantum-safe algorithms.

03

A wide partner network

Brokers, agents, bancassurance partners, reinsurers and healthcare providers exchange data through portals, APIs and file transfers, each with its own cryptography.

04

Supervisors expect a plan

DORA applies to insurers and reinsurers, GDPR asks for state-of-the-art protection of health data, and the EU roadmap dates high-risk systems for 2030.

Where the cryptography sits at an insurer

Each card is a system we inventory. Its coloured edge shows how exposed its cryptography is.

CUSTOMERS AND DISTRIBUTION CORE PLATFORMS PARTNERS Customer portal and app TLS 1.3 · OAuth/OIDC Brokers and agents TLS · SAML SSO Staff and service centre VPN · Kerberos Web and API edge mTLS · JWS Claims platform TLS · AES-256 Identity and PKI PKI · LDAPS Policy administration TLS · TDE Document archive ande-signatures PAdES (RSA/ECDSA) · RFC 3161 Health and medical data TLS · AES-256 Bancassurance and payments mTLS · OAuth 2.0 Reinsurers SFTP · PGP · AS2 Hospitals and providers TLS · IPsec HNDL HNDL HNDL
Public-key cryptography a quantum computer breaks Symmetric keys or legacy algorithms to check HNDLTraffic worth recording today to read later Illustrative, a typical estate rather than a client’s.

What you receive

  • A CBOM of the whole insurer, in CycloneDX 1.7
  • Risk-ranked findings weighted by data shelf life
  • A tailored migration roadmap with dates and owners
  • A readiness list for partners, reinsurers and vendors
  • Evidence for supervisors and auditors

An actionable plan, not a list of intentions

Every action in the roadmap says what to change, why - the finding behind it - who owns it, how long it takes and in which quarter. Opened up, it adds the steps, what it waits on, how done is proven and which rule it serves.

Migration roadmap Insurance · Q1–Q4 2027
Estimated completion
Q4 2028
Actions this year
12
Open work
38engineer-weeks
HNDL links still open
2
PreparationBaseline understandingPlanning and executionMonitoring and evaluation
Q1 2027 9 wk
A-01 Done

Name a migration owner and adopt a cryptography policy

No owner for cryptographic change

CISO · 2 wk

A-02 In progress

Classify data by shelf life: life, health, claims

Life and health files kept 30+ years

Data protection · 3 wk

A-03

Complete the CBOM across portals, policy, claims and archives

4 platforms not yet scanned

Platform team · 4 wk

Q2 2027 10 wk
A-04 HNDL

Hybrid TLS on the customer and broker portals

F-006 · ECDHE only on portals and broker APIs

Network team · 5 wk

A-05

Retire TLS 1.0 on legacy broker interfaces

F-015 · 6 interfaces on TLS 1.0

Platform team · 2 wk

A-06 Vendor

Get PQC dates from reinsurers and partners

RSA and PGP on 23 partner exchanges

Procurement · 3 wk

Q3 2027 14 wk
A-07 HNDLVendor

Hybrid key exchange on reinsurer file transfers

F-012 · SFTP with classical key exchange to 6 reinsurers

Network team · 6 wk

A-08

Plan long-term validation for e-signed contracts

Signatures must verify for the life of the policy

Legal and PKI · 4 wk

A-09

AES-256 and re-wrapped keys for health data

F-019 · 128-bit keys on medical files

Data platform · 4 wk

Q4 2027 7 wk
A-10

Pilot ML-DSA token signing on the identity provider

RS256 tokens on every portal

Identity team · 4 wk

A-11

Re-scan and update the CBOM

Confirm the Q2–Q3 changes

CISO · 1 wk

A-12

Evidence pack for supervisors and auditors

DORA review cycle

Compliance · 2 wk

A-07

Hybrid key exchange on reinsurer file transfers

Network team · 6 engineer-weeks · Q3 2027

HNDLVendor

Why

F-012 · SFTP to 6 reinsurers uses classical key exchange only. The files carry claims and medical data kept for 30+ years (HNDL).

Steps

  1. Upgrade the SFTP servers to OpenSSH 10, which offers mlkem768x25519-sha256
  2. Agree a switch date with each reinsurer
  3. Move the IPsec tunnels to hybrid IKEv2 (RFC 9370)
  4. Re-scan both ends of every exchange
Waits on
Each reinsurer’s SSH and VPN support
Done when
All 6 exchanges negotiate hybrid key exchange, and every partner date is recorded
Serves
DORA ICT third-party risk · GDPR Art. 32
Illustrative: actions, findings and figures are invented for this page, in the format the platform produces.

Start with the data that has to last longest