SolutionsInsurance
AI security and governance built for insurers.
Govern the AI in underwriting and claims, keep policyholder data out of prompts and show auditors evidence graded by how it was obtained.
Policyholder data · at the gateway: claims-bot held for a person before ColossalX (payout); underwriter to ColossalX; service-bot refused before ColossalX (injection); ColossalX with data redacted, to provider A (health ID redacted).
In short
AI governance for insurers, in ColossalX, means one owned inventory of the models, agents and AI vendors in underwriting, claims and service, policyholder data redacted from prompts and answers, an owner and a second approver before an agent is admitted, IRDAI cyber circulars mapped beside India DPDP, and evidence graded by how it was obtained.
DSCI and BCG found that AI-specific controls such as formal AI governance, agent monitoring and runtime guardrails are
still being built across the sector.
The context
Why insurers are looking hard at AI now.
BFSI is attacked more often, financial services pay the most for a breach, and AI controls are still being built.
1.6 times
INR 40.9 crore
58%
Insurance
Where AI meets policyholder data, and what holds it.
Four places where AI meets policyholder data, each held by a control.
Nobody can say which policyholder data reached which outside model.
The controlLineage from gateway traffic shows which agent sent which kinds of personal data to which model.
A claims agent approves a payout with nobody looking.
The controlA risky tool call waits for a named person; if the check cannot run, it waits.
An underwriting agent goes live before anyone owns or reviews it.
The controlRegistered is not approved: an owner, a second approver and guardrails come first.
Third-party AI vendors are in use, but nobody assessed them.
The controlThe AI vendor inventory flags each vendor in use but not assessed.
Regulators and frameworks
What regulators ask for, and how ColossalX relates.
Mapped frameworks, what each asks of an insurer, and the dates that matter.
Mapped to
- IRDAI cyber circularsIRDAI cyber circularsInformation and cyber security governance, controls and incident reporting for insurers.
- India DPDPIndia DPDPConsent and purpose limits for personal data, with consent managers.
- EU AI ActEU AI ActFor insurers serving the EU: life and health pricing AI is high-risk.
- ISO/IEC 42001ISO/IEC 42001An AI management system: policy, roles, risk and controls.
- NIST AI RMFNIST AI RMFGovern, map, measure and manage AI risk across its life.
- GDPRGDPRLawful basis, purpose limits and rights for EU personal data.
Regulatory clock: 13 Nov 2026 India DPDP consent manager rules start (PIB, DPDP Rules 2025); 13 May 2027 India DPDP core obligations start (PIB, DPDP Rules 2025); 2 Dec 2027 EU AI Act Annex III high-risk obligations apply (Gibson Dunn).
What you see
What you see, and what you can show an auditor.
An agent caught calling through the gateway before anyone owned it, beside the evidence pack an auditor can check.
An illustrative agent dossier for a claims triage agent found in gateway traffic: its own identity and trust zone, an admission checklist with a guardrail profile, an accountable owner and a second approver, and the controls to suspend, quarantine or kill it.
Evidence pack · an outline: Inventory Models, agents and vendors, owned; Admission Owner and second approver, recorded; Runtime Redactions, refusals, approval holds; Audit A sealed, timestamped archive. Graded A to D.
What the evidence pack shows4
- Which agents run in underwriting and claims, who owns each, and how each one entered the inventory.
- Each redaction, refusal and approval hold, with the policy that made it.
- AI vendors in use but not assessed, carried into the risk register as owned work.
- Evidence graded A to D by how it was obtained, verified by a second person.
Honest by design
What we will not tell you.
Admission · monitor, then enforce: Day 0 Agent seen in traffic (not yet registered); Day 0 Time-boxed exception (monitor mode, still serving); Day 30 Exception expires (owner and approver needed).
x, not measured
Monitor-then-enforce rollouts let an unadmitted agent keep serving under a time-boxed exception.
All 4 limits
- Redaction finds the identifiers its presets and your own patterns describe, not ones nobody defined.
- Jurisdiction-pack content is a starting point for your counsel to review, not legal advice.
- ColossalX holds no certification and is delivered as SaaS only.
Questions
Questions buyers ask
How should insurers govern AI used in underwriting and claims?
Start with an inventory of the models, agents and AI vendors used in underwriting and claims, with an owner for each. Then control what they do with policyholder data, hold high-impact actions such as payouts for a named person, test the defences and keep the evidence. ColossalX covers each step, from inventory to graded evidence.
Does ColossalX map the IRDAI cyber circulars?
Yes. ColossalX maps its controls to the IRDAI cyber circulars alongside India DPDP, ISO/IEC 42001, NIST AI RMF, the EU AI Act, SOC 2 and GDPR, and assesses them from live signals. Frameworks are mapped to and assessed against, never certified; ColossalX holds no certification of its own, and jurisdiction-pack content is a starting point for your counsel.
How is policyholder data protected in AI prompts?
Guardrails at the AI gateway detect personal data in prompts and answers and redact it, using presets for India DPDP, EU GDPR, US HIPAA, PCI DSS and others, plus your own identifiers such as policy numbers. Data lineage then shows which agent sent which kinds of personal data to which model.
How do we prove AI controls to auditors?
Hand them evidence that collects itself from runtime signals, graded A to D by how it was obtained, verified by a second person and timestamped daily. Withdrawn evidence is kept, not deleted, and an audit runs from a risk-based plan to a sealed, timestamped archive, with findings carried into the risk register.
Can we track third-party AI vendors that are in use but not assessed?
Yes. The AI vendor inventory in the risk register flags vendors that are in use but not assessed, and findings about them become owned work. Threat intelligence matched to your vendors and models turns a warning about a model into a recorded decision, which can become a restriction at the gateway.
Next step
Know your x, claim by claim.
See ColossalX on an insurer's questions: which AI touches policyholder data, and what you can show an auditor.
- 01Tell us what you run
- 02See the four verbs on it
- 03Decide where to start