EvidenceSheet
CIS Controls v8.1 · CIS Control 6: Access Control Management

6.3 Require MFA for Externally-Exposed Applications

Require multi-factor authentication, where the application supports it, on every internet-facing application, whether the enterprise's own or a third party's; switching it on centrally in the directory or single sign-on service counts as compliance. Implementation Groups: IG1, IG2 and IG3 (part of the IG1 essential cyber hygiene baseline, so every enterprise applies it). Asset type: Users. Security function: Protect.

Source: CIS Controls v8.1, 6.3. 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 CIS Controls v8.1 in the compliance library.

Scope: Implementation Groups: IG1, IG2, IG3. Security function: Protect; asset type: Users.

Each safeguard shows its Implementation Groups. IG1 is the essential baseline for every enterprise, IG2 adds to it, IG3 is all 153. Version 8.1 adds the Govern security function and asks for more processes to be documented; numbering is unchanged from v8.

3
artefacts
1
held by a system
1
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. 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

  • SSO or IdP conditional access policies requiring MFA · Identity provider / directory

periodic reviewEvidence produced at each review

  • Exception records · Identity provider / directory

governing documentDocuments that govern the control

  • Inventory of internet-facing applications with MFA status · 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

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

6.2 Establish an Access Revoking Process · 6.4 Require MFA for Remote Network Access