01Description
Multi-factor authentication was not enforced for all user accounts. Some accounts, or some sign-in paths, accepted a password alone.
02Impact
Accounts without MFA can be taken over with a guessed, phished or leaked password. Attackers routinely spray passwords against cloud tenants and target exactly the accounts excluded from MFA policies.
03Severity
Typically
High
Typically High. High by default. Critical where administrators or accounts with access to sensitive data can sign in with a password alone.
04How to verify
- 1Review Conditional Access or equivalent policies for exclusions, gaps and report-only policies.
- 2Identify users not registered for MFA.
- 3Check whether legacy authentication or other paths bypass MFA requirements.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Enforce MFA for all users through Conditional Access, with emergency access accounts as the only documented exclusions.
- 2Block legacy authentication.
- 3Require phishing-resistant MFA, such as passkeys or FIDO2 keys, for administrators.
- 4Review policy exclusions regularly.
06References
Draft findings like this from your own evidence
Book a demo