Versatile AI Risk Assessment
Banking and insurance

Life and health insurance risk assessment and pricing

Also known as: AI-based underwriting and pricing in life and health insurance

Insurers estimate an applicant's mortality or illness risk to determine whether to accept them and what premium to charge.

Explore the interactive model

Export handout

A concise PDF covering how the system works, its data flows and points to investigate, ready to share.

The explanations and measures describe the typical system design. Extensive personal changes add an appendix.

Understand the use case

What defines this use case?

Before policy inception, the model analyses health information, laboratory values and other details and assigns a risk class. US life insurer MassMutual uses such a model. BaFin states that German insurers have so far rarely used AI for this purpose.

This page describes a typical system design. Actual data flows and permissions depend on your implementation.

System design
Analysis and processing
Ability to act
Action permissions depend on integration
Fields of use
insurance
Also known as
underwriting, risk assessment, pricing

How it works, step by step

System design and data flows

  1. Input data

    Health answers, laboratory values, findings, occupation and circumstances arrive with the application.

    Applicants answer health questions themselves; clinicians and laboratories provide findings. The system assesses a specific person's age, occupation and circumstances.

  2. Processing

    The model estimates the person's mortality or illness risk.

    The model processes permitted application and risk characteristics to provide an assessment for insurance underwriting. Rating rules turn this assessment into a proposal. Acceptance, exclusions and pricing take place in the subsequent insurance process.

  3. Results

    The model recommends a risk class and thus acceptance, a surcharge, exclusions or rejection.

    The result describes the defined model task. A match, category or forecast acquires its professional significance only in conjunction with the underlying data and intended use.

  4. Use and impact

    The recommendation determines whether the person is insured and the premium paid throughout the policy term.

    Integration determines whether the result is simply displayed, adopted after approval or written directly into a business application. These variants differ in their data flows and permissions.

Explore the system design: Select a component to see its task, incoming and outgoing data, and role in the use case. The guided walkthrough explains each phase. Then use Yes, Uncertain and No to represent your specific system variant.

How the system is built

9 review first9 clarify6 baseline threats

InputProcessingResultImpact Externalaccess 04 Input 40 Third-partycontent 00 AI model 11 Providerservice 02 Documentcollection 00 Memory 00 Training andfeedback 30 OtherAI agents 00 Tools andinterfaces 00 Result 00 Business appor equipment 01 person 10 Affectedperson 00 AI serviceswithout approval 01 Externalaccess 04 Input 40 Third-partycontent 00 AI model 11 Providerservice 02 Documentcollection 00 Memory 00 Training andfeedback 30 OtherAI agents 00 Tools andinterfaces 00 Result 00 Business appor equipment 01 person 10 Affectedperson 00 AI serviceswithout approval 01
  • Present
  • Depends on your system
  • Absent
  • Review first
  • To clarify

In this system design: 9 to review first, 9 to clarify, 6 baseline threats.

Architecture as a list

How it differs from similar use cases

Data and information

Input data and information sources

Applicants answer health questions themselves; clinicians and laboratories provide findings. The system assesses a specific person's age, occupation and circumstances.

Processing and operating environment

Reinsurers and vendors supply underwriting models adopted by primary insurers.

Storage and further use

Insurers train these models on their own application and claims data. Claims under issued policies can feed into later model versions, often only years later.

Results and data sharing

Some insurers accept favourable scores without further review; others send every recommendation to underwriters.

Using a provider does not automatically determine where processing takes place. Storage location, subcontractors, deletion periods and use for training must be checked for the specific deployment.

Assess risks and determine measures

From understanding the system to analysing risks

  1. Define the system boundary

    Record data, participants, interfaces and permissions. Resolve uncertain characteristics in the model.

  2. Investigate threats

    Relate review candidates to actual data flows: what could happen, and who would be affected?

  3. Assess risk

    Assess impacts and likelihood in the deployment context. The number of review candidates is not a risk score.

  4. Provide evidence of measures

    Select appropriate controls, assign responsibilities and define effectiveness checks. Document residual risks and approvals.

Key threats in the application context

  • 4 particularly important
  • 5 typical
  • 9 depending on the system
  • 6 additional threats for every AI system

