6.6 Establish and Maintain an Inventory of Authentication and Authorization Systems
List every system the enterprise uses to authenticate or authorise users, both in-house and provider-hosted, and review that list at least yearly. Implementation Groups: IG2 and IG3 (not in the IG1 baseline; applies from IG2 upward). Asset type: Software. Security function: Identify.
Source: CIS Controls v8.1, 6.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 CIS Controls v8.1 in the compliance library.
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.
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
none for this control
periodic reviewEvidence produced at each review
- Annual review record · Document repository
governing documentDocuments that govern the control
- Register of identity providers, directories, PAM and SSO systems including hosted ones · Policy repository / GRC workspace
- Architecture diagram of authentication flows · Policy repository / GRC workspace
First move
Common gaps auditors find
- SaaS identity stores not listed
- Inventory not updated after migrations
- No owner for each system
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.5 Require MFA for Administrative Access · 6.7 Centralize Access Control