CC5.2: Technology controls

General controls over technology are in place: access to systems is restricted, changes are managed, and infrastructure is configured and maintained securely.

Category: Security (common criteria, required in every SOC 2 report) · Series: CC5 (Control activities) · 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 CC5.2

The Policyseed crosswalk points CC5.2 at 3 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 4 (Policy Statements). Owner: Security Owner.
• P09 Change Management Policy, section 4 (Policy Statements). Owner: Engineering Lead.
• P20 Network and Infrastructure Security Policy, section 4 (Policy Statements). Owner: Engineering Lead.

Evidence examples for CC5.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.

• Cloud IAM configuration export showing role-based groups rather than individual grants
• Branch protection settings export for production repositories
• Infrastructure-as-code repository with pull request history for infrastructure changes

Related criteria in CC5 (Control activities)

• CC5.1: Selecting control activities
• CC5.3: Policies and procedures

Previous: CC5.1 Selecting control activities. Next: CC5.3 Policies and procedures. 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.