trio.so
Templates

Cyber Insurance Requirements: Checklist of Device Controls

Cyber insurance requirements, control by control: what insurers ask about MFA, EDR, patching and encryption, and the evidence to attach. Free checklist.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on

Cyber insurance requirements are the security controls an insurer expects you to have before it quotes, binds or renews a policy. They arrive as questions on the application or the renewal questionnaire: is MFA on for email and remote access, is EDR on every endpoint, how many days do critical patches take, are laptops encrypted, are backups offline and tested. Your answers feed the underwriting decision, and they matter again if you ever make a claim.

This checklist covers 14 controls that insurers commonly ask about. For each one you get what insurers ask, what a good answer usually looks like and the evidence to attach. Carriers set their own bar, so treat the targets as common examples. Check your carrier's actual questionnaire and talk to your broker. The free download has the checklist as a PDF and an editable Word file, plus an Excel tracker that flags answers your evidence doesn't support.

In short

  • Insurers ask about the controls that stop common attacks: MFA, EDR, patch timing, encryption, admin rights, backups, remote access and a few more.
  • "Yes" usually means every user, device or system in scope. Below 100%, the honest answer is "Partial", with the gap and a fix date.
  • Collect dated evidence for every answer: exports, screenshots of settings, policies and test records.
  • Start four to eight weeks before renewal, so there is time to close gaps instead of describing them.

What Insurers Require and Why

Most of what insurers ask maps to how attacks start: stolen passwords used on email or remote access, unpatched systems facing the internet, ransomware that spreads through admin rights, and backups that get encrypted along with everything else. CISA's #StopRansomware Guide recommends the same controls insurers ask about. It calls for phishing-resistant MFA on email, VPNs and accounts that reach critical systems, offline encrypted backups that are tested, an incident response plan that has been exercised, and closing unused ports such as RDP.

The questions come in a few forms: a short application for smaller companies, a longer one above a size threshold, and supplements on single topics. Travelers, for example, lists a separate Multi-Factor Authentication Supplement next to its CyberRisk application. At renewal you usually answer again, and the bar may have moved since last year.

Insurers rely on the answers when a loss happens. In Travelers v. International Control Services (2022), the insurer said the company's application described MFA that in fact only protected its firewall. After a ransomware attack, the two sides agreed the policy was void from the start.

If you are still choosing coverage, start with our guides to cyber liability insurance and cybersecurity insurance. The FTC's small business guidance also lists what a policy should cover, from breach response costs to attacks on data held by your vendors.

The Cyber Insurance Checklist at a Glance

ControlWhat insurers checkEvidence to attach
Multi-Factor AuthenticationMFA on email, remote access, admin accounts and cloud appsMFA enrollment report, sign-in policy
EDR and Endpoint ProtectionEDR on all endpoints and servers, alerts reviewedEDR device export vs inventory count
Patch TimingCritical patches applied within the stated daysPatch report, open critical CVEs with age
Full-Disk EncryptionDisk encryption on laptops and phonesDevice list with encryption status
Admin Rights and Least PrivilegeNo local admin for users; separate admin accountsLocal admin list, privileged account review
BackupsOffline or immutable backups, restore testedRestore test record, backup job report
Device InventoryHardware and software inventory kept currentDated inventory export
Email SecurityEmail filtering and DMARC in placeDMARC record, filtering policy
Security Awareness TrainingSecurity training and phishing tests, trackedCompletion report, phishing results
Incident Response PlanWritten incident response plan, tested yearlyPlan with version date, tabletop record
End-of-Life SystemsNo unsupported OS or software, or a registerOS version report, EOL register
Remote Access and RDP ExposureNo internet-facing RDP; MFA on remote accessExternal port scan, firewall rules
Vendor and Third-Party AccessVendor access limited, MFA-protected and reviewedVendor access list, review date
Logging and AlertingCentral logs kept and alerts reviewedRetention settings, alert review records
Evidence per control: exports and reports for device controls, documents and test records for plans and backups
Evidence per control: exports and reports for device controls, documents and test records for plans and backups

Control by Control: What to Ask, Target and Attach

Values in brackets are examples. Replace them with what your carrier asks for and what your tools can do.

1. Multi-Factor Authentication

