Workshop Description
Policy administration platforms such as Guidewire PolicyCenter, Duck Creek, and Majesco use TLS 1.2/1.3 for API communication, RSA or ECDSA certificates for digital signatures on policy documents, and AES-256 for data at rest. Claims processing adds payment rail encryption (PCI DSS scope), FNOL intake channel security, and adjudication workflow signing. Every one of these cryptographic touchpoints requires assessment and migration planning under the NIST post-quantum standards finalised in 2024.
The challenge specific to insurance is operational continuity. Policy administration systems typically run on 12-to-18-month release cycles. Claims platforms integrate with dozens of external parties (loss adjusters, repair networks, medical providers, payment processors) whose own PQC readiness varies. A migration plan that ignores these constraints will fail. This workshop builds a Cryptographic Bill of Materials (CBOM) for each participant's environment, sequences migration by regulatory priority (EIOPA/PRA submission channels first, then payment rails, then internal systems), and addresses the hybrid deployment patterns needed for backward compatibility during transition.
What participants cover
- NIST FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), FIPS 205 (SLH-DSA), and draft FIPS 206 (FN-DSA): algorithm characteristics, key sizes, and performance trade-offs for insurance workloads
- CBOM methodology applied to insurance software stacks: policy administration, claims processing, bordereaux exchange, and regulatory reporting
- Solvency II Pillar 2 ORSA integration: incorporating quantum cryptographic risk into Own Risk and Solvency Assessment
- PRA SS2/21 operational resilience: classifying cryptographic dependencies as important business services
- Lloyd's Market Bulletin Y5381: cyber risk governance expectations and cryptographic upgrade planning
- Hybrid deployment patterns (ML-KEM + X25519, ML-DSA + ECDSA) for systems that must maintain backward compatibility during migration