Cyber Insurance Checklist: 9 Controls to Prove Before You Apply

JD Sentz
November 13, 2026
Cyber insurance checklist for small businesses, 360 Business Solutions

This cyber insurance checklist covers the security controls to have in place, and be able to prove, before an insurer writes or renews a policy. It's written for owners of small firms in Buffalo and Western New York, especially medical, accounting, legal and financial offices. Each item says what the control is, what proof usually looks like, and where small offices tend to come up short.

The short version comes from JD Sentz, COO and CTO of 360 Business Solutions, who fills out these questionnaires with clients: "All of it. They're going to want to know what your endpoint protection is, EDR, XDR, your incident response, MFA enablement, password complexity, conditional access, IP allowlisting or VPN connectivity. A new thing nowadays is AI and automation."

What do insurers require before they'll cover you?

Here's JD's list of what insurers ask about:

  • Multi-factor authentication (MFA)
  • Endpoint detection and response (EDR or XDR) on every computer and server
  • Password complexity rules and conditional access
  • Remote access through a VPN or an IP allowlist
  • A written incident response plan
  • Your use of AI tools and automation

Three more are worth having ready, because CISA or JD treats each one as a basic:

  • Backups kept apart from your network, and tested
  • Separate admin accounts
  • Email filtering and staff phishing training

The exact questions vary by carrier and by policy size. Your broker can tell you which ones your carrier treats as deal breakers. 360 Business Solutions, a managed IT and compliance company in Amherst, NY, helps small firms put these controls in place and gather the proof. Call (716) 650-7200.

The cyber insurance checklist: 9 controls to have in place

1. MFA everywhere it matters

Expect a question about MFA. Have it on email, remote access and any account with admin rights. A yes needs to be true for every user, including the owner and the person who "never logs in remotely."

Proof: a screenshot or report from your Microsoft 365 or Google admin console showing MFA enforced for all users. CISA's guidance to small businesses is plain about it: require multi-factor authentication.

2. EDR or XDR on every device

Insurers ask about endpoint detection and response by name, not just antivirus. EDR is software that watches for suspicious behavior and can isolate a device.

Proof: the product name, a device count that matches your actual computers and servers, and who monitors it.

3. Password rules that are actually enforced

This is where JD sees the most trouble when 360 takes over a new client: "Password hygiene is terrible. Passwords are stored on devices or on paper. Passwords are very weak, and there is no requirement to change them."

Proof: your password policy settings, plus a password manager in place of the sticky note on the monitor.

4. Conditional access

Conditional access decides who can sign in, from where and from which devices. A login from an unknown laptop in another country gets blocked even with the right password.

Proof: the policies set in your Microsoft 365 admin center. If nobody at your office knows what that means, that's the answer to the question.

5. Remote access locked to a VPN or IP allowlist

Insurers ask how staff reach the office systems from home. The safe answer is a VPN or IP allowlist, not an open remote desktop port. An open RDP port is public-facing, and as JD puts it, "just opening a port allows a bad actor to potentially try to brute-force access or find vulnerabilities within that platform to access those resources." CISA's ransomware guide says the same thing: don't expose remote desktop on the internet.

JD's preferred setup is a VPN that ties every remote user to the business's public IP address, with access allowed only from that address.

Proof: a description of how remote access works, and a firewall with no open remote desktop ports.

6. Backups kept separate, and tested

Ransomware goes after backups too. A backup that sits on the same server it protects can be encrypted right along with everything else. CISA's ransomware guide recommends offline, encrypted backups and regular tests that prove you can restore from them.

JD has seen the difference a tested backup makes. In one case from his career, an IT staffer gave admin rights to a compromised device after what looked like a printer driver login request, and ransomware hit an entire file share. All services were restored within 24 hours from the previous night's backup. The data created that day was lost.

Proof: where backups live, how often they run, and the date of your last restore test.

7. A written incident response plan