Questionnaires often split MFA into separate questions: email, remote access, privileged accounts, cloud apps and sometimes the backup console. Each needs its own honest answer. The usual gaps are service accounts, shared mailboxes, break-glass admin accounts and legacy mail protocols that skip MFA (IMAP, POP and basic SMTP authentication), so list those before the form asks. Our MFA guide compares the methods.

  • What insurers ask: Is MFA enforced for email, for every remote access path, for privileged and admin accounts, and for cloud apps? For all users, or some?
  • What good usually looks like: MFA on for every user's email and cloud apps, every VPN or remote desktop gateway, and every admin account, with phishing-resistant methods (security keys, passkeys) for admins.
  • Evidence to attach: An MFA enrollment report from your identity provider by user; the sign-in policy that requires MFA; a list of excluded accounts with the reason for each.

2. EDR and Endpoint Protection

Insurers ask for EDR because antivirus matches known files, while EDR records process behavior and lets someone investigate and contain a device. Expect two follow-ups: does it cover every endpoint and server, and who responds at night and on weekends. Coalition's 2025 guidance for small businesses notes that EDR tools are often deployed but not configured properly, so coverage and configuration both count. If you are deciding between running EDR yourself and buying a service, see EDR vs MDR.

  • What insurers ask: Is endpoint detection and response deployed on all endpoints and servers? Who reviews its alerts, and outside business hours?
  • What good usually looks like: EDR on every laptop, desktop and server, with alerts reviewed by a named person, team or managed detection and response (MDR) provider around the clock.
  • Evidence to attach: An EDR console export of protected devices next to your device inventory count; the MDR contract or on-call rota.

3. Patch Timing

Patch questions ask for a number of days, so decide on one. A common choice is 14 days for critical patches and faster for vulnerabilities in CISA's Known Exploited Vulnerabilities (KEV) catalog. CISA and Coalition both put internet-facing systems first: VPN appliances, firewalls and anything else reachable from outside. A patch that has downloaded but waits for a restart is still open. The patch management policy template sets the timelines in writing.

  • What insurers ask: How many days does it take to apply critical and high-severity patches? Are internet-facing systems patched first?
  • What good usually looks like: Critical patches applied within [14] days, and known exploited vulnerabilities (CISA KEV) and internet-facing systems faster, for example within [7] days.
  • Evidence to attach: A patch report showing each device's status; the list of open critical vulnerabilities with their age; your patch policy.

4. Full-Disk Encryption

Encryption is one of the easier answers to prove, because the operating system reports it. The question usually covers laptops and mobile devices; some forms add removable media and backups. Desktops in a locked office or servers in a data center may be out of scope, but say so instead of ticking Yes. Store recovery keys centrally, or a forgotten PIN turns into lost data. Our guide to full-disk encryption covers BitLocker, FileVault and phones.

  • What insurers ask: Are laptops and mobile devices encrypted? What about removable media and backups?
  • What good usually looks like: BitLocker on every Windows laptop, FileVault on every Mac, encryption on every phone that holds company data, and recovery keys stored centrally.
  • Evidence to attach: A device list export with an encryption status column; the encryption policy; the count of unencrypted devices and why.

5. Admin Rights and Least Privilege

Admin rights let ransomware switch off security tools and move to other machines. Insurers ask whether everyday users are local administrators, whether IT uses separate admin accounts, and how many privileged accounts exist. CISA's guide recommends separate administrator accounts used only for admin work. Count service accounts and the built-in local administrator in your answer. The access control policy template puts these rules in one document.

  • What insurers ask: Do users have local admin rights on their devices? Are admin accounts separate from everyday accounts? How many privileged accounts exist?
  • What good usually looks like: No standing local admin for users, separate named admin accounts for IT, and a privileged account list reviewed [every quarter].
  • Evidence to attach: A list of local administrator accounts per device; the privileged accounts in your directory with owners; the last access review record.

6. Backups

Backups are how you recover if ransomware encrypts your systems, and CISA notes that most ransomware actors try to find and delete or encrypt backups they can reach. That is why the question asks where backups live as well as whether you have them. Write down every restore test with the date, the system, how long it took and whether it worked; that record is the evidence. Our backup and recovery policy template covers retention and testing.

  • What insurers ask: Are backups kept offline, immutable or otherwise out of reach of the main network? Are they encrypted? When did you last test a restore?
  • What good usually looks like: 3-2-1 copies with at least one offline or immutable, backup consoles behind MFA, and a restore test [every quarter] with the result written down.
  • Evidence to attach: A backup job report; the last restore test record (date, system restored, time taken); a screenshot of MFA on the backup console.

7. Device Inventory

You can't answer coverage questions without a device count. If the inventory lists 140 devices and the EDR console shows 128, the EDR answer is Partial until the other 12 are found. An inventory fed by your device management tool stays current; a spreadsheet updated by hand falls behind.

  • What insurers ask: Do you keep an up-to-date inventory of hardware and software? How do you find devices that aren't managed?
  • What good usually looks like: Every device listed with owner, serial number, OS version and installed software, fed by your management tool rather than typed by hand.
  • Evidence to attach: An inventory export with its date; the device count compared with your EDR and backup counts.

