CIS Controls v8
CIS Control 5: Account Management

CIS Controls v8 CIS-5.1: Establish and Maintain an Inventory of Accounts

Keep a register of every account the enterprise manages, covering both user and administrator accounts. At a minimum each entry should hold the person's name, the username, the start and end dates, and the department. Confirm that every active account is authorised on a regular cycle of at least once a quarter.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 63 controls across 23 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

PCI DSS 4.0 · 7 controls

  • 8.2.1 8.2.1 Unique ID assigned to every user
  • 8.2.4 8.2.4 User ID lifecycle changes authorized
  • 8.2.5 8.2.5 Terminated users' access revoked immediately
  • 9.3.1 9.3.1 Personnel physical access procedures for the CDE
  • 9.4.1 9.4.1 Physical security of all media
  • 7.2.4 7.2.4 User accounts and privileges reviewed every six months
  • 7.2.5 7.2.5 Application and system accounts least privilege

NIST SP 800-53 Rev 5 · 5 controls

FedRAMP High · 4 controls

  • AC-2 Account Management
  • AC-2(7) Privileged User Accounts
  • IA-2 Identification and Authentication (Organizational Users)
  • IA-4 Identifier Management

FedRAMP Moderate · 4 controls

  • AC-2 Account Management
  • AC-2(7) Privileged User Accounts
  • IA-2 Identification and Authentication (Organizational Users)
  • IA-4 Identifier Management

HIPAA Security Rule · 4 controls

NIST SP 800-66 Rev 2 · 4 controls

  • ASBv3-PA-4 Review and reconcile user access regularly
  • IM-1 Use centralized identity and authentication system
  • PA-3 Manage lifecycle of identities and entitlements

CMMC 2.0 · 3 controls

ISO 27001:2022 · 3 controls

ISO 27701:2019 · 3 controls

  • 6.5.1 Responsibility for assets
  • 6.6.1 Business requirements of access control
  • 6.6.2 User access management
  • NIST-CSF-ID.AM-01 Inventories of hardware managed by the organization are maintained
  • NIST-CSF-PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization
  • NIST-CSF-PR.AA-05 Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties

NIST SP 800-171 Rev 3 · 3 controls

  • ANSSI-HYG-05 Maintain an Exhaustive Inventory of Privileged Accounts
  • ANSSI-HYG-08 Identify Each Person by Name and Separate User and Administrator Roles
  • MYHR-REG-11 Ensuring required information is given to the System Operator
  • MYHR-SEC-2 Access controls and user account management
  • ISM-0407 Secure record of user access authorisations
  • ISM-1647 Disabling privileged access after 12 months

C5 (Germany) · 2 controls

  • C5-IDM-02 Granting and change of user accounts and access rights
  • C5-IDM-05 Regular review of access rights
  • ASD37-18 Restrict administrative privileges (Essential)

ISO 27002:2022 · 1 control

  • 5.16 Identity management

SOC 2 · 1 control

  • SOC2-CC6.2 CC6.2 Registering and authorising users before issuing credentials

UK Cyber Essentials · 1 control

  • CE-AC.4 Privileged Account Approval and Tracking

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in CIS Control 5: Account Management

You are reading one control. How much of CIS Controls v8 have you already done?

CIS Controls v8 CIS-5.1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 240 were rejected on the ISO 27001:2022 pair alone.

Query this from an agent

The graph holds this control, the 63 it maps to, and the evidence behind each claim, over MCP and REST.