SOC 2May 5, 202611 min read

SOC 2 CC6.3: Least Privilege, Segregation of Duties, and Access Reviews That Hold Up

SOC 2 CC6.3 explained by an auditor: role-based access, least privilege, segregation of duties in small teams, role changes, and access reviews that hold up.

On this page · 13 sections
Key takeaways
  • SOC 2 CC6.3 requires that access to data, software, functions, and other protected assets be authorized, modified, and removed based on roles, responsibilities, or system design, with consideration of least privilege and segregation of duties.
  • The criterion says "giving consideration to." It does not require perfect segregation of duties. Small teams can meet it with technical guardrails and compensating detective controls.
  • Role changes are the CC6.3 event most organizations miss. Joiners and leavers get a process. Movers often keep their old access.
  • An access review only counts if it is precise: complete population, an independent reviewer, the right level of detail, and evidence that inappropriate access was actually removed.

What is SOC 2 CC6.3?

SOC 2 CC6.3 is the Trust Services Criterion that governs what users can do once they have access. It requires a service organization to authorize, modify, or remove access to data, software, functions, and other protected information assets based on roles, responsibilities, or the system design and changes. In doing so, the organization must give consideration to the concepts of least privilege and segregation of duties. CC6.3 is a common criterion, so it applies to every SOC 2 examination.

Where CC6.2 asks whether someone should have an account at all, CC6.3 asks whether the access attached to that account is the right access.

Question Criterion Example evidence
Is the access control system built and configured correctly? CC6.1 SSO and MFA configuration, network segmentation, encryption
Should this person have credentials, and were they removed when they left? CC6.2 Approved access request, offboarding ticket
Does this person have only the access their role requires, and does it change when their role changes? CC6.3 Role matrix, role-change ticket, access review results

What are the CC6.3 points of focus?

The 2017 Trust Services Criteria (With Revised Points of Focus, 2022) list four points of focus under CC6.3. They describe how the criterion can be met and are not mandatory requirements.

Point of focus What it means in practice Example control
Creates or Modifies Access to Protected Information Assets Access is created or changed based on authorization from the asset owner, following roles and least privilege Role-based access requests approved by the system owner; access changes on role transfer
Removes Access to Protected Information Assets Access is removed when it is no longer needed, including when responsibilities change Removal of prior-role access as part of the transfer process
Uses Access Control Structures Access control structures, such as role-based access controls, restrict access, limit permissions, and separate incompatible duties Defined roles in the identity provider and cloud IAM; branch protection that prevents self-approval of code
Reviews Access Roles and Rules Roles and access rules are reviewed periodically for unnecessary or inappropriate individuals and system accounts, and modified as appropriate Quarterly review of production roles and the people and service accounts in them

Note that the review point of focus explicitly mentions system and service accounts as well as people. Reviews that cover only human users leave a gap auditors increasingly ask about.

What does least privilege mean for a SOC 2 audit?

Least privilege means each user and system account has only the access required to perform its function, and no more. For SOC 2 purposes, the auditor looks for evidence that access is assigned through defined roles rather than ad hoc grants, and that elevated access is limited to people who need it.

In a typical SaaS environment, the areas that attract the most scrutiny are:

  • Production infrastructure. Who can change production, and is that a small, defined group?
  • Customer data. Who can read customer data directly, outside the application, and is that access logged?
  • Cloud administrator roles. Is full administrator access held by a few named people, with day-to-day work done in narrower roles?
  • Identity provider administration. Who can create users and change MFA policy? This is effectively the key to everything else.

Just-in-time access, where an engineer requests time-limited elevation for a specific task and the grant expires automatically, is an effective way to demonstrate least privilege. It turns standing privileged access into an approved, logged, temporary event. It is not required, but it simplifies both the control and the evidence.

How do small teams meet segregation of duties in SOC 2?

Small teams meet segregation of duties in SOC 2 by combining technical restrictions on the most sensitive actions with detective controls that would reveal misuse. The criterion requires consideration of segregation of duties, not perfect separation. An auditor will not expect a 15-person startup to have separate development, operations, and security teams.

The question the auditor asks is whether any single person can make an unauthorized change to the system or data without detection. Common ways to answer it:

