What this policy is
Specifies how identities are issued, what access they receive, how access is reviewed, and when it must be revoked. Covers both human users and service accounts across every system in scope.
Why every organization needs one
Most security incidents trace back to over-privileged or unrevoked access. The policy is the basis for the joiner/mover/leaver process and for every periodic access review.
What a competent Access Control Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Identity lifecycle (joiner/mover/leaver)
- Least-privilege principle
- Role-based vs attribute-based access
- Privileged-access management
- Periodic access review cadence
- Review cadence (typically annual) and version control
- Approval, sign-off and effective date
How iCompaas tracks this policy
The icompaas policy-doc producer manages this document through an 8-state lifecycle: draft → generated → internal_qa → customer_review → in_review → approved → signed (with rejected as a terminal side-state). The producer publishes a policy_doc_access_control_policy_signed compliance finding once at least one document of this kind reaches the signed state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).
Compliance frameworks that reference this policy
The icompaas compliance controls library links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.
| Framework | Control | Title | Component |
|---|---|---|---|
| ISO/IEC 27001:2022 | A.5.3 | Segregation of duties | Organizational controls |
| ISO/IEC 27001:2022 | A.5.15 | Access control | Organizational controls |
| ISO/IEC 27001:2022 | A.5.16 | Identity management | Organizational controls |
| ISO/IEC 27001:2022 | A.5.18 | Access rights | Organizational controls |
| ISO/IEC 27001:2022 | A.8.2 | Privileged access rights | Technological controls |
| ISO/IEC 27001:2022 | A.8.3 | Information access restriction | Technological controls |
| ISO/IEC 27001:2022 | A.8.5 | Secure authentication | Technological controls |
| ISO/IEC 27001:2022 | A.8.11 | Data masking | Technological controls |
| ISO/IEC 27001:2022 | A.8.18 | Use of privileged utility programs | Technological controls |
| ISO/IEC 27701:2025 | A.1.2.5 | Obtain & record consent | Conditions for collection and processing |
| ISO/IEC 27701:2025 | A.1.3.9 | Providing copy | Obligations to PII principals |
| ISO/IEC 27701:2025 | A.2.5.8 | Engagement of subcontractor | PII sharing, transfer & disclosure (processors) |
| ISO/IEC 27701:2025 | A.3.8 | Identity management | Security considerations |
| ISO/IEC 42001:2023 | A.7.2 | Data for development and enhancement of AI systems | Technological controls |
14 controls across 3 frameworks reference this policy.
About this page
This article is part of the iCompaas Policy Documents library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.