Getting cyber insurance used to mean answering a short questionnaire and writing a check. That is no longer how it works. Underwriters now audit your technical controls before they issue a policy, and many small businesses fail that audit without knowing why. If you are running a business with fewer than a few hundred employees and you want coverage that actually pays out, a practical cyber insurance requirements checklist will show you exactly where your environment stands before you apply.
This article walks you through the controls underwriters look for most often. Read it, and you will know what to fix, what to document, and what questions to ask your broker or IT provider before you fill out that application.
Why Cyber Insurance Applications Got Much Harder
A few years ago, a small business could answer a cyber insurance application in twenty minutes with a rough yes to most questions. That era is over.
Underwriters got burned by a surge in ransomware and business email compromise claims. They responded by tightening requirements, raising premiums, and adding technical questionnaires that look more like a security audit than a simple form. Carriers now want proof, not promises.
What changed in practice: insurers ask whether you have specific controls in place and whether you can document them. The gap we see most often when we start reviewing a new client's environment is that the technology exists but was never enforced. Admin accounts have MFA available but it was never turned on for the whole team, or backups run nightly but no one has tested a restore in over a year. Those are the gaps that show up on a claim denial.
The controls underwriters focus on most are not exotic. Multifactor authentication, endpoint protection, patched systems, offsite backups, and a written incident response plan appear on nearly every application. The gap for most small businesses is not technology. It is documentation and consistency.
If your IT is managed in-house or by a provider, now is the time to ask directly: can you show me evidence for each of these controls? The application will ask. Have the answer ready before you start.
Cyber Insurance Requirements Checklist Non-Negotiables
Underwriters now treat three controls as the floor, not a bonus. If you cannot document all three, expect a coverage denial or a premium you cannot afford.
Multi-factor authentication (MFA) means a login requires a second proof of identity beyond a password, such as a code sent to your phone. Start with admin accounts, remote access, and any privileged user before rolling it out to everyone else (CISA). Most carrier applications ask whether remote desktop and email admin accounts are MFA-protected as a standalone yes/no. A no on that line alone can trigger a sublimit or exclusion on your policy.
Endpoint detection and response (EDR) is security software that watches devices for suspicious behavior in real time, not just known virus signatures. A standard antivirus product no longer satisfies most applications. Many carrier forms ask you to name your current endpoint tool. If the tool you name does not qualify as EDR, that section can flag your application for manual review or push you into a higher-risk tier.
Tested backups means a full, recent backup stored offline or in a separate cloud account, with a documented restore test. A backup you have never tested is not a backup for underwriting purposes. Backup questions on carrier applications typically ask three things: whether backups are stored offline, whether they are tested, and when the last test occurred. If you cannot answer all three, that section alone can cap your ransomware sublimit. A managed disaster recovery service can handle the testing and documentation for you. For more on protecting backups from ransomware attacks, see the ransomware checklist for small firms after the SafePay warning.
If you currently cannot check yes on one of these controls, fix the gap before you apply rather than self-reporting a no. Some insurers allow a coverage-effective date after remediation, so you can get the control in place and then apply. Applying with a known gap often results in an exclusion, a sublimit, or an outright denial.
Building even a basic cybersecurity program around these controls gives you a foundation that serves the business well beyond the insurance application itself (NIST).
What Privileged Access Management Means for Small Teams
Privileged access means accounts that can install software, change settings, or access sensitive data across your whole network. Underwriters want to know these accounts are locked down. Many applications include a direct question about whether privileged accounts are separated from daily-use accounts. A no there raises flags across multiple scoring categories at once, so this is not a question to leave unanswered.
For a small team, this comes down to a few practical steps. First, every admin account should be separate from the daily-use account for the same person. You log in as a regular user, then elevate only when the task requires it. Second, those privileged accounts need multi-factor authentication without exception. Third, limit who has them. If five people have domain admin rights and only one person needs them, revoke the other four.
Domain controllers, the servers that manage user logins across your network, need special attention. Keep them off the general internet. Use a separate, managed server to pull updates to them rather than giving domain controllers direct internet access (CISA). A PAM tool, even a basic one, helps you log and monitor every time someone uses a privileged account. That log is exactly what an underwriter or auditor wants to see.
If you are not sure where to start, CISA's Cyber Essentials guide is built specifically for small businesses and small local government agencies, and it walks through these controls in plain language (CISA).
Email Security Controls on Almost Every Application
Email security has three layers underwriters consistently ask about: SPF, DKIM, and DMARC.
SPF (Sender Policy Framework) tells receiving mail servers which servers are allowed to send email from your domain. DKIM (DomainKeys Identified Mail) adds a cryptographic signature to outgoing messages so recipients can verify they were not altered in transit. DMARC ties both together and tells receiving servers what to do when a message fails those checks: quarantine it, reject it, or let it through.
Most applications ask whether DMARC is configured and what your policy is set to. Run your domain through a DMARC lookup tool to see your current setting in under a minute. The result shows whether you are set to none, quarantine, or reject. A policy of none means emails that fail checks still reach inboxes. Some carriers score a DMARC policy of none the same as having no DMARC at all, so the policy value matters as much as whether the record exists.
Beyond authentication records, expect questions about email filtering. Can you block malicious attachments? Do you scan links before users click them? Do you have a process for flagging messages that impersonate your own domain? If your business email runs on a hosted platform, most of these controls are available in the admin console. The gap is usually configuration, not cost. Document what you have turned on before you sit down with the application.
Employee Training Documentation That Counts as Evidence
Saying training happened is not the same as proving it. Underwriters want records they can verify, not a checkbox on the application. The documentation format that generates the most pushback is a self-attestation, a statement from the owner saying employees received security training, with no dates, no platform name, and no individual completion records. Underwriters treat that the same as no documentation at all.
The formats that hold up best are completion certificates from a recognized platform, dated sign-off sheets with employee names, and quiz scores that show comprehension, not just attendance. A screenshot of a completed course from a named platform carries more weight than a note in your calendar. Frequency matters as much as format. Annual training is the common floor. If you can show quarterly reminders or phishing simulation results, include them. Document the date, the topic, and who completed it.
Keep these records somewhere you can retrieve them quickly. A shared folder with dated files works. An HR or IT platform that timestamps completions works better.
Logs of system activity support your overall security posture as well. Event logs can confirm whether incidents occurred and what was affected (CISA). A centralized log tool ties your technical controls to your documented processes and gives an adjuster something concrete to review alongside your training records (CISA). Bring both sets of records to the application. Gaps in either will generate follow-up questions.
How Your Answers Affect Premiums and Coverage Limits
Underwriters score your application against a set of expected controls. The more controls you can document, the lower the perceived risk, and the lower your premium. Missing controls push the risk calculation in the wrong direction, and that shows up in your quote.
Coverage limits work the same way. A policy that covers a higher loss threshold requires stronger evidence of your security posture. If your documentation is thin, the insurer may cap your limit below what your business actually needs, or attach exclusions that carve out the exact scenarios you are trying to cover.
Some carriers will decline to quote at all if core controls are absent. Others will quote but add a sublimit, a lower ceiling for specific claim types such as ransomware or business email compromise.
Small businesses often have solid controls in place but weak documentation. The gap costs them on price and coverage even though the technical risk is comparable to a better-documented competitor. Frameworks built for smaller organizations can help you map what you have to what underwriters expect (NIST). Review your application answers alongside your documentation before you submit. What you can prove matters as much as what you have done.
Pull your completed application and your documentation folder and read them side by side before you submit anything. Every answer you give an underwriter should point to a specific policy, log, or configuration record you can produce on request, because a claim denial rarely comes from what you failed to build and almost always comes from what you failed to prove. If you would like help working through this checklist, book a free 30-minute call with Joshua to talk through what your environment needs. Our cybersecurity services and managed IT services cover each of these controls end to end.




