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

What this control requires

The entity internally communicates information, including objectives and responsibilities for internal control, necessary to support the functioning of internal control.
— SOC 2 (2017 TSC), Criterion CC2.2

In plain English

The entity internally communicates information, including objectives and responsibilities for internal control, necessary to support the functioning of internal control. In practice, this means you can prove you information communications-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 CC2.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.

Operational checklist

  • Information. Document the trigger, the owner and the cadence.
  • 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.
  • Scope: communications, objectives, 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: Internal Communications (Original component: Communication and Information).

Common pitfalls

  • Policies that no engineer has read; the version in Confluence drifts from the version that's actually being enforced.

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 management