Regulation & Assurance

IRDAI cyber security guidelines 2026

A practical evidence guide to the IRDAI 2026 Information and Cyber Security Guidelines for insurers and covered intermediaries.

Evidence checklist for insurer incidents, assurance, testing, governance, exceptions and suppliers.
In this article 7 sections
ShareLinkedInWhatsAppEmail

Key takeaways

  • The Insurance Regulatory and Development Authority of India (IRDAI) issued revised Information and Cyber Security Guidelines on 6 April 2026. Covered entities must comply from the current financial year, 2026–27.
  • Prepare evidence for incident reporting, annual assurance, testing, Chief Information Security Officer (CISO) independence, exceptions and third parties.
  • Keep the control record, its owner, review date, evidence and unresolved limitation together.
  • Use the 30-day check below to find gaps before an assurance review.

Information correct as at 31 October 2026.

Who must follow the 2026 Guidelines?

The Insurance Regulatory and Development Authority of India (IRDAI) issued revised Information and Cyber Security Guidelines on 6 April 2026, replacing the 2023 Guidelines. They apply to insurers, foreign re-insurance branches, IRDAI-regulated insurance intermediaries and the Insurance Information Bureau of India. Insurance agents, micro-insurance agents, point-of-sale persons and individual surveyors are outside the Guidelines’ direct scope; insurers must ensure they follow a minimum security framework under the insurer’s Board-approved policy. The circular requires compliance from the current financial year, 2026–27. IRDAI Information and Cyber Security Guidelines, 2026, circular and Annexures A–B (official document page)

What evidence should an insurer be ready to show?

A practical review asks who performed a control, when it ran and how the organisation handled exceptions or findings. The six categories below are an editorial evidence checklist, not IRDAI-prescribed headings.

A practical evidence checklist (editorial categories, not IRDAI headings)
AreaEvidence to assemble
Incident reportingNotice/detection times, decision record, Indian Computer Emergency Response Team (CERT-In) report reference and required regulator notifications
Annual assurance auditApproved scope, auditor appointment, findings, closure owners and submission record
Penetration testingAuthorised scope, test report, assessor status, remediation and retest
CISO independenceReporting line, role description, goals and relevant committee records
Security exceptionsControl, risk, compensating measures, correct approver, expiry and reassessment
Third parties and cloudContract clauses, service scope, certificate/status checks and exit evidence

Incident reporting

The Indian Computer Emergency Response Team (CERT-In) requires specified cyber incidents to be reported within six hours of being noticed or brought to notice. IRDAI’s Guidelines assign the CISO responsibility for ensuring incidents are reported to CERT-In and other relevant stakeholders or regulators within the stipulated time. These are distinct reporting routes; assess the incident against each applicable requirement. CERT-In FAQs on Cyber Security Directions of 28 April 2022, questions 24 and 30

Keep the time the incident was noticed or brought to the organisation’s notice, the reporting decision, the CERT-In report time and reference, and any required IRDAI or other regulator notification. Confirm the reporting trigger for the specific event with the compliance owner.

Annual assurance

Insurers submit the signed annual audit report, with Board comments, to IRDAI by the earlier of 90 days after financial year end or 30 days after audit completion. Do not use a calendar example without confirming the organisation’s year-end and the applicable date-counting convention. IRDAI Information and Cyber Security Guidelines, 2026, circular and Annexures A–B (official document page)

Insurance intermediaries submit their annual audit report to the insurer or insurers within 30 days of audit completion; the auditor or audit firm must meet the Annexure IV eligibility requirements. Keep the approved scope, auditor appointment and independence record, findings, closure owners, target dates and submission acknowledgement together. IRDAI Information and Cyber Security Guidelines, 2026, circular and Annexures A–B (official document page)

Penetration testing

For internet-facing information assets and systems, the Guidelines require vulnerability assessment at least every six months and external grey-box or white-box penetration testing every six months by a CERT-In-empanelled auditor. Testing in a test environment is allowed only in unavoidable circumstances, with production-equivalent version and configuration; deviations go to the ISRMC for approval. Security testing is also required for changes before production. IRDAI Information and Cyber Security Guidelines, 2026, circular and Annexures A–B (official document page)

For each test, retain the authorised scope, excluded systems, test method, assessor empanelment status on the relevant date, report, remediation plan and retest evidence. Keep accepted residual risks separate from verified technical closure.

Governance

