EvidenceSheet
Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) · Identity Management

IM-6 Use strong authentication controls

Enforce phishing-resistant multi-factor authentication for all users with Conditional Access policies and risk-based controls.

Source: Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark), IM-6. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open Azure Security Benchmark v3 (renamed Microsoft cloud security benchmark) in the compliance library.

4
artefacts
2
held by a system
0
at each review
easy
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Conditional Access policy export · Policy repository / GRC workspace
  • MFA coverage report · Identity provider / directory

periodic reviewEvidence produced at each review

none for this control

governing documentDocuments that govern the control

  • Authentication methods policy · Policy repository / GRC workspace
  • Sign-in risk policy · Policy repository / GRC workspace

First move

Automate the pull from your Policy repository / GRC workspace. Version-controlled policy set with approval metadata; review dates tracked as records, not a calendar note.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

IM-5 Use single sign-on (SSO) for application access · IM-7 Restrict resource access based on conditions