Risk Preventive approach Compensating approach if prevention is not practical
An engineer merges and deploys their own unreviewed code Branch protection requiring at least one approval from someone other than the author before merge Post-deployment review of all changes merged without independent approval
An administrator grants themselves elevated access Elevation requests approved by another person Alerting and periodic review of privilege changes by someone outside the admin group
One person can both modify customer data and erase the logs Logs shipped to a separate account the operator cannot modify Independent review of log integrity and access to the logging account
The only database administrator reviews their own access Another manager or the security lead performs the review Review by a second person of the administrator's activity logs

Write down which incompatible duties exist in your environment and how each one is handled. A short segregation of duties matrix, even one page, gives the auditor a clear basis for testing and shows that the consideration the criterion asks for actually happened. Change management controls under CC8.1 often carry much of the segregation of duties weight for engineering teams, so make sure the two are described consistently in your system description.

Why are role changes the most missed CC6.3 event?

Role changes are missed because most access processes are triggered by hiring and termination, and transfers do not create an obvious event. An engineer who moves into a sales engineering role, or a support agent promoted to team lead, often keeps their old access and gains new access on top of it. Over time, long-tenured employees accumulate the broadest access in the company.

The fix has two parts:

  1. Trigger on the change. A department or title change in the HR system should create an access modification ticket, just as a hire does.
  2. Remove before adding, or at least alongside. The ticket should list access to remove from the old role, not only access to grant for the new one.

When an auditor tests CC6.3, a common procedure is to obtain a list of role changes from HR for the period, sample them, and inspect whether prior-role access was removed. Organizations that have never run this process often discover exceptions in their own data before the auditor does, which is the right time to find them.

What makes a user access review acceptable to an auditor?

A user access review is acceptable when it is precise enough that inappropriate access would actually be identified and removed. Auditors evaluate the review as a control in its own right, and a signed-off spreadsheet is not enough on its own.

Five characteristics separate a review an auditor can rely on from one that fails:

  1. Complete population. The review covers every in-scope system, including those outside SSO, and the user listing used is generated from the system itself with evidence of when and how it was produced.
  2. Right level of detail. The reviewer sees each user's role or permission level, not just names. Approving a list of names cannot detect excessive privilege.
  3. Independent reviewer. Nobody approves their own access. The system owner or manager reviews, and someone else reviews the reviewer's access.
  4. Evidence of follow-through. Access flagged for removal has a ticket and a removal timestamp. A review that flags changes but never makes them is a failed control.
  5. Timeliness. The review is completed within the window your policy defines, and that window is consistent across the period.

How often should access reviews be performed for SOC 2?

The SOC 2 criteria do not set a frequency for access reviews. Your policy sets it, and the auditor tests against it. Quarterly reviews of production, privileged, and customer-data access are common practice, with less sensitive systems reviewed semi-annually or annually. Whatever you choose, apply it consistently. A quarterly review that was skipped in one quarter of a Type 2 period is a straightforward exception.

How do auditors test CC6.3?

Auditors test CC6.3 by examining how access is structured and then sampling the events that should change it. Typical procedures in a SOC 2 Type 2 include:

  • Inspecting the role design. The auditor reviews the documented roles and the permissions attached to them, and compares a sample of users' actual permissions with the roles they hold.
  • Sampling access requests and changes. For new access and role changes, the auditor inspects approvals and checks that the access granted matches the role.
  • Sampling role changes. As described above, the auditor checks whether prior-role access was removed.
  • Testing privileged access. The auditor obtains the list of users with administrator or production-change rights and asks management to justify each one.
  • Testing access reviews. The auditor selects review instances across the period and inspects the population, the reviewer, the detail reviewed, and the follow-through on changes.

Sample sizes depend on control frequency and population size. A quarterly access review in a twelve-month period gives the auditor four instances, and many auditors will test some or all of them. See SOC 2 sample sizes for common approaches.

What evidence do auditors request for CC6.3?

Evidence What it demonstrates
Role matrix or role definitions for in-scope systems Access control structures exist and are documented
Identity provider group and cloud IAM role exports Actual permissions match the documented roles
List of privileged users with business justification Least privilege for the most sensitive access
Segregation of duties matrix with compensating controls Consideration of segregation of duties
HR report of role changes in the period Population for testing access modification
Access modification tickets for sampled role changes Access was changed and prior access removed
Branch protection and deployment pipeline settings Technical enforcement of separation between authoring and approving changes
Access review records with user listings, reviewer, decisions, and removal tickets Periodic review of roles and rules, with follow-through

