← SOC 2 · CC6 — Logical and Physical Access
CC6.3 — Access modification and removal
Requirement
The entity authorises, modifies or removes access to data and systems based on roles, responsibilities or the system design, and removes access promptly on termination or role change.
What the engine looks for
Every group below must be satisfied — by an affirmative statement, not a plan, a hedge or a denial — for the control to count as covered. A term ending in … matches any word it begins. Supporting terms do not change the verdict — they raise confidence and distinguish a policy that names a mechanism from one that gestures at a category.
Finding any of these outranks coverage — a policy that admits the gap is worse than silence.
Equivalent controls elsewhere
Matched on shared topics. Satisfying this control usually moves these too.
| Framework | Control | Title | Shared topics |
|---|---|---|---|
| ISO 27001 | A.5.16 | Identity management | access-control offboarding |
| ISO 27001 | A.5.18 | Access rights review | access-review access-control |
| ISO 27001 | A.6.5 | Responsibilities after termination or change of employment | offboarding access-control |
| PCI DSS 4.0.1 | 7.2 | Access granted by least privilege and reviewed every six months | access-control access-review |
| PCI DSS 4.0.1 | 8.2 | Unique IDs and user account lifecycle | access-control offboarding |
| HIPAA | 164.308(a)(3)(ii)(C) | Termination procedures (A) | offboarding access-control |
| HIPAA | 164.308(a)(4)(ii)(C) | Access establishment and modification (A) | access-review access-control |
| GLBA | 314.4(c)(1) | Access controls on customer information | access-control access-review |