IndustryInsuranceIRDAI

Post-quantum readiness for insurers in India

IRDAI has not set a post-quantum deadline, but since April 2026 its cyber security audit asks whether insurers keep an up-to-date cryptographic inventory to prepare for post-quantum cryptography. Because policy and health records stay sensitive for decades, insurers have more reason than most to start now.

7 min readReviewed 8 November 20263 sources

Insurers hold some of the longest-lived personal data in the economy. A life policy can run for decades, and health and claims records stay sensitive for as long as the person is alive. Data like this is what "harvest now, decrypt later" attackers want: they record encrypted traffic or copy encrypted archives today and wait for a quantum computer able to break the public-key cryptography that protects it. This page sets out what IRDAI now asks for, where the cryptography sits in an insurer, and what to do in the next two quarters.

What your regulators expect

STATUS AT 8 NOV 2026

IRDAI has not issued a PQC migration mandate or deadline. Since April 2026, however, its cyber security audit asks whether you keep an up-to-date cryptographic inventory to prepare for post-quantum cryptography (PQC). That makes the inventory an audit question now, not a future one.

IRDAI Information and Cyber Security Guidelines, 2026 (6 April 2026)

On 6 April 2026 IRDAI issued revised guidelines (circular IRDAI/GA&HR/CIR/MISC/51/4/2026). They revise the guidelines issued on 24 April 2023 and "set out the minimum standards and governance mechanisms to be adopted by all Regulated Entities"[1]. The circular says all of the following "shall strictly adhere" to the guidelines from the current financial year:

  • insurers, including foreign reinsurance branches;
  • brokers and corporate agents;
  • web aggregators;
  • TPAs (third-party administrators);
  • insurance marketing firms and insurance repositories;
  • insurance self-network platforms (ISNPs) and corporate surveyors;
  • motor insurance service providers (MISPs) and common service centres (CSCs);
  • the Insurance Information Bureau of India.

Three parts are directly relevant to post-quantum readiness.

  • A new crypto-inventory audit control. IRDAI's summary of changes (Annexure A) lists a new control in the auditor's report. The Asset Management (ID.AM) section of the Annexure III questionnaire now asks: "Does the organization maintain an up-to-date inventory of its cryptographic assets to ensure preparedness for transition to post-quantum cryptographic environments?" The guidelines require an independent assurance audit every year[1].
  • Cryptographic Controls policy (§2.12). This section covers cryptography for data in transit and at rest. It requires a risk assessment of where encryption is used and a key-management policy covering keys "through their whole lifecycle". It says the type and strength of algorithms "shall be based on the criticality of the business information handled", and that key lengths "shall comply with contractual requirements and regulations laid down by competent authorities"[1].
  • Supply-chain controls (ID.SC). The audit asks whether vendors follow the insurer's cyber security policy, whether third parties are assessed periodically, and whether contracts (SLAs) require prior written permission before a provider outsources further. It also asks whether cloud providers are MeitY-empanelled with a valid STQC audit status[1].

The new control asks whether an inventory exists and is kept current. It does not set algorithms, a CBOM (cryptographic bill of materials) format or a migration date. The guidelines also have no quantum-specific requirement beyond this question.

DST / National Quantum Mission roadmap (May 2026). This is advisory.

The DST task-force report includes Banking, Financial Services and Insurance (BFSI) among the critical information infrastructure (CII) sectors on accelerated timelines[2]:

  • foundations by 31 December 2027;
  • high-priority systems migrated by 31 December 2028;
  • full PQC adoption by 31 December 2029.

It also says that "any network handling data with a long shelf life or extended confidentiality requirements shall be prioritised". It names personal health data and financial records as information that "must remain secure for long periods". The report calls its testing framework "a guiding document for the sectoral regulators", IRDAI among them. It advises asking vendors for CBOMs from FY 2026–27 and making them mandatory from FY 2027–28. None of this is an IRDAI requirement unless IRDAI adopts it.

CERT-In v2.0 (9 July 2025). This is technical guidance.

CERT-In's Technical Guidelines on SBOM, QBOM & CBOM, AIBOM and HBOM say organisations "must maintain an accurate and up-to-date CBOM/QBOM" for cryptographic systems they use, develop or procure (§8.4.1.3). They also recommend tiered PQC terms in vendor contracts (§8.5.4)[3]. For an insurer, this is the most detailed public description of what a cryptographic inventory should contain. That makes it a practical template for answering IRDAI's audit question.

Where the cryptography sits in an insurer

The table below shows typical patterns, not findings about any particular insurer. Rank them by how long the data must stay confidential, not only by system criticality.

