trio.so
How-Tos

How to Answer a Cyber Insurance Questionnaire

How IT should answer the device questions on a cyber insurance questionnaire: honest partial answers, evidence to attach, common mistakes and who signs.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on

A cyber insurance questionnaire is the set of security questions an insurer asks before it quotes or renews a policy. Most of the questions land on IT: MFA, EDR, patching, encryption, admin rights, backups, remote access. This guide covers how to answer the device questions honestly, which evidence to attach, the mistakes that cause trouble later and who should sign.

For the full list of controls and what insurers expect for each, see our cyber insurance requirements checklist. The same free download (a PDF and Word checklist and an Excel evidence tracker) goes with both guides.

Why the Answers Matter

The insurer uses your answers to decide whether to offer cover, at what price and with which exclusions, and it relies on them again if you make a claim. Read the declaration above the signature line before anyone signs. In Travelers v. International Control Services (2022), the insurer said the application described MFA that only protected the company's firewall. After a ransomware attack, both sides agreed the policy was void from the start.

A "Partial" with a fix date is an ordinary answer on these forms. Write one whenever the evidence doesn't support a full "Yes".

Before You Start

  1. Get the carrier's actual form and every supplement that comes with it, such as a separate MFA or ransomware supplement. Last year's copy may not have the same questions.
  2. Read the definitions. What the form calls MFA, EDR, remote access or an offline backup decides whether your setup counts.
  3. Agree the scope: which companies, offices and devices the policy covers. Questions about all endpoints usually include servers and cloud machines.
  4. Give each question an owner who checks the control and pulls the evidence, and set your own deadline two weeks before the carrier's.
  5. Note every question you are unsure about and ask your broker how to answer it, before you guess.

Typical Device Questions and How to Answer Them

Carriers word their questions differently. These are paraphrased versions of the device questions that come up most often, with what each one is really asking:

Typical questionWhat it is really askingHow to answerEvidence
Do you enforce MFA for all remote access to your network?Every VPN, remote desktop gateway, remote support tool and vendor path, for every accountYes only if no remote path works without MFA. List the exceptions if any.Sign-in policy screenshot, VPN or gateway MFA setting
Is MFA required for email, for all users?Every mailbox, including shared and service accounts and legacy protocolsPartial if shared mailboxes or basic authentication still work without MFA.MFA enrollment report by user
Is EDR deployed on all endpoints and servers?Coverage against your device count, and whether the tool fits the form's definition of EDRPartial with the percentage if the EDR console count is below the inventory count.EDR device export next to the inventory export
How many days does it take to apply critical patches?The time your patch report shows, which may differ from your policy's targetGive the number your patch report supports, and say how internet-facing systems are handled.Patch report, open critical vulnerabilities with age
Are laptops and mobile devices encrypted?Disk encryption on every laptop and phone in scopePartial with the count of unencrypted devices and the plan for each.Device list export with an encryption column
Do end users have local administrator rights?Standing admin rights on everyday accountsNo only if no everyday user is a local admin. List approved exceptions.Local admin accounts per device
Do you keep a hardware and software inventory?Whether you know what you haveYes if a tool keeps it current; say how unmanaged devices are found.Dated inventory export
Do you run any unsupported operating systems or software?End-of-life systems and how they are isolatedYes if you do, with the list, isolation and retirement dates.OS version report, end-of-life register
Is RDP accessible from the internet?Port 3389 or other remote desktop services exposed directlyAnswer from an external scan result.External port scan result, firewall rules
Are backups offline or immutable, and tested?Whether ransomware could reach the backups, and proof that restores workGive the date of the last restore test. Untested backups make the testing part a No.Restore test record, backup job report

Yes, Partial or No: Answering Honestly

Yes needs 100% of the scope and evidence; Partial needs the percentage, gaps, compensating control and a date
Yes needs 100% of the scope and evidence; Partial needs the percentage, gaps, compensating control and a date

Yes means the control is in place for everything the question covers, today, and you can show it. One server without EDR or one admin account without MFA makes it Partial. Partial is the right answer for many companies, so give the underwriter what they need to judge it: the coverage, what is missing, any compensating control and the date it will be fixed. No is fine when it is true; add the plan if there is one. Use N/A only when the thing asked about doesn't exist, for example remote access questions when there is no remote access at all.

A compensating control is something that reduces the same risk another way. A Windows 10 PC that has to stay can sit on its own network segment with no internet or email access. A shared mailbox without MFA can have direct sign-in blocked, so people reach it only through their own MFA-protected accounts. Describe it in one sentence; don't use it to turn a Partial into a Yes.

Example wording for a partial MFA answer:

Partial. MFA is enforced for 92% of accounts, including every user and admin account. Direct sign-in is blocked on two shared mailboxes, and one service account is limited to a single internal IP address. Both will have MFA or be removed by January 15, 2027.

What Evidence to Attach

Some carriers ask for proof with the application; others ask later, or only after a claim. Collect it now either way, in one dated folder per renewal:

  • Exports and reports from the systems themselves: MFA enrollment by user, the EDR device list, a patch report, a device list with encryption status, an inventory export, local admin accounts.
  • Screenshots of settings with the date and the console visible: the sign-in policy that requires MFA, the VPN's MFA setting, DMARC, backup retention.
  • Policies and plans with a version date: patch management, access control, backup and the incident response plan.
  • Records that show something happened: the last restore test, the last tabletop exercise, the last access review, training completion.

