SOC 2Apr 28, 202611 min read

SOC 2 CC6.2: User Provisioning, Offboarding, and the Evidence Auditors Sample

SOC 2 CC6.2 explained by a practicing auditor: how to approve access before credentials, remove it on time, and prepare the evidence auditors sample in Type 2.

On this page · 13 sections
Key takeaways
  • SOC 2 CC6.2 governs the user access lifecycle. Users must be registered and authorized before they receive credentials, and their credentials must be removed when access is no longer authorized.
  • The criterion applies to internal and external users whose access the service organization administers. Users your customers administer inside your product usually fall under complementary user entity controls instead.
  • The AICPA does not set a deadline for removing access. Your own policy sets it, and the auditor tests you against that commitment.
  • The most common CC6.2 exceptions are access granted before approval, terminated users still active in a system outside SSO, and contractors missing from the HR record the auditor uses as the population.

What is SOC 2 CC6.2?

SOC 2 CC6.2 is the Trust Services Criterion that governs how users get access and how they lose it. Before issuing system credentials and granting access, the service organization must register and authorize new internal and external users whose access it administers. When a user's access is no longer authorized, their credentials must be removed. CC6.2 is a common criterion, so it applies to every SOC 2 examination.

The criterion has two halves, and auditors test them separately:

  1. Before access: a user is registered and authorized before credentials are issued.
  2. After access ends: credentials are removed when access is no longer authorized, typically at termination or contract end.

The 2022 revised points of focus add a third theme that connects the two: reviewing whether existing credentials are still appropriate.

What are the CC6.2 points of focus?

The 2017 Trust Services Criteria (With Revised Points of Focus, 2022) list three points of focus under CC6.2. As with all points of focus, they illustrate how the criterion can be met. They are not mandatory requirements.

Point of focus What it means in practice Example control
Creates Access Credentials to Protected Information Assets Credentials are created based on authorization from the system's asset owner or an authorized custodian Access requests approved by the manager and system owner in a ticketing tool before provisioning
Reviews Appropriateness of Access Credentials Existing credentials are reviewed periodically for unnecessary and inappropriate individuals Quarterly or semi-annual user access review of in-scope systems
Prevents the Use of Credentials When No Longer Valid Processes disable, destroy, or otherwise prevent the use of credentials when they are no longer valid Offboarding checklist triggered by HR, with deactivation in the identity provider and every non-SSO system

The access review point of focus also appears under CC6.3, which addresses roles and least privilege. In most SOC 2 reports, one periodic access review control is mapped to both criteria. That is acceptable, provided the review checks both whether each person should have an account (CC6.2) and whether their level of access fits their role (CC6.3).

Which users does CC6.2 cover?

CC6.2 covers internal and external users whose access is administered by the service organization. This scope phrase matters more than most readers realize.

User type Covered by CC6.2? Notes
Employees Yes The core population for onboarding and offboarding testing
Contractors and consultants Yes, if you administer their access Frequently missed because they are not in the HR system
Vendor support personnel with access to your systems Yes, if you create and remove their accounts Includes managed service providers and outsourced developers
Customer users you provision on the customer's behalf Yes For example, accounts your support team creates during onboarding
Customer users the customer administers in your product Usually no Typically addressed through complementary user entity controls
Service accounts, API keys, and other non-human identities Partially Credential management for infrastructure and software is a CC6.1 point of focus, but auditors often test owners and removal alongside CC6.2

The customer-administered case is the one that causes confusion. If your product lets a customer's administrator add and remove their own users, you do not control whether those users are approved or removed on time. Your SOC 2 report should say so. The customer's responsibility is usually listed as a complementary user entity control, such as "user entities are responsible for removing access for their personnel who no longer require it."

How quickly must access be removed for SOC 2?

The SOC 2 criteria do not set a specific time limit for removing access. CC6.2 requires that credentials be removed when access is no longer authorized. The service organization defines what "timely" means in its own policy, and the auditor tests whether removal happened within that defined window.

Common policy commitments include:

  • Same day or by end of the last working day for workforce identity provider accounts.
  • Within 24 hours of termination for all in-scope systems.
  • Immediately for involuntary terminations, coordinated with HR.