A total of 24 threats from the threat catalogue may be relevant to this use case.

Also review: whether the system disadvantages groups

Check whether selection, ranking or assessment disadvantages people with protected characteristics, such as sex, age or origin.

Priority review points

  1. Overreliance

    Underwriters may accept an unfavourable risk class without reviewing health information. The person then receives a surcharge or rejection based only on an estimate.

  2. Model Drift & Degradation

    The model knows earlier cohorts' mortality and illness patterns. Better treatment or a changed applicant population makes risk classes inaccurate.

  3. Privacy Attacks

    The model learned from many people's health data. Repeated queries can reveal whether a specific person or condition appeared in training.

  4. Adversarial Inputs

    Someone who knows which details worsen risk classes can deliberately alter health answers. The system then recommends different policy terms than accurate answers would produce.

5 further review candidates in the typical design

Other relevant threats

  1. Training Data Poisoning

    Your own training or operational feedback can introduce manipulated data into training datasets.

    Listed because of this characteristic

    • Learns from your own data
  2. Targeted Poisoning / Label Poisoning

    Falsified training labels can deliberately shift model outputs.

    Listed because of this characteristic

    • Learns from examples with correct answers
  3. Backdoor ML Model

    Training data or an adopted base model can introduce hidden triggers for misbehaviour.

    Listed because of this characteristic

    • Learns from your own data
  4. Sensitive Information Disclosure

    Confidential content can appear in answers, supplied context or logs.

    Listed because of these characteristics

    • Processes personal data
    • Processes confidential data
  5. Exfiltration from ML Application

    Protected data can leak through tools, network connections, storage or insiders.

    Listed because of this characteristic

    • Processes confidential data

Up to 9 further threats may apply, depending on your system design. Nine threats need to be reviewed for every AI system. Three of these are particularly important here and are therefore listed above.

System features and open questions

Each Yes adds further threats to your checklist, up to 9 in total. If you cannot yet answer a question, include its threats in your review.

How many threats a Yes adds
  • Added by this Yes

How your system is built

  1. Changes data or triggers processes1 threat
  2. Optimises a specified metric1 threat

How your system is built

Can the system change things itself, such as storing data, sending messages, initiating transactions or granting permissions?

Some insurers accept favourable scores without further review; others send every recommendation to underwriters.

If yes, add

Is the system intended to maximise a specified metric, such as revenue, utilisation or clicks?

An insurer setting thresholds by acceptance rate or expected claims costs directs the system towards a business objective.

If yes, add

How you operate the system

These questions arise for almost every AI system.

Controls and implementation

Measures for the priority review areas are expanded. Each linked measure explains how to implement it.

Controls for the remaining threats are available on their pages in the threat catalogue.

AI Act provisions

When AI Act provisions apply
  1. Art. 4: AI literacy

    For every AI system Applies since 2 February 2025.

  2. Annex III no. 5 point c: Life and health insurance

    In typical use Review trigger from 2 December 2027.

Applies to every AI system

Art. 4: AI literacy

Applies if staff or appointed representatives operate or use AI systems.

Applies since 2 February 2025.

Obligations and details for Art. 4: AI literacy
Who bears the obligations
Provider, Deployer, Product manufacturer, Provider of a general-purpose AI model

Detailed obligations

May apply in typical use

Annex III no. 5 point c: Life and health insurance

Applies if the system assesses risk or sets prices for a natural person, for example for term life or private health insurance.

Applies from 2 December 2027.

Obligations and details for Annex III no. 5 point c: Life and health insurance
The general condition is
Applies if the system assesses risk or sets prices for people's life or health insurance.
Who bears the obligations
Provider, Deployer, Product manufacturer

Detailed obligations

Classify your system with the quick checker All obligations in the obligations compass

Cross-cutting threats

Review these threats for every AI system, whatever its purpose.

Why these threats always belong on the checklist

Atypical system features

View 16 further questions

If any of these features does apply to your system, add the listed threats.

Sources

Related use cases

Also in the field of Banking and insurance

Often used together with

Updated: 30 September 2026. Review checklist rules version 0.3.2, threat catalogue version 2026.10.24.2. How these pages are structured