What are the most common CC6.3 exceptions?

1. Access reviews without follow-through

The reviewer marked three users for removal, and two of them still had access a month later. The review operated, but the outcome did not.

2. Reviewers approving their own access

The head of engineering reviews the production access list, which includes the head of engineering. Have a peer or the security lead review that line.

3. Reviews based on names only

The review listed user names for the cloud account but not their roles, so nobody could tell that a former intern still held an administrator role.

4. Movers keeping old access

A support agent who moved to marketing kept access to the customer support console, which contains customer data.

5. Too many administrators

Half the engineering team holds the full cloud administrator role "because it's easier." The auditor will ask for justification for each one, and convenience is not a justification.

6. Service accounts excluded from review

The review covered people but not the service accounts with production write access. The 2022 point of focus specifically includes system and service accounts.

How does CC6.3 map to ISO 27001:2022?

The table shows close ISO/IEC 27001:2022 Annex A equivalents. It is a practitioner mapping, not an official crosswalk.

CC6.3 theme Closest ISO 27001:2022 Annex A controls
Segregation of duties A.5.3 Segregation of duties
Access control policy and role-based access A.5.15 Access control
Provisioning, modifying, reviewing, and removing access rights A.5.18 Access rights
Privileged access A.8.2 Privileged access rights
Restricting access to information and functions A.8.3 Information access restriction

How should you prepare for CC6.3?

  1. Document your roles. List the roles for each in-scope system and what each one can do.
  2. Shrink the administrator group. Move day-to-day work into narrower roles and keep full administrator access for a few named people.
  3. Write a one-page segregation of duties matrix. Name the incompatible duties and the preventive or compensating control for each.
  4. Add a role-change trigger. Make HR transfers create an access modification ticket that removes old access.
  5. Tighten the access review. Include permissions, service accounts, and non-SSO systems, separate reviewers from the reviewed, and track removals to completion.

A SOC 2 readiness assessment from Ledger Audits includes a dry run of your access review and role-change process, so you can see where an auditor would push before fieldwork begins.

Frequently asked questions

What does SOC 2 CC6.3 require?

SOC 2 CC6.3 requires a service organization to authorize, modify, or remove access to data, software, functions, and other protected information assets based on roles, responsibilities, or system design and changes. The organization must give consideration to least privilege and segregation of duties when doing so.

Does SOC 2 require segregation of duties?

SOC 2 requires consideration of segregation of duties, not complete separation. A small company can meet CC6.3 by preventing the riskiest combinations technically, such as requiring independent code review before merge, and by using compensating detective controls where full separation is not practical.

How often should user access reviews be done for SOC 2?

SOC 2 does not prescribe an access review frequency. The service organization sets the frequency in its policy and the auditor tests against it. Quarterly reviews for production, privileged, and customer-data access are common, with less sensitive systems reviewed semi-annually or annually.

What is the difference between CC6.2 and CC6.3?

CC6.2 governs whether a user should have credentials: authorization before access and removal when access ends. CC6.3 governs what access the user has: role-based assignment, least privilege, segregation of duties, modification when roles change, and periodic review of roles and rules.

Is role-based access control required for SOC 2?

Role-based access control is not mandatory, but the CC6.3 points of focus name it as an example of an access control structure. Most SaaS companies use roles in their identity provider and cloud platform because roles make least privilege easier to enforce, review, and evidence.

Do service accounts need to be included in SOC 2 access reviews?

Including service accounts is strongly advisable. The 2022 revised point of focus on reviewing access roles and rules refers to inappropriate system or service accounts as well as individuals. Auditors increasingly expect service accounts with production access to have owners and to appear in periodic reviews.


Get independent eyes on it before your auditor or buyer does.

Ledger Audits provides readiness and internal audit work only. We never issue SOC 2 reports or ISO certificates, which keeps our review independent of your examination.

Book a discovery call
Get started

Book a discovery call

Tell us where you are in your SOC 2 or ISO 27001 journey and what you need to pass. We will tell you, honestly, what it takes.

01A 30‑minute call with a lead auditor, not a sales rep.
02An honest read on your framework, scope, and timeline.
03A fixed, written figure within one business day.

Prefer email? [email protected]

Discovery requestConfidential

We reply within one business day. Your details stay confidential.