Cyber insurance is a policy that reimburses part of the costs of a cyber incident, under the terms and limits agreed. Insurance does not stop attacks, and insurers often ask about the protections an organization already has before they offer cover. This article explains what a policy typically covers and excludes, the questions insurers commonly ask, and how to prepare before applying.
What a policy covers and does not cover
The NAIC (the US association of state insurance regulators) published its 2026 Report on the Cybersecurity Insurance Market, which uses 2025 data. It says ransomware may be covered, subject to policy terms and exclusions, while social engineering and funds transfer fraud may be excluded, limited by a sublimit, or handled under a separate crime policy.
The NAIC advises buyers to ask the insurer which controls the policy requires and how quickly incidents must be reported. This report describes the US market, and policies in Thailand may differ, so read the actual policy wording and ask a broker or legal counsel. This article is not legal or insurance advice.
May be covered
- Ransomwaresubject to terms and exclusions
May be excluded or limited
- Social engineeringmay be excluded or sublimited
- Funds transfer fraudmay sit in a crime policy
What insurers commonly ask
There is no central standard that sets what insurers ask, and each insurer's form differs. The list below covers topics that several security providers' materials name consistently. Those are marketing blogs, not official requirements, so treat the list only as preparation guidance and rely on the insurer's actual form.
- MFA: is MFA (multi-factor authentication) used for email, remote access and administrator accounts? For safer options see which MFA is safer
- EDR: is EDR (software that detects and responds to threats on user machines and servers) deployed on most machines? Compare options in EDR, XDR and MDR
- Backups: are there backups that ransomware cannot reach, and has recovery been tested? See Backup 3-2-1-1-0
- Incident response plan: is there a written plan, and has it been rehearsed?
- Updates and training: are critical vulnerabilities patched within a set time, and is staff trained on phishing?
Our view: answer truthfully and keep evidence, such as a screenshot of the MFA setting or a restore test result. An overstated answer on the form can become an issue when a claim is made. Have legal counsel or the broker review the answers before they are sent.
Four steps to prepare before applying
- Check current status: compare existing controls with the list above, and note each gap with an owner
- Close the gaps asked about most: start with MFA, backups and the incident response plan, because they are quick to fix and the results are clear
- Collect evidence: keep documents and screenshots in one place, with the date checked
- Review the policy: read the exclusions, sublimits and incident-notice time, and compare them with the risks the organization worries about most
A rehearsed incident response plan is good evidence. Start with the incident response plan under NIST SP 800-61, and when a real incident happens see the first 5 steps against ransomware. Our view: insurance helps with costs after an incident, but it does not replace prevention and recovery.
Where to start
- This week: ask the broker or insurer for the real question form, and mark the items you cannot yet answer
- This month: close the gaps in MFA, backups and the incident response plan, and keep the evidence
- Before applying: have legal counsel or the broker review the answers and the policy exclusions
- Unsure what is missing: start with our assessment