Choose a commitment you can meet every time, including over weekends and holidays. An aggressive policy you miss twice is worse than a realistic one you meet consistently, because every miss is a testable deviation. Whatever you commit to should match the language in your policies and in the control description that appears in your SOC 2 report.

How do auditors test CC6.2?

Auditors test CC6.2 by building populations from an authoritative source, selecting samples, and comparing dates. The procedures below are typical in a SOC 2 Type 2 examination. Specific procedures are set by the service auditor's judgment under AT-C Section 205.

Testing new user provisioning

  1. The auditor obtains a list of new hires and new contractors for the review period, usually from the HR information system or contractor management records.
  2. The auditor assesses whether that list is complete and accurate, for example by tracing it to a system report and checking the parameters used to generate it.
  3. For each sampled user, the auditor inspects the access request and approval and compares the approval date with the date access was first granted.
  4. The auditor checks that the access granted matches the access approved.

Testing terminations

  1. The auditor obtains the list of terminated employees and ended contracts for the period.
  2. For each sampled termination, the auditor compares the termination date with the deactivation date in the identity provider and in each in-scope system not connected to SSO.
  3. The auditor may also compare current user listings from in-scope systems against the termination list to look for any terminated user who is still active.

That last step catches what sampling can miss. It is also why a single orphaned account in a production database can become an exception even when every sampled offboarding ticket looks clean. Sample sizes for these tests depend on the population size and the control frequency. Our guide to SOC 2 sample sizes explains the common approaches.

Worked example: how one offboarding becomes an exception

The following illustrative timeline shows how a well-intentioned offboarding still produces a CC6.2 exception.

Date and time Event Evidence the auditor sees
Friday 5:00 p.m. Engineer's last working day ends HR record: termination date Friday
Friday 5:20 p.m. IT disables the identity provider account, revoking SSO access to all connected apps Identity provider deactivation log
Friday 5:25 p.m. Laptop locked through MDM MDM action log
Tuesday 11:00 a.m. Database administrator notices a local database account belonging to the engineer and disables it Database audit log
Fieldwork Auditor compares the termination date with deactivation dates across in-scope systems Database deactivation is four days late against a 24-hour policy

Nothing in this example was malicious, and the SSO revocation was prompt. The exception exists because one in-scope system relied on a local account outside the identity provider. The fix is structural: either put the database behind SSO or add it to the offboarding checklist with an owner, and confirm completion before the ticket closes. The same issue shows up under CC6.1 as a coverage gap. See SOC 2 CC6.1 for that side of it.

What evidence do auditors request for CC6.2?

Evidence What it demonstrates
Access control policy or procedure defining approval and removal requirements The standard the auditor tests against, including your removal timeline
HR system reports of new hires and terminations for the period, with report parameters A complete and accurate population
Contractor and vendor access register Coverage of external users who are not in the HR system
Access request tickets with approver, approval date, and access requested Authorization before credentials are issued
Identity provider user creation and deactivation logs Timing of provisioning and removal
User listings from in-scope systems not connected to SSO Detection of orphaned or terminated accounts
Completed offboarding checklists Each in-scope system and asset was addressed
Periodic user access review records, including changes made as a result Review of the appropriateness of existing credentials

Make sure the timestamps line up. If your ticketing tool, HR system, and identity provider use different time zones, document that before fieldwork. A deactivation that appears a day late because of a UTC conversion is avoidable noise.

What are the most common CC6.2 exceptions?

These patterns recur across SOC 2 Type 2 engagements.

1. Access granted before approval

An engineer is added to the production AWS account on their first day, and the approval in the ticket is dated two days later. The approval exists, but it did not precede access, so the control did not operate as described. Configure the workflow so provisioning cannot start until approval is recorded.

2. Terminated users active in non-SSO systems

As in the worked example, the identity provider was updated promptly, but a local account in a database, a cloud console, or a legacy tool was not. This is the single most frequent CC6.2 finding I see.

3. Contractors outside the population

