SC.6 Multi-Factor Authentication for Cloud Services
MFA must be applied to all administrative accounts on cloud services and to all user accounts on cloud services where supported by the provider.
3
artefacts
1
held by a system
0
at each review
moderate
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- AWS IAM MFA report · Identity provider / directory
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Entra Conditional Access policy · Policy repository / GRC workspace
- Google Workspace 2SV report · Policy repository / GRC workspace
First move
Start with the 1 of 3 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- admin breakglass without MFA
- legacy SaaS without MFA
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 sheetSC.5 Password-Based Authentication Quality · SC.7 Educate Users on Strong Passwords