CC6.2 and CC6.3 are two SOC 2 criteria under the Security category that cover how access is granted, changed, and removed. In short, CC6.2 is about registering and authorizing users before access is granted, and CC6.3 is about authorizing, modifying, or removing access based on roles and responsibilities, with consideration of least privilege and segregation of duties.
This guide explains what each criterion asks and what evidence teams commonly retain. It is a criteria-focused companion to CC6.1 Logical Access Controls Explained with Evidence Examples and to the broader employee onboarding and offboarding evidence guide. The criteria text comes from the AICPA Trust Services Criteria. Which controls you use to meet them is your decision, and your auditor decides whether they are suitably designed and, for Type 2, operating effectively.
What CC6.2 Covers
CC6.2 addresses what happens before system credentials are issued and access is granted. The criterion refers to registering and authorizing new internal and external users, and to removing credentials when access is no longer authorized.
Typical control activities include:
- A documented request and approval step before an account is created
- Approval by someone with authority over the system or the user's role
- Identity checks appropriate to the user type, such as employee, contractor, or customer
- A process to disable credentials that are no longer needed
What CC6.3 Covers
CC6.3 addresses the ongoing lifecycle after access exists. It refers to authorizing, modifying, or removing access to data, software, functions, and other protected assets based on roles, responsibilities, or system design, giving consideration to least privilege and segregation of duties.
Typical control activities include:
- Role definitions that map to access levels, see role-based access control
- Approval for access changes when someone moves roles
- Timely removal of access when someone leaves
- Periodic user access reviews
Provisioning vs Deprovisioning Evidence
| Stage | Question an auditor may ask | Example evidence |
|---|---|---|
| Request | Was access requested through a defined channel? | Ticket or request record with requester and date |
| Approval | Did an authorized person approve it? | Approval comment, workflow record, or sign-off |
| Grant | Does the access granted match the approval? | Account or group membership export showing the role |
| Change | Was a role change approved and applied? | Change ticket and updated group membership |
| Removal | Was access removed when it was no longer needed? | Termination ticket and account disable record with timestamps |
Population and Sampling for Type 2
For a SOC 2 Type 2 examination, auditors usually ask for a population, such as all new hires, role changes, and terminations during the audit period. They then select a sample and request the records above for each sampled person. Sampling methods vary by auditor, so confirm expectations early. See SOC 2 Type 2 sampling for how selection generally works.
Questions worth answering before fieldwork:
- Can you produce a complete list of joiners, movers, and leavers for the period?
- Can you match each person to a request, an approval, and a removal date?
- Do HR records and system accounts line up?
Common Gaps
- Access granted by message or verbal request with no record
- Approver is the same person who received the access, which can raise segregation of duties questions
- Offboarding done in the main identity provider but not in connected tools
- Shared or service accounts with no owner
- Removal that happens, but without a timestamp that proves when
Each missed follow-up can be recorded as a control deviation, so it helps to catch gaps early through exception management.
A Practical Checklist
- Write a short access request and approval procedure
- Define roles and who approves each
- Keep requests in one system of record
- Run an offboarding checklist that covers every connected tool
- Reconcile HR records to system accounts on a schedule
- Retain exports with dates for the full audit period
How AuditFlo.co Helps
AuditFlo.co helps teams keep continuous evidence collection records and audit-period history from connected systems, which can make it easier to assemble populations and sample records. AuditFlo.co does not grant or revoke access, does not issue SOC 2 reports, does not certify compliance, and does not replace auditors.
Sources
- AICPA, Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy (2017, with revised points of focus 2022): criteria CC6.2 and CC6.3