Insurance & Financial Services
Securing the insurance sector
Insurers, brokers and TPAs hold decades of policyholder, claims and health data. These are exactly the records IRDAI's cyber-security and IS-audit guidelines and the DPDP Act 2023 were written to protect. We run IRDAI-mandated audits, close gaps ahead of regulator deadlines and secure the digital platforms insurance is now sold through.
Our insurance practice draws on the same team that has audited 125+ banks and financial institutions, with insurance clients including PINC Insurance and KennCo Insurance, so controls are tested the way financial regulators expect.
- IRDAI cyber-security & IS audit guidelines
- DPDP Act 2023 policyholder-data obligations
- ISO 27001 / 22301 alignment
- TPRM third-party & vendor risk
Key challenges we solve
IRDAI cyber-security & IS audit requirements
Protection of policyholder & claims data
Secure digital onboarding and portals
Third-party and vendor risk exposure
Services for Insurance & Financial Services
The capabilities most relevant to your sector. Each links to full details.
Audit, Governance & Compliance
IRDAI cyber-security and IS audits plus DPDP Act 2023 readiness.
View service →VAPT & Offensive Security
Testing of policy-admin systems, customer portals and claims APIs.
View service →Managed Security & SOC
Monitoring for data exfiltration across core insurance systems.
View service →Identity & Access Management (IAM)
Least-privilege access for agents, brokers, TPAs and surveyors.
View service →Security Engineering & Incident Response
Breach-response planning aligned to IRDAI incident-reporting timelines.
View service →Insurance security questions
Rarely through the core policy platform itself. The weak points are the channels around it: agent and point-of-sale portals, broker and web aggregator integrations, claims intake and document upload, customer self-service apps, and call centres that can reset access. Insurers hold health details, KYC records, nominee data and bank details in one place, so a single compromised partner login can expose a lot. We map the data flows first and then test the channels where outside parties touch them.
Beyond policy, the guidelines expect a named CISO, an Information Security Risk Management Committee that the CISO sits on, an annual review of the cyber security policy, and an independent assurance audit each year, with the plan and reports going to the Audit Committee, Board or Principal Officer. For a security team, that means audit evidence has to be ready every year, not assembled in a rush: asset inventory, access reviews, test reports and closure records that a separate auditor can verify.
All the way, as far as the guidelines are concerned. They extend to intermediaries such as brokers, TPAs, web aggregators and insurance repositories, and insurers must have a Board-approved policy to make sure those parties comply for as long as the engagement lasts. Even partners that only hold paper copies of your data are expected to give annual self-certification. In practice we help insurers tier their partners by data held and system access, then test the integrations that carry the most sensitive records.
Both, and treating them separately leaves a gap. Account takeover on policyholder portals, OTP interception, fake documents uploaded into claims workflows and persuasive calls to support staff all combine technical and human weaknesses. A useful assessment includes the claims and customer-service workflows end to end: what a caller can change on a policy, what a forged document can trigger, and whether anomalies reach a person who can stop a payout.
Cashless networks connect your claims systems to hospital information systems and TPA platforms that you do not control. The risks are exposed APIs, shared credentials, file transfers carrying medical records, and a hospital's own ransomware event interrupting claim processing. We test the integration endpoints on your side, review how partner access is granted and revoked, and check that you can isolate one hospital or TPA connection without halting the rest.
CERT-In's 2022 directions apply to bodies corporate and require listed incidents to be reported within six hours of noticing them, a designated point of contact, and ICT logs retained for 180 days within India. For insurers the practical difficulty is that relevant logs sit across the policy administration system, claims platform, customer portals and TPA or cloud environments. Confirming in advance which of those retain logs, for how long, and who can produce them quickly saves hours when it matters. Your IRDAI reporting obligations apply separately.
Talk to an insurance security specialist
IRDAI audits, DPDP Act readiness and policyholder-data protection, delivered by a CERT-In empanelled partner.