The Information Security Risk Management Committee (ISRMC) meets at least quarterly; its quorum is the Chief Information Security Officer (CISO) and at least two other members. The CISO reports to the top executive overseeing risk management or, in that person’s absence, directly to the CEO; the CISO must not report directly to the Head of IT and must not receive business targets. IRDAI Information and Cyber Security Guidelines, 2026, circular and Annexures A–B (official document page)

A practical evidence set includes the organisation chart, CISO role description and objectives, committee terms of reference, dated minutes, quorum and open-action records. These records help show how governance operates; they are not a substitute for the prescribed policy.

Security exceptions

The Guidelines require a case-by-case exception with risk assessment and approval: the CISO approves exceptions not exceeding three months; the Risk Management Committee approves exceptions exceeding three months; and the Board also approves exceptions exceeding one year. Record the request, risk treatment, approver, expiry and review evidence. IRDAI Information and Cyber Security Guidelines, 2026, circular and Annexures A–B (official document page)

  • Record the requirement and reason for the exception.
  • Name the approver, approval date and applicable authority tier.
  • Record compensating measures, residual risk, expiry and reassessment date.
  • Keep the approval linked to the control owner and closure plan.

Vendors and cloud services

For vendor engagements, the Guidelines call for contractual right-to-audit terms. An ISO 27001 certificate may be accepted only when the service provided falls within its certification scope. For cloud services, use a Ministry of Electronics and Information Technology (MeitY)-empanelled cloud service provider (CSP) and check the data centre’s valid Standardisation Testing and Quality Certification (STQC) or government-appointed equivalent audit status. Check contractual return, deletion and exit provisions against the applicable cloud requirements. IRDAI Information and Cyber Security Guidelines, 2026, circular and Annexures A–B (official document page)

A review record can link each service to the applicable clause, contract language, certificate scope and validity, current cloud status, and exit evidence. These are separate checks; a general security certificate does not establish that every service or control is covered. IRDAI Information and Cyber Security Guidelines, 2026, circular and Annexures A–B (official document page)

Agents and intermediaries

Insurance agents, micro-insurance agents, point-of-sale persons and individual surveyors are not directly within the Guidelines’ scope. The insurer remains responsible for setting a minimum security framework for these roles through its Board-approved policy. Intermediaries regulated by IRDAI are in scope, with applicability details and classifications in Annexures I and II. IRDAI Information and Cyber Security Guidelines, 2026, circular and Annexures A–B (official document page)

What evidence gaps should an insurer check?

  • Exceptions without a named approver, expiry date or recorded risk.
  • Findings marked closed without validation evidence.
  • Older contracts that may not contain the required clauses.
  • Certificates accepted without checking service scope and validity.
  • Incident timelines reconstructed after the event.

These are practical examples to check, not findings attributed to IRDAI or measured claims about the insurance sector.

What should the insurer do in the next 30 days?

  • Pull the exception register and identify missing approver, risk, expiry or reassessment records.
  • Check the last applicable tests, scope, assessor status, remediation and retest.
  • Sample vendor contracts against the current verified clauses.
  • Confirm the CISO reporting line and objectives against HR and governance records.
  • Walk through a reportable incident timeline and record unresolved handoffs.
  • Confirm quarterly ISRMC meetings, quorum and actions against the primary clause.
  • Calendar audit submission dates after legal/compliance confirms the counting convention.

This article is general information for awareness and education. It is not legal, regulatory or professional advice and does not take into account the circumstances of your organisation. Laws, standards and threats change; check the primary sources cited and take qualified advice before acting.

How Bravewall helps

Bravewall coordinates cybersecurity programmes around agreed requirements, responsibilities and evidence. For a specific insurer, applicability and legal interpretation remain with its compliance function and advisers.

Sources and further guidance

Regulatory applicability depends on the organisation and the provisions in force. Check the linked primary sources before acting.

Related reading and capabilities

Frequently asked questions

When did the IRDAI 2026 cyber security guidelines take effect?

IRDAI issued them on 6 April 2026 and states that covered entities must comply from the current financial year. Confirm entity applicability against the circular and Annexure B.

How soon must reportable incidents be sent to CERT-In?

Within six hours of the incident being noticed or brought to notice, for incidents covered by the Directions. The FAQs explain what can be provided when full details are not yet available.

How often must insurers conduct penetration tests?

The Guidelines require external grey-box or white-box penetration testing of internet-facing information assets and systems every six months by a CERT-In-empanelled auditor.

Who approves a security exception?

The CISO approves exceptions up to three months, the Risk Management Committee approves exceptions over three months, and the Board also approves those over one year.