What this control covers

This control enforces the principle of least privilege by limiting system access for users and processes to only what is necessary for their organizational tasks. It mandates that access to security functions and security-relevant information is restricted, and that access privileges are reviewed and adjusted periodically to ensure they remain appropriate. This control supports the Access Management System capability within the Access Control (3.1) family.

Why it matters

Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.

How to implement

AWS

Codify the policy intent as SCPs, AWS Config conformance packs, and Security Hub standards so the cloud enforces what the document says.

Azure

Codify in Azure Policy initiatives (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.

On-premises

Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.

Evidence to collect

  • policy_document — A signed, version-controlled policy stating leadership intent and the named owner.
  • infra_scan — See the iCompaas Evidence library for the canonical source for this evidence type.

Signed policy or standard documents the safeguard. Focus: Least Privilege.

Quick checklist

  • Access — Management / Privilege
  • Information — Management / Privilege
  • Least — Management / Privilege
  • Access Control — Management / Privilege
  • System — Management / Privilege
  • Risk — Management / Privilege

Related articles on this site