Comparison tables

Security frameworks compared: who must use them and how they are checked

Security frameworks compared: who must use them and how they are checked Each number links to the cell's source. Cells checked unless the cell shows another date.
FrameworkWho uses itMandatory for whomScopeCertification or attestationAssessorCycle
NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29, published February 26, 20241Who uses itOrganizations of all sizes and sectors, including industry, government, academia and nonprofits, regardless of the maturity of their cybersecurity programs2Mandatory for whomNIST says the CSF may be adopted voluntarily and through governmental policies and mandates2ScopeA taxonomy of high-level cybersecurity outcomes under six functions: Govern, Identify, Protect, Detect, Respond and Recover. It does not prescribe how outcomes are achieved.2Certification or attestationNot confirmed (see Method)AssessorNot confirmed (see Method)CycleNot confirmed (see Method)
NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations (September 2020, updated December 10, 2020; Release 5.2.0 issued August 27, 2025)3Who uses itInformation systems and organizations; the controls are flexible and customizable and are implemented as part of an organization-wide risk management process3Mandatory for whomFederal agencies must meet the FIPS 200 minimum security requirements using SP 800-53 controls, starting from a tailored low, moderate or high baseline matched to the system's impact level4ScopeA catalog of security and privacy controls against threats including hostile attacks, human errors, natural disasters, structural failures, foreign intelligence entities and privacy risks3Certification or attestationNot confirmed (see Method)AssessorNot confirmed (see Method)CycleFederal agencies have up to one year from final publication of changes to the SP 800-53 controls and baselines to comply with them (FIPS 200)4
NIST SP 800-171 Rev. 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations (May 2024)5Who uses itFederal agencies, in contracts or other agreements with nonfederal organizations that handle Controlled Unclassified Information (CUI)5Mandatory for whomDoD contractors: under DFARS 252.204-7012(b)(2), covered contractor information systems not operated on behalf of the Government must meet NIST SP 800-171. The clause contracting officers must use under Class Deviation 2026-O0025, Revision 3 (252.204-7012, JUN 2026) names SP 800-171 Revision 2, in effect when the solicitation is issued or as the contracting officer authorizes (as of 2026-11-14)8ScopeConfidentiality of CUI in components of nonfederal systems that process, store or transmit CUI, or that protect those components5Certification or attestationNo scheme is set on the publication page; the companion SP 800-171A gives procedures to assess the requirements5AssessorNot confirmed (see Method)CycleNot confirmed (see Method)
Cybersecurity Maturity Model Certification (CMMC) Program, 32 CFR part 170; its November 2026 Phase 2 transition is suspended under DFARS Class Deviation 2026-O0025, Revision 3 (as of 2026-11-14)8Who uses itDoD contract and subcontract awardees that process, store or transmit Federal Contract Information (FCI) or CUI on contractor information systems6Mandatory for whomDoD solicitations and contracts above the micro-purchase threshold where a contractor will handle FCI or CUI (except those only for COTS items), phased in under 32 CFR 170.3 over four phases starting with the effective date of the 48 CFR CMMC acquisition rule6ScopeLevel 1: FAR 52.204-21 safeguards. Level 2: NIST SP 800-171 R2. Level 3: selected NIST SP 800-172 requirements.6Certification or attestationLevel 1 and Level 2 self-assessments, Level 2 and Level 3 certification assessments; each followed by an affirmation of continuing compliance6AssessorSelf-assessments: the contractor. Level 2 certification: an authorized or accredited C3PAO. Level 3: DCMA DIBCAC.6CycleLevel 1 self-assessment every year; Level 2 and Level 3 assessments every three years; affirmation after each assessment and annually6
CISA Cross-Sector Cybersecurity Performance Goals (CPGs) 2.07Who uses itCritical infrastructure operators, as a baseline broadly applicable across critical infrastructure; aimed at helping small- and medium-sized organizations start their cybersecurity efforts7Mandatory for whomVoluntary7ScopeA subset of IT and OT security practices aligned to the NIST CSF 2.0 functions, including Govern; sector-specific goals build on them7Certification or attestationNot confirmed (see Method)AssessorNot confirmed (see Method)CycleNot confirmed (see Method)

Get the data: CSV · JSON

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.

Method

We compared each framework using its owner's own publication or page: NIST's CSRC pages and PDFs for CSF 2.0, SP 800-53, FIPS 200 and SP 800-171, the eCFR for the CMMC Program rule (32 CFR part 170), DPCAP's Class Deviation 2026-O0025, Revision 3 for the status of CMMC Phase 2 and for DFARS 252.204-7012 as contracting officers must now use it (opened 2026-11-14), and CISA's page for its Cross-Sector Cybersecurity Performance Goals. Licensed frameworks (SOC 2, HITRUST CSF, PCI DSS, CIS Controls) are left out because their owners' terms, read on 2026-11-14 and linked under Omitted, do not permit this use without written permission (see Omitted). Each cell was checked against its source on 2026-11-13 and re-checked on 2026-11-14. A cell is left out where the owner's page does not state the fact (see Omitted). ISO/IEC 27001 is left out because iso.org refused automated and browser access on 2026-11-13, and no other source may stand in for the owner's page. Cost drivers are not compared because no official source states them. This table explains the frameworks; it is not legal advice.

