CC2.1 Relevant, quality information to support internal control (COSO principle 13)
The organisation obtains or produces relevant, good-quality information and uses it so internal control can function. Points of focus: there is a process to decide what information the control components and objectives need; systems capture data from inside and outside the organisation; relevant data is turned into information; and that information stays produced on time, kept up to date, correct and whole, reachable when needed, secured, capable of verification and kept, and is reviewed for relevance. The 2022 revision adds five points: internal and external data flows are documented and used in control design; system components (infrastructure, software, data, external systems, endpoints and roles) are recorded and kept current as assets; information is classified by its characteristics, such as personal data, customer confidential data or intellectual property, so threats and controls can be identified; people running controls work from reports they can trust to be whole, correct, up to date and valid; and the physical location and custody of assets is tracked, especially where they sit outside the organisation's own premises, such as on vendor equipment or staff-owned phones.
Source: SOC 2 (2017 Trust Services Criteria), CC2.1. 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.
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
- Asset inventory recording owner, classification and physical location, including assets held by vendors or on personal devices · Physical access / facilities
- Bring-your-own-device policy and register of company data held off premises · Physical access / facilities
periodic reviewEvidence produced at each review
- Controls or reconciliations over the completeness and accuracy of reports used in control operation · Document repository
governing documentDocuments that govern the control
- Data flow diagrams for in-scope systems, internal and external · Policy repository / GRC workspace
- Information classification scheme applied to in-scope data · Policy repository / GRC workspace
First move
Common gaps auditors find
- Data flow diagrams missing or not updated after architecture changes
- Reports used by control owners never checked for completeness and accuracy
- Asset inventory lacks location or classification
- Customer data on vendor systems or staff phones absent from the inventory
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 sheetCC1.5 Accountability for internal control responsibilities (COSO principle 5) · CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)