35 controls
300 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.
CISA Cross-Sector Cybersecurity Performance Goals 2.0 Evidence & Implementation Kit
35 controls is the documentation set somebody has to write. This is that set,
already written: an adopt-ready artifact for every control in policy and procedure text you
edit rather than draft, and the evidence checklist an auditor asks for against each.
See what is in it, $249
The same set every buyer of this kit receives. Nothing here is produced on request.
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 |
CPG-1.A | Changing Default Passwords | 82 |
CPG-1.B | Minimum Password Strength | 0 |
CPG-1.C | Unique Credentials | 110 |
CPG-1.D | Revoking Credentials for Departing Employees | 63 |
CPG-1.E | Separating User and Privileged Accounts | 0 |
CPG-1.F | Phishing-Resistant MFA | 0 |
CPG-2.A | Asset Inventory | 26 |
CPG-2.B | Prohibit Connection of Unauthorized Devices | 26 |
CPG-2.C | Hardware and Software Approval Process | 0 |
CPG-2.D | Disable Macros by Default | 0 |
CPG-2.E | Document Device Configurations | 0 |
CPG-2.F | No Exploitable Services on the Internet | 0 |
CPG-2.G | Limit OT Connections to Public Internet | 0 |
CPG-2.H | Document Network Topology | 0 |
CPG-3.A | Log Collection | 132 |
CPG-3.B | Secure Log Storage | 132 |
CPG-3.C | Strong and Agile Encryption | 102 |
CPG-3.D | Secure Sensitive Data | 0 |
CPG-4.A | Organizational Cybersecurity Leadership | 0 |
CPG-4.B | OT Cybersecurity Leadership | 9 |
CPG-4.C | Basic Cybersecurity Training | 94 |
CPG-4.D | OT-Specific Cybersecurity Training | 0 |
CPG-5.A | Vulnerability Disclosure Program | 72 |
CPG-5.B | Mitigating Known Vulnerabilities | 0 |
CPG-5.C | No Exploitable Services on the Internet | 0 |
CPG-5.D | Vulnerability Disclosure Program | 0 |
CPG-6.A | Vendor and Supplier Incident Reporting | 68 |
CPG-6.B | Supply Chain Incident Reporting | 196 |
CPG-7.A | Incident Reporting | 14 |
CPG-7.B | Incident Response Plans | 6 |
CPG-7.C | System Backups | 5 |
CPG-7.D | Incident Response Testing | 14 |
CPG-8.A | Network Segmentation | 146 |
CPG-8.B | Email Security (DMARC) | 0 |
CPG-8.C | Encrypted DNS | 119 |
Tell me when CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0 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.
- Segmentation diagram
- DMARC reject record
- Encrypted DNS policy
- Firewall rule review
- Network segmentation diagram
- Network segmentation (VPC/subnets/security groups)
- Incident response plan and playbooks
- Tabletop exercise reports
- Incident ticket history with timelines
- Forensic toolkit and chain-of-custody log
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 CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.0, 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