SystemCryptography typically in useWhy it matters for quantum migrationPriority
Health claims and TPA linksMutual TLS APIs, SFTP, file encryption with public keys, VPNs to TPAsHealth and claims data stays sensitive for decades, which makes it a prime harvest-now target; it crosses organisational boundariesP0: longest shelf life, many parties
Data sharing with hospitals (cashless)TLS portals and APIs, site-to-site VPNs, emailed or uploaded documentsClinical documents travel over links you do not fully controlP0: inventory every link and owner
Agent, broker and aggregator portalsTLS with RSA or ECDSA certificates, signed SSO tokens, API keysInternet-facing; many partners are themselves IRDAI-regulated and audited on a subset of the same controls, depending on their access to your systemsP0: public exposure
Customer portals and mobile appsTLS, certificate pinning, app code signing, e-KYC integrationsRecorded sessions expose identity and policy data; pinned certificates make rotation slowP0 for TLS; P1 for signing
Policy administration and core insurance platformTLS between tiers, database and backup encryption, service certificates, vendor librariesHolds the long-lived policy record; mostly vendor code, so you need the vendor's CBOMP1: drive through vendor CBOMs
Digitally signed policy documentsRSA or ECDSA signatures and certificatesA signed policy may need to verify for its whole term; plan for re-signing or archive timestampingP1: long validity
Payment gateways and premium collectionTLS to the gateway, signed callbacks, tokenisationMostly provider-managed; your migration follows the provider's roadmapP1: ask providers for dated plans
Corporate network and remote accessIPsec or TLS VPNs, client certificates for devicesThe guidelines require client certificates for hardware joining the trusted network; those are public-key credentialsP1: often tied to appliance refresh
Backups and archivesAES, with keys often wrapped under RSA in a key managerArchives outlive systems; AES-256 holds up, but RSA key wrapping does notP2: check key wrapping and AES-128 use
Figure 1 · Typical cryptographic exposure in an Indian insurer. Source: KavachQ analysis; IRDAI Information and Cyber Security Guidelines 2026, §2.12 and asset-management controls[1]; DST task-force report on long-shelf-life data[2].

Where to start

  1. Prepare evidence for the new audit question. Your next IRDAI audit can ask about a cryptographic inventory, so build one in a structured format rather than a spreadsheet of certificates. Start with a free public TLS scan of customer, agent and partner domains. Then follow how to find weak cryptography and the CBOM guide.
  2. Rank data by shelf life. Health, claims and life-policy data usually come first. The Mosca inequality and harvest-now-decrypt-later explainers show how to set the order.
  3. Extend the inventory to third parties. TPAs, brokers, web aggregators and cloud providers already sit inside IRDAI's supply-chain controls. Add CBOM and PQC-roadmap clauses to renewals using the PQC procurement requirements guide. Check what comes back against how to validate a CBOM.
  4. Anchor the plan to DST's CII dates. Map the inventory to the 2027 / 2028 / 2029 milestones on the India roadmap, so the board sees a dated plan, not only an audit answer.
  5. Benchmark against the sector. Compare with peers on the India BFSI PQC readiness index.

How KavachQ helps

  • An inventory your auditor can check. KavachQ Discover builds the cryptographic inventory, and Seal signs it as a CycloneDX 1.7 CBOM with ML-DSA-65, verifiable offline.
  • Long-lived data first. Harvest-now-decrypt-later exposure and a Mosca timeline show which systems protect data that must stay confidential longest, such as policy and health records.
  • IRDAI in the regulatory map. Findings are mapped to IRDAI alongside the other Indian regulators.
  • Suppliers in view. Track which vendors block your migration, with a signed vendor scorecard for each.

Frequently asked questions

Does IRDAI require post-quantum cryptography?

Not yet. IRDAI's Information and Cyber Security Guidelines, 2026 do not set a PQC migration deadline or required algorithms. Their auditor's report does ask whether you keep a current record of your cryptographic assets, so you are ready to move to post-quantum cryptography.

What changed in IRDAI's 2026 cyber security guidelines?

IRDAI issued revised guidelines on 6 April 2026 (IRDAI/GA&HR/CIR/MISC/51/4/2026), revising the April 2023 guidelines. Among the new audit controls are a cryptographic-asset inventory for post-quantum preparedness, a check that service-level agreements require providers to get prior written permission before any further outsourcing, and checks that cloud providers are MeitY-empanelled with valid STQC audit status.

Do IRDAI's cyber guidelines apply to TPAs and brokers?

Yes. The 6 April 2026 circular says insurers, foreign reinsurance branches and intermediaries shall strictly adhere to the guidelines from the current financial year. The intermediaries named include brokers, corporate agents, web aggregators, TPAs, insurance marketing firms, insurance repositories, ISNPs, corporate surveyors, MISPs and CSCs, as well as the Insurance Information Bureau of India.

Why is harvest-now-decrypt-later a bigger risk for insurers?

Insurance data stays sensitive for a long time. Life policies run for decades and health records stay personal for life. India's DST task force says networks handling data with a long shelf life should be prioritised, and names personal health data among information that must stay secure for long periods.

What should an insurer's cryptographic inventory contain?

IRDAI does not prescribe a format. CERT-In's v2.0 guidelines give the most detailed Indian model: a CBOM recording algorithms, keys, protocols and certificates for each asset. It should cover your own systems and those of TPAs, brokers and other service providers.

Sources

  1. IRDAI, Information and Cyber Security Guidelines, 2026, circular IRDAI/GA&HR/CIR/MISC/51/4/2026 with Annexure A (summary of changes) and Annexure B (guidelines and auditor's report) (April 2026) — irdai.gov.in/en/document-detail?documentId=9189223
  2. DST / National Quantum Mission, Report on Quantum-Safe Ecosystem in India (May 2026) — dst.gov.in/sites/default/files/Quantum-Safe-Ecosystem-in-India.pdf
  3. CERT-In, Technical Guidelines on SBOM, QBOM & CBOM, AIBOM and HBOM v2.0 (July 2025) — cert-in.org.in/PDF/TechnicalGuidelines-on-SBOM,QBOM&CBOM,AIBOM_and_HBOM_ver2.0.pdf

Sources checked 8 November 2026. Standards and regulations change; always read the issuing body's current publication. This guide is general information, not legal advice.

For your sector

See what your estate actually runs

Start with a free scan of a public domain, then scope a pilot that produces a signed CBOM for a real slice of your estate.