Insurance & asset management | Modelled case study
Measure cryptographic concentration across an insurer's SaaS estate
Which critical business processes depend on the same certificate authority, cloud KMS, identity provider, or unsupported algorithm?
The modelled organisation
A recognisable problem reaches the operating agenda
This composite scenario follows the Third-Party Risk · Enterprise Architecture · Procurement functions. It is grounded in the cited problem context but does not identify a real customer.
Operating environment
An insurer or asset manager retains long-life policy, claims, portfolio, and customer records while relying on administrators, SaaS providers, brokers, and external evidence sources.
What is at stake
The organisation must preserve confidentiality and evidential integrity across decades without losing claims continuity, regulatory accountability, or vendor portability.
Situation
Vendor reviews happen contract by contract, obscuring shared cryptographic dependencies that can fail across underwriting, claims, finance, and customer service together.
Event that forces action
DORA register preparation, a strategic-provider review, or an outage with cross-vendor impact.
Concrete system boundary
Systems this case study puts in scope
The model is specific about the operational surfaces that must be discovered, changed, or independently checked.
critical SaaS applications
shared cloud KMS providers
identity and certificate authorities
vendor exit and data-export paths
Modelled case study walkthrough
How this organisation would use QNSI
The walkthrough connects the real-world problem to a bounded QNSI contribution and an independently reviewable result.
Recognise the operating condition
Vendor reviews happen contract by contract, obscuring shared cryptographic dependencies that can fail across underwriting, claims, finance, and customer service together.
Frame the decision the owners must make
Which critical business processes depend on the same certificate authority, cloud KMS, identity provider, or unsupported algorithm?
Apply QNSI to the controlled boundary
Normalize vendor crypto dependencies, key-custody claims, assurance status, and service ownership in a QNSI-backed inventory.
Leave the team with a concrete result
A concentration heat map linking cryptographic providers to critical insurance processes and exit constraints.
Prove the result in the organisation's environment
Procurement verifies vendor evidence, contractual audit rights, substitutability, data export, and tested exit plans.
What useful success looks like
A decision artifact plus proof from the real environment
The model stops at a target result. It becomes an actual case study only when a customer produces and independently validates this evidence in production.
Decision artifact
A concentration heat map linking cryptographic providers to critical insurance processes and exit constraints.
Independent validation boundary
Procurement verifies vendor evidence, contractual audit rights, substitutability, data export, and tested exit plans.
Real-world problem grounding
Primary sources behind the model
These sources establish the external requirement, failure mode, or risk context used to model this case. They do not endorse HEOSSI or prove that QNSI completed the scenario.
Customer evidence status
This is modelled, not a customer claim
The organisation is a composite and the result is a target state. This page does not prove a deployment, customer outcome, certification, legal conclusion, regulator endorsement, or completed control.