SOC 2 (2017 TSC)·Criterion CC1.2·high·Component: Common Criteria (Security)

What this control requires

The board of directors demonstrates independence from management and exercises oversight of the development and performance of internal control.
— SOC 2 (2017 TSC), Criterion CC1.2

In plain English

The board of directors demonstrates independence from management and exercises oversight of the development and performance of internal control. In practice, this means you can prove you internal management-level controls on a defined cadence.

Why it matters

Every SOC 2 audit opinion is built control-by-control from the Trust Services Criteria. A missing or failing criterion produces an exception in the report, which buyers, partners and procurement teams read line-by-line during vendor reviews.

This control is rated high. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

What an auditor looks for

A SOC 2 auditor (under AT-C §§ 105/205) tests both design and operating effectiveness over the audit window. For each criterion they expect a written control, a control owner, a population of events, and a sample tested against the population — including remediation tickets for exceptions.

Within Common Criteria (Security), the assessor will trace your implementation back to the catalogue reference (Criterion CC1.2) and look for objective evidence on the latest two assessment cycles.

How to implement

Policy Management

Docs. Keep each policy in version-controlled Markdown alongside the code that implements it; ship a signed PDF snapshot at each annual review and link the SHA into the SoA.

Secure Development

Pipeline. Require code review, SAST (Semgrep / Snyk Code), SCA (Dependabot / Renovate), secret-scanning and IaC scanning in the merge pipeline.

Branch protection. Protected branches enforce reviews, signed commits and passing CI before merge; document the protection rules as the control evidence.

Operational checklist

  • Internal. Document the trigger, the owner and the cadence.
  • Risk. Document the trigger, the owner and the cadence.
  • Control. Document the trigger, the owner and the cadence.
  • Security. Document the trigger, the owner and the cadence.
  • Management. Document the trigger, the owner and the cadence.
  • Scope: management.

Evidence to collect

  • Policy Document. A signed and version-controlled policy / standard / procedure document.
  • Infra Scan. Continuous infrastructure-posture telemetry — AWS Config, Azure Policy compliance, GCP Organisation Policy, Wiz / Prisma findings.

Signed policy or standard documents the safeguard. Focus: Board Independence and Oversight (Original component: Control Environment).

Common pitfalls

  • Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.
  • CI security checks set to warn-only; the merge button is faster than the security feedback.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

Related controls in SOC 2 (2017 TSC)

References

Topics: governance riskpolicy managementsecure development