CC6.7·medium·Component: Common Criteria (Security)What this control requires
The entity restricts the transmission, movement, and removal of information to authorized internal and external users and processes, and protects it during transmission, movement, or removal to meet the entity's objectives.
In plain English
The entity restricts the transmission, movement, and removal of information to authorized internal and external users and processes, and protects it during transmission, movement, or removal to meet the entity's objectives. In practice, this means you can prove you information objectives-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.
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 CC6.7) and look for objective evidence on the latest two assessment cycles.
How to implement
Physical Security
Inheritance. For cloud-only operations, inherit physical controls from the provider's SOC 2 / ISO 27001 report and document the inheritance in the SoA.
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.
- External. Document the trigger, the owner and the cadence.
- Risk. Document the trigger, the owner and the cadence.
- Physical. Document the trigger, the owner and the cadence.
- Scope: objectives, controls, 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: Transmission Controls (Original component: Logical and Physical Access Controls).
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.
- ISO/IEC 27001:2022 A.7.3 — Securing offices, rooms and facilities
- HIPAA (45 CFR Part 164) 164.312(b) — Audit Controls
- NIST SP 800-53 Rev. 5 CP-7 — Alternate Processing Site
- GDPR Article 1 — Subject-matter and objectives
- NIST SP 800-171 Rev. 3 3.13.15 — Session Authenticity
Related controls in SOC 2 (2017 TSC)
- Criterion CC5.2 — Technology Control Activities to Support Objectives
- Criterion CC2.2 — Internal Communications
- Criterion CC5.1 — Control Selection and Development
- Criterion PI1.4 — Output Controls
- Criterion PI1.5 — Storage Controls
- Criterion CC2.3 — External Communication on Internal Control Matters
References
- AICPA / ASEC — SOC 2 (2017 TSC)
- Catalogue identifier:
Criterion CC6.7
Topics: governance riskphysical securitypolicy management