Omitted

What was left out, and why.

  • A row left out: iso.org returned HTTP 403 to every request on 2026-11-13 (curl and a headless browser), so the owner's page could not be opened; editorial rules allow facts on ISO/IEC 27001 only from iso.org.
  • NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29, published February 26, 2024 · Certification or attestation: The CSF 2.0 publication describes no certification or attestation scheme; no official source states one.
  • NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29, published February 26, 2024 · Assessor: NIST names no assessor for the CSF.
  • NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29, published February 26, 2024 · Cycle: NIST sets no assessment cycle for the CSF.
  • NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations (September 2020, updated December 10, 2020; Release 5.2.0 issued August 27, 2025) · Certification or attestation: SP 800-53 and FIPS 200, as opened, do not set a certification or attestation scheme; agency authorization rules sit in other documents not opened for this table.
  • NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations (September 2020, updated December 10, 2020; Release 5.2.0 issued August 27, 2025) · Assessor: Not stated in the sources opened.
  • NIST SP 800-171 Rev. 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations (May 2024) · Assessor: SP 800-171 names no assessor; assessments under DoD rules are covered in the CMMC row.
  • NIST SP 800-171 Rev. 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations (May 2024) · Cycle: Not stated in SP 800-171 or DFARS 252.204-7012 as opened.
  • CISA Cross-Sector Cybersecurity Performance Goals (CPGs) 2.0 · Certification or attestation: CISA describes no certification for the CPGs.
  • CISA Cross-Sector Cybersecurity Performance Goals (CPGs) 2.0 · Assessor: CISA names no required assessor for the CPGs; its page mentions assessors and its CSET evaluation tool, which were not compared.
  • CISA Cross-Sector Cybersecurity Performance Goals (CPGs) 2.0 · Cycle: Not stated on the CISA page.
  • A row left out: SOC 2 (AICPA attestation) is left out: the AICPA & CIMA Terms and Conditions (https://www.aicpa-cima.com/help/terms-and-conditions), as read on 2026-11-14, permit personal, non-commercial use of the site only and prohibit automated access, so its pages cannot be used here without written permission.
  • A row left out: HITRUST CSF is left out: the HITRUST Terms of Use (https://hitrustalliance.net/terms-of-use), as read on 2026-11-14, bar commercial use of any part of the site without a written agreement and prohibit automated extraction.
  • A row left out: PCI DSS is left out: the PCI Security Standards Council's Terms and Conditions (https://www.pcisecuritystandards.org/terms_and_conditions/), as read on 2026-11-14, permit use of site content for personal, non-commercial purposes only and bar use for any non-personal purpose without a separate written agreement.
  • A row left out: CIS Critical Security Controls are left out: the CIS Terms of Use for Non-Member CIS Products (https://www.cisecurity.org/terms-of-use-for-non-member-cis-products) and the CIS Logos, Trademark, and Intellectual Property Use Policy (https://www.cisecurity.org/cis-logos-and-trademark-use-policy), as read on 2026-11-14, license the Controls under CC BY-NC-ND 4.0 and allow use of CIS marks only on publications that serve only as noncommercial information, without a written agreement with CIS.

Notes

  • CMMC Level 2 and Level 3 draw on NIST SP 800-171 Revision 2 as incorporated by reference in 32 CFR part 170, while NIST's current revision of SP 800-171 is Revision 3.

Sources

  1. National Institute of Standards and Technology. NIST CSWP 29, The NIST Cybersecurity Framework (CSF) 2.0 (publication page). Checked .
  2. National Institute of Standards and Technology. The NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29 (PDF), sections 1 and 2. Checked .
  3. National Institute of Standards and Technology. NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations (publication page). Checked .
  4. National Institute of Standards and Technology. FIPS 200, Minimum Security Requirements for Federal Information and Information Systems, sections 8, 10 and 4. Checked .
  5. National Institute of Standards and Technology. NIST SP 800-171 Rev. 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations (publication page). Checked .
  6. U.S. Department of Defense. 32 CFR part 170, Cybersecurity Maturity Model Certification (CMMC) Program, sections 170.3, 170.14 to 170.18 and 170.22. Checked .
  7. Cybersecurity and Infrastructure Security Agency. Cross-Sector Cybersecurity Performance Goals. Checked .
  8. Department of War, Defense Pricing, Contracting, and Acquisition Policy. Class Deviation 2026-O0025, Revision 3: Revolutionary FAR Overhaul Part 40, DFARS Part 240 (memorandum and attachments), signed September 3, 2026 (digital signature). Checked .

How we source and check every fact: Editorial standards · Corrections

Last reviewed .

Spotted an error? Tell us and we will check it and correct the table where needed.