CC1.3 CC1 · Control Environment · Security (Common Criteria)

CC1.3 — Organizational structure and reporting lines

COSO Principle 3 — Management establishes structures, reporting lines, and appropriate authorities and responsibilities in pursuit of objectives.

Also written as CC 1.3, TSC CC1.3, SOC2 CC1.3, SOC 2 Type 2 CC1.3.

What SOC 2 CC1.3 requires

Organizational structure and reporting lines is one of 5 criteria in the Control Environment (CC1) series of the Security (Common Criteria) category. COSO Principle 3 — Management establishes structures, reporting lines, and appropriate authorities and responsibilities in pursuit of objectives. CC1 criteria come from the COSO framework rather than from security practice, so the evidence is governance paperwork — charters, minutes, signed acknowledgements — and it usually lives with HR, legal, or the board rather than with the security team.

Audit evidence assessors look for

When preparing for a SOC 2 audit against CC1.3, gather artefacts such as:

  • Org chart with security reporting lines
  • Role descriptions defining control responsibilities
  • RACI matrix for key control activities
  • Delegation-of-authority documentation

ISO 27001 mapping

CC1.3 corresponds to the following ISO 27001:2022 Annex A control(s): A.5.2. If you already run an ISO 27001 ISMS, map your existing evidence for these controls to CC1.3 rather than duplicating work.

Map CC1.3 to ISO 27001 & NIST CSF →
Crosswalk this criterion in the Control Mapper & Gap Assessment.
Document the risk →
Record treatment for gaps against CC1.3 in the Risk Register.

Other Control Environment criteria

CC1.1 Integrity and ethical values CC1.2 Board independence and oversight CC1.4 Commitment to competence CC1.5 Accountability for internal control

All CC1 Control Environment criteria →

Frequently asked questions

Is CC1.3 required for a SOC 2 report?

Yes. CC1.3 sits in the Common Criteria, which apply to every SOC 2 engagement regardless of which additional categories you scope in — there is no SOC 2 report that omits them.

How does an auditor test CC1.3?

In a Type 1 report the auditor assesses design only — does a control exist at a point in time that would meet CC1.3 if it operated. In a Type 2 report they also test operating effectiveness by sampling evidence from across the review period, typically 3 to 12 months. That difference is why Type 2 evidence has to be continuous rather than assembled the week before fieldwork.

What happens if CC1.3 fails testing?

A control that fails becomes an exception, which the auditor describes in the report along with management's response. Exceptions do not automatically make a report "failed" — a SOC 2 report is an opinion, not a pass/fail certificate — but a qualified opinion is what customers notice, so remediate and re-test before fieldwork closes where you can.

Does SOC 2 CC1.3 map to ISO 27001?

Yes — CC1.3 aligns with ISO 27001:2022 Annex A control(s) A.5.2. If you already run a certified ISMS, re-point that evidence rather than building a parallel set; the underlying control is the same and only the reporting format differs.