Cyber Insurance Requirements in 2026: What Regulated Organizations Need to Qualify and Keep Coverage
Published · 9 min read

What Cyber Insurance Is, and What It Is Not
Cyber insurance can pay for part of the cost of a breach or a ransomware event. It is not a substitute for the security program your regulators, clients, and partners already expect. A policy also is not a guarantee that a claim will be paid. Underwriters ask detailed questions about the controls you have in place. If the answers do not match the environment, or if a required control has lapsed since you applied, the carrier can deny or limit the claim.
This guide is for medical practices, law firms, accounting and other financial firms, and other regulated organizations that are applying for a policy, renewing one, or trying to understand why a premium went up or an application was declined. It replaces a set of overlapping articles that covered the same ground by industry. NorthStar helps with the technical controls and the documentation that applications ask for. NorthStar does not sell insurance, and it does not guarantee that you will obtain coverage or pay a lower premium. For how that work is scoped, see our cyber insurance services and the cyber insurance readiness item in our services catalog.
Do HIPAA, the FTC Safeguards Rule, or ABA Ethics Rules Require You to Buy a Policy?
No. The HIPAA Security Rule requires administrative, physical, and technical safeguards for electronic protected health information. It does not require a medical practice to carry cyber insurance. The FTC Safeguards Rule (16 CFR Part 314) requires a written information security program for covered financial institutions, including many accounting and tax firms. It also does not require a policy. The American Bar Association's formal ethics opinions on cybersecurity and data breaches, including Formal Opinion 483, address competence, confidentiality, and how to respond when a breach occurs. They do not require a firm to purchase a particular insurance product.
Those programs and a cyber insurance application still overlap in practice. The same controls (access management, logging, backups, incident response, vendor oversight, and staff training) show up in regulatory examinations and in underwriting questionnaires. Building them once, and keeping evidence current, serves both. A policy does not satisfy HIPAA, the Safeguards Rule, or your ethical duties by itself, and being "in compliance" on paper does not automatically bind a carrier to pay a claim.
What Do Applications Commonly Ask You to Show?
Requirements vary by carrier, limit, and industry. There is no single national checklist. The National Association of Insurance Commissioners has described a cyber insurance market in which underwriting has become more detailed as losses have grown. In the applications we help clients complete, these questions come up again and again:
- Multifactor authentication (MFA) on email, remote access, privileged and administrator accounts, and systems that hold sensitive data (electronic health records, financial applications, matter or document management, and cloud storage).
- Endpoint detection and response, not only signature-based antivirus, with a way to isolate a compromised device.
- Backups that are encrypted, tested, and held in a way that ransomware cannot easily encrypt them, often including an offline or immutable copy, plus evidence that a restore has been tested on a schedule.
- A written incident response plan that names owners, notification duties, and how evidence will be preserved, plus some proof that the plan has been exercised.
- Email security and anti-phishing controls, because business email compromise and credential theft remain common claim drivers.
- Security awareness training for staff, often with phishing simulations, and records that the training happened.
- Privileged access control and timely patching, including who has administrative rights and how quickly critical vulnerabilities are addressed.
- Vendor and business-associate oversight, especially when a third party stores or processes patient, client, or customer data.
Answer only what is true today. An application that overstates MFA coverage, backup testing, or monitoring is a claim risk later, even if the misstatement was unintentional. If a control is partial, say so and document the gap. For the assessment work behind those answers, see our risk assessment service. For email and endpoint questions, see cybersecurity services. For backup and restore testing, see backup and disaster recovery.
What Does a Cyber Insurance Policy Typically Cover?
Policy language differs, and the only terms that matter are the ones in your contract with the carrier. In general, organizations evaluate both first-party and third-party coverage:
- First-party breach response: forensic investigation, notification, credit or identity monitoring, and related crisis costs.
- Ransomware and extortion: negotiation support and, where legal and approved by the carrier, payment facilitation. Many policies impose conditions, sublimits, or exclusions here.
- Business interruption: lost income and extra expense while systems are down, sometimes including dependent or contingent interruption when a vendor is the one offline.
- Data recovery and system restoration after an attack.
- Third-party liability: defense and settlements when patients, clients, or other parties bring claims.
- Regulatory defense and, sometimes, civil fines or penalties where the policy allows it. Coverage for government fines is limited or excluded in many forms. Do not assume a HIPAA, FTC, state, or professional-board penalty will be paid.
Cyber insurance is also not the same as professional liability or errors-and-omissions coverage. A legal malpractice policy, a CPA firm's professional liability policy, or a similar E&O form typically addresses mistakes in professional services. It often does not cover a ransomware outage, a business-email-compromise wire loss, or the cost of notifying affected people after a network intrusion. Read both forms, and ask your broker where the seams are, before you assume one will fill a gap in the other.
What Should You Know About Cost and Limits?
Premiums and deductibles vary widely. Carriers look at industry, revenue, records or matter volume, prior claims, the limits you want, and the controls and evidence you can show. A medical practice, a law firm, and a CPA firm will not be quoted the same way, and two organizations of the same size can be quoted very differently if one has tested backups and complete MFA and the other does not.
Because those numbers move with the market and with your own posture, this article does not publish a premium table. Treat any generic "average cost" you see elsewhere as unverified unless the source is current and named. The practical steps that most often change a quote or a declination are the ones above: close real control gaps, then apply with evidence that matches the environment. NorthStar cannot promise a lower premium or a particular limit. A hospital-system example of control work done before a renewal is in our cyber insurance case study. Results depend on the carrier, the facts, and the work completed.
Why Do Claims Get Denied or Limited?
The failures we see most often are not exotic. They are mismatches between the application and the environment:
- MFA was described as deployed, but it was missing on email, a VPN, a cloud console, or a privileged account involved in the incident.
- Backups existed, but they had not been tested, were in the same logical path the ransomware encrypted, or could not be restored in time.
- The incident response plan was a template, was not followed, or did not exist in written form when the carrier asked for it.
- A vendor or business associate caused or contributed to the incident, and the relationship, contract, or oversight described in the application was not in place.
- A control had been true at application and had since lapsed: an expired tool, a new system brought up without MFA, or training that was not repeated.
Documentation matters as much as the tool. If you cannot show configuration, logs, test results, or a current plan, the carrier may treat the control as missing. Keep the evidence current between renewals, not only during the application week. For incident-response planning and exercises, see our incident response service. For training records, see security awareness training.
How Should You Prepare Before You Apply or Renew?
A straightforward sequence, whether you are a medical practice preparing a HIPAA-aligned package, a law firm reviewing ethics and client duties, or a financial or accounting firm under the Safeguards Rule, looks like this:
- Inventory the systems and vendors in scope, including email, backups, remote access, and anyone who holds your sensitive data.
- Compare that environment to the questionnaire you will have to sign, and note every question you cannot answer with evidence.
- Close the gaps that would make an honest answer unfavorable or untrue, then collect the artifacts (screenshots that can be reproduced, policies, test tickets, training rosters, vendor contracts) before you submit.
- Work with your broker on limits, retentions, and exclusions, including ransomware conditions and regulatory coverage, rather than shopping only on price.
- Keep the program running after the binder is issued. A renewal, a claim, or a new system can reopen every question you just answered.
An independent test can strengthen both the application and the program. Our penetration testing service is an assumed-breach test of the environment, with a retest after remediation. It is not a guarantee of coverage. A security check can also surface obvious gaps early. That check is not an insurance underwriting review.
Where to Go Next
Start with your broker and with the official rules that already apply to you: the HIPAA Security Rule for health care, the FTC Safeguards Rule for covered financial firms, and ABA ethics guidance for law firms, along with the NAIC's cyber insurance resources for market context. Then use the service pages that map to the work in this guide: cyber insurance readiness, risk assessment, incident response, backup and disaster recovery, security awareness training, and penetration testing. Industry overviews are also on our healthcare, financial services, and law firm pages, and in the services catalog.
If you want help implementing or documenting controls before an application or a renewal, visit the cyber insurance service page or call 866-337-9096. We can help you tell the truth on the application and close the gaps that would make that truth hard to live with. We cannot bind a policy or promise a premium.
Industry Resources
Cyber Insurance Readiness
See how NorthStar helps regulated organizations implement and document the controls cyber insurers commonly ask about. NorthStar does not sell insurance and does not guarantee coverage or lower premiums.
Learn More →About the author

Ken Satkunam, CISM
President & Founder, NorthStar Technology Group
Ken has spent over 25 years in IT leadership, serving in roles from technical support to CIO for organizations as large as 23,000 employees. He founded NorthStar Technology Group in 2000 to help regulated organizations build secure, compliant, and operationally resilient technology environments. Ken holds the Certified Information Security Manager (CISM) credential from ISACA and is the co-author of the Amazon best-seller "Cyber Attack Prevention." He has been quoted in industry publications including eWeek and DM News, and NorthStar has been recognized on the Inc. 5000 list in both 2024 and 2025.