The auditor's termination population comes from the HR system, and contractors managed by a department head never appear in it. When the auditor later finds a former contractor with active access, the problem is both the late removal and the incomplete population. Maintain a contractor register that feeds offboarding.

4. Shared accounts that cannot be removed for one person

A shared login used by several team members cannot be removed when one of them leaves without breaking access for the others. Shared accounts also undermine CC6.1. Replace them with named accounts wherever the system supports it.

5. Access reviews that change nothing

A quarterly access review that is signed off every time with no changes, while the system has accumulated stale accounts, suggests the review is not operating with enough precision. Auditors inspect what the reviewer saw and what happened next.

6. Rehires and role changes treated as new hires

A returning employee whose old accounts were reactivated rather than re-requested skips authorization entirely. Treat rehires as new users and require fresh approval.

How should non-human credentials be handled under CC6.2?

Non-human credentials, such as service accounts, API keys, and machine tokens, should follow the same register, authorize, and remove pattern as human users. The 2022 points of focus place credential management for infrastructure and software under CC6.1, but auditors increasingly ask about these identities during CC6.2 testing because they share the same lifecycle risk.

A defensible approach:

  • Every service account and long-lived key has a named human owner.
  • Creation of privileged service accounts requires approval.
  • When an owner leaves, their service accounts and keys are reassigned or revoked as part of offboarding.
  • Service accounts are included in the periodic access review.

How does CC6.2 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.2 theme Closest ISO 27001:2022 Annex A controls
Registering users and managing identities A.5.16 Identity management
Issuing and protecting credentials A.5.17 Authentication information
Provisioning, review, and removal of access rights A.5.18 Access rights
Responsibilities at termination A.6.5 Responsibilities after termination or change of employment

A step-by-step offboarding process that holds up in a SOC 2 audit

  1. Trigger from HR. The termination record in the HR system creates an offboarding ticket automatically, with the termination date and time.
  2. Disable the identity provider account first. This revokes access to every SSO-connected application in one step.
  3. Work the non-SSO list. The ticket lists every in-scope system that uses local accounts, each with an owner who confirms removal.
  4. Handle non-human credentials. Reassign or revoke service accounts and API keys the user owned.
  5. Recover or wipe devices. Lock the device through MDM and arrange return. Disposal of returned hardware is covered by CC6.5.
  6. Close with evidence. The ticket cannot close until every line has a completion timestamp. Keep the ticket as the evidence record.

If you want a second set of eyes before fieldwork, a SOC 2 readiness assessment from Ledger Audits reperforms the termination test the way your service auditor will, including the comparison of system user listings against HR records.

Frequently asked questions

What does SOC 2 CC6.2 require?

SOC 2 CC6.2 requires a service organization to register and authorize new internal and external users before issuing system credentials and granting access, for users whose access it administers. It also requires that user credentials be removed when access is no longer authorized, such as at termination or the end of a contract.

How fast do you have to remove access for SOC 2?

SOC 2 does not specify a deadline for removing access. The service organization defines its own timeline in policy, such as same day or within 24 hours of termination, and the auditor tests whether removal happened within that timeline across a sample of terminations in the review period.

Do contractors count for SOC 2 CC6.2?

Yes. CC6.2 covers external users whose access the service organization administers, which includes contractors, consultants, and vendor personnel with accounts on your systems. Contractors are a frequent source of exceptions because they often do not appear in the HR records auditors use to build the termination population.

Are customer users in scope for CC6.2?

Customer users are in scope only when the service organization administers their access. When customers manage their own users in your application, responsibility for approving and removing those users typically sits with the customer and is described in the SOC 2 report as a complementary user entity control.

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

CC6.2 addresses whether a user should have credentials at all: registration and authorization before access, and removal when access ends. CC6.3 addresses what that user can do: authorizing, modifying, and removing access based on roles, least privilege, and segregation of duties, including changes when someone moves to a new role.

Is a user access review required for SOC 2?

The criteria do not name a mandatory access review, but reviewing the appropriateness of access credentials is a point of focus under both CC6.2 and CC6.3. Nearly every SOC 2 report includes a periodic access review control, commonly quarterly for production and privileged access, because it is the most practical way to demonstrate that stale access is detected and removed.


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.