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

CC1.2 — Board independence and oversight

COSO Principle 2 — The board of directors demonstrates independence from management and exercises oversight of internal control.

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

What SOC 2 CC1.2 requires

Board independence and oversight is one of 5 criteria in the Control Environment (CC1) series of the Security (Common Criteria) category. COSO Principle 2 — The board of directors demonstrates independence from management and exercises oversight of internal control. 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.2, gather artefacts such as:

  • Board or advisory committee charter
  • Meeting minutes showing security / internal-control oversight
  • Independence disclosures for board members
  • Periodic reports from management to the board on control performance

ISO 27001 mapping

CC1.2 has no clean one-to-one ISO 27001:2022 Annex A equivalent — it is largely a governance or reporting expectation that ISO 27001 handles through the management-system clauses (4–10) rather than an Annex A control. Treat it as its own requirement rather than assuming ISMS evidence covers it.

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

Other Control Environment criteria

CC1.1 Integrity and ethical values CC1.3 Organizational structure and reporting lines CC1.4 Commitment to competence CC1.5 Accountability for internal control

All CC1 Control Environment criteria →

Frequently asked questions

Is CC1.2 required for a SOC 2 report?

Yes. CC1.2 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.2?

In a Type 1 report the auditor assesses design only — does a control exist at a point in time that would meet CC1.2 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.2 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.