CC5.2 General controls over technology (COSO principle 11)
General controls over technology are selected and developed to support objectives. Points of focus: management understands how business processes and automated controls depend on technology general controls; controls over infrastructure support complete, accurate and available processing; security management controls limit access rights to authorised users in line with their jobs and protect assets from external threats; and controls over acquisition, development and maintenance of technology support management's objectives.
Source: SOC 2 (2017 Trust Services Criteria), CC5.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.
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
none for this control
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Inventory of IT general controls covering access, change, operations and development · Policy repository / GRC workspace
- Mapping of automated business controls to the systems and general controls they rely on · Document repository
- Infrastructure management procedures (patching, capacity, backups) · Policy repository / GRC workspace
First move
Common gaps auditors find
- Automated controls relied on with no testing of the underlying general controls
- Cloud infrastructure outside the scope of general controls
- Development and acquisition not governed by any control
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 sheetCC5.1 Selecting control activities that mitigate risk (COSO principle 10) · CC5.3 Deploying controls through policies and procedures (COSO principle 12)