Insurers want to know what happens when something goes wrong: who you call, who decides, how you reach your carrier. At the practices JD walks into, incident response documentation is usually missing, and so is tabletop testing, where the team talks through a fake incident before a real one.

Proof: the plan itself, a few pages is fine, and the date you last walked through it.

8. Separate admin accounts

When financial examiners review a firm's IT, JD says, "a big one is privileged access." The same question is worth being ready for on an insurance application. It comes down to whether the person with admin rights uses that same account for email and web browsing. It shouldn't. Day-to-day work happens on a normal account, and admin work happens on a separate one, used only when needed.

Proof: a list of admin accounts and who holds them. Fewer is better.

9. Email filtering and phishing training

Phishing has gotten harder to spot. JD's description: an email "can come across like a document you would expect to receive from an email address you would expect to receive it from." 360 puts Proofpoint email filtering on its clients. Training matters too, though JD is realistic about it: after training, "there are always a few who still" click.

Proof: the email filtering product you use, and records of staff training and any phishing tests.

The newer question: AI and automation

JD has started seeing insurers ask about AI and automation. Have a simple list ready: which AI tools your staff use, what client information goes into them, and who approved them. If the honest answer is "we don't know," find out before the application is due.

Where small firms usually come up short

When 360 takes over a new client, or walks into a medical practice, JD sees the same gaps, and most of them line up with the checklist above:

  • Weak passwords, written down or saved on devices, never changed
  • Firewalls that were never locked down, with open ports
  • No VPN or IP allowlisting, so systems face the public internet
  • No written policies or procedures for how the office runs its IT
  • Backups and incident plans that have never been tested

Most of these are fixable once someone owns them. They get skipped because nobody does. A part-time IT person or a break-fix vendor fixes what breaks and doesn't fill out the insurance questionnaire.

Answer the application honestly

Treat the application like a statement of fact, because it is one. If you check "yes" on MFA and two users don't have it, that's a problem you want to find before your carrier does. Ask your broker how your policy handles an answer that turns out to be wrong.

A better approach is to close the gaps first, then fill out the form.

What your IT company can and can't do

Your IT provider can put the controls in place, document them, and help you answer the technical questions accurately. It can't sell you a policy, decide what your carrier will accept, or promise you'll be approved. That part belongs to your broker and your insurer.

If your renewal is coming up and the questionnaire is full of terms you don't recognize, our compliance and security team can walk through it with you, item by item. Call us at (716) 650-7200.

Frequently asked questions

What are the typical requirements for cyber insurance?

JD's list: endpoint protection (EDR or XDR), incident response, MFA, password complexity, conditional access, IP allowlisting or VPN connectivity, and now AI and automation. Backups, separate admin accounts and email security round out the list. Carriers word the questions differently, so check your own application.

Does cyber insurance require MFA?

MFA is on the list JD sees insurers ask about. Expect the question to cover email, remote access and admin accounts, and check your carrier's application for the exact wording.

What does cyber insurance cover?

Coverage varies by policy. Ask your broker what yours includes and what it excludes. This post covers the security side: what you need to prove to get a policy in the first place.

Can my IT company fill out the insurance application?

It can answer the technical questions and give you the proof to back them up. You still sign it, so read every answer before you do.

We're a regulated firm. Does this overlap with our compliance rules?

A lot of it does. If your firm falls under the FTC Safeguards Rule, MFA, encryption, monitoring and an incident response plan are already on your list. Our FTC Safeguards Rule checklist covers those requirements, and the same work answers a good part of the insurance questionnaire. For day-to-day support, see our managed IT services.

This post explains what insurers commonly ask for. It isn't insurance or legal advice. Talk to your broker about your policy.

‍

Ready to Talk?

Your first conversation is on us.

Free 30-Minute Technology Assessment

  • Review your current IT setup
  • Identify compliance gaps and quick wins
  • Explore AI & automation opportunities
  • No pitch. No pressure. Just clarity.
Loading booking calendar...