{
 "page": "https://insights.moraph.com/compare/security-frameworks",
 "csv": "https://insights.moraph.com/compare/security-frameworks.csv",
 "publisher": "Moraph",
 "license": "https://creativecommons.org/licenses/by/4.0/",
 "license_note": "License: CC BY 4.0. Underlying government texts are public domain or under their own terms.",
 "attribution": "Moraph Insights, https://insights.moraph.com/compare/security-frameworks",
 "slug": "security-frameworks",
 "title": "Security frameworks compared: who must use them and how they are checked",
 "sector": "Cross-sector",
 "lens": "Security & Resilience",
 "in_short": "Only some of these are required by rule: federal agencies must use NIST SP 800-53 controls to meet FIPS 200, DoD contractors with covered contractor information systems must apply NIST SP 800-171 under DFARS 252.204-7012, and CMMC applies to DoD contracts involving FCI or CUI. NIST CSF 2.0 may be adopted voluntarily or through government policies and mandates, and CISA describes its Cross-Sector Cybersecurity Performance Goals as voluntary. For CMMC, Level 2 certification assessments are done by an authorized or accredited C3PAO and Level 3 by DCMA DIBCAC, and Level 2 and Level 3 assessments repeat every three years.",
 "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.",
 "published": "2026-11-13",
 "last_reviewed": "2026-11-14",
 "columns": [
  {
   "id": "framework",
   "label": "Framework"
  },
  {
   "id": "who_uses",
   "label": "Who uses it"
  },
  {
   "id": "mandatory",
   "label": "Mandatory for whom"
  },
  {
   "id": "scope",
   "label": "Scope"
  },
  {
   "id": "certification",
   "label": "Certification or attestation"
  },
  {
   "id": "assessor",
   "label": "Assessor"
  },
  {
   "id": "cycle",
   "label": "Cycle"
  }
 ],
 "rows": [
  {
   "id": "nist-csf-2",
   "cells": {
    "framework": {
     "text": "NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29, published February 26, 2024",
     "source": "s1",
     "checked": "2026-11-14"
    },
    "who_uses": {
     "text": "Organizations of all sizes and sectors, including industry, government, academia and nonprofits, regardless of the maturity of their cybersecurity programs",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "mandatory": {
     "text": "NIST says the CSF may be adopted voluntarily and through governmental policies and mandates",
     "source": "s2",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "A taxonomy of high-level cybersecurity outcomes under six functions: Govern, Identify, Protect, Detect, Respond and Recover. It does not prescribe how outcomes are achieved.",
     "source": "s2",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "nist-sp-800-53",
   "cells": {
    "framework": {
     "text": "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)",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "who_uses": {
     "text": "Information systems and organizations; the controls are flexible and customizable and are implemented as part of an organization-wide risk management process",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "mandatory": {
     "text": "Federal 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 level",
     "source": "s4",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "A catalog of security and privacy controls against threats including hostile attacks, human errors, natural disasters, structural failures, foreign intelligence entities and privacy risks",
     "source": "s3",
     "checked": "2026-11-14"
    },
    "cycle": {
     "text": "Federal 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)",
     "source": "s4",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "nist-sp-800-171",
   "cells": {
    "framework": {
     "text": "NIST SP 800-171 Rev. 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations (May 2024)",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "who_uses": {
     "text": "Federal agencies, in contracts or other agreements with nonfederal organizations that handle Controlled Unclassified Information (CUI)",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "mandatory": {
     "text": "DoD 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)",
     "source": "s13",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "Confidentiality of CUI in components of nonfederal systems that process, store or transmit CUI, or that protect those components",
     "source": "s5",
     "checked": "2026-11-14"
    },
    "certification": {
     "text": "No scheme is set on the publication page; the companion SP 800-171A gives procedures to assess the requirements",
     "source": "s5",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "cmmc",
   "cells": {
    "framework": {
     "text": "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)",
     "source": "s13",
     "checked": "2026-11-14"
    },
    "who_uses": {
     "text": "DoD contract and subcontract awardees that process, store or transmit Federal Contract Information (FCI) or CUI on contractor information systems",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "mandatory": {
     "text": "DoD 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 rule",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "Level 1: FAR 52.204-21 safeguards. Level 2: NIST SP 800-171 R2. Level 3: selected NIST SP 800-172 requirements.",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "certification": {
     "text": "Level 1 and Level 2 self-assessments, Level 2 and Level 3 certification assessments; each followed by an affirmation of continuing compliance",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "assessor": {
     "text": "Self-assessments: the contractor. Level 2 certification: an authorized or accredited C3PAO. Level 3: DCMA DIBCAC.",
     "source": "s7",
     "checked": "2026-11-14"
    },
    "cycle": {
     "text": "Level 1 self-assessment every year; Level 2 and Level 3 assessments every three years; affirmation after each assessment and annually",
     "source": "s7",
     "checked": "2026-11-14"
    }
   }
  },
  {
   "id": "cisa-cpgs",
   "cells": {
    "framework": {
     "text": "CISA Cross-Sector Cybersecurity Performance Goals (CPGs) 2.0",
     "source": "s12",
     "checked": "2026-11-14"
    },
    "who_uses": {
     "text": "Critical infrastructure operators, as a baseline broadly applicable across critical infrastructure; aimed at helping small- and medium-sized organizations start their cybersecurity efforts",
     "source": "s12",
     "checked": "2026-11-14"
    },
    "mandatory": {
     "text": "Voluntary",
     "source": "s12",
     "checked": "2026-11-14"
    },
    "scope": {
     "text": "A subset of IT and OT security practices aligned to the NIST CSF 2.0 functions, including Govern; sector-specific goals build on them",
     "source": "s12",
     "checked": "2026-11-14"
    }
   }
  }
 ],
 "sources": [
  {
   "id": "s1",
   "title": "NIST CSWP 29, The NIST Cybersecurity Framework (CSF) 2.0 (publication page)",
   "publisher": "National Institute of Standards and Technology",
   "url": "https://csrc.nist.gov/pubs/cswp/29/the-nist-cybersecurity-framework-csf-20/final",
   "checked": "2026-11-14"
  },
  {
   "id": "s2",
   "title": "The NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29 (PDF), sections 1 and 2",
   "publisher": "National Institute of Standards and Technology",
   "url": "https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf",
   "checked": "2026-11-14"
  },
  {
   "id": "s3",
   "title": "NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations (publication page)",
   "publisher": "National Institute of Standards and Technology",
   "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final",
   "checked": "2026-11-14"
  },
  {
   "id": "s4",
   "title": "FIPS 200, Minimum Security Requirements for Federal Information and Information Systems, sections 8, 10 and 4",
   "publisher": "National Institute of Standards and Technology",
   "url": "https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.200.pdf",
   "checked": "2026-11-14"
  },
  {
   "id": "s5",
   "title": "NIST SP 800-171 Rev. 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations (publication page)",
   "publisher": "National Institute of Standards and Technology",
   "url": "https://csrc.nist.gov/pubs/sp/800/171/r3/final",
   "checked": "2026-11-14"
  },
  {
   "id": "s7",
   "title": "32 CFR part 170, Cybersecurity Maturity Model Certification (CMMC) Program, sections 170.3, 170.14 to 170.18 and 170.22",
   "publisher": "U.S. Department of Defense",
   "url": "https://www.ecfr.gov/current/title-32/subtitle-A/chapter-I/subchapter-G/part-170",
   "checked": "2026-11-14"
  },
  {
   "id": "s12",
   "title": "Cross-Sector Cybersecurity Performance Goals",
   "publisher": "Cybersecurity and Infrastructure Security Agency",
   "url": "https://www.cisa.gov/cross-sector-cybersecurity-performance-goals",
   "checked": "2026-11-14"
  },
  {
   "id": "s13",
   "title": "Class Deviation 2026-O0025, Revision 3: Revolutionary FAR Overhaul Part 40, DFARS Part 240 (memorandum and attachments), signed September 3, 2026 (digital signature)",
   "publisher": "Department of War, Defense Pricing, Contracting, and Acquisition Policy",
   "url": "https://www.acq.osd.mil/dpap/dars/classdev/DFARS_RFO/Part-240/2026-O0025_Rev3_TAB_A_Deviation_Memo.pdf",
   "checked": "2026-11-14"
  }
 ],
 "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."
 ],
 "omitted": [
  {
   "where": "iso-iec-27001/all",
   "reason": "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."
  },
  {
   "where": "nist-csf-2/certification",
   "reason": "The CSF 2.0 publication describes no certification or attestation scheme; no official source states one."
  },
  {
   "where": "nist-csf-2/assessor",
   "reason": "NIST names no assessor for the CSF."
  },
  {
   "where": "nist-csf-2/cycle",
   "reason": "NIST sets no assessment cycle for the CSF."
  },
  {
   "where": "nist-sp-800-53/certification",
   "reason": "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."
  },
  {
   "where": "nist-sp-800-53/assessor",
   "reason": "Not stated in the sources opened."
  },
  {
   "where": "nist-sp-800-171/assessor",
   "reason": "SP 800-171 names no assessor; assessments under DoD rules are covered in the CMMC row."
  },
  {
   "where": "nist-sp-800-171/cycle",
   "reason": "Not stated in SP 800-171 or DFARS 252.204-7012 as opened."
  },
  {
   "where": "cisa-cpgs/certification",
   "reason": "CISA describes no certification for the CPGs."
  },
  {
   "where": "cisa-cpgs/assessor",
   "reason": "CISA names no required assessor for the CPGs; its page mentions assessors and its CSET evaluation tool, which were not compared."
  },
  {
   "where": "cisa-cpgs/cycle",
   "reason": "Not stated on the CISA page."
  },
  {
   "where": "soc-2/all",
   "reason": "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."
  },
  {
   "where": "hitrust/all",
   "reason": "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."
  },
  {
   "where": "pci-dss/all",
   "reason": "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."
  },
  {
   "where": "cis-controls/all",
   "reason": "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."
  }
 ],
 "corrections": [
  {
   "date": "2026-11-14",
   "text": "The SP 800-171 row's DFARS cell quoted only the codified text of DFARS 252.204-7012(b)(2) (the SP 800-171 in effect when the solicitation is issued). It now cites Class Deviation 2026-O0025, Revision 3, whose version of the clause, which contracting officers must use, names SP 800-171 Revision 2."
  },
  {
   "date": "2026-11-14",
   "text": "The CISA CPGs row said the goals are for critical infrastructure entities of all sizes; CISA's page does not say that. It now says what the page says: a baseline broadly applicable across critical infrastructure, aimed at helping small- and medium-sized organizations."
  }
 ]
}
