Your Cyber Insurance Form Asks About MFA and Backups. Can You Prove Your Yes?

Your Cyber Insurance Form Asks About MFA and Backups. Can You Prove Your Yes?

· by IDE Solutions

Short answer: A cyber insurance questionnaire asks yes or no questions about multi-factor sign-in, backups, updates and who has admin rights. Insurers can check your answers after a claim, so a guessed yes is a risk. Look up each answer in your Microsoft 365 settings before you sign, and fix any gaps first.

When the renewal form for your cyber policy arrives, it usually lands on the desk of whoever is least able to answer it: the owner or the office manager. The questions look simple. "Is multi-factor authentication enabled for all users?" "Are backups tested?" Ticking yes takes a second, and that is exactly the problem.

A policy is a contract built on your answers. If a claim comes in and the insurer finds that one of them was wrong, the dispute is about your form, not about the attacker. This article walks through the questions that appear most often and shows where in Microsoft 365 the true answer lives. If you would rather have someone else do the checking, our Microsoft 365 security assessment produces exactly this evidence.

Quick answers

Do all cyber insurers ask the same questions? No. Each insurer uses its own form, but many start from the same template. In Germany that is the non-binding risk questionnaire of the insurance association GDV, which insurers adapt and extend.

Can I just answer yes and fix it later? It is a bad bet. The form describes the state of your systems on the day you sign, and a wrong answer can give the insurer grounds to dispute a claim. Fix first, then answer.

Who should fill in the form? The person who signs it, together with whoever runs your IT. The owner carries the contractual risk, so the owner should see the evidence behind each yes.

How long does a proper check take? For a Microsoft 365 company of 10 to 50 people, a few hours of looking at settings, if someone knows where to look.

What is the insurer really asking?

The GDV publishes a non-binding model questionnaire for cyber policies. It sorts companies into risk categories by revenue and activity and uses yes or no questions. Its own text says it is aimed mainly at external attackers. Individual insurers add their own questions on top, so your form may be longer, but the themes repeat.

Behind every question sits the same thought: could one stolen password or one lost day of data put this company out of business? The insurer wants to know how likely that is. The rest of this article follows the themes in the order they usually appear.

Is multi-factor sign-in really on for everyone?

This is the question that matters most, and the one most often answered with a hopeful yes. "We use MFA" can mean three very different things: it is switched on for every account, it is switched on for most accounts, or the owner turned it on once for themselves.

To get the true answer, open the Microsoft Entra admin center and look at the authentication methods registration report. It lists every user and whether they have registered a second factor. Then check the policy that enforces it, either Security Defaults or Conditional Access. Registered is not the same as required: a user can have a phone registered and still be allowed to sign in with a password alone.

Three groups are forgotten again and again: shared mailboxes with a sign-in enabled, service accounts used by old scanners or line-of-business software, and the owner or director who was "too busy" for the setup. Each one is an exception an insurer would not accept. Which method counts matters too. We covered the coming end of Microsoft-provided text-message codes in our article on SMS sign-in codes, and the reasons attackers get past weak second factors in the payroll phishing case.

Are your backups tested, and who can delete them?

Forms ask whether backups exist, whether they are kept separate from the main network, and whether you have tried restoring from them. The third part is where companies stumble. A backup that has never been restored is a hope, not a control.

The Microsoft 365 trap is subtler. Many owners assume Microsoft backs up their mailboxes and SharePoint files. Microsoft keeps the service running, but retention and recycle-bin rules are not a backup you control. We explain the split in who is responsible for Microsoft 365 backup. If your answer is "Microsoft does it", write down what you could actually recover, and how fast, before you tick the box.

For the on-premises side, an insurer will often ask whether a copy is offline or cannot be changed by an attacker who gets admin rights. The idea behind the 3-2-1-1-0 backup rule answers that question. Proper backup and recovery services include a restore test with a date and a result you can show.

