How to Answer Your Cyber Insurance Security Questionnaire
Your cyber insurance questionnaire is a promise, not paperwork. Here's how to answer it honestly, gather evidence, and fix gaps before your renewal deadline.
The renewal email shows up on a Tuesday afternoon. Your broker needs the cyber insurance security questionnaire filled out by Friday, and it's 40 questions long. Do you enforce MFA on all remote access? Are your backups immutable? Do you have EDR on every endpoint? You think the answer to most of them is "yes, mostly," and that word "mostly" is the problem.
I've sat with a lot of IT managers and business owners going through this exact form. The questions look simple, but each one is a promise. If you check "yes" and the truth is "partly," you may have just given the carrier a reason to deny a claim later.
This guide walks through what insurers are actually asking, how to answer honestly without tanking your premium, and how to fix the gaps you find before the deadline. My partner Mukesh has spent 25 years in cybersecurity, and a lot of what's below comes from the two of us working through these forms with clients.
In this guide
- Why the questionnaire matters more than the premium
- The questions almost every carrier asks
- How to answer each section of the cyber insurance questionnaire honestly
- Gather evidence before you answer
- Fixing gaps fast when the renewal deadline is close
- Common mistakes that cause denied claims
- Frequently asked questions
Why the questionnaire matters more than the premium
Most people treat the security questionnaire as a hoop to jump through to get a quote. Carriers treat it as the factual basis of the policy. Your answers are usually incorporated into the application, and the application is often part of the contract.
That means a wrong answer isn't just a paperwork error. If you suffer a ransomware attack and the investigation shows MFA wasn't actually on the VPN you said it was on, the carrier may argue misrepresentation. There has been at least one widely reported case where an insurer went to court to rescind a policy over an MFA answer that turned out to be inaccurate.
So the goal isn't to get every box to "yes." The goal is to make every answer true, and then make as many of them "yes" as you can afford.
Who should fill it out
The form often lands on the owner or CFO because the broker sends it to whoever signs the check. That person usually can't verify whether EDR is on all 85 laptops. Have your IT lead or MSP fill in the technical answers, and have an officer of the company review and sign it. Both people should understand what they're attesting to.
The questions almost every carrier asks
Every carrier words things differently, but the same core controls show up on nearly every application I've seen for small and mid-sized businesses. If you know these, you know most of the form.
- Multi-factor authentication on email, remote access (VPN, RDP, remote tools), cloud apps and admin accounts.
- Endpoint detection and response (EDR) on workstations and servers, ideally with someone watching the alerts 24/7.
- Backups that are offline, immutable or otherwise separated from your main network, and tested.
- Patching, especially how fast you apply critical patches and whether you run any end-of-life software.
- Email security, including filtering, link scanning and sometimes SPF, DKIM and DMARC.
- Security awareness training and phishing simulations for staff.
- Privileged access, meaning who has admin rights and whether admin accounts are separate from daily-use accounts.
- Remote access exposure, such as whether RDP is open to the internet.
- Incident response plan, and whether you've tested it.
- Funds transfer controls, such as callback verification before changing vendor bank details or sending wires.
Manufacturers often get extra questions about operational technology and network segmentation. If your shop-floor machines share a flat network with the office, expect that to come up. I covered that topic in more detail in how to secure shop-floor (OT) networks without stopping production.
How to answer each section of the cyber insurance questionnaire honestly
Here's how I'd approach the sections that cause the most trouble. For each one, the question to ask yourself is: "If an investigator checked this tomorrow, would they agree with my answer?"
Multi-factor authentication
This is the one carriers care about most, and it's where "mostly" creeps in. A typical question reads something like "Is MFA required for all remote access to your network?" The word "all" matters.
Before you answer, list every way someone can get in from outside:
- Microsoft 365 or Google Workspace email
- VPN or firewall remote access
- Remote desktop tools (RDP gateways, ScreenConnect, TeamViewer and similar)
- Your MSP's remote management tool
- Cloud apps with company data (ERP, accounting, file sharing)
- Vendor access to machines on the shop floor
If even one of those lacks MFA, the honest answer is "no" or "partial," with an explanation. Many forms have a comments field. Use it: "MFA enforced on email and VPN. Rolling out to ERP by March 1."
EDR and monitoring
Carriers want to know if you have EDR (not just traditional antivirus) and whether it covers every endpoint. They increasingly ask whether alerts are monitored around the clock, either by your team or a managed detection and response (MDR) service.
Pull a count from your EDR console and compare it to your asset list. If the console shows 72 devices and you have 85 computers, find the missing 13 before you answer. Older machines on the plant floor that can't run the agent should be noted, not hidden.
Backups
The common wording asks whether backups are "offline," "air-gapped" or "immutable," and whether they're tested. A NAS sitting on the same network with the same admin password usually doesn't meet that bar, because ransomware can reach it.
Be ready to answer three things: where the backup copies live, whether an attacker with domain admin could delete them, and when you last restored something to prove they work. If you've never done a test restore, do one this week and write down the date and result.
Patching and end-of-life systems
Expect questions like "How quickly are critical patches applied?" and "Do you run any unsupported operating systems?" Small manufacturers often have a Windows 7 or Windows 10 machine running a CNC controller or a piece of test equipment.
That's not automatically a disqualifier. What carriers want to see is that you know about it and have contained it, for example by isolating it on its own network segment with no internet access. Answer honestly and describe the compensating control.
Training and funds transfer
Most applications ask how often staff complete security training and whether you run phishing simulations. Once a year with a video doesn't hold up well anymore. Many carriers look for regular training plus simulated phishing tests.
Funds transfer fraud questions catch people off guard. If your accounting team will change a vendor's bank account based on an email, that's a gap. A simple written rule fixes it: any change to payment details gets verified by calling a known phone number, not one from the email.
Gather evidence before you answer
I always tell clients to answer the questionnaire like you'll have to prove it, because one day you might. Spend an hour building a folder of evidence before you start checking boxes.
Here's a practical evidence checklist:
- Screenshot of MFA enforcement settings in Microsoft 365 or Google Workspace (conditional access or security defaults)
- VPN or firewall config showing MFA on remote access
- EDR console export showing device count and agent status
- Asset inventory to compare against the EDR count
- Backup job report plus a dated test-restore record
- Patch compliance report from your RMM or Windows Update tooling
- List of end-of-life systems and how each one is isolated
- Training completion report and recent phishing simulation results
- Your incident response plan, with the date it was last reviewed
- Written funds transfer verification procedure
Date everything. If you ever need to show what was true when you signed the application, a dated folder is worth a lot more than someone's memory.
Fixing gaps fast when the renewal deadline is close
Once you've checked your answers against reality, you'll probably find a few gaps. The good news is that several of the controls carriers weight most heavily are also the fastest to fix.
Quick wins (days, not months)
- Turn on MFA for email. In Microsoft 365 this can often be done in an afternoon for a small company, with a short heads-up to staff.
- Close exposed RDP. If RDP is reachable from the internet, shut it off and move remote access behind a VPN with MFA.
- Run a test restore. Pick a file server or a key folder, restore it, and document it.
- Write the funds transfer rule. One paragraph, signed off by the owner, shared with accounting.
- Separate admin accounts. Give IT staff a separate admin login and remove admin rights from daily accounts.
Bigger projects (weeks)
- Deploying EDR to every endpoint, and adding 24/7 monitoring
- Moving backups to an immutable or offline target
- Segmenting the shop floor from the office network
- Replacing or isolating end-of-life systems
If the bigger items can't be done before the deadline, say so in the comments with a target date. In my experience, a clear plan with dates usually reads better to an underwriter than a vague "yes." Ask your broker how the carrier treats in-progress items; some will accept a remediation timeline.
For a broader view of which controls to prioritize first, see Cybersecurity for Roanoke small businesses: 10 steps to protect your company.
Common mistakes that cause denied claims
These are the patterns I see most often. None of them are dishonest on purpose. They come from rushing or from the wrong person filling out the form.
- Answering for the policy you wish you had. Checking "yes" because the project is planned, not done.
- Forgetting one access path. MFA on email but not on the VPN, or not on the vendor's remote tool for the shop floor.
- Confusing antivirus with EDR. Built-in or legacy antivirus is not the same thing, and carriers know it.
- Assuming backups are safe because they exist. Backups that ransomware can encrypt don't count as offline.
- Letting controls drift after renewal. You answer "yes" in January, someone disables MFA for a "temporary" exception in June, and it never gets turned back on.
- Not reading the policy's conditions. Some policies require you to maintain the controls you described for the whole term. Read that section with your broker.
That fifth one is sneaky. I recommend a quarterly check of the same evidence folder. It takes an hour and keeps your answers true all year, not just on the day you signed. If you work with defense contracts, the same habit pays off for CMMC; I wrote about that in CMMC Level 1 vs. Level 2: which one does your manufacturing shop need?.
A quick note: I'm not an attorney or an insurance agent. How your answers affect coverage depends on your specific policy wording and state law, so confirm anything important with your broker and your attorney.
Frequently asked questions
What happens if I answer the cyber insurance questionnaire wrong?
It depends on the policy and the circumstances, but an inaccurate answer can give the carrier grounds to deny a claim or, in some cases, try to rescind the policy. If you realize you answered something incorrectly, tell your broker right away and ask how to correct it. Fixing it before a claim is far better than explaining it after.
Do I need EDR to get cyber insurance?
Many carriers now ask for EDR, and some won't quote certain coverage levels without it. Even where it isn't strictly required, having EDR with active monitoring often helps your pricing and terms. Check with your broker on what your specific carrier expects.
Can I get cyber insurance without MFA?
It's become much harder. Most carriers treat MFA on email, remote access and admin accounts as a baseline requirement. If you don't have it yet, turning it on for email and remote access is usually the single fastest way to improve your application.
Who should fill out the cyber insurance security questionnaire?
The person who actually manages your systems, whether that's an internal IT lead or your MSP, should answer the technical questions. An owner or officer should review and sign it, because they're attesting on behalf of the company. If you outsource IT, ask your provider to walk through the answers with you rather than just sending them back.
How long does it take to get ready for a cyber insurance renewal?
If your basics are in place, gathering evidence and filling out the form can take a day or two. If you have gaps like missing MFA or no EDR, plan on a few weeks to close them. Starting 60 to 90 days before renewal gives you room to fix things instead of explaining them.
Get a second set of eyes before you sign
If your renewal is coming up and you're not sure whether "mostly" is good enough, we can help. Our free cybersecurity assessment looks at the same controls insurers ask about, including MFA coverage, endpoint protection, backups and remote access, and gives you a plain-English list of what's in good shape and what needs work.
There's no obligation, and you'll walk away knowing which answers on your questionnaire you can stand behind. Request your free cybersecurity assessment and we'll set up a time that works for you.
Related reading
- Cybersecurity for Roanoke small businesses: 10 steps to protect your company
- How to secure shop-floor (OT) networks without stopping production
- MSP vs. hiring a full-time IT person: a real cost breakdown
Harsha is a co-founder of SoftwarePac Technologies in Roanoke, VA, and a network engineer with 15 years of experience.




