Cyber insurance is often bought the way people buy a warranty: quickly, without reading it, in the hope of never using it. That is a mistake. A cyber policy is a contract full of conditions that depend on how your systems are actually run. Read it the way an engineer reads a specification, and you will know what you are really buying, and what you need to do so a claim is paid.
This article is a practical reading guide, not insurance or legal advice. Always confirm details with your broker and the policy wording.
What does a cyber insurance policy usually cover?
Business policies are typically split into first-party cover (your own losses) and third-party cover (claims against you). Common sections include:
| Section | What it pays for | Engineer's note |
|---|---|---|
| Incident response | Forensic investigators, legal advice, crisis communications | Often must use the insurer's panel firms |
| Data restoration | Recovering or recreating data and systems | Usually does not cover upgrading systems beyond their previous state |
| Business interruption | Lost profit while systems are down | Subject to a waiting period; you must prove the loss |
| Cyber extortion | Response costs and, where lawful and permitted, ransom-related costs | Typically requires insurer consent before any payment |
| Privacy and network liability | Defence and damages if customers or partners sue | Check whether contractual liabilities are excluded |
| Regulatory proceedings | Defence costs, and fines only where insurable by law | Fines are often not insurable; read carefully |
| Notification costs | Informing affected people, call centres, monitoring | Relevant to DPDP breach intimation duties |
| Funds transfer fraud / social engineering | Money lost to fake invoices or impersonation | Often a sub-limit, and often conditional on call-back verification |
What IRDAI has said about individual cyber cover
For individuals, IRDAI issued guidance suggesting that personal cyber policies cover areas such as theft of funds, identity theft, phishing, unauthorised online transactions, email spoofing, cyber stalking, malware and data restoration, cyber extortion and data breach. The guidance includes a model policy, but recognises that standardising cyber policies is not desirable because threats evolve quickly. It also notes that non-delivery of goods bought online is primarily a business risk, and that for small claims up to Rs 5,000 insurers may accept a complaint on the National Cyber Crime Reporting Portal instead of an FIR (Majmudar & Partners analysis of the IRDAI guidance). Business policies are separately negotiated and vary far more.
What do cyber insurance policies commonly exclude?
- Gross negligence or deliberate acts by the insured.
- Known or prior incidents: anything you knew about, or should have known about, before cover started.
- Failure to maintain stated controls: if the proposal form said MFA was enforced and it was not, the insurer may dispute the claim.
- Unpatched vulnerabilities: some wordings exclude or reduce cover for exploitation of vulnerabilities left unpatched beyond a stated period.
- War and state-backed attacks: wording varies and matters; read the definitions.
- Infrastructure failure: outages of power, internet or major cloud providers may be excluded or limited.
- Betterment: improving systems beyond their previous state after an incident.
- Contractual penalties you agreed to with clients, unless specifically covered.
- Theft of intellectual property value: the lost value of trade secrets is rarely covered.
What will underwriters ask you?
Proposal forms have become detailed. Expect questions like these, and answer them precisely:
- Is MFA enforced for email, remote access (VPN, RDP) and privileged accounts?
- Do you keep offline or immutable backups, and when did you last test a restore?
- How quickly are critical patches applied to internet-facing systems?
- Do you use endpoint detection and response on laptops and servers?
- Is anyone monitoring security alerts around the clock?
- Do you have a written incident response plan, and has it been tested?
- Do payment changes require independent verification?
- How much personal and payment data do you hold, and is it encrypted?
- Have you had any incidents or claims in the past few years?
- Do you comply with applicable laws, such as CERT-In Directions and the DPDP framework?
How to avoid a denied claim
Before you buy
- Answer the proposal honestly and specifically. "MFA on email for all users; VPN MFA rollout in progress, due next month" is better than an optimistic "yes". A declared control that turns out not to exist hands the insurer an argument.
- Get evidence ready: screenshots or reports that prove MFA enforcement, backup tests and patch timelines.
- Match limits to real exposure. Estimate what a week of downtime and a breach notification exercise would actually cost you.
- Read sub-limits, especially for social engineering fraud and ransomware.
During the policy year
- Keep the controls you declared in place. If something changes, tell the insurer.
- Store the insurer's 24x7 claims number in your incident response plan.
- Know the panel: which forensic and legal firms the insurer requires.
When an incident happens
- Notify the insurer early, as the policy requires. Notifying late can itself put the claim at risk.
- Do not pay anyone, or engage costly vendors, without consent where the policy requires it.
- Preserve evidence. Insurers and their forensic teams need logs, images and timelines; CERT-In's requirement to keep 180 days of ICT logs in India helps here too (CERT-In Directions, 2022).
- Meet your legal reporting duties regardless of insurance: CERT-In within 6 hours, DPDP breach intimations where personal data is involved, and police complaints for fraud.
- Keep a cost log from the first hour.
Five definitions to read before signing
Many disputes turn on definitions, not on headline cover. Before you sign, read how the policy defines:
- "Computer system": does it include cloud services and systems run by your vendors, or only hardware you own?
- "Security event" or "cyber incident": does it require a targeted attack, or does any unauthorised access count?
- "Waiting period" for business interruption: how many hours of downtime before cover starts?
- "Insured": are subsidiaries, directors and employees included?
- "Retroactive date": from when must the incident have started to be covered?
Ask your broker to explain each one against a realistic scenario, such as ransomware arriving through a vendor's remote support tool.
Is cyber insurance worth it for an Indian SME?
It can be, particularly if downtime would be expensive, you hold significant personal data, or clients require it in contracts. But insurance transfers part of the financial loss; it does not restore customer trust or prevent the outage. Treat it as the last layer after MFA, backups, patching and monitoring, not as a replacement. Improving those controls also tends to make cover easier to obtain on better terms.
How Cehpoint can help
Cehpoint's virtual CISO service helps you answer insurer proposal forms accurately, gathers the evidence underwriters ask for, and closes the control gaps that lead to exclusions or denied claims. If an incident occurs, our digital forensics team works alongside your insurer's process to document what happened, and a consultation is a simple way to review your current policy against your real setup.