# CIS Controls v8 5.1 — Establish and Maintain an Inventory of Accounts - Source: https://support.icompaas.com/compliance/cis-controls-v8/5-1-establish-and-maintain-an-inventory-of-accounts - Section: [Compliance](https://support.icompaas.com/compliance) › [CIS Critical Security Controls v8](https://support.icompaas.com/compliance/cis-controls-v8) › Control 5 — Account Management - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **CIS Controls v8**·Control `5.1`·critical·Component: **Identify** ## What this control requires > Establish and maintain an inventory of all accounts managed in the enterprise. The inventory must include both user and administrator accounts. The inventory, at a minimum, should contain the person's name, username, start/stop dates, and department. Validate that all active accounts are authorized, on a recurring schedule at a minimum quarterly, or more frequently. > > — CIS Controls v8, Control 5.1 ### In plain English Establish and maintain an inventory of all accounts managed in the enterprise. In practice, this means you can prove you establish and maintain administrator-level controls on a defined cadence. ## Why it matters The CIS Controls are an industry-vetted, prioritised defence: skipping a safeguard widens the attack surface that the safeguards above and below it assume is closed. Audit frameworks (FedRAMP, PCI DSS, HIPAA) all cite CIS as evidence of due care. This control is rated **critical** in the source catalogue. Treat gaps here as production incidents in the risk register, not housekeeping. ## What an auditor looks for A CIS-aligned reviewer wants to see (a) which Implementation Group you are targeting, (b) a documented owner for the safeguard, and (c) a tooling or process artefact (config, scan output, ticket) that proves the safeguard runs on the cadence the control demands. Within **Identify**, the assessor will trace your implementation back to the catalogue reference (Control 5.1) and look for objective evidence on the latest two assessment cycles. ## How to implement #### Asset Inventory **AWS.** AWS Config Aggregator across every account + region gives a real-time inventory; ship the daily snapshot to S3 and surface drift in Security Hub. **Azure.** Azure Resource Graph plus Defender for Cloud's inventory blade enumerates every subscription; export to Log Analytics for retention and Workbooks for reporting. **GCP.** Cloud Asset Inventory exports a daily feed of every resource and IAM binding; query via BigQuery and alert on appearance/disappearance. **Endpoints.** Pipe MDM telemetry (Intune / Jamf / Workspace ONE) into your CMDB so laptops and phones are inventoried with the same rigour as cloud resources. #### Policy Management **Docs.** Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA. ### Operational checklist - **Establish And Maintain.** Document the trigger, the owner and the cadence. - **Validate.** Document the trigger, the owner and the cadence. - **Scope:** administrator, user, administrator accounts, username, enterprise. ## Evidence to collect - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Signed policy or standard documents the safeguard. Focus: Establish and Maintain an Inventory of Accounts. ## Common pitfalls - Inventories that exclude SaaS, shadow IT and ephemeral cloud resources (Lambda, Cloud Run, K8s pods) miss the assets where most modern incidents start. - Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced. ## Related controls in CIS Controls v8 - [**Control 2.2** — Ensure Authorized Software is Currently Supported](https://support.icompaas.com/compliance/cis-controls-v8/2-2-ensure-authorized-software-is-currently-supported) - [**Control 7.5** — Perform Automated Vulnerability Scans of Internal Enterprise Assets](https://support.icompaas.com/compliance/cis-controls-v8/7-5-perform-automated-vulnerability-scans-of-internal-enterprise-assets) - [**Control 7.6** — Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets](https://support.icompaas.com/compliance/cis-controls-v8/7-6-perform-automated-vulnerability-scans-of-externally-exposed-enterprise-assets) - [**Control 3.2** — Establish and Maintain a Data Inventory](https://support.icompaas.com/compliance/cis-controls-v8/3-2-establish-and-maintain-a-data-inventory) - [**Control 5.5** — Establish and Maintain an Inventory of Service Accounts](https://support.icompaas.com/compliance/cis-controls-v8/5-5-establish-and-maintain-an-inventory-of-service-accounts) - [**Control 18.1** — Establish and Maintain a Penetration Testing Program](https://support.icompaas.com/compliance/cis-controls-v8/18-1-establish-and-maintain-a-penetration-testing-program) ## References - [Center for Internet Security — CIS Controls v8](https://www.cisecurity.org/controls/v8) - Catalogue identifier: `Control 5.1` Topics: governance riskasset inventorypolicy managementprivileged access ## Related compliance guidance - [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them. - [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.