8. Email Security

Coalition's 2025 list for small businesses has protecting email accounts as its own action, and CISA's guide recommends DMARC. Expect questions on gateway filtering, attachment handling, external sender tags and DMARC. A DMARC policy of p=none only reports; quarantine or reject is what stops spoofed mail from your domain.

  • What insurers ask: Do you filter inbound email for malicious links and attachments? Are SPF, DKIM and DMARC set up? Do you mark external email?
  • What good usually looks like: Gateway filtering with risky attachment types blocked or held, external mail tagged, and DMARC at quarantine or reject.
  • Evidence to attach: Your DMARC record; a screenshot of the mail filtering policy; the attachment types you block.

9. Security Awareness Training

Insurers ask how often people are trained and whether you can prove it. Track completion per person and keep the phishing simulation results; most training platforms export both. New starters are the usual gap, so train people when they join instead of waiting for the next annual cycle.

  • What insurers ask: Do employees get security awareness training and phishing simulations? How often, and do you track completion?
  • What good usually looks like: Training at hire and [every year], phishing simulations [every quarter], and completion tracked per person.
  • Evidence to attach: A training completion report; phishing simulation results; the training schedule.

10. Incident Response Plan

The plan should name who decides, who calls the insurer, which outside firms you'll use and how you reach them if email is down. Check whether your policy requires you to use the insurer's incident response panel or to call its hotline first, and put that number in the plan. CISA recommends exercising the plan and keeping a printed copy. Our data breach response plan and incident report template cover the documents.

  • What insurers ask: Do you have a written incident response plan? When was it last tested, and does it include the insurer's notification steps?
  • What good usually looks like: A written plan with roles, contacts and the insurer's breach hotline, a tabletop exercise [every year], and a printed copy kept offline.
  • Evidence to attach: The plan with its version date; the last tabletop exercise record and its actions.

11. End-of-Life Systems

Unsupported systems no longer get security fixes. Windows 10 support ended on October 14, 2025, so a Windows 10 machine without Extended Security Updates now counts. If you can't retire a system, for example a PC that drives a plotter or a machine controller, list it with how it is isolated and when it will be replaced, and disclose it in the answer.

  • What insurers ask: Do you run operating systems or software that no longer get security updates? If so, how are they isolated?
  • What good usually looks like: No unsupported systems, or a short register of each one with its isolation, compensating controls and retirement date.
  • Evidence to attach: An OS version report across devices; the end-of-life register with compensating controls.

12. Remote Access and RDP Exposure

Insurers ask about RDP directly because anyone can check it from the outside, and CISA's guide tells organizations to turn off unused ports and protocols such as RDP on TCP port 3389. Check with an external port scan or your firewall's NAT rules. Remote support tools that stay installed and running count as remote access too.

  • What insurers ask: Is Remote Desktop Protocol (RDP) reachable from the internet? How do staff and vendors connect remotely, and is MFA on every path?
  • What good usually looks like: No RDP open to the internet; remote access only through a VPN or gateway with MFA; unused remote access tools removed.
  • Evidence to attach: An external port scan showing port 3389 closed; a firewall rule export; a screenshot of MFA on the VPN or gateway.

13. Vendor and Third-Party Access

Your MSP and software vendors can have more access than most employees. Insurers ask whether that access uses named accounts with MFA, whether it is limited to when it's needed, and whether you review it. On the coverage side, the FTC suggests checking that a policy covers attacks on your data held by vendors and other third parties. The vendor management policy template covers reviews and contract terms.

  • What insurers ask: Do vendors or an MSP have remote access to your systems? Is that access limited, protected by MFA and logged? Do you check vendors' security?
  • What good usually looks like: Named vendor accounts with MFA, access granted only when needed, a quarterly review of who has access, and contracts that require breach notification.
  • Evidence to attach: The vendor access list with the last review date; contract clauses on security and notification; vendor security questionnaires.

14. Logging and Alerting

Logs answer the first questions after an incident: what happened, when and on which systems. Insurers ask whether you collect logs centrally, how long you keep them and whether anyone reviews the alerts. CISA's guide recommends centralized log management. Pick a retention period your tools can hold and write it down.

  • What insurers ask: Do you collect security logs centrally? How long do you keep them, and who reviews the alerts?
  • What good usually looks like: Logs from identity, endpoints, firewalls and email kept centrally for [90 days to 12 months], with alerts reviewed by a named person or provider.
  • Evidence to attach: A screenshot of log retention settings; a sample of alert review records; the SIEM or log tool's source list.

