We value your privacy

We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking "Accept All", you consent to our use of cookies.

Powered by
    BisGentech logo
    AI & Technology Assessment
    AI & Technology Assessment
    Back to Insights

    Cybersecurity & Resilience

    What Cybersecurity Insurers Are Asking in 2026

    Cybersecurity insurers increasingly ask for evidence of specific controls before issuing or renewing coverage. Learn what underwriters commonly review and how a small or growing business can prepare.

    Benjamin IsidoreNovember 16, 20269 min read

    A decade ago, a cybersecurity insurance application might have asked a handful of general questions. In 2026, many applications read more like a security questionnaire, with specific questions about multifactor authentication, endpoint protection, backups, and incident response. For a growing business, understanding what is being asked, and why, can make the difference between a smooth renewal and a difficult one.

    This article describes controls that cybersecurity insurers commonly review. It is not a guarantee of coverage, and it is not a substitute for reading your own application or speaking with a licensed insurance broker. Insurer requirements vary, and the only authoritative source for what a specific policy requires is the insurer issuing it.

    Why cybersecurity controls influence underwriting

    Insurers price coverage based on the likelihood and severity of a claim. Many cyber claims trace back to a small number of causes: compromised credentials, ransomware, business email compromise, and failed or incomplete backups. When a business can show it has reduced exposure to these common causes, an insurer has more confidence in the risk it is taking on.

    This is why underwriting has moved toward evidence rather than assertions. A question that once asked whether your business was secure now asks specifically whether multifactor authentication is enforced on email, remote access, and administrator accounts, and whether backups have been tested. Published insurer application forms illustrate the shift: carriers such as Beazley and Chubb ask separately about MFA on remote access, web-based email, and privileged or domain administrator accounts, and request the percentage of endpoints covered by endpoint detection and response rather than a simple yes or no. The specific questions vary by carrier and policy, but the direction, from assertion to evidence, is consistent across the market.

    Multifactor authentication and privileged access

    Multifactor authentication (MFA) is among the most consistently reviewed controls. CISA recommends MFA as a high-impact step that can block many common attacks, and its Cybersecurity Performance Goals 2.0 (CPG 2.0) identify phishing-resistant MFA as a priority practice.

    Insurers commonly ask whether MFA is enforced, not merely available, across email, remote access, cloud services, and administrative accounts. A frequent problem is incomplete coverage: MFA enabled for most employees but not for a legacy administrator account or a remote-access method. Those exceptions can become the entry point an attacker uses, and they can also become the reason a claim is later questioned.

    Privileged accounts, the accounts that can change system settings or access large amounts of data, often receive particular scrutiny. An insurer may ask how administrative access is granted, monitored, and revoked when someone leaves.

    Endpoint security and monitoring

    Insurers increasingly look beyond traditional antivirus toward endpoint detection and response (EDR), software that watches device behavior for signs of an active attack rather than matching only known malware signatures. Some carriers ask what percentage of the endpoint fleet is covered by EDR or a comparable monitored service, and partial or incomplete coverage can trigger conditions or sublimits. This is a common expectation, not a universal mandate; whether EDR is required, and at what coverage level, depends on the carrier, the coverage limit, and the business's risk profile.

    For a small business without dedicated security staff, this expectation is often met through a managed service that provides monitoring and alert response. The key point for underwriting is that someone is responsible for noticing and acting on an alert, not only that a tool is installed.

    Backup protection and recovery testing

    Backups are judged on both design and proven recovery. A common baseline is the 3-2-1 model: three copies of data, on two different media types, with one copy stored offsite. Offsite storage protects against site-level failures, but it is not the same as protection from ransomware. Insurers may separately ask whether backups are protected from ransomware through immutable or offline copies that an attacker cannot encrypt or delete, a distinct safeguard that complements rather than replaces offsite storage.

    Testing matters as much as architecture. A backup that has never been restored provides little evidence that recovery would work during a real incident, so insurers commonly ask for restoration test records.

    Incident response planning

    A written incident response plan tells an insurer that a business has thought through what it would do during an incident, not only how it would try to prevent one. CISA's CPG 2.0 include practicing incident response plans to maintain and improve them, and reporting known incidents to CISA and other required parties within applicable time frames.

    A practical plan for a growing business does not need to be elaborate. It should identify who leads the response, how to contain an incident, how to communicate internally and with affected parties, and how to preserve evidence. Reviewing the plan periodically, and after any real incident, is more valuable than writing it once.

    Vendor and third-party risk

    Many incidents begin through a vendor, supplier, or technology provider rather than a direct attack on the business. Insurers may ask how the business evaluates third-party risk, whether critical vendors have their own security commitments, and what happens to data when a vendor relationship ends.

    If your business is working through how to assess vendor risk, the BisGentech vendor-risk articles walk through where blind spots commonly appear and what a vendor-risk assessment should tell you.

    If you are not sure where sensitive data is shared with third parties, the Sensitive Data Discovery Checklist can help you identify the locations before you answer underwriting questions about data handling.

    Security questionnaires and supporting evidence

    Common supporting documents include MFA configuration records, backup and restoration test reports, an incident response plan, security awareness training records, and a list of administrative accounts and their access.

    One of the most important points is accuracy. Answering a security questionnaire inaccurately, whether by overstatement or omission, can put coverage at risk after a claim, depending on the policy and the facts. If a control is only partially implemented, it is better to say so than to assert it is fully in place.

    This is not a theoretical risk. In a 2022 federal case, Travelers Property Casualty Company of America sought to rescind a cyber insurance policy issued to International Control Services, Inc. (ICS) after a ransomware attack, alleging that ICS had misrepresented the extent to which it used multifactor authentication on its application. The parties stipulated to a court order rescinding the policy and declaring it void from inception. The case illustrates how an inaccurate application answer, not just the breach itself, can determine whether coverage exists. It is one example, not a universal rule, and outcomes depend on the policy language and the specific facts.

    Practical preparation steps

    • Review the current policy and application before renewal so there are no surprises about what is being asked.
    • Confirm where MFA is enforced and identify any exceptions, legacy accounts, or shared accounts.
    • Verify endpoint protection is deployed and that someone is responsible for responding to alerts.
    • Check that backups follow a 3-2-1 model with one offsite copy, include an immutable or offline copy where ransomware is a concern, and have a recent, documented restore test.
    • Update or write a simple incident response plan and review it with the people who would carry it out.
    • Gather supporting evidence in advance rather than assembling it under renewal pressure.
    • Answer every question accurately; when a control is partial, describe it honestly.

    Common practices, not universal requirements

    The controls described here reflect common underwriting practices, not a universal checklist. No federal law requires every small business to carry cybersecurity insurance, and there is no single set of requirements every insurer applies. Client contracts, state breach-notification laws, and sector-specific rules can make coverage effectively necessary for some businesses, but the specific controls a policy requires depend on the insurer, the policy, and the business's risk profile.

    The NIST Cybersecurity Framework (CSF) 2.0 and CISA's CPG 2.0 provide a common language for many of these controls. Aligning your program with them does not guarantee coverage or a specific premium, but it can make it easier to answer underwriting questions consistently and to show that your security program is intentional.

    If you are working through how to prioritize practical cybersecurity steps for your business, the AI & Technology Assessment is a structured way to clarify your current position and identify the next steps that matter most.

    Key Takeaways

    • Cybersecurity underwriting increasingly asks for evidence of specific controls, not general assertions of security.
    • MFA, endpoint protection, tested backups, and a written incident response plan are among the controls insurers commonly review.
    • Incomplete MFA coverage and untested backups are frequent gaps that can affect both underwriting and claims.
    • Answering questionnaires accurately matters; misrepresentation can put coverage at risk after a claim, as illustrated by the 2022 Travelers v. ICS rescission case.
    • These are common practices, not universal requirements; specific controls depend on the insurer, policy, and business risk profile.

    Sources and References

    1. CISA — Cybersecurity Performance Goals 2.0 (CPG 2.0, October 2025 update aligning to NIST CSF 2.0) (source)
    2. NIST — Cybersecurity Framework (CSF) 2.0 (source)
    3. CISA — Require Multifactor Authentication (MFA guidance) (source)
    4. NIST — Small Business Cybersecurity (source)
    5. Lockton — Travelers v. ICS underscores need to respond carefully to cyber insurance application questions (2022) (source)
    6. Beazley — Cyber insurance application (MFA on remote access, email, and privileged accounts) (source)
    7. Chubb — Cyber ERM proposal form (EDR coverage percentage, offline backups, MFA second-factor definition) (source)

    About the Author

    Benjamin Isidore

    Founder & CEO, BisGentech

    Benjamin Isidore is the Founder and CEO of BisGentech. He helps growing small and medium-sized businesses clarify technology decisions, improve operations, and strengthen security with practical, business-first guidance built on more than 24 years of technology leadership.