Security 101

Why Don’t Vulnerability Scanners Find Microsoft 365 Misconfigurations?

Vulnerability scanners look for software flaws. Much of Microsoft 365 risk sits in settings, and in the paths between them.

Vulnerability scanners compare software versions with published flaws, and most Microsoft 365 exposure sits in settings instead. A Conditional Access exclusion or legacy authentication left switched on carries no CVE, so a scanner has nothing to match it against.

Accelerynt’s Microsoft Control Validation Assessment checks those settings in your live tenant, along with your external attack surface and the attack paths between them. The Accelerynt Security Platform repeats the check on a schedule your team sets.

What scanners miss

  • Scanners find software flaws. They match installed versions against published vulnerabilities and rate each one by severity.
  • Settings carry no CVE. A standing admin role or a risky app consent setting is a configuration choice.
  • The risk sits in the chain. A minor setting becomes critical when it connects to another gap.
  • You need both. Keep scanning for patches, and validate configuration alongside it.

What do Microsoft 365 misconfigurations look like?

These patterns sit in identity, access and collaboration settings, which is exactly where a version check never looks.

Legacy authentication left on

Legacy protocols do not support multifactor authentication. On any account where they stay enabled, a password is enough to sign in.

Standing admin roles

Admin roles assigned permanently, instead of activated when needed, stay usable at every hour of the day.

Open app consent

When users can consent to apps freely, an app can gain access to mail or files through a legitimate token, and its permissions often go unreviewed.

Forwarding without a record

A forwarding rule can send mail outside the tenant, and if audit logging is off or retention is short, the record of it may be gone.

99%

Share of password spray attacks that use legacy authentication protocols, according to Microsoft. Source: Microsoft Learn, block legacy authentication with Conditional Access.

Why does the path matter more than the single finding?

One finding on its own looks manageable. The risk appears when findings connect: an account excluded from Conditional Access, still able to use a legacy protocol, with standing access to Exchange Online.

Attack path analysis maps those connections the way an attacker would follow them, then ranks fixes by how many paths each one breaks. A checklist weighs every finding the same, while a path view shows which single change removes the most risk.

QuestionVulnerability scanningConfiguration validation
What it checksSoftware versions and missing patchesSettings in identity, access and collaboration
What it compares againstPublished vulnerability databasesThe baseline your team approved
How findings are rankedA severity score for each flawHow many attack paths each finding is part of
What it leaves outSettings that have no CVEUnpatched software
Both belong in a security program. Each covers what the other leaves out.

For how to turn ranked findings into a plan, read how to turn security findings into a remediation roadmap.

How do you validate Microsoft 365 configuration?

  1. Set the baseline. Write down the approved state for Conditional Access, admin roles, app consent, mail flow and sharing, mapped to the frameworks you report against. CISA’s SCuBA baselines are a useful public reference.
  2. Include non-human identities. Review app registrations, service principals, managed identities and automation accounts along with user accounts, because apps often keep permissions after their project ends.
  3. Map findings into paths. Connect findings across identity, access and mail settings to see which ones combine, then rank fixes by the number of paths each one breaks.
  4. Check for drift on a schedule. Compare live settings with the baseline on a recurring schedule and on demand, and route each change to its owner with what changed and when.
  5. Report with evidence. Show leadership and auditors which controls are enforcing, which accounts are covered and what changed since the last review.

Source for the public baselines: CISA, Secure Cloud Business Applications (SCuBA) project.

App identities need their own review. Read how to find risky app registrations and service principals.

Where does Microsoft Secure Score fit?

Secure Score measures every tenant against the same list of Microsoft recommendations, so it cannot reflect the decisions your team made about your own environment, and it does not connect findings into paths. Validation measures your tenant against the baseline your team approved. For the full comparison, read whether there is something better than Microsoft Secure Score.

How Accelerynt validates Microsoft 365 configuration

The Microsoft Control Validation Assessment validates your tenant configuration and your external attack surface in the same engagement. Every finding names the specific account, policy or role behind it, findings map to MITRE ATT&CK, and your team walks through each one with Accelerynt’s Microsoft security engineers before receiving a prioritized remediation roadmap.

The Accelerynt Security Platform repeats that validation on a schedule your team sets and on demand, with read-only permissions. It records each change with before and after values and the account responsible, and maps findings to 15 frameworks, including NIST CSF 2.0, CIS Microsoft 365 and CISA SCuBA. For why settings that changed are the real exposure, see our post on guarding the wrong door.

Validation needs a baseline to measure against. If you want a published one, read how to use the CIS Microsoft 365 benchmark.

Posture tools differ in what they check and how they report it. Read how to compare Microsoft 365 security posture tools before you choose one.

Frequently asked questions

Why do vulnerability scanners miss Microsoft 365 misconfigurations?

Scanners match software versions against published vulnerabilities. A misconfiguration, such as a broad Conditional Access exclusion or legacy authentication left on, is a setting with no CVE, so a scanner has nothing to match. Accelerynt’s Microsoft Control Validation Assessment checks those settings in your live tenant.

What is attack path analysis for Microsoft 365?

It maps how separate findings connect into routes an attacker could follow, then ranks fixes by how many routes each one breaks. Accelerynt maps findings to MITRE ATT&CK attack chains and shows which single fix breaks the most paths across your environment.

What is the difference between a vulnerability and a misconfiguration?

A vulnerability is a flaw in software that the vendor fixes with a patch. A misconfiguration is a setting your team controls that is in an unsafe state, and changing the setting is the only fix.

How often should Microsoft 365 configuration be validated?

On a recurring schedule, and again after significant changes, because settings move between audits as admins troubleshoot and Microsoft updates defaults. The Accelerynt Security Platform scans on a schedule your team configures and on demand, with drift detection on critical controls between scans.

Talk to a Microsoft security engineer

We work inside your Microsoft environment, with your team, and show you where to focus first.