# CIS Controls v8 6.2 — Establish an Access Revoking Process - Source: https://support.icompaas.com/compliance/cis-controls-v8/6-2-establish-an-access-revoking-process - Section: [Compliance](https://support.icompaas.com/compliance) › [CIS Critical Security Controls v8](https://support.icompaas.com/compliance/cis-controls-v8) › Control 6 — Access Control Management - Last updated: 2026-06-05 - Publisher: iCompaas, Inc. (https://www.icompaas.com) **CIS Controls v8**·Control `6.2`·critical·Component: **Protect** ## What this control requires > Establish and follow a process, preferably automated, for revoking access to enterprise assets, through disabling accounts immediately upon termination, rights revocation, or role change of a user. Disabling accounts, instead of deleting accounts, may be necessary to preserve audit trails. > > — CIS Controls v8, Control 6.2 ### In plain English Establish and follow a process, preferably automated, for revoking access to enterprise assets, through disabling accounts immediately upon termination, rights revocation, or role change of a user. In practice, this means you can prove you establish user-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 **Protect**, the assessor will trace your implementation back to the catalogue reference (Control 6.2) and look for objective evidence on the latest two assessment cycles. ## How to implement 1. Write a short policy stating intent, scope and named owner. 2. Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy. 3. Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it. 4. Review on a documented cadence and capture the review in the risk register or compliance tracker. ### Operational checklist - **Establish.** Document the trigger, the owner and the cadence. - **Protect.** Document the trigger, the owner and the cadence. - **Scope:** user, identity management, enterprise. ## Evidence to collect - **Identity Scan.** IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in. - **Policy Document.** A signed and version-controlled policy / standard / procedure document. Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Signed policy or standard documents the safeguard. Focus: Establish an Access Revoking Process. ## How it maps to other frameworks Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit. - [**ISO/IEC 27001:2022 A.5.16** — Identity management](https://support.icompaas.com/compliance/iso-27001-2022/a-5-16-identity-management) - [**ISO/IEC 27701:2025 A.3.8** — Identity management](https://support.icompaas.com/compliance/iso-27701-2025/a-3-8-identity-management) - [**BSI C5:2020 IDM-02** — Granting and change of user accounts and access rights](https://support.icompaas.com/compliance/bsi-c5-2020/idm-02-granting-and-change-of-user-accounts-and-access-rights) - [**NIST SP 800-171 Rev. 3 3.5.1** — User Identification and Authentication](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-5-1-user-identification-and-authentication) - [**SOC 2 (2017 TSC) CC1.5** — Accountability for Internal Control Responsibilities](https://support.icompaas.com/compliance/soc-2-trust-services-criteria/cc1-5-accountability-for-internal-control-responsibilities) ## Related controls in CIS Controls v8 - [**Control 6.1** — Establish an Access Granting Process](https://support.icompaas.com/compliance/cis-controls-v8/6-1-establish-an-access-granting-process) - [**Control 9.2** — Use DNS Filtering Services](https://support.icompaas.com/compliance/cis-controls-v8/9-2-use-dns-filtering-services) - [**Control 6.8** — Define and Maintain Role-Based Access Control](https://support.icompaas.com/compliance/cis-controls-v8/6-8-define-and-maintain-role-based-access-control) - [**Control 6.7** — Centralize Access Control](https://support.icompaas.com/compliance/cis-controls-v8/6-7-centralize-access-control) - [**Control 5.6** — Centralize Account Management](https://support.icompaas.com/compliance/cis-controls-v8/5-6-centralize-account-management) - [**Control 5.2** — Use Unique Passwords](https://support.icompaas.com/compliance/cis-controls-v8/5-2-use-unique-passwords) ## References - [Center for Internet Security — CIS Controls v8](https://www.cisecurity.org/controls/v8) - Catalogue identifier: `Control 6.2` Topics: governance riskidentity accessidentity managementaccess reviewprivileged accesschange management ## 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.