How to Answer the Questionnaire

Answer for the scope the question names: "all endpoints" means servers too, and "all users" includes service and shared accounts. If coverage is below 100%, write "Partial" with the percentage, what is missing, the compensating control and the date it will be fixed. Answer with what is in place on the day you sign, not with a rollout that finishes next month, and keep a copy of everything you send.

Our guide on how to answer a cyber insurance questionnaire goes question by question through the device section, with example wording for partial answers, the evidence to attach, the common mistakes and who should sign.

Cyber Insurance Readiness Checklist (Free Download)

The checklist PDF: cover, a control page with the answer form, and the filled-in example
The checklist PDF: cover, a control page with the answer form, and the filled-in example
  • PDF checklist (Cyber-Insurance-Readiness-Checklist-trio.so.pdf): a one-page summary, a page per pair of controls with what insurers ask, a target example, the evidence to attach and a place to record your answer, eight answering tips and a filled-in example.
  • Word checklist (Cyber-Insurance-Readiness-Checklist-trio.so.docx): the same content with fillable fields and tick boxes.
  • Excel evidence tracker (Cyber-Insurance-Evidence-Tracker-trio.so.xlsx): a Controls tab that flags a Yes below 100%, missing evidence, evidence older than 90 days and overdue reviews, and an optional Devices tab that computes encryption, patch and EDR coverage from a device export. Formulas only, no macros.
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

The example company, Example Co (fictional), is an 85-person design firm a month from renewal. It answered 10 controls Yes, 3 Partial and 1 No. The tracker marks 8 rows to fix before anyone signs. The EDR, patch and encryption rows say Yes while the device list shows 89%, 75% and 91% coverage. Two evidence files are older than 90 days, and the email row has no evidence file. MFA at 92%, a Windows 10 plotter PC and a vendor's shared login are marked as gaps to disclose.

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.
  • BitLocker and LUKS recovery keys stored in the console.
  • 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.
  • Policy status for each device: applied, failed or pending.
  • A Microsoft Defender Antivirus policy for Windows, each Windows device's antivirus and signature status, and an alert when a device reports its anti-malware turned off.
  • The Microsoft Defender for Endpoint integration, which shows Defender's devices and their open alerts next to each trio.so device record.
  • 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.
  • A data streamer that sends trio.so data to Splunk, Datadog, Microsoft Sentinel or Elastic.

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

Export this evidence from your own devices

trio.so enforces disk encryption on laptops and phones, shows patch findings with CVSS, EPSS and KEV, keeps an inventory with owner, serial and OS version, and exports the device list to CSV for your questionnaire.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions

MFA on email, remote access and admin accounts; EDR on endpoints and servers; critical patches applied within a set number of days; disk encryption on laptops and phones; no local admin rights for everyday users; offline or immutable backups with tested restores; an incident response plan; and no RDP exposed to the internet. Many questionnaires also ask about email filtering, training, end-of-life systems, vendor access and logging.

Many applications ask whether EDR covers every endpoint and server and who responds to its alerts, and some carriers treat it as a condition for cover. Antivirus alone may only count as a partial answer. Requirements differ by carrier and company size, so check your carrier's questionnaire and ask your broker how they define EDR.

There is no single number. Questionnaires usually ask how many days you take, and 14 or 30 days for critical patches are common answers, with known exploited vulnerabilities and internet-facing systems handled faster. State the number your patch report supports, and keep the report.

Most questionnaires ask about MFA on email, on every remote access path, on privileged and admin accounts and on cloud apps, as separate questions. Some also ask about MFA on the backup console. Answer each one for every account it covers, including service accounts and shared mailboxes.

Most carriers rely on your signed answers, but some ask for proof or check from the outside, and after a claim the evidence matters most. Keep dated exports and reports from your systems (MFA enrollment, EDR coverage, patch status, device encryption), screenshots of key settings, your policies and plans, and records of restore tests and tabletop exercises.

That depends on the policy and the law that applies, so ask your broker or a lawyer. Insurers rely on the application, and a material misstatement can affect a claim or the policy itself. In Travelers v. International Control Services (2022), the parties agreed the policy was void after the insurer said the MFA answers were inaccurate.

No. A checklist like this one helps you gather answers and evidence before the questionnaire arrives. The carrier's form decides what is asked, how it is worded and how the answers are scored, so always answer the actual questionnaire and check unclear questions with your broker.

Related

From the blog

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