IM-6 Use strong authentication controls
Enforce phishing-resistant multi-factor authentication for all users with Conditional Access policies and risk-based controls.
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
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
- Legacy authentication not blocked
- MFA bypassed by service accounts
- SMS used as primary factor
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 sheetIM-5 Use single sign-on (SSO) for application access · IM-7 Restrict resource access based on conditions