EvidenceSheet

CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)

Information needed for internal control, including objectives and control duties, is communicated inside the organisation. Points of focus: a process lets all personnel understand and carry out their control duties; management and the board exchange what each needs; separate channels such as a whistle-blowing line exist when normal routes fail; the method suits timing, audience and content; people who design, run or monitor controls are told their responsibilities and changes to them; staff know how to report failures, incidents and concerns; objectives and changes are communicated promptly; a security awareness programme builds knowledge and good behaviour; and at system level, staff are told how the system and its boundaries operate, its objectives, and changes that affect them. The 2022 revision adds, for privacy engagements, a privacy awareness programme for personnel and telling staff how to report a suspected privacy incident.

Source: SOC 2 (2017 Trust Services Criteria), CC2.2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open SOC 2 (2017 Trust Services Criteria) in the compliance library.

These are criteria, not controls: you design controls that meet them, and which criteria are in scope follows the categories your report covers (Security always; Availability, Confidentiality, Processing Integrity and Privacy only if chosen). A Type 2 report tests that the controls operated across the period, so the evidence asked for is samples across that period, not one copy.

5
artefacts
2
held by a system
1
at each review
moderate
to go live
HR system / LMS
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

  • Security awareness training content and completion records · HR system / LMS
  • Privacy awareness training module, completion records and the staff route for reporting suspected privacy incidents (privacy engagements) · HR system / LMS

periodic reviewEvidence produced at each review

  • Whistle-blower or anonymous reporting channel and evidence it is publicised · Policy repository / GRC workspace

governing documentDocuments that govern the control

  • Published information security policies accessible to staff with change notices · Policy repository / GRC workspace
  • Internal incident and concern reporting procedure · Policy repository / GRC workspace

First move

Start with the 2 of 5 artefacts that already live in a system (HR system / LMS); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

CC2.1 Relevant, quality information to support internal control (COSO principle 13) · CC2.3 Communication with external parties about internal control (COSO principle 15)