CC6.1: Logical access security

The company protects its systems and data with identity, authentication, authorization, encryption and network controls that are designed around what needs protecting.

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

The Policyseed crosswalk points CC6.1 at 4 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.

Evidence examples for CC6.1

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.

  • Identity provider MFA enforcement policy screenshot (for example the Okta or Google Workspace admin console)
  • Cloud IAM role and group listing for the production account
  • Encryption-at-rest settings screenshot for the production database and object storage
  • Password manager admin report showing enrollment of all staff

Related criteria in CC6 (Logical and physical access controls)

Previous: CC5.3 Policies and procedures. Next: CC6.2 User registration and deprovisioning. 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.