SOC 2 and ISO 27001Published Last reviewed November 20268 min read
Short answer
Cyber insurance applications usually ask about MFA on email, remote access and admin accounts, endpoint detection and response, offline or immutable backups, email filtering, privileged access, patching, an incident response plan and security awareness training. In Microsoft 365, back each answer with dated evidence: Conditional Access policies and Entra reports, the Defender device inventory, Microsoft 365 Backup policies, Defender for Office 365 settings, PIM, Intune update reports and training records.
Check where you stand: take the cyber insurance renewal check. About two minutes, no email needed.
Update, November 2026
Microsoft’s retirement page now lists February 1, 2027 for most users and July 1, 2027 for Global Administrators and external users as the dates Microsoft provided SMS and voice authentication retire, and since October 30, 2026 organizations that still need those methods can configure a telephony provider through Microsoft Security Store. In one tenant, Ethereum Tech raised Microsoft Secure Score from 28% to 68% in six weeks; your starting point and timing will differ.
A cyber insurance renewal is a set of yes or no questions about your security controls, and every yes should point to something you can show. For a business on Microsoft 365, most of that proof already sits in Entra, Intune, Defender and the Microsoft 365 admin center. The work is pulling it together before you sign, and answering no, or not yet, where the evidence is thin.
What security controls do cyber insurance applications ask about?
Most applications ask about the same short list: multifactor authentication on email, remote access and admin accounts, endpoint detection and response, backups kept offline or immutable, email filtering, privileged access, patching, an incident response plan and security awareness training. The wording changes from one application to the next. The controls rarely do.
The list tracks federal guidance. CISA’s #StopRansomware Guide tells organizations to implement phishing resistant MFA for all services, use EDR or application allowlisting on all assets, maintain offline, encrypted backups of critical data, create and regularly exercise an incident response plan, and prioritize patching of known exploited vulnerabilities. CISA’s Known Exploited Vulnerabilities (KEV) catalog is the list it recommends for setting those patch priorities. If your controls follow that guidance, most of the application becomes documentation.
Watch for questions about MFA methods, not just MFA. Microsoft made passkeys the default sign in experience in Entra ID starting September 1, 2026, and has announced the retirement of Microsoft provided SMS and voice authentication starting February 1, 2027. If text messages are still your main second factor, say so and show the plan to move off them.
What Microsoft 365 evidence answers each insurance question?
Pair every question with a report or setting you can export, with a date on it. Exports beat screenshots, because exports show scope. This is the map we use:
| Application question | Where the evidence lives | What to export |
|---|---|---|
| MFA on email | Conditional Access policy requiring MFA for all users, plus a policy blocking legacy authentication | Policy settings with assignments and exclusions; the Authentication methods activity usage view |
| MFA on remote access | Conditional Access policy on the VPN or remote access app, if it signs in through Entra ID | Policy settings and sample sign in log entries, or the VPN vendor’s MFA settings |
| MFA on admin accounts | Conditional Access policy requiring phishing resistant authentication strength for admin roles | Policy settings and an export of role assignments |
| Endpoint detection and response | Defender for Business or Defender for Endpoint device inventory | Onboarding status and sensor health for every device, compared with Intune |
| Offline or immutable backups | Microsoft 365 Backup policies, plus whatever protects servers and other systems | Policy scope, recovery window and a restore task record |
| Email filtering | Defender for Office 365 preset security policies and configuration analyzer | Preset policy assignments, the analyzer comparison, and SPF, DKIM and DMARC records |
| Privileged access | Privileged Identity Management and the Global Administrator list | Eligible and active assignments and PIM audit history |
| Patching | Intune Windows update reports and Defender Vulnerability Management | Quality update status and a weaknesses export checked against the KEV catalog |
| Incident response plan | Outside Microsoft 365, supported by Purview Audit and Defender incidents | Dated plan, tabletop notes and proof that auditing is on |
| Security awareness training | Attack simulation training or your training platform | Training completion by user |
Licensing shapes what you can show. Microsoft 365 Business Premium includes Defender for Business with EDR, Entra ID P1 and Defender for Office 365 Plan 1. Privileged Identity Management needs Entra ID P2, Attack simulation training needs Defender for Office 365 Plan 2 or Microsoft 365 E5, and the Authentication methods activity report needs Entra ID P1 or P2. Without a license, the evidence has to come from somewhere else, such as a role assignment export and a documented approval process for admin access.
How do you avoid answering yes to something you cannot prove?
Read each question for its scope words, such as all, every and including, and answer only what your evidence covers. Most wrong answers are not lies. They are true statements about most of the environment, written as if they covered all of it.
Across the 200+ Microsoft 365 and Azure tenants we work in, these gaps come up most:
- MFA registered but not required. The user registration details report shows who is MFA capable. It does not prove a policy forces MFA. The usage view, which splits sign ins by single factor and multifactor requirement, is closer to proof.
- Exclusions in Conditional Access. Service accounts, shared mailboxes and emergency access accounts are often excluded. Emergency accounts are a legitimate exclusion, but list them and explain how they are protected.
- Legacy authentication left open. Microsoft notes that legacy protocols do not support MFA, which is why attackers use them to get around it. A tenant that requires MFA but still allows IMAP or POP sign ins cannot claim MFA on all email access.
- EDR on laptops but not servers. Compare the Defender device inventory with your Intune and server lists, and filter for devices that can be onboarded or have inactive sensors.
- Backups that do not match the question. Microsoft 365 Backup covers SharePoint, OneDrive and Exchange. Microsoft describes its storage as append only and says backups are immutable unless a Backup admin deletes them through offboarding, with a 90 day grace period. That is a strong answer for those workloads and says nothing about a line of business server or an accounting database.
When the honest answer is mostly, answer accurately and attach a short note: what is covered, what is not, and when the gap will close.
Why is an inaccurate answer on a cyber insurance application a risk?
Because the insurer relies on the application when it issues the policy, and a claim is when those answers get tested. If an investigation after an incident shows a control was not in place as described, the insurer may dispute the claim, and in some cases may try to rescind the policy.
Incidents produce their own evidence. Entra sign in logs show whether MFA was satisfied for the session an attacker used, the Defender portal shows whether the affected device was onboarded, and the Purview audit log shows what happened in the mailbox. We have run a full Microsoft 365 incident response for an adversary in the middle session token theft, an attack that steals a session after the user has completed MFA. In a case like that, the logs show exactly which protections applied, so your application answers and your logs should tell the same story.
This is not legal advice. Ask your broker how your policy treats the application, and bring in counsel if a question is ambiguous.
How should a small or midsize firm build the evidence pack before renewal?
Get the application early, give every control question an owner and an evidence source, fix the quick gaps, and export everything with dates into one folder. The same pack serves SOC 2 and ISO 27001 auditors, who ask for much of the same evidence.
- Ask your broker for the renewal application as early as you can and list every control question.
- Map each question to the evidence in the table above and name one owner.
- Export Conditional Access policies with their assignments and exclusions, the user registration details report, the Defender device inventory and the configuration analyzer results.
- Fix what you can before answering, such as blocking legacy authentication or onboarding missing devices, then export again.
- Run a restore test from your backups and keep the restore task record.
- Hold a tabletop exercise against your incident response plan. NIST SP 800-61 Rev. 3, published in April 2025, ties incident response to the NIST Cybersecurity Framework 2.0 and is a sound reference for the plan.
- Write short, factual notes for partial answers and have an executive review the application before signing.
Microsoft Secure Score history is useful context, though it measures configuration rather than answering any single question. Our post on Microsoft Secure Score for small businesses explains how to read it. Our cyber insurance evidence service builds this pack, and a Microsoft 365 security assessment finds the gaps before an underwriter does.
If your renewal is coming up, book a 30 minute call and we will go through your application questions against what your tenant can actually show.
Frequently asked questions
Will a strong Microsoft Secure Score satisfy an underwriter?
Rarely on its own. Secure Score measures how many recommended settings are turned on, while an application asks about specific controls and their scope. Include your Secure Score history as context if it helps, but answer each question with the policy, report or export that proves that particular control.
Do Microsoft 365 retention policies count as backups?
Not by themselves. Retention policies, versioning and the recycle bin help recover content, but Microsoft recommends evaluating Microsoft 365 Backup or a partner solution built on its Backup Storage platform for fast, bulk recovery after ransomware. Describe exactly what you have rather than calling retention a backup on the application.
Does Microsoft 365 Business Premium include endpoint detection and response?
Yes. Business Premium includes Microsoft Defender for Business, which provides endpoint detection and response, next generation protection and automated investigation for organizations with up to 300 users. Servers need the Defender for Business Servers add on or another server product, so confirm servers appear in the device inventory before answering.
What if we cannot meet a control by the renewal date?
Answer accurately and explain. A short note that states what is in place, what is missing and when it will be finished is better than a yes you cannot support. Ask your broker whether compensating controls are accepted, and keep evidence of progress for the midterm review or the next renewal.
Does security awareness training need phishing simulations?
Applications usually ask whether training happens and how often, and some ask about phishing simulations too. Attack simulation training in Defender for Office 365 Plan 2 or Microsoft 365 E5 provides both, with completion reports by user. NIST SP 800-50 Rev. 1 is a useful guide for designing the training program itself.