Updates, antivirus and the devices behind the sign-in

Expect questions on patching: how quickly are security updates installed, and is anything still running that the vendor no longer supports? In Microsoft 365 companies this usually comes down to Windows, Office and the browser on every laptop, including the one the sales rep takes home.

The honest evidence is a device report, not a promise. If your laptops are enrolled in Intune, the compliance and update reports show it per device. If they are not enrolled, there is nothing to show, and "we trust people to click update" will not read well after an incident. Our article on patch management for small business describes a rhythm that fits a small team.

The same section often asks about endpoint protection. Many insurers now expect more than a free antivirus: some form of detection and response that someone actually watches. Microsoft Defender for Business covers the technology, and our overview of Defender for Business shows what it includes. The open question for the form is who reads the alerts.

How many people are administrators?

Questions about privileged access ask whether admin accounts are separate from everyday ones, and how many exist. A common finding in small tenants is five or six Global Administrators, most of whom are staff who needed one task done once, years ago.

In the Microsoft 365 admin center, filter the user list by role. Anyone with Global Administrator who also reads email on that account is a risk worth fixing. A good target for a company your size is a small number of named admins, each with a separate admin account that has no mailbox and always requires a second factor. The checklist in our Microsoft 365 hardening guide covers this step by step.

Can you show that staff were trained and a plan exists?

Two questions are about people and paper. Has staff received security awareness training, and do you have an incident response plan that someone has read? Neither is technical, yet they are the ones with the lowest bar to clear and the highest rate of "no".

A plan does not need thirty pages. One page is enough if it answers who decides, who calls the insurer, who calls the IT partner, and where the phone numbers are kept when email is down. Keep a copy outside Microsoft 365. Many policies also require you to report an incident to the insurer within a stated time, so know where that number is before you need it. Writing this down is part of governance and compliance work, and the same page often helps with customer security questionnaires.

A one-hour check before you sign

You do not need to run a full audit to get most of the value. Work through this list with whoever runs your IT and keep a screenshot for each line:

  • The authentication methods report shows a registered second factor for every user, shared and service accounts included.
  • A policy requires that second factor, and you know which accounts are excluded and why.
  • The last successful restore test has a date, a scope and a result.
  • At least one backup copy cannot be changed or deleted with a normal admin login.
  • Every laptop appears in a device report, and none runs an unsupported version of Windows or Office.
  • The list of Global Administrators is short, named and reviewed.
  • A one-page incident plan exists, including the insurer's reporting number.

Every line you cannot tick is a line to fix, or to answer honestly with a date for when it will be done. Many insurers accept "in progress, finished by March" better than a yes that later turns out to be false. Ask your broker how the insurer treats that wording.

What about answers that are only partly true?

The hardest cases are the ones in between. MFA is on for 18 of 20 users. Backups run nightly but nobody has restored from them. The honest move is to treat a partly true yes as a no, fix the gap, and then answer yes with evidence on file.

If the form leaves room for comments, use it. A sentence such as "MFA enforced for all users except two service accounts, scheduled for replacement" is far safer than a plain yes. If the form allows only yes or no, ask your broker in writing how to answer, and keep the reply. That email is part of your paper trail.

Cost is a fair concern, and we do not promise that fixing these points lowers your premium. What we can say from the tenants we look after: the fixes above are mostly configuration work, not new licences, and one afternoon of settings cleanup removes most of the findings an insurer would care about.

Get your insurance answers checked before you sign

We review your Microsoft 365 tenant against the questions insurers ask and hand you a short report: what is true today, what is not, and what to fix first. You sign the form knowing every yes has a screenshot behind it.

If the review turns up gaps, our cloud security team can close them in the same engagement, and day-to-day care of the tenant can follow through Microsoft 365 management.

This article was drafted with AI assistance and reviewed, edited and approved by IDE Solutions before publication. More in our Impressum.

More Articles