Every account that nobody can name, explain or switch off is a working credential waiting for an attacker, and CIS Control 5 exists to make that list empty. This guide is the implementation page for Control 5 (Account Management) of the CIS Critical Security Controls v8.1. It covers the six Safeguards with their Implementation Groups, the thresholds CIS writes into them (quarterly validation, 45 days for dormant accounts, password lengths), how the Control applies to service accounts and other non-human identities, and the evidence an assessor will ask for. It is for IAM engineers, IT managers and GRC leads. For the programme view of all 18 Controls read the CIS Controls Guide; for permissions and MFA, which CIS places in Control 6, see the CIS Control 6 Access Control Management Guide.
Key takeaways
- Control 5 is about the accounts themselves. CIS scopes it as processes and tools to assign and manage authorisation to credentials for user, administrator and service accounts; what those accounts may do is Control 6.
- Four Safeguards are IG1, two are IG2. Account inventory (5.1), unique passwords (5.2), dormant accounts (5.3) and dedicated administrator accounts (5.4) are IG1; service account inventory (5.5) and centralised account management (5.6) start at IG2.
- The numbers are specific. Validate accounts at least quarterly, disable or delete dormant accounts after 45 days of inactivity where supported, and use at least 8 characters for passwords behind MFA and 14 without.
- Service accounts are the usual gap. Because 5.5 is IG2, an IG1 organisation can score well on Control 5 while service accounts, API keys and cloud workload identities remain uncounted. Bring 5.5 forward whatever your target group.
- Evidence is mostly data, not policy. Assessors want account exports, last sign-in dates, review sign-offs and the ratio of dormant accounts still enabled, so automate those reports early.
What it is and who it applies to
CIS defines Control 5 as using processes and tools to assign and manage authorisation to credentials for user accounts, including administrator accounts, as well as service accounts, to enterprise assets and software. It applies to every directory and every system that keeps its own accounts: Active Directory and Microsoft Entra ID, Google Workspace, cloud provider IAM, SaaS applications with local logins, databases, network devices and operating system local accounts.
Control 5 sits between the inventories and access control. It needs the asset and software inventories from Controls 1 and 2 to know where accounts can exist, and it feeds Control 6, which governs access granting, revoking and MFA. Default accounts shipped with products are covered by Safeguard 4.7 in the CIS Control 4 Secure Configuration of Enterprise Assets and Software Guide, but most programmes manage them in the same inventory.
- Small organisations (IG1): one identity provider, a password manager, separate admin accounts for the few people who need them and a quarterly export reviewed by the IT lead usually meet the four IG1 Safeguards.
- Mid-sized organisations (IG2): add a service account register with named owners and a single directory that SaaS and infrastructure authenticate against through SSO and SCIM provisioning.
- Large or regulated organisations (IG3): Control 5 has no IG3-only Safeguards, so maturity shows in automation: joiner-mover-leaver workflows, identity governance campaigns and machine identity discovery.
CIS states that v8.1 did not change Implementation Group assignments, so the levels below hold for both v8 and v8.1.
Structure and key requirements
Titles are as CIS publishes them; the requirement column summarises the Safeguard text as given in the CIS Controls Assessment Specification.
| Safeguard | Title | IG | What it requires |
|---|---|---|---|
| 5.1 | Establish and Maintain an Inventory of Accounts | IG1 | Inventory of all accounts managed in the enterprise, user and administrator; at minimum person's name, username, start and stop dates and department; validate that active accounts are authorised at least quarterly |
| 5.2 | Use Unique Passwords | IG1 | Unique passwords for all enterprise assets; best practice at least 8 characters for accounts using MFA and 14 for accounts not using MFA |
| 5.3 | Disable Dormant Accounts | IG1 | Delete or disable accounts after 45 days of inactivity, where supported |
| 5.4 | Restrict Administrator Privileges to Dedicated Administrator Accounts | IG1 | Administrator privileges only on dedicated admin accounts; browsing, email and productivity work from the user's primary non-privileged account |
| 5.5 | Establish and Maintain an Inventory of Service Accounts | IG2 | Inventory of service accounts with at minimum department owner, review date and purpose; review at least quarterly that active service accounts are authorised |
| 5.6 | Centralize Account Management | IG2 | Manage accounts through a directory or identity service |
Reading the password and dormancy thresholds
- 5.2 and NIST SP 800-63B-4: NIST's current guidance requires at least 15 characters for passwords used as a single factor and at least 8 when the password is only used within multi-factor authentication, forbids composition rules and periodic forced changes, and requires checking new passwords against a blocklist of common and compromised values. Meeting NIST also meets the CIS 14 and 8 character figures. See the Password Policy Guide (NIST-aligned).
- Uniqueness means per asset too: a shared local administrator password across every laptop fails 5.2 even if each human uses a unique directory password. Windows LAPS is the standard fix; see the LAPS Guide.
- 45 days versus 90 to 180: Microsoft notes many organisations choose 90 to 180 days for inactive users. CIS sets 45, so record any longer threshold as a documented deviation with the reason (for example seasonal staff) rather than quietly using it.
- Where supported: some accounts cannot be disabled automatically (break-glass accounts, appliance accounts). List them as exceptions with owner and compensating control, for example vaulting and alerting on any sign-in.
Identity and NHI requirements
Safeguard 5.5 is the only place in the CIS Controls that names service accounts as their own inventory, and in most estates non-human identities far outnumber people. CIS's minimum fields (owner department, review date, purpose) are a floor. A register that actually supports quarterly review needs more.
| Field | Why it matters | Where to get it |
|---|---|---|
| Owner (named person and department) | CIS minimum; someone must answer the quarterly review | Ownership attestation campaigns |
| Purpose and consuming system | CIS minimum; lets reviewers judge whether it is still needed | Change records, CMDB relationships |
| Review date | CIS minimum; the Assessment Specification fails the Safeguard if the review is over three months old | Governance tool or register |
| Identity type and platform | AD service account, gMSA, Entra service principal or managed identity, AWS IAM user or role, Google Cloud service account, API key, SaaS integration token | Directory and cloud IAM exports |
| Credential type and age | Static passwords and keys need rotation; managed identities do not | AWS IAM credential report, key metadata |
| Last used | Drives the 5.3 dormancy decision for non-human accounts | Sign-in logs, access key last-used dates, service account insights |
| Privilege level | Links to Control 6 least privilege and to 5.4 | Group and role membership |
- Prefer identities without static secrets: group Managed Service Accounts in Active Directory have their passwords managed by Windows through the Key Distribution Service, and cloud managed identities and workload identity federation remove long-lived keys. See the Group Managed Service Accounts (gMSA) Guide and the OWASP NHI Top 10 NHI7 Long-Lived Secrets Guide.
- Apply dormancy to machines too: Google Cloud flags service accounts that have not authenticated in the past 90 days through the
google.iam.serviceAccount.Insightinsight type, but warns to cross-check usage outside Google Cloud such as domain-wide delegation before disabling. The AWS IAM credential report givesaccess_key_1_last_used_dateandpassword_last_used, but excludes service-specific credentials and keys beyond the first two per user. - Keep humans off service accounts: in the Okta 2023 support system breach a service account's credentials were saved in an employee's personal Chrome profile and later used by an attacker. Interactive sign-in by a human on a service account should alert. See the OWASP NHI Top 10 NHI10 Human Use of NHI Guide.
- Offboard non-human accounts: when the consuming system is retired, disable the account and revoke its credentials in the same change. See the NHI Offboarding and Decommissioning Guide.
For the full service account programme, see the Service Account Security Guide and the Service Account Inventory Template.
Implementation steps
- Find every account store. From the Control 1 and 2 inventories, list each directory, cloud tenant, SaaS application, database and device type that holds accounts. This list is the scope of 5.1 and 5.6.
- Export and normalise (5.1). Pull accounts from each store with name, username, department, created date, disabled date and last sign-in. In Entra ID,
signInActivityneeds theAuditLog.Read.AllandUser.Read.Allpermissions, andlastSuccessfulSignInDateTimerequires an Entra ID P1 or P2 licence. - Match to HR. Join human accounts to the HR record. Accounts with no matching active worker are the first clean-up list.
- Disable dormant accounts (5.3). Run the 45-day rule in report mode for one cycle, confirm exceptions with owners, then disable automatically. Delete after a retention period so that a disabled account cannot be quietly re-enabled for years.
- Split administrator accounts (5.4). Issue separate admin accounts, remove admin rights from daily accounts, block mail and web browsing for admin accounts by policy, and where possible use privileged access workstations. See the Privileged Access Management Guide.
- Fix passwords (5.2). Enforce length and a blocklist in the directory, deploy LAPS for local administrators, and vault shared or device accounts with unique values.
- Build the service account register (5.5). Discover service accounts by naming convention, password-never-expires flags, service principal and key listings, then run an ownership campaign. Accounts with no owner after the campaign are disabled in a pilot with a rollback window.
- Centralise (5.6). Connect SaaS and infrastructure to the identity provider through SAML or OIDC and provision with SCIM, so leaver processing reaches every application. See the Joiner-Mover-Leaver Guide.
- Run quarterly validation. Schedule reviews for both registers, store the sign-off, and track completion. Treat a missed quarter as a failed control, as the Assessment Specification does.
Rollback: disable rather than delete during the first cycles, keep a list of what each automated run disabled, and give owners a fast re-enable route with a ticket. Breakage from disabling an unknown service account is the main reason programmes stall, so pilot on one platform first.
Evidence and assessment
The CIS Controls Assessment Specification measures 5.1 and 5.5 by the percentage of required inventory fields present and of accounts with complete information, and fails both if the last validation is more than three months old. For 5.3 it measures the percentage of dormant accounts still enabled.
| Safeguard | Evidence an assessor expects | KPI |
|---|---|---|
| 5.1 | Account inventory export with required fields; last quarterly review sign-off | Accounts with complete records; days since last validation (under 90) |
| 5.2 | Directory password policy, blocklist setting, LAPS or vault coverage report | Endpoints with unique local admin passwords (target 100 per cent) |
| 5.3 | Dormancy report with last sign-in dates; automated disable job logs; exceptions list | Accounts inactive over 45 days still enabled (target 0) |
| 5.4 | List of admin accounts mapped to owners; proof daily accounts hold no admin rights | Privileged roles held by non-dedicated accounts (target 0) |
| 5.5 | Service account register with owner, purpose, review date; quarterly review evidence | Service accounts with a named owner; service accounts unused over 90 days |
| 5.6 | Identity provider application list, SSO and SCIM coverage report | Applications authenticating through the central directory |
- Detection: alert on new accounts outside the provisioning workflow (ATT&CK T1136 Create Account), changes to privileged group membership or account properties (T1098 Account Manipulation), sign-in to a dormant or disabled-then-re-enabled account, and default or cloud account use (T1078.001, T1078.004).
- Trend, not snapshot: report orphaned and dormant account counts monthly; a sudden rise usually means a broken leaver feed.
Mapping to other frameworks
| Control 5 area | NIST SP 800-53 Rev. 5 | NIST CSF 2.0 | ISO/IEC 27001:2022 Annex A |
|---|---|---|---|
| Account inventory and lifecycle (5.1, 5.5, 5.6) | AC-2 Account Management, IA-4 Identifier Management | PR.AA-01 | A.5.16 Identity management |
| Passwords (5.2) | IA-5 Authenticator Management | PR.AA-01 | A.5.17 Authentication information |
| Dormant accounts (5.3) | AC-2(3) Disable Accounts | PR.AA-05 | A.5.18 Access rights |
| Dedicated admin accounts (5.4) | AC-6(2) Non-privileged Access for Nonsecurity Functions, AC-6(5) Privileged Accounts | PR.AA-05 | A.8.2 Privileged access rights |
The CIS Controls Navigator holds the authoritative mappings. CSF 2.0 PR.AA-01 explicitly covers identities and credentials for "authorized users, services, and hardware", which supports including non-human accounts in scope. See the Control Mapping Guide.
Common pitfalls
- Dormant accounts that stay enabled: the Colonial Pipeline attack used a legacy VPN account that was no longer in use but had never been disabled and had no MFA. A working 5.3 job removes that route.
- Inventorying only the main directory: SaaS local accounts, database logins and network device accounts sit outside the identity provider and outside reviews until 5.6 brings them in.
- Admin rights on daily accounts: an administrator reading email from a privileged account turns any phishing click into domain or tenant compromise. 5.4 is IG1 for this reason.
- Service accounts with no owner: the register lists them but nobody answers the quarterly review, so they never get disabled. Make unanswered reviews trigger a disable in a pilot window.
- Reviews as rubber stamps: managers approve hundreds of lines at once. Give reviewers last sign-in and privilege data and show only the exceptions. See the Access Reviews Guide.
- Using human dormancy logic for machines: a batch job that runs quarterly looks dormant at 45 days. Set per-account expected frequency in the register instead.
Practitioner checklist
- List every account store and include it in the 5.1 scope.
- Hold name, username, start and stop dates and department for every human account, and validate quarterly.
- Enforce password length (at least 14 characters without MFA, 8 with) and a blocklist; deploy LAPS for local administrators.
- Disable accounts inactive for 45 days automatically, with a documented exceptions list.
- Give administrators separate accounts and remove admin rights from daily accounts.
- Build a service account register with owner, purpose, review date, credential type and last used, even if your target is IG1.
- Replace static service account passwords and keys with gMSAs, managed identities or federation where possible.
- Connect applications to the central directory with SSO and SCIM.
- Alert on accounts created outside provisioning and on interactive use of service accounts.
Standards and references
- CIS: Control 5 Account Management
- CIS: CIS Critical Security Controls Version 8.1
- CIS: Controls Assessment Specification (source repository)
- NIST: SP 800-63B-4 Authentication and Authenticator Management
- NIST: SP 800-53 Rev. 5
- Microsoft Learn: How to manage inactive user accounts
- AWS: Generate credential reports for your AWS account
- Google Cloud: Service account insights
Related NHI Mgmt Group resources: CIS Controls Guide · Service Account Security Guide · Non-Human Identity (NHI) Guide · OWASP NHI Top 10 NHI1 Improper Offboarding Guide · CIS Control 4 Secure Configuration of Enterprise Assets and Software Guide