6.3 Require MFA for Externally-Exposed Applications
Require all externally-exposed enterprise or third-party applications to enforce MFA, where supported. Enforcing MFA through a directory service or SSO provider is a satisfactory implementation of this Safeguard.
4
artefacts
2
held by a system
1
at each review
easy
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
- Evidence the safeguard is implemented: Require MFA for Externally-Exposed Applications · Identity provider / directory
- Configuration / tooling output demonstrating the safeguard · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Records showing the safeguard is operating (logs, reports, reviews) · SIEM / log platform
governing documentDocuments that govern the control
- Policy/standard covering CIS Control 6 (Access Control Management) · Policy repository / GRC workspace
First move
Automate the pull from your Identity provider / directory. Scheduled export of users, roles and MFA state from the directory; access-review completion pulled from the IdP, not a spreadsheet.
Common gaps auditors find
- Safeguard implemented for some assets but not all in scope
- No evidence of ongoing operation (point-in-time only)
- Implementation Group IG1 baseline not met
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 sheet6.2 Establish an Access Revoking Process · 6.4 Require MFA for Remote Network Access