CC1.2 COSO Principle 2: Board exercises oversight responsibility
What the standard requires
AICPA publishes the criteria at no cost but retains copyright, so the criteria text cannot be redistributed inside this product.
The criteria a SOC 2 examination reports against, covering security (the common criteria), availability, processing integrity, confidentiality, and privacy. The common criteria are organised around the COSO framework; a service organization selects which of the other four categories are in scope.
Download free from AICPA & CIMA →If your organisation holds a licence for SOC 2 Type II, CMDash can load the real text against every control through the framework import, where it is stamped as tenant-provided.
Maps to 1 control in 1 other framework
| Framework | Control |
|---|---|
| NIST Cybersecurity Framework 2.0 | GV.RR-01 Organizational leadership is responsible and accountable for cybersecurity risk |
Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.
Integrations that carry evidence for this family
These connectors produce data relevant to SOC 2 Type II’s Control Environment family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.
In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.