22 controls
1 frameworks share controls with it
United States
verified against its source document
Every control below is one this framework asks for. The right hand column counts how
many other frameworks in our corpus carry the same control, which is the difference between
doing this work once and doing it again for the next standard.
There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.
What you already have
Frameworks whose controls overlap this one, most first. If you run any of them, the
count is roughly what you have already evidenced.
Every control
| Code | Control | Also in |
|---|
ACCESS-1 | Establish and Maintain Identities | 1 |
ACCESS-2 | Control Logical and Physical Access | 1 |
ARCH-1 | Establish a Cybersecurity Architecture Strategy | 1 |
ARCH-2 | Implement Network Protections | 1 |
ARCH-3 | Implement Data Security | 1 |
ASSET-1 | Manage IT and OT Asset Inventory | 1 |
ASSET-2 | Manage Asset Configuration and Changes | 1 |
PROGRAM-1 | Establish and Maintain the Cybersecurity Program | 1 |
RESPONSE-1 | Detect and Analyze Cybersecurity Events | 1 |
RESPONSE-2 | Respond to and Recover from Cybersecurity Incidents | 1 |
RESPONSE-3 | Plan for Continuity of Operations | 1 |
RISK-1 | Establish a Cyber Risk Management Strategy and Program | 1 |
RISK-2 | Identify and Analyze Cyber Risk | 1 |
RISK-3 | Manage and Respond to Cyber Risk | 1 |
SITUATION-1 | Perform Logging and Monitoring | 1 |
SITUATION-2 | Establish and Maintain a Common Operating Picture | 1 |
THIRD-1 | Identify and Manage Third-Party Risk | 1 |
THIRD-2 | Manage Supplier Relationships and Incident Notification | 1 |
THREAT-1 | Identify and Respond to Cyber Threats | 1 |
THREAT-2 | Reduce Cybersecurity Vulnerabilities | 1 |
WORKFORCE-1 | Establish Cybersecurity Responsibilities and Workforce | 1 |
WORKFORCE-2 | Develop Cybersecurity Workforce and Awareness | 1 |
Tell me when C2M2 files something new
One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.
What an auditor will ask you to produce
The artefacts named on the failure modes this framework speaks to.
- TPSP register
- AOC collection log
- contractual responsibility matrix
- monitoring cadence
- vendor monitoring schedule
- annual review reports
- Encryption + pseudonymisation evidence
- Incident response playbook
- Affected data subject notification
- Data subject breach notification when high-risk
How programmes fail on this
Failure modes named by this framework and others. Each opens the full record.
What this page is
A control-level reference for C2M2, drawn from our framework corpus. Control codes and
titles are references to the standard, not reproductions of it. The overlap counts and the
auditor artefacts are our own work and are the part you will not find elsewhere.
Measure this against what you already run ·
All frameworks · Today's edition