CISA's Cross-Sector Cybersecurity Performance Goals (CPGs) are, in the agency's own words, "a prioritized subset of information technology (IT) and operational technology (OT) cybersecurity practices aimed at meaningfully reducing risks to both critical infrastructure operations and the American people." They were built from "the most common and impactful threats and adversary tactics, techniques, and procedures (TTPs) observed by CISA and its government and industry partners," which CISA says makes them "a common set of protections that all critical infrastructure entities — from large to small — should implement." Unlike a certification scheme or a full risk-management framework, CISA is explicit that the CPGs are meant to be "a floor — not a ceiling" of cybersecurity protections.
Key takeaways
- In July 2021, President Biden signed National Security Memorandum (NSM)-5, Improving Cybersecurity for Critical Infrastructure Control Systems.
- CISA also replaced the old "Complexity" rating with "Ease of Implementation" and added worked definitions for the Cost/Impact/Ease-of-Implementation scoring that accompanies every goal.
- A detail many readers miss is that CISA's three ratings are defined, not just colored dots.
- For an OT or IoT manufacturer, the practical question is which CPGs a customer can only meet if the vendor's product supports them.
Where did the CPGs come from?
In July 2021, President Biden signed National Security Memorandum (NSM)-5, Improving Cybersecurity for Critical Infrastructure Control Systems. Per CISA's own documentation, NSM-5 "required CISA, in coordination with the National Institute for Standards and Technology (NIST) and the interagency community, to develop baseline CPGs that are consistent across all critical infrastructure sectors." CISA ran a public comment period in early 2022, published CPG version 1.0 in October 2022 with an initial structure mapped to cybersecurity standards and best practices, and then reorganized the goals around the NIST Cybersecurity Framework's functions in the March 2023 version 1.0.1 release, after sector partners asked for clearer CSF alignment.
CISA's statutory basis for the program is 6 U.S.C. §652: the CPG 2.0 report states CISA "collaborates with the National Institute of Standards and Technology (NIST) and other federal partners to maintain baseline cybersecurity goals for critical infrastructure," alongside a related but separate workstream of sector-specific goals (SSGs) developed since 2023 with federal sector risk management agencies.
What changed in version 2.0?
CISA released CPG Version 2.0 (December 2025) to "align with the NIST Cybersecurity Framework 2.0, incorporate three years of operational feedback, and address emerging threats with data-driven recommendations." The headline structural change is a new sixth function, GOVERN, mirroring NIST CSF 2.0's own addition of a governance function (see our NIST CSF 2.0 guide). CISA's change log describes the goal: "The new GOVERN function integrates leadership accountability, oversight, and risk management into everyday cybersecurity practices."
Alongside the new function, CISA's report documents three other kinds of change from version 1.0.1:
- Consolidation. OT-only goals were folded into universal ones that now cover IT, IoT and OT together (CISA's report folds "1.0.1 OT-only goals (1.B/1.C/1.D; 2.I/2.J; 2.W/2.X) into universal goals"), because, as CISA puts it, "modern infrastructures blur IT, internet of things (IoT), and OT."
- Four net-new goals, filling gaps CISA says 1.0.1 didn't explicitly address: Proactive Program Management (1.B), Managed Service Provider Risk (1.E), Least-Privilege Enforcement (3.H), and Incident Communication Procedures (5.A).
- Three deletions, with each one's intent folded into a broader goal rather than dropped: Security.txt Deployment (old 4.C) merged into Maintain Vulnerability Disclosure/Reporting Process (2.D); Detect Relevant Threats/TTPs (old 3.A) consolidated under Identify Adverse Events (4.B); and Vendor/Supplier Cybersecurity Requirements (old 1.I) merged into Supply Chain Incident Reporting & Vulnerability Disclosure (1.D).
CISA also replaced the old "Complexity" rating with "Ease of Implementation" and added worked definitions for the Cost/Impact/Ease-of-Implementation scoring that accompanies every goal.
What are the six functions and their goals?
Counting the lettered goals in CISA's CPG 2.0 report:
| Function | Goals | Example |
|---|---|---|
| GOVERN | 1.A–1.E (5) | 1.A Establish Cybersecurity Responsibilities; 1.E Manage Risks from Managed Service Providers |
| IDENTIFY | 2.A–2.E (5) | 2.A Manage Organizational Assets; 2.B Mitigate Known Vulnerabilities |
| PROTECT | 3.A–3.S (19) | 3.A Change Default Passwords; 3.F Implement Multifactor Authentication (MFA) |
| DETECT | 4.A–4.B (2) | 4.A Establish Malicious Code Detection; 4.B Identify Adverse Events |
| RESPOND | 5.A–5.B (2) | 5.A Establish Incident Communication Procedures; 5.B Establish Incident Reporting Procedures |
| RECOVER | 6.A (1) | 6.A Execute Incident Recovery Plan |
Each goal in the report is documented with the same fixed structure: an Outcome, a Recommended Action, the Risk Addressed and its Scope, a NIST CSF 2.0 Reference, additional NIST SP 800-53/800-82 cross-references, Support Resources, and ratings for Cost, Impact, and Ease of Implementation. CISA's selection criteria require every goal to have "demonstrated value in reducing the risk or impact of commonly observed, cross-sector threats," be "clear, actionable, and easily definable," and be "reasonably straightforward and not cost-prohibitive for small- and medium-sized entities to successfully implement" — CISA's worked example is "ensuring that none of an organization's internet-facing systems have any known exploited vulnerabilities (KEVs)" as a suitable CPG, versus "implement zero trust" as not currently suitable because many small organizations can't absorb it before finishing the more basic goals.
CISA's goal-count conventions have shifted across published versions as items were split, merged, or renumbered, and the agency states a targeted revision cycle of roughly 24 to 36 months for CPG 2.0 (the original 1.0.1 slick sheet cites a faster 6-to-12-month cycle). Treat any specific total as a snapshot of the version reviewed, and confirm against the current CPG List and CPG Checklist on cisa.gov before building compliance tooling around an exact count.
What do the Cost, Impact and Ease of Implementation ratings mean?
A detail many readers miss is that CISA's three ratings are defined, not just colored dots. The CPG 2.0 report (pages 10–11) gives concrete bands, and notes the ratings "primarily apply to IT infrastructure" rather than OT:
| Rating | Low / Simple | Moderate | High / Complex |
|---|---|---|---|
| Cost (of annual security budget) | Less than 5 % | Between 5 % and 15 % | Greater than 15 % |
| Impact (adverse effects prevented) | Prevents "limited adverse effects" — mission continues | Prevents "serious adverse effects" — some mission functions lost | Prevents "severe or catastrophic adverse effects" — mission cannot be supported |
| Ease of Implementation | "A few months … minimal technical expertise" | "4 to 8 months … moderate technical expertise" | "Closer to a year or longer … significant technical expertise" |
CISA also recommends a cost-benefit analysis for any high-cost goal an organization chooses not to implement, comparing quantified benefits (productivity/downtime, response effort, replacement costs) against life-cycle costs. The Impact definitions deliberately "mirror the NIST Risk Management Framework system categorization (Low, Moderate, High)."
Which goals are cheapest for the most impact?
Reading the ratings in the 2.0 report, a cluster of goals carries Low cost, High impact and Simple implementation — the natural first wave, and several are things a device maker directly influences:
| Goal | Rating (Cost / Impact / Ease) |
|---|---|
| 3.A Change Default Passwords | Low / High / Simple |
| 3.B Establish Minimum Password Strength | Low / High / Simple |
| 3.C Create Unique Credentials | Low / High / Simple |
| 3.G Administrators Maintain Separate Accounts | Low / High / Simple |
| 3.H Implement the Principles of Least Privilege | Low / High / Simple |
By contrast, goals like 2.B Mitigate Known Vulnerabilities and 2.C Obtain Independent Validation of Cybersecurity Controls are rated High cost / High impact / Complex, and network segmentation (3.I) and strong encryption (3.K) sit on the harder end too — useful context when a customer asks why their vulnerability-management program is taking longer than changing default passwords did.
Which goals depend on what a device maker ships?
For an OT or IoT manufacturer, the practical question is which CPGs a customer can only meet if the vendor's product supports them. Several goals are effectively product requirements in disguise:
| CPG goal | What the product must provide | Related fix guide |
|---|---|---|
| 3.A Change Default Passwords | No shared default password; forced change on first use; the report notes hard-coded control-system passwords need compensating controls | Hard-coded credentials |
| 3.B Minimum Password Strength | Support for "a password length of 16 or more characters … when technically feasible" | — |
| 3.F Implement MFA | MFA on remotely accessible accounts, "using the strongest available method" — ideally phishing-resistant FIDO/WebAuthn or PKI | — |
| 3.K Utilize Strong Encryption | Encryption, digital signatures and hashes for communications; no plaintext credential storage | — |
| 3.Q Maintain Log Collection & Storage | Exportable, tamper-evident security logs (or, where logs are "non-standard or not available," collectable network traffic) | — |
| 2.D Maintain Vulnerability Disclosure Process | A reachable intake (e.g. RFC 9116 security.txt) and timely acknowledgement — a vendor obligation, see CISA's bad practices | — |
| 1.D Supply Chain Incident Reporting & Vulnerability Disclosure | Contractual notification of incidents/vulnerabilities, and for OT "serial numbers, checksums, digital certificates/signatures … to verify the authenticity of vendor-provided OT hardware, software, and firmware" | — |
This is the same demand signal behind CISA's Secure by Demand guidance: buyers increasingly ask vendors to make these baseline outcomes achievable out of the box rather than as expensive add-ons.
Worked example (synthetic): answering a customer CPG questionnaire
The following is a synthetic illustration. A water utility sends an OT controller vendor a questionnaire derived from the CPGs. The vendor answers only for what the product enables:
3.A / 3.B / 3.C"The controller ships with no default password; first boot forces a unique credential of at least 16 characters." — enables the customer's cheapest, highest-impact goals. 3.F MFA"Remote engineering access supports PKI-based client certificates." — enables the customer's OT MFA goal. 3.K Encryption"Management traffic uses TLS 1.3; firmware images are signed." 1.D authenticity"Each release publishes a SHA-256 checksum and a signature; release notes carry a CSAF VEX feed." — supports the customer's supply-chain verification. 2.D disclosure"security.txt and a 90-day coordinated-disclosure policy are published."
The vendor does not claim to implement the customer's organizational goals (1.A governance, 5.B incident reporting) — those stay the asset owner's responsibility.
Not mandatory, not comprehensive, not a maturity model?
CISA's report is direct about what the CPGs are not. Under a list titled "Importantly, the CPGs are not," it states they are not Comprehensive ("do not identify all the cybersecurity practices needed to protect every organization"), not a risk management or full cybersecurity program ("do not cover broader approaches to risk management or risk prioritization that other frameworks, such as the NIST CSF, articulate"), not Mandated by CISA ("CISA intends for organizations to voluntarily adopt the CPGs"), and not a maturity model (the practices apply uniformly rather than being tiered, though the companion CPG Worksheet lets organizations prioritize by Cost, Impact and Complexity).
How do the CPGs relate to the NIST CSF?
CISA frames the CPGs as complementary to, not a substitute for, the NIST Cybersecurity Framework: "The CPGs are a prioritized subset of the NIST CSF categories and subcategories and do not identify all the cybersecurity practices needed to protect every organization." Every CPG practice maps to a corresponding NIST CSF subcategory, and CISA states that "organizations that have already adopted and implemented the NIST CSF will not need to perform additional work to implement the relevant CPGs." In practice CISA positions the CPGs as a quick-start layer — identify which practices yield the greatest risk reduction, prioritize investment, and communicate that prioritization to non-technical leadership — before or alongside building a fuller program on the CSF (see our NIST CSF 2.0 guide) or on sector-specific standards such as ISA/IEC 62443 for OT environments (see our IEC 62443-3-3 guide).
What are the common pitfalls?
- Reading the ratings as opinions. Cost/Impact/Ease have numeric definitions (5 %/15 % of budget; 4–8 months); use them as stated.
- Treating the IT ratings as OT-accurate. CISA says the ratings "primarily apply to IT infrastructure" — OT cost and effort are usually higher.
- Hard-coding a goal count. The lettered total shifts between versions; anchor tooling to the current CPG List, not a number.
- Answering a vendor questionnaire with organizational claims. A product enables a customer's goals; it does not implement the customer's governance or incident-reporting goals.
- Stopping at the floor. CISA calls the CPGs a floor, not a ceiling; they are the first layer under a broader CSF-based program.
A workable starting point
Run the self-evaluation firstCISA's four-step process starts with reviewing existing controls against the CPG list — organizations already following NIST CSF or ISA/IEC 62443 may already satisfy several goals without extra work. Sequence by the Cost/Impact/Ease ratings, not just to check a box — start with the Low/High/Simple cluster (default passwords, unique credentials, least privilege) before the High-cost/Complex goals. Don't treat the CPGs as a finish lineCISA calls them a floor; a mature program uses them as the first layer under a broader NIST CSF-based program. Revisit the goal list on CISA's own cadenceWith a stated 24–36 month revision cycle (and a track record of structural changes, like the GOVERN function in 2.0), hard-coding a specific goal count into internal tooling risks drifting out of date.
Where does automated firmware analysis help?
CISA frames the CPGs as a floor, not a scored framework — SoftWSP doesn't certify an organization against them. What the platform does is narrower and sits under goal 2.B (Mitigate Known Vulnerabilities): its firmware scan extracts a CycloneDX software bill of materials from a binary image and matches the components against NVD, CISA's Known Exploited Vulnerabilities catalog, FIRST EPSS and CISA's CSAF ICS advisories, then drafts a report that cites the record behind each finding for an engineer to review (see our KEV + EPSS guide for how those signals rank the list). That gives a team working 2.B concrete, cited evidence about the components in a product's firmware; it does not assign CPG Cost/Impact/Ease ratings, claim a goal is met, or detect credentials or configuration — an engineer maps findings to the relevant goal.
SoftWSP's device and firmware work can help map a connected product's security program against the CPGs and adjacent frameworks like the NIST CSF and ISA/IEC 62443: see device & firmware security services.
This guide summarises CISA's own published CPG reports; it does not constitute legal or compliance advice, and CISA's current CPG List and CPG Checklist on cisa.gov, not this summary, govern the exact goal count at any given time.
Put this guide to work
Frequently asked questions
What are the CISA Cross-Sector Cybersecurity Performance Goals?
CISA's own CPG Version 2.0 report (December 2025) states the CPGs "are a prioritized subset of IT and OT cybersecurity practices aimed at meaningfully reducing risks to both critical infrastructure operations and the American people," informed by "the most common and impactful threats and adversary tactics, techniques, and procedures (TTPs) observed by CISA and its government and industry partners," making them "a common set of protections that all critical infrastructure entities—from large to small—should implement." The report is explicit that the CPGs are a floor, not a ceiling: "CISA intends for the CPGs to be a floor—not a ceiling—of cybersecurity protections."
Are the CPGs mandatory?
No. The CPG 2.0 report states plainly, under a list of what the CPGs are explicitly "not": "Mandated by CISA: CISA intends for organizations to voluntarily adopt the CPGs to enable prioritization of security investments toward the most critical outcomes, in conjunction with broader frameworks, like the NIST CSF." The same section also clarifies the CPGs are not comprehensive, not a full risk-management program, and not a maturity model with tiered categories.
How many CPGs are there, and how are they organized?
Version 1.0.1 (March 2023) contained 38 goals organized under the NIST Cybersecurity Framework's five original functions — Identify, Protect, Detect, Respond, Recover — per CISA's March 2024 slick sheet, which shows a 9/24/1/3/1 split across those five functions. Version 2.0 (October/December 2025) restructured the set: it added a sixth function, GOVERN, consolidated several OT-only goals into universal ones, added four net-new goals (Proactive Program Management, Managed Service Provider Risk, Least-Privilege Enforcement, and Incident Communication Procedures), and removed three goals whose intent was folded into others (Security.txt Deployment, Detect Relevant Threats/TTPs, and Vendor/Supplier Cybersecurity Requirements). Counting the lettered goals in the CPG 2.0 report: GOVERN has 5 (1.A–1.E), IDENTIFY has 5 (2.A–2.E), PROTECT has 19 (3.A–3.S), DETECT has 2 (4.A–4.B), RESPOND has 2 (5.A–5.B), and RECOVER has 1 (6.A) — 34 goals total in the lettered list this guide reviewed. CISA's own count in prior public summaries has used slightly different totals across versions as goals were consolidated or split; treat any precise cross-version count as something to re-verify against the current CPG List and CPG Checklist documents on cisa.gov rather than assumed fixed forever, since CISA states a targeted revision cycle of 24 to 36 months for the CPGs.
Where did the CPGs come from, and how do they relate to NIST?
Per the CPG 2.0 report and CISA's March 2024 slick sheet, in July 2021 President Biden signed National Security Memorandum (NSM)-5, "Improving Cybersecurity for Critical Infrastructure Control Systems," which "required CISA, in coordination with the National Institute for Standards and Technology (NIST) and the interagency community, to develop baseline CPGs that are consistent across all critical infrastructure sectors." CISA published a first comment draft in February 2022, version 1.0 in October 2022, and reorganized the goals around the NIST CSF's five functions in the March 2023 version 1.0.1 release after sector feedback asked for clearer CSF alignment. CISA's CPG 2.0 report states that under its 6 U.S.C. §652 statutory authority, CISA "collaborates with the National Institute of Standards and Technology (NIST) and other federal partners to maintain baseline cybersecurity goals for critical infrastructure."
How do the CPGs differ from the NIST Cybersecurity Framework (CSF)?
CISA's own report draws this distinction directly: the CPGs are "a prioritized subset of the NIST CSF categories and subcategories" and "do not identify all the cybersecurity practices needed to protect every organization or fully safeguard national and economic security and public health and safety." The CSF (see our [NIST CSF 2.0 guide](/guides/nist-csf-2-0/)) is a comprehensive risk-management framework covering the full breadth of an organization's cybersecurity program; the CPGs are explicitly a narrower, prioritized starting point built for organizations — especially small and medium ones — that need to know where to begin. CISA's CPG 2.0 report states every CPG practice "aligns and maps to a corresponding subcategory in the NIST CSF," and that organizations which have already implemented the CSF "will not need to perform additional work to implement the relevant CPGs." CPG 2.0 added a GOVERN function specifically to mirror NIST CSF 2.0's new emphasis on organizational governance, per the CPG 2.0 report's October 2025 update summary.
Sources
- CISA: Cross-Sector Cybersecurity Performance Goals, Version 2.0 (full report, December 2025)
- CISA: Cross-Sector Cybersecurity Performance Goals — slick sheet (as of March 2024)
- CISA: Cross-Sector Cybersecurity Performance Goals (CPGs) — overview page
- CISA: Cross-Sector Cybersecurity Performance Goals, Version 1.0.1 (March 2023 report)
- NIST: Cybersecurity Framework (CSF) 2.0 — official overview page
- IETF: RFC 9116, A File Format to Aid in Security Vulnerability Disclosure (security.txt)
About this guide
SoftWSP Firmware Security Desk
Covers the Firmware vulnerabilities & fixes cluster: 129 guides.

In this cluster
Questions about this page?
