CC6.3: Role-based access and least privilege

Access is granted by role and limited to what the job requires, privileged access is restricted, and permissions are reviewed and adjusted on a schedule.

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.3

The Policyseed crosswalk points CC6.3 at one policy. 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, sections 4 (Policy Statements) and 5 (Procedures). Owner: Security Owner.

Evidence examples for CC6.3

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.

Role-to-permission matrix for production systems (identity provider groups, cloud IAM roles, source control teams)
Quarterly access review spreadsheet with removals noted and Security Owner sign-off
Identity provider admin role listing showing a small named set of administrators
Access change tickets for privilege escalations in the period with approval recorded

Related criteria in CC6 (Logical and physical access controls)

Previous: CC6.2 User registration and deprovisioning. Next: CC6.4 Physical access. 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.