Check that the numbers agree. If the inventory has 140 devices and the EDR export has 128, fix the gap or answer Partial before you attach both. Remove passwords, keys and personal data from anything you send.

Common Mistakes

  • Answering Yes when coverage isn't 100%, because the tool is deployed and most devices have it.
  • Answering with the plan instead of the current state: a rollout that finishes next month is still a No or a Partial today.
  • Trusting a dashboard's percentage without checking its device count against the inventory.
  • Forgetting servers, cloud machines, service accounts, shared mailboxes and contractors' devices.
  • Copying last year's answers, or leaving a hard question blank.
  • Letting someone outside IT answer technical questions without IT checking them.
  • Sending evidence without keeping a copy of exactly what went to the carrier.

Who Should Sign

The application is usually signed by an officer of the company, such as the CEO, CFO or owner, because it is the company's statement to the insurer. IT should prepare the technical answers, attach the evidence and confirm each one in writing to the person who signs. The tracker in the download has an owner and a last-verified date for every control for this reason. Ask your broker who the carrier expects to sign, and whether a separate supplement, such as an MFA attestation, needs its own signature.

Checklist and Evidence Tracker

The download is shared with the requirements checklist: a PDF and Word checklist with the 14 controls, a one-page summary and eight answering tips, and an Excel tracker that flags a Yes below 100%, missing or stale evidence and overdue reviews. Its Devices tab computes encryption, patch and EDR coverage from a device export, so the percentages in your Partial answers come from the devices.

The tracker's Example tab: answers, coverage and the checks raised for a made-up company
The tracker's Example tab: answers, coverage and the checks raised for a made-up company

Where trio.so Fits

Export this evidence from your own devices. trio.so doesn't sell insurance, back up data or replace your EDR, email filter or training platform. It covers the device side of the questionnaire: it sets controls on Windows, macOS, Linux, iOS/iPadOS and Android devices and lets you export the evidence that they are in place. For the device questions, trio.so gives you:

  • Disk encryption enforced on laptops (BitLocker on Windows, FileVault on Mac) and on phones, with each device's encryption status in the device list.
  • Patch findings with CVSS, EPSS and CISA KEV scores, OS updates through Auto Patch policies, third-party fixes through remediation plans, and the result for each device.
  • A device inventory with each device's owner, serial number, OS version and installed apps (Windows, macOS, iOS and Android).
  • Export of the device list to CSV, with the same columns the console shows, and of each device's installed software.
  • Compliance evidence you can export for auditors and insurers.
  • Console roles, and an export of console members with their roles and last-active date to CSV, for reviewing who (including an MSP or vendor) can manage your devices.
  • MFA at user sign-in and single sign-on (SAML 2.0 or OIDC) for your apps, on the Zero Trust plan.

trio.so's own EDR for Windows, macOS and Linux is coming soon. Backups, email filtering, security training and the incident response plan stay with your own tools and team. Plans start at $5 per device.

Start free trial Book a demo

14-day free trial. No credit card required.

Related Templates and Guides

Sources. Last reviewed November 2026. Control descriptions are our summary of common insurer questions and of public guidance from CISA, the FTC, Travelers and Coalition; the wording is ours. trio.so is not affiliated with or endorsed by any insurer, broker or government agency. This article is general information, not insurance or legal advice.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Back each device answer with an export

trio.so shows each device's encryption status, patch findings and installed apps, and exports the device list and compliance evidence, so the coverage numbers in your answers come from the devices.

Start free trial

Get Ahead of the Curve

Every organization today needs a solution to automate time-consuming tasks and strengthen security. Without the right tools, manual processes drain resources and leave gaps in protection. trio.so is designed to solve this problem, automating key tasks, boosting security, and ensuring compliance with ease.

Don't let inefficiencies hold you back.

Every organization today needs a solution to automate time-consuming tasks and strengthen security. Without the right tools, manual processes drain resources and leave gaps in protection. trio.so is designed to solve this problem, automating key tasks, boosting security, and ensuring compliance with ease.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions

It is the set of security questions an insurer asks on a new application or at renewal, sometimes with supplements on single topics such as MFA. The answers help decide whether cover is offered, the price and any exclusions, and the insurer relies on them if you make a claim.

Yes, where the form allows it, and it is often the honest answer. Give the coverage percentage, what is missing, any compensating control and the date it will be fixed. If the form only offers Yes or No, add a note or ask your broker how to disclose the gap.

Answer No or Partial for the current state and give the date it will be in place. Ask your broker how the gap affects the quote. Don't answer Yes for a control that is still being rolled out.

IT should answer the technical questions and collect the evidence, with input from whoever runs backups, email and training. An officer of the company usually signs. Your broker can confirm who the carrier expects to sign.

Attach what the carrier asks for, and keep the rest ready: dated exports such as MFA enrollment, EDR coverage, patch status and device encryption, screenshots of key settings, your policies and plans, and records of restore tests and exercises.

Related

From the blog

The related industry news, interviews, technologies, and resources.