CC6.2: User registration and deprovisioning

New users are created only after approval, credentials are issued to the right person, and access is removed promptly when someone leaves or no longer needs it.

Category: Security (common criteria, required in every SOC 2 report) · Series: CC6 (Logical and physical access controls) · TSC 2017 (2022 points of focus)

That summary is Policyseed’s own paraphrase, written to be read next to the policy sections below. The authoritative wording is the AICPA’s Trust Services Criteria, which the CPA firm tests your controls against during the examination.

Policies that address CC6.2

The Policyseed crosswalk points CC6.2 at 2 policies. Each link opens the full sample text at the section an auditor would read. Section 4 holds the statements management commits to; section 5 holds the procedures that produce evidence.

P03 Access Control Policy, section 5 (Procedures). Owner: Security Owner.
P18 Human Resources Security Policy, section 5 (Procedures). Owner: People/HR Lead.

Evidence examples for CC6.2

Artifacts a company of 5 to 200 people can realistically produce. The Audit Kit’s evidence checklist lists them per policy with an owner column so each one has a name against it before the examination.

Onboarding access request tickets showing manager approval before account creation
Offboarding checklist and identity provider deactivation timestamp for each leaver in the period
Quarterly access review spreadsheet comparing active accounts to the HR roster, signed by the Security Owner

Related criteria in CC6 (Logical and physical access controls)

Previous: CC6.1 Logical access security. Next: CC6.3 Role-based access and least privilege. All 38 criteria are listed on the template index.

Policyseed provides governance policy templates and AI tailoring. It is not legal advice and not a compliance guarantee. Management adopts the policies; the CPA firm performs the SOC 2 examination.