CC1.2: Oversight by leadership
Someone independent of day-to-day operations (a board, an advisor, or the CEO for a small company) oversees how security controls are designed and whether they keep working.
Category: Security (common criteria, required in every SOC 2 report) · Series: CC1 (Control environment) · TSC 2017 (2022 points of focus)
That summary is Policyseed’s own paraphrase, written to be read next to the policy sections below. The authoritative wording is the AICPA’s Trust Services Criteria, which the CPA firm tests your controls against during the examination.
How auditors usually test CC1.2
Expect to be asked who oversees the security program from outside day-to-day operations, and for proof that this oversight happened during the period: meeting minutes, a board pack page or an advisor's review notes, each with a date. At a small company the CEO often fills this role. The usual gap is that security was discussed but never written down, so nothing dated shows leadership reviewed risks or control results.
Policies that address CC1.2
The Policyseed crosswalk points CC1.2 at 2 policies. Each link opens the full sample text at the section an auditor would read. Section 4 holds the statements management commits to; section 5 holds the procedures that produce evidence.
- P01 Information Security Policy, section 3 (Roles and Responsibilities). Owner: Security Owner.
- P17 Risk Assessment and Management Policy, section 5 (Procedures). Owner: Security Owner. Working template: Risk register template (.xlsx), the register this policy requires, with starter risks and the policy's 1-5 scoring scales.
Preparing for ISO 27001 as well? The same policies are mapped to Annex A controls on the ISO 27001 policy templates page, so one document set can serve both. The Annex A controls that share a policy with CC1.2 are listed in the SOC 2 to ISO 27001 mapping.
Evidence examples for CC1.2
Artifacts a company of 5 to 200 people can realistically produce. The Audit Kit’s evidence checklist lists them per policy with an owner column so each one has a name against it before the examination.
- Leadership or board meeting notes showing a security update as an agenda item at least twice a year
- Memo or email appointing the Security Owner, signed by the approver
- Annual risk assessment summary presented to leadership with the date it was reviewed
Related criteria in CC1 (Control environment)
- CC1.1: Integrity and ethical values
- CC1.3: Structure, reporting lines and authority
- CC1.4: Competent people
- CC1.5: Accountability
Previous: CC1.1 Integrity and ethical values. Next: CC1.3 Structure, reporting lines and authority. All 38 criteria are listed on the template index.
Policyseed provides governance policy templates and AI tailoring. It is not legal advice and not a compliance guarantee. Management adopts the policies; the CPA firm performs the SOC 2 examination.