Lesson 3 of 12 · about 60 minutes · Updated November 14, 2026
The Standards Map: Which Security Frameworks Apply, Who Requires Them and How They Fit Together
You'll be able to
- Sort any security standard into its kind: outcome framework, control catalog, management system standard, attestation report, or contract and program rule
- Explain who requires each major standard and what happens on failure, including the laws in Ohio, Iowa, Idaho and HITECH section 13412 that point to frameworks
- Describe NIST CSF 2.0's six Functions, Tiers and Profiles and use it as the index for a program and for board reporting
- State the November 2026 status of SP 800-53 Release 5.2.0, SP 800-171 Rev. 2 and Rev. 3, CMMC, ISO/IEC 27001:2022, CIS Controls v8.1, SOC 2, PCI DSS v4.0.1 and FedRAMP 20x
- Use NIST's informative references and the OLIR catalog to map one control to many obligations without treating a mapping as equivalence
- Recognize the documented ways organizations get into trouble with framework claims, scores and scope
Start here: the short version
- "Security standard" is used for five different kinds of documents: outcome frameworks (NIST Cybersecurity Framework 2.0), control catalogs (NIST SP 800-53, CIS Controls), certifiable management system standards (ISO/IEC 27001), audit reports (SOC 2), and contract or program rules (PCI DSS, CMMC, FedRAMP). Knowing which kind you hold tells you who checks it, how often, and what it proves.
- Few U.S. laws name a framework. HIPAA, the FTC Safeguards Rule and state "reasonable security" laws set risk-based duties and leave the method to the organization. Contracts, customers, card brands, the Defense Department, federal and state cloud programs and insurers are what force a specific standard on most organizations.
- NIST CSF 2.0, published Feb. 26, 2024, is the common index: six Functions (Govern, Identify, Protect, Detect, Respond, Recover), 22 Categories and 106 Subcategories. Use it to organize the program and report to the board, and use a control catalog under it to do the work.1
- Status on Nov. 13, 2026: SP 800-53 is at Release 5.2.0 (Aug. 27, 2025); SP 800-171 Rev. 3 is final, but defense contracts still require Rev. 2; CMMC Phase 2, due Nov. 10, 2026, was suspended July 13, 2026, with no restart date announced; PCI DSS v4.0.1's future-dated requirements have been mandatory since March 31, 2025; only the 2022 edition of ISO/IEC 27001 can be certified after Oct. 31, 2025; and the AICPA released proposed 2027 SOC 2 criteria for comment on Oct. 26, 2026.
- Crosswalks let one well-run control answer many documents. NIST publishes free mappings from CSF 2.0 to SP 800-53, ISO/IEC 27001:2022, CIS Controls v8.1, PCI DSS v4.0.1 and others through its Online Informative References (OLIR) program.2
- Saying you "follow" a framework is a factual claim that can be tested. The SEC's 2023 complaint against SolarWinds and False Claims Act settlements with defense contractors turned on statements about framework compliance that internal assessments did not support.
- Idaho state agencies must use the current NIST CSF as the basis for assessing their security programs (ITA Policy P4140), and Ohio and Iowa give businesses whose written programs reasonably conform to a recognized framework a defense in data breach lawsuits.
Rule and standard versions described: NIST Cybersecurity Framework 2.0 (NIST CSWP 29, Feb. 26, 2024) with NIST SP 1308 (final, 2026) and SP 1347 (final, Aug. 25, 2026); NIST SP 800-53 Rev. 5, Release 5.2.0 (Aug. 27, 2025), and SP 800-53B; NIST SP 800-37 Rev. 2 (December 2018); NIST SP 800-171 Rev. 2 (Jan. 28, 2021 update) and Rev. 3 (May 14, 2024); the CMMC program rule, 32 CFR Part 170 (89 FR 83092, effective Dec. 16, 2024), the DFARS CMMC rule (90 FR 43560, effective Nov. 10, 2025) and DFARS Class Deviation 2026-O0025, Revision 3 (Sept. 3, 2026); ISO/IEC 27001:2022 with Amd 1:2024, ISO/IEC 27002:2022 and ISO/IEC 27000:2026 (described, not reproduced); CIS Critical Security Controls v8.1 (June 2024); AICPA 2017 Trust Services Criteria with revised points of focus (2022) and the Oct. 26, 2026 exposure drafts; PCI DSS v4.0.1 (June 2024); HITRUST assessments, FedRAMP (including FedRAMP 20x) and GovRAMP program pages; COBIT 2019; Ohio Revised Code 1354.01 to 1354.05 (effective Nov. 2, 2018); Iowa Code chapter 554G (2023 Acts, ch. 63); HITECH Act section 13412 (Public Law 116-321, Jan. 5, 2021); Idaho Code 67-827A and Idaho Technology Authority Policy P4140 (revised Aug. 20, 2024). All were read or checked Nov. 13, 2026. Standards and the rules that cite them change often; check the publisher's or regulator's current text before relying on any point.
Before you change anything. Plan changes to production systems, test them first, keep a way back, and follow your change management process. For clinical, plant-floor or other safety systems, involve the vendor, your safety lead and qualified engineers (see modules 109 and 111).
A hospital system's chief information security officer gets four requests in one week. The board's audit committee wants a one-page view of "where we stand against NIST." A health plan customer wants the hospital's HITRUST certification. The hospital's research institute has a Defense Department grant that mentions NIST SP 800-171 and CMMC. And the cyber insurance renewal form asks whether the organization follows "a recognized framework such as NIST CSF, ISO 27001 or CIS." None of these requests uses the same words, and two of them use the same words to mean different things.
This lesson is the map. It explains what each of the major security standards is, who writes it, what kind of document it is, who requires it and how it is checked, what changed through November 2026, and how the documents fit together so that one security program can answer all of them. It is written for executives, board members, general counsel's offices and compliance officers, CISOs and security staff, auditors, procurement and vendor managers, public officials, and the reporters, advocates and legislators who ask them questions.
Module 73 covered the same standards at small and medium business scale, including a decision table for small firms, rough costs, and a worked example of a 40-person machine shop choosing a path; see Security Frameworks and Standards: NIST CSF, CIS, ISO 27001, SOC 2 and CMMC. Merchant levels, self-assessment questionnaires and card data scoping are in PCI DSS and Payment Security. This lesson does not repeat those; it goes further on what large and regulated organizations face: overlapping obligations, federal and state program rules, the status of each standard in 2026, and how to run one control set that serves many masters.
Inside this module, lesson 2, Risk Management in Plain Terms, explains the risk process (including the NIST Risk Management Framework) that every standard here assumes you already run. Lesson 4 covers the board's oversight duty and SEC disclosure. Lesson 8 covers how to read a vendor's SOC 2 report, and lesson 12 holds the free resource library. The sector modules apply these standards in context: the HIPAA Security Rule for health care, the GLBA Safeguards Rule for accounting and tax firms, and IEC 62443 and NIST SP 800-82 for plants and industrial control systems.

Five kinds of documents people call "standards"
Most confusion in security compliance starts with treating unlike documents as alike. A framework, a control catalog, a management system standard, an audit report and a contract rule each answer a different question. Before comparing any two, sort them into these five kinds.
1. Outcome frameworks
An outcome framework describes what good looks like without saying how to get there. The NIST Cybersecurity Framework (CSF) is the leading example. NIST's own abstract says the CSF "does not prescribe how outcomes should be achieved"; instead it links to other documents that do.1 Frameworks are good for organizing a program, setting priorities and explaining the program to a board in plain language. They are poor at telling an engineer what to configure. Nobody certifies an organization against the CSF; there is no CSF auditor and no CSF certificate, whatever a vendor's marketing says.
2. Control catalogs and baselines
A control catalog lists specific safeguards. NIST SP 800-53 is the largest, with 20 families of security and privacy controls; NIST SP 800-171 is a smaller set of requirements derived from it for contractors; the CIS Critical Security Controls are a short, prioritized list written by a nonprofit. Catalogs come with "baselines" or groups that say which controls fit which level of risk. They answer "what exactly should we do?" and they can be assessed control by control.3
3. Management system standards
ISO/IEC 27001 is a different animal. It sets requirements for an information security management system (ISMS): the leadership commitment, risk assessment, policies, internal audits, management reviews and corrective actions that keep a program running and improving. Its Annex A lists 93 reference controls, but the organization decides which apply through its own risk process and records the choice in a Statement of Applicability. An accredited certification body audits the management system and issues a certificate. It is the only document on this map that produces an internationally recognized certificate of conformity.
4. Attestation and assessment reports
A SOC 2 report is not a standard at all. It is a report by a licensed CPA firm, under AICPA attestation standards, giving an opinion on a service organization's controls measured against the AICPA's Trust Services Criteria.4 HITRUST assessments, CMMC assessments, PCI DSS Reports on Compliance and FedRAMP packages are also forms of evidence: they record that someone looked at a set of controls on certain dates and what they found. The value of evidence depends on who did the looking, how independent they were, what was in scope, and how long ago it happened.
5. Contract and program rules
Some standards bind you only because you signed something or want to sell to someone. PCI DSS is enforced through card brand rules and the merchant agreement with your bank, not by statute; the PCI Security Standards Council says whether an entity must comply or validate "is at the discretion of organizations that manage compliance programs," such as the card brands and acquiring banks.5 CMMC binds defense contractors through clauses in their contracts. FedRAMP and GovRAMP decide whether federal or state and local agencies may buy a cloud service. These rules are the ones with the clearest consequences: lose the contract, lose the ability to take cards, lose the government market.
And then the law
Laws and regulations sit above all five. A few name frameworks, as the next section shows, but most impose a duty of "reasonable" or "appropriate" security and leave the choice of method to the organization. The HIPAA Security Rule is the clearest case: its 2003 structure of standards and "addressable" implementation specifications was designed to be flexible, and as of Oct. 28, 2026 the January 2025 proposal to rewrite it was still not final.6 When a regulator later judges whether security was reasonable, a documented program built on a recognized framework is usually the best evidence an organization can offer.
Who requires what: law, contract, customer and insurer
For a large organization the honest answer to "which standard applies to us?" is usually "several, for different reasons." The table sorts the common drivers. The right column is the one that matters most in practice: who can actually check, and what happens if you fail.
| Driver | Examples | What it usually requires | Who checks and the consequence |
|---|---|---|---|
| Federal agency law | FISMA for federal agencies; OMB Circular A-130 | NIST standards, including FIPS 199 categorization, SP 800-53 controls and the SP 800-37 Risk Management Framework | Inspectors general, GAO, OMB; findings in public reports |
| Sector regulation | HIPAA Security Rule; FTC Safeguards Rule (16 CFR Part 314); NYDFS 23 NYCRR Part 500; bank examiners | A risk-based program with named elements; no single framework mandated | OCR, FTC, NYDFS, bank regulators; penalties, consent orders |
| State law for state agencies | Idaho Code 67-827A; ITA Policy P4140 | Idaho agencies: the current NIST CSF as the basis for assessments, plus multifactor sign-in7 | Idaho Office of Information Technology Services; legislative audits |
| State safe harbor laws | Ohio Rev. Code 1354.01 to 1354.05; Iowa Code chapter 554G | Voluntary: a written program that reasonably conforms to a listed framework earns a defense in breach lawsuits | A court, after a breach |
| Defense contracts | DFARS 252.204-7012; CMMC clauses 252.204-7021 and 7025 | NIST SP 800-171 Rev. 2 for covered defense information; CMMC level named in the solicitation | Contracting officer, DCMA, C3PAOs; loss of award; False Claims Act liability |
| Card payments | Merchant agreement, card brand rules | PCI DSS v4.0.1 | Acquiring bank, Qualified Security Assessor; fees, higher costs, loss of card acceptance |
| Selling cloud services to government | FedRAMP; GovRAMP for state and local buyers | Controls based on NIST SP 800-53 and the program's own rules | FedRAMP or GovRAMP program office, third-party assessors; no listing, no sale |
| Enterprise customers | Master services agreements, security addenda, questionnaires | SOC 2 Type 2 (U.S.), ISO/IEC 27001 certificate (global), HITRUST (health care) | The customer's vendor risk team; lost deals and renewals |
| Insurers | Cyber policy applications and renewals | Specific controls (multifactor sign-in, backups, endpoint detection) more than named frameworks | Underwriters; denied coverage, exclusions, higher premiums |
Laws that point to frameworks
A small but important group of laws reward or require framework use without making any one framework mandatory.
HITECH's recognized security practices (2021). Public Law 116-321, signed Jan. 5, 2021, added section 13412 to the HITECH Act. When HHS decides HIPAA fines, audits or settlement terms, it "shall consider" whether a covered entity or business associate "adequately demonstrated that it had, for not less than the previous 12 months, recognized security practices in place." The law defines those practices to include standards and guidance developed under the NIST Act (that is, the CSF and NIST special publications), the approaches published under section 405(d) of the Cybersecurity Act of 2015 (the health sector's HICP guide), and other programs recognized by regulation, and it lets the organization choose which.8 The law does not excuse a breach. It rewards documented, year-old practice when penalties are set.
Ohio's safe harbor (2018). Ohio Senate Bill 220, effective Nov. 2, 2018, gives a business an affirmative defense to tort claims alleging failure to implement reasonable security if it creates, maintains and complies with a written cybersecurity program that "reasonably conforms to an industry recognized cybersecurity framework."9 Ohio Revised Code 1354.03 lists the qualifying frameworks: the NIST CSF, NIST SP 800-171, NIST SP 800-53 and 800-53A, the FedRAMP security assessment framework, the CIS Controls, and the ISO/IEC 27000 family; or, for regulated entities, the HIPAA Security Rule, GLBA Title V or FISMA; or PCI DSS combined with one of the listed frameworks. One rule deserves attention from every compliance office: when a listed framework publishes a final revision, a business relying on it must conform to the revision "not later than one year after the publication date stated in the revision."10 For an Ohio business that relied on CSF 1.1, that clock started when CSF 2.0 was published on Feb. 26, 2024.
Iowa's safe harbor (2023). Iowa Code chapter 554G, enacted in 2023 Acts chapter 63, follows the Ohio model with the same six frameworks, a similar list of federal regimes, and the same one-year limit for catching up to a revision. It also states plainly that it creates no private right of action.11 Other states have adopted similar defenses; their texts differ, so the compliance office should read each state's current statute before relying on one.
Idaho's rule for its own agencies. The Idaho Technology Authority (ITA), which sets statewide information technology policy, adopted the NIST CSF for state agencies in 2016. ITA Policy P4140, last revised Aug. 20, 2024, says: "State agencies shall adopt the current NIST Cybersecurity Framework as the basis for assessing their cybersecurity programs." The 2024 revision added the word "current" and pointed to CSF 2.0.7 Separately, Idaho Code 67-827A directs the Office of Information Technology Services to ensure that all state agencies "implement and maintain cybersecurity best practices" and to require multifactor sign-in for access to state systems.12 This lesson did not find a comparable safe harbor statute for private businesses in the Idaho Code; check the current code before assuming none exists.
Rules that name elements, not frameworks. The FTC Safeguards Rule, NYDFS Part 500 and the HIPAA Security Rule each list required program elements (a qualified person in charge, a written risk assessment, access controls, encryption, multifactor authentication, training, vendor oversight, incident response). None tells a company to adopt CSF or ISO. A framework is still the practical way to show that each required element exists, works and is reviewed. Lesson 4 covers NYDFS and the Safeguards Rule's board reporting duties.
Contracts, customers and insurers
For most private organizations the real force comes from the money. A defense subcontractor faces NIST SP 800-171 because its prime contractor flows down DFARS 252.204-7012. A software company faces SOC 2 because its largest customers will not renew without it. A hospital faces PCI DSS in its gift shop and parking garage because it takes cards, and HITRUST because a payer asked. A city faces GovRAMP questions when it buys cloud software, and its insurer asks whether every administrator signs in with a second factor. Each of these can be met from one well-run program, if the program was built with the map in mind.
NIST Cybersecurity Framework 2.0: the common index
NIST released the original Cybersecurity Framework in February 2014 for critical infrastructure, updated it as version 1.1 in April 2018, and published CSF 2.0 as NIST Cybersecurity White Paper 29 on Feb. 26, 2024. The 2.0 edition dropped the critical infrastructure framing; NIST now says the CSF can be used "by any organization, regardless of its size, sector, or maturity."1 It is free, short (32 pages) and public domain.
The six Functions and the new Govern function
The CSF Core is a hierarchy: Functions, then Categories, then Subcategories (specific outcomes). Version 2.0 has six Functions:
| Function | NIST's short description (quoted) | Examples of what sits under it |
|---|---|---|
| Govern (GV) | "strategy, expectations, and policy are established, communicated, and monitored" | Organizational context, risk management strategy, roles and authorities, policy, oversight, supply chain risk management |
| Identify (ID) | "current cybersecurity risks are understood" | Asset management, risk assessment, improvement |
| Protect (PR) | safeguards to manage the organization's cybersecurity risks "are used" | Identity and access control, awareness and training, data security, platform security, resilience of technology infrastructure |
| Detect (DE) | "Possible cybersecurity attacks and compromises are found and analyzed" | Continuous monitoring, adverse event analysis |
| Respond (RS) | "Actions regarding a detected cybersecurity incident are taken" | Incident management, analysis, reporting, mitigation |
| Recover (RC) | "Assets and operations affected by a cybersecurity incident are restored" | Recovery plan execution, recovery communication |
Govern is the big change from version 1.1. It pulls governance outcomes that had been scattered or missing into one place and adds a full Category on cybersecurity supply chain risk management (GV.SC). Its six Categories are Organizational Context, Risk Management Strategy, Roles, Responsibilities, and Authorities, Policy, Oversight, and Cybersecurity Supply Chain Risk Management.1 For boards this matters: the CSF now speaks directly to who decides, who is accountable, and how leadership checks that the strategy is working, the same subjects covered in lesson 4. Counting the outcomes listed in the CSF 2.0 Core, there are 22 Categories and 106 Subcategories, down from 23 Categories and 108 Subcategories in version 1.1.
Tiers and Profiles
Tiers describe how rigorous an organization's risk governance and management practices are: Tier 1 (Partial), Tier 2 (Risk Informed), Tier 3 (Repeatable) and Tier 4 (Adaptive). NIST describes Tier 1 as an approach in which the risk strategy "is managed in an ad hoc manner."1 Tiers are not maturity scores for individual controls and not grades to put in a press release. They are a way for leadership to decide how formal the program should be given the organization's risks, and to see where practice falls short of intent.
Profiles are where the CSF becomes a working tool. A Current Profile describes the outcomes the organization is achieving now; a Target Profile describes the outcomes it has chosen to reach, given new requirements, threats and technology. The gap between them becomes the plan. Community Profiles are published baselines for a sector, technology or threat, which an organization can start from: NIST has finalized CSF 2.0 Community Profiles for ransomware risk management (IR 8374 Rev. 1), incident response (SP 800-61 Rev. 3, April 3, 2025) and transit (IR 8576), and has drafts for manufacturing and other areas.13
The CSF's free supporting library
NIST surrounds the CSF with free material: Quick-Start Guides for small businesses, enterprise risk management, supply chain risk and organizational profiles; Implementation Examples for each Subcategory; and translations in more than ten languages. In 2026 NIST finalized SP 1308, a Quick-Start Guide on connecting cybersecurity to enterprise risk management and workforce management, and SP 1347, the Informative References Quick-Start Guide, which explains how to find and use the mappings described later in this lesson.14 NIST also maintains the NIST IR 8286 series on cybersecurity and enterprise risk management, updated in December 2025 to align with CSF 2.0; lesson 2 explains how to use it.13
What the CSF is not
- Not a certification. There is no CSF certificate. A vendor that says it is "NIST certified" is describing its own assessment, or a different program.
- Not a control list. PR.AA-03 says "Users, services, and hardware are authenticated." It does not say how. The how lives in SP 800-53, CIS, ISO or the organization's own standards.1
- Not a guarantee. An organization can map every Subcategory and still be breached. The CSF's value is that it makes gaps visible and decisions traceable.
- Not mandatory for private organizations, unless a contract, a state agency policy such as Idaho's, or a customer says so.
NIST SP 800-53 Rev. 5: the master control catalog
NIST Special Publication 800-53, Security and Privacy Controls for Information Systems and Organizations, is the most detailed public control catalog in the world. Revision 5 was published in September 2020 and updated Dec. 10, 2020. Its abstract describes "a catalog of security and privacy controls" meant to protect organizations and individuals "from a diverse set of threats and risks, including hostile attacks, human errors, natural disasters, structural failures, foreign intelligence entities, and privacy risks."3
The 20 control families
The controls are grouped into 20 families, each with a two-letter identifier: Access Control (AC), Awareness and Training (AT), Audit and Accountability (AU), Assessment, Authorization and Monitoring (CA), Configuration Management (CM), Contingency Planning (CP), Identification and Authentication (IA), Incident Response (IR), Maintenance (MA), Media Protection (MP), Physical and Environmental Protection (PE), Planning (PL), Program Management (PM), Personnel Security (PS), PII Processing and Transparency (PT), Risk Assessment (RA), System and Services Acquisition (SA), System and Communications Protection (SC), System and Information Integrity (SI), and Supply Chain Risk Management (SR).3 Each control has a base statement and often numbered "enhancements" that add strength, written as IA-2(1) and so on. Many controls contain organization-defined parameters, blanks the organization fills in (how many failed sign-ins before a lockout, how often to review access), which is how one catalog fits a three-person agency office and a cabinet department.
Revision 5 made three changes large organizations still feel. It rewrote controls as outcomes rather than as duties of the "information system," so private companies could use them without translation. It merged privacy controls into the catalog and added the PII Processing and Transparency family. And it added the Supply Chain Risk Management family. It also moved the baselines out to a companion document, SP 800-53B.15
Baselines, overlays and assessments
SP 800-53B sets low, moderate and high security control baselines and a privacy baseline. A federal system is assigned to low, moderate or high impact using FIPS 199 (the potential harm to confidentiality, integrity or availability), and the matching baseline is the starting control set, which the agency then tailors.15 "Overlays" adjust a baseline for a special setting; NIST SP 800-82 Rev. 3, for example, contains an operational technology overlay, explained in module 111 lesson 2. SP 800-53A gives assessment procedures for every control, which is what auditors and inspectors general test against. The whole cycle of categorize, select, implement, assess, authorize and monitor is the Risk Management Framework in SP 800-37 Rev. 2 (December 2018), covered in lesson 2.16
Release 5.2.0 (August 2025)
NIST now updates SP 800-53 through numbered releases of the online catalog. Release 5.2.0, issued Aug. 27, 2025, responded to Executive Order 14306 and focused on "improving the security and reliability of software updates and patches." It added new controls SA-15(13), SA-24 and SI-02(07), revised discussion text in other controls, and updated the SP 800-53A assessment procedures; SP 800-53B was re-released without content changes.17 NIST's publication page showed no newer release and no Revision 6 as of Nov. 13, 2026.3 In November 2025 NIST posted a final mapping from CSF 2.0 to SP 800-53 Release 5.2.0.13
Who uses SP 800-53
Federal agencies must, under FISMA and OMB policy. FedRAMP's traditional baselines are built on it. Many states, including Idaho, write agency standards that cite it. Ohio and Iowa list SP 800-53 and 800-53A as qualifying frameworks for their safe harbors.10 Large private organizations that want the most detail, especially those that sell to government or run critical infrastructure, use it as their master catalog and map everything else to it. Smaller organizations usually find it too large to use directly and start with CIS or the CSF instead.
NIST SP 800-171: protecting CUI outside the government
Controlled Unclassified Information (CUI) is sensitive government information that is not classified but must be protected by law, regulation or policy: export-controlled technical data, some law enforcement and health records, critical infrastructure details and the like. NIST SP 800-171 sets the security requirements for "components of nonfederal systems that process, store, or transmit CUI." It is derived from the moderate baseline of SP 800-53, trimmed to what a contractor's system needs.18
| SP 800-171 Rev. 2 | SP 800-171 Rev. 3 | |
|---|---|---|
| Published | February 2020, updated Jan. 28, 2021 | May 14, 2024 |
| Requirements | 110, in 14 families | 97 (counting requirements not withdrawn), in 17 families |
| New families | Planning; System and Services Acquisition; Supply Chain Risk Management | |
| Organization-defined parameters | Few | Many; the agency, or failing that the organization, fills in values |
| What DoD contracts require (Nov. 2026) | Yes, under DFARS 252.204-7012 and class deviations | Not yet required for DoD; DoD has kept Rev. 2 as the baseline |
The fewer requirements in Rev. 3 do not mean less work: many were combined, and Rev. 3 is more specific. In May 2024 DoD issued Class Deviation 2024-O0013 telling contracting officers to keep requiring Rev. 2, and its September 2026 class deviation again "requires baseline compliance with NIST SP 800-171 Rev 2" under DFARS 252.204-7012.19 Organizations that also serve civilian agencies should watch the proposed FAR CUI rule, which would apply 800-171 across the government; it was not final as of this check. A NIST mapping between CSF 2.0 and SP 800-171 Rev. 3 is available through OLIR.2 NIST also updated SP 800-172, the enhanced requirements for CUI tied to critical programs, as Rev. 3 on May 13, 2026; CMMC Level 3 still refers to the February 2021 edition.
CMMC 2.0: where defense contractors stand in November 2026
The Cybersecurity Maturity Model Certification (CMMC) program exists because self-attestation to SP 800-171 did not work well. DoD's program rule, 32 CFR Part 170, was published Oct. 15, 2024, at 89 FR 83092 and took effect Dec. 16, 2024.20 The companion DFARS acquisition rule, which puts CMMC into contracts through solicitation provision 252.204-7025 and clause 252.204-7021, was published Sept. 10, 2025, at 90 FR 43560 and took effect Nov. 10, 2025, starting Phase 1.21
| Level | Requirements | Who assesses | How often |
|---|---|---|---|
| Level 1 (Self) | 15 requirements from FAR 52.204-21 (basic safeguarding of federal contract information); all must be met, no plan of action allowed | The contractor, with an annual affirmation by a senior official | Every year |
| Level 2 (Self) | The 110 requirements of NIST SP 800-171 Rev. 2 | The contractor | Every three years, with annual affirmation |
| Level 2 (C3PAO) | The same 110 requirements | A Certified Third-Party Assessment Organization (C3PAO) | Every three years, with annual affirmation |
| Level 3 (DIBCAC) | Level 2 (C3PAO) status plus 24 selected requirements from NIST SP 800-172 (February 2021) | DCMA's Defense Industrial Base Cybersecurity Assessment Center | Every three years, with annual affirmation |
Conditional status is possible at Levels 2 and 3 if the organization reaches the minimum score, with open items closed within 180 days.20 The rule planned a four-phase rollout, each phase starting a year after the last. DoD estimated that 8,350 medium and large entities would need Level 2 certification assessments. Its own cost estimates for other-than-small entities, which exclude the cost of actually implementing the controls, were about $117,768 per three-year cycle for a Level 2 C3PAO assessment and $41,050 for the Level 3 government assessment portion.20
The July 2026 suspension
On July 13, 2026, the Department of War (the secondary name the Defense Department has used since a September 2025 executive order) suspended Phase 2, which would have made Level 2 C3PAO assessments the default starting Nov. 10, 2026, and created a CMMC review and reform task force with 60 days to examine the program. DoW Chief Information Officer Kirsten Davies called cybersecurity a "critical, nonnegotiable priority" but said the program was creating "prohibitive compliance costs and unacceptable bureaucratic burdens."22 DFARS Class Deviation 2026-O0025, Revision 3, signed Sept. 3, 2026, carries out the memo: it permits Level 1 (Self) or Level 2 (Self) requirements in procurements, requires baseline compliance with SP 800-171 Rev. 2 under DFARS 252.204-7012, "Suspends the November 2026 CMMC Phase 2 transition," and directs contracting officers to remove third-party CMMC requirements from existing contracts at the next option or scheduled modification.19
As of Nov. 13, 2026, no restart date had been announced. Independent trackers checked in mid-October reported that the task force report had gone to the CIO around Sept. 11, 2026, but had not been made public, and that the 32 CFR Part 170 rule itself had not been rescinded or amended.23 The CMMC Accreditation Body reported in late September 2026 that 117 C3PAOs were authorized and 2,362 final Level 2 certificates and 71 conditional Level 2 certificates had been issued; existing certifications stay valid for their three-year terms.24 This lesson could not confirm any official CMMC announcement made between Oct. 28 and Nov. 13, 2026.
What did not change matters more than what did. DFARS 252.204-7012 still requires SP 800-171 for covered defense information and 72-hour incident reports to DoD; self-assessment scores still go into the Supplier Performance Risk System (SPRS); and the Justice Department's Civil Cyber-Fraud Initiative still uses the False Claims Act against contractors that misstate compliance. A suspension of third-party assessments is not a suspension of the underlying duty.

ISO/IEC 27001:2022: the certifiable management system
ISO/IEC 27001 is published jointly by the International Organization for Standardization and the International Electrotechnical Commission. The current edition, the third, was published in October 2022, after editions in 2005 and 2013.25 It is a paid standard; this lesson describes it and does not reproduce it. The overview standard for the family, ISO/IEC 27000, reached its sixth edition in July 2026 and is listed by ISO as free to obtain.26
Clauses 4 to 10: the management system
The requirements an auditor tests are in clauses 4 through 10, which follow the common structure ISO uses for all its management system standards (quality, environment, safety and so on):
- Context of the organization (clause 4): the issues and interested parties that matter, and the scope of the ISMS.
- Leadership (clause 5): top management commitment, the information security policy, roles and authorities.
- Planning (clause 6): risk assessment and risk treatment, the Statement of Applicability, objectives and planning of changes.
- Support (clause 7): resources, competence, awareness, communication and documented information.
- Operation (clause 8): carrying out the risk assessments and treatment plans.
- Performance evaluation (clause 9): monitoring and measurement, internal audit and management review.
- Improvement (clause 10): nonconformities, corrective action and continual improvement.
Amendment 1 of February 2024, titled "Climate action changes," added climate change to clauses 4.1 and 4.2: the organization must determine whether climate change is a relevant issue and whether interested parties have climate-related requirements. It was part of a coordinated change ISO made across dozens of management system standards, did not create a new edition, and does not add a security control.27 Auditors now ask about it, and a one-paragraph, honest answer in the context analysis is usually enough for an office-based firm; a data center operator exposed to heat, flood or water shortage has more to say.
Annex A: 93 controls in four themes
Annex A lists reference controls, and its companion ISO/IEC 27002:2022 gives guidance on each. The 2022 revision cut the list from 114 controls in 14 domains to 93 controls in four themes, merging many and adding 11 new ones.28
| Theme | Controls | Examples |
|---|---|---|
| Organizational | 37 | Policies, roles, threat intelligence (new), information security for use of cloud services (new), ICT readiness for business continuity (new), supplier relationships |
| People | 8 | Screening, terms of employment, awareness and training, remote working |
| Physical | 14 | Physical perimeters, physical security monitoring (new), equipment siting |
| Technological | 34 | Secure authentication, configuration management (new), information deletion (new), data masking (new), data leakage prevention (new), monitoring activities (new), web filtering (new), secure coding (new) |
An organization does not have to implement all 93. It must compare its risk treatment against Annex A to make sure nothing necessary was overlooked, and document in the Statement of Applicability which controls apply, which do not and why. That document is the first thing a sophisticated customer should ask for after the certificate.
Certification and the 2025 transition
Certification bodies, which should themselves be accredited by a national accreditation body, run a two-stage initial audit, then surveillance audits in the following years and a recertification audit on a three-year cycle. Certificates to the 2013 edition had to be moved to the 2022 edition by Oct. 31, 2025, under the international accreditation community's transition rules (IAF MD 26); after that date, accredited 2013 certificates were no longer valid.29 A vendor still showing a 2013 certificate in 2026 is showing an expired document.
Three cautions apply to every ISO certificate. First, read the scope: a certificate for "corporate IT at the Denver headquarters" says nothing about the cloud product your organization buys. Second, check the accreditation: certificates from unaccredited "certification mills" exist and carry little weight. Third, a certificate shows that a management system is running; it does not promise that every control within it is strong. Related standards extend the family: ISO/IEC 27017 for cloud controls, 27018 for personal data in public clouds, 27701 for privacy management, and ISO/IEC 42001 (2023) for artificial intelligence management systems, which many organizations now certify alongside 27001.
CIS Critical Security Controls v8.1: the prioritized list
The Center for Internet Security, a nonprofit, publishes the CIS Critical Security Controls, a prioritized set of defensive actions built from what attackers actually do. Version 8.1, released June 25, 2024, kept the 18 Controls and 153 Safeguards of version 8 and added a governance security function and new asset classes so the Controls line up with CSF 2.0's Govern function.3031
The 18 Controls are: Inventory and Control of Enterprise Assets; Inventory and Control of Software Assets; Data Protection; Secure Configuration of Enterprise Assets and Software; Account Management; Access Control Management; Continuous Vulnerability Management; Audit Log Management; Email and Web Browser Protections; Malware Defenses; Data Recovery; Network Infrastructure Management; Network Monitoring and Defense; Security Awareness and Skills Training; Service Provider Management; Application Software Security; Incident Response Management; and Penetration Testing.32
The Safeguards are sorted into three Implementation Groups. IG1, which CIS calls "essential cyber hygiene," is the floor for every organization; IG2 adds Safeguards for organizations with several departments and regulated data; IG3 includes all of them, for organizations facing determined attackers. CIS's published v8 counts are 56 Safeguards in IG1, 130 cumulative in IG2 and all 153 in IG3; CIS says the 153 total did not change in v8.1.31 For a large organization, IG1 is not a finish line but a test: if any business unit cannot show IG1, the organization has a basic gap no amount of policy will cover.
CIS also publishes the CIS Benchmarks, consensus secure configuration guides for operating systems, cloud services and applications, and maps the Controls to CSF 2.0, SP 800-53, PCI DSS and other documents. NIST lists a CIS Controls v8.1 to CSF 2.0 mapping in its catalog.2 The Controls document itself is free and licensed under Creative Commons (CC BY-NC-ND 4.0), which allows noncommercial sharing without modification.32 Ohio and Iowa name the CIS Controls among their safe harbor frameworks.11
SOC 2 and the rest of the SOC family
System and Organization Controls (SOC) is the AICPA's family of reporting services that CPA firms provide about controls at service organizations. Large organizations deal with several kinds:
| Report | What it covers | Who reads it |
|---|---|---|
| SOC 1 | Controls at a service organization relevant to its customers' financial reporting (payroll processors, claims administrators, trust and custody services) | The customer's financial statement auditors and controller |
| SOC 2 | Controls relevant to security, availability, processing integrity, confidentiality or privacy, measured against the Trust Services Criteria | Customers' security, vendor risk and compliance teams, under a restricted-use agreement |
| SOC 3 | A short, general-use version of a SOC 2 opinion, without the detailed test results | Anyone; often posted on a website |
| SOC for Cybersecurity | An entity's whole cybersecurity risk management program, not a service | Boards, investors, business partners |
| SOC for Supply Chain | Controls over a production, manufacturing or distribution system, using the same five categories as SOC 2 | Customers of manufacturers and distributors |
The AICPA's SOC page describes SOC 2 as reporting on controls "relevant to security, availability, processing integrity, confidentiality, or privacy" and names the SOC for Cybersecurity and SOC for Supply Chain guides.4 The criteria in force are the 2017 Trust Services Criteria with revised points of focus published in 2022, available free from the AICPA with a free account.33 Security, the "common criteria," is in every SOC 2; the other four categories are added when the service makes promises in those areas.
Type 1, Type 2 and the parts of the report that matter
A Type 1 report gives the CPA's opinion on whether controls were suitably designed as of a single date. A Type 2 report adds whether they operated effectively over a period, usually six to twelve months, and lists the tests performed and any exceptions found. Enterprise buyers usually require Type 2. When reading one, a vendor manager should look at five things: the period covered (and whether a bridge letter covers the gap to today, see lesson 8); the system description and what is outside it; the auditor's opinion (unqualified, qualified or adverse); the exceptions in the test results and management's responses; and the "complementary user entity controls," the controls the vendor expects the customer to run. Subservice organizations, such as the cloud provider the vendor runs on, are either "carved out" (excluded, so you need their report too) or "inclusive."
The proposed 2027 criteria
On Oct. 26, 2026, the AICPA's Assurance Services Executive Committee released exposure drafts of proposed revisions to the Trust Services Criteria and the SOC 2 Description Criteria, titled the "Proposed 2027 SOC 2" criteria, saying they are intended to "enhance the relevance, clarity, and usability" of the criteria for today's technology and third-party risks.34 The drafts themselves are behind a free AICPA account; this lesson did not read them and cannot report their contents, comment deadline or effective date. Organizations that issue or rely on SOC 2 reports should read the drafts and plan for reports issued under the new criteria in 2027 or later.
PCI DSS v4.0.1: the card industry's contract standard
The Payment Card Industry Data Security Standard is written by the PCI Security Standards Council, founded by the major card brands, and applies to any entity that stores, processes or transmits cardholder data or could affect its security. Version 4.0.1, announced June 11, 2024, was a limited revision of v4.0 that fixed errors and clarified wording without adding or deleting requirements. Version 4.0 was retired Dec. 31, 2024, leaving v4.0.1 as the only active version.35 The council's standards page, checked Nov. 13, 2026, mentions no newer version.5
The standard has 12 principal requirements grouped under six goals: (1) install and maintain network security controls; (2) apply secure configurations; (3) protect stored account data; (4) protect cardholder data with strong cryptography during transmission over open, public networks; (5) protect systems and networks from malicious software; (6) develop and maintain secure systems and software; (7) restrict access by business need to know; (8) identify users and authenticate access; (9) restrict physical access; (10) log and monitor all access; (11) test security of systems and networks regularly; and (12) support information security with organizational policies and programs. When v4.0 came out in 2022, the council marked a large group of new requirements as best practices until March 31, 2025; they are now mandatory, including multifactor authentication for all access into the cardholder data environment and controls over scripts on payment pages. The PCI SSC said the v4.0.1 revision "does not impact the effective date of these new requirements."35
For large organizations, PCI DSS raises three issues small merchants rarely face: validating as a Level 1 merchant or service provider with an annual Report on Compliance by a Qualified Security Assessor; using the "customized approach," which lets a mature organization meet a requirement's stated objective in its own way with a documented targeted risk analysis; and scoping, because network segmentation and tokenization decide how much of a hospital, university or retailer is in scope at all. Module 73 lesson 5 covers merchant levels, questionnaires and scope reduction.

HITRUST, FedRAMP, GovRAMP and COBIT
HITRUST
HITRUST is a private organization whose HITRUST CSF (not to be confused with the NIST CSF) combines requirements from HIPAA, NIST, ISO, PCI and other sources into one control framework, assessed by approved external assessors and quality-checked by HITRUST before it issues a certification. Health plans and large health systems often require it of vendors. HITRUST's page lists three main validated assessments: e1, with 43 controls, valid one year; i1, with 182 control requirements, valid one year; and r2, a risk-based assessment valid two years. It also lists AI security and AI risk management assessments and a NIST CSF 2.0 add-on to r2.36 HITRUST is a paid, licensed program; its framework is not free to reproduce. Module 109 lesson 6 covers how health care organizations use it with business associates.
FedRAMP and FedRAMP 20x
The Federal Risk and Authorization Management Program, run by the General Services Administration, decides which cloud services federal agencies may use. Congress put it in statute in the FedRAMP Authorization Act of December 2022, and OMB memo M-24-15 (2024) directed its modernization; FedRAMP said in January 2026 it would complete the initial modernization required by both that year.37 The traditional "Rev5" path uses baselines built on NIST SP 800-53.
FedRAMP 20x, announced in March 2025, is the replacement path. It ran a Low pilot from April to September 2025 (26 complete packages) and a Moderate pilot from Nov. 18, 2025 through March 2026, with the first pilot authorizations on March 6, 2026. In its own words, "The pilots are over. FedRAMP 20x is here to stay." It now issues certifications in classes: Class A (for mature providers entering the federal market), Class B (common, light-use services) and Class C (enterprise services used across an agency), with Class D (high impact) to be developed in a pilot planned for fiscal 2027. FedRAMP says it will "stop accepting new Rev5 Certifications on June 11, 2027."38 On Nov. 2, 2026, it announced the first full 20x Class C certification, and on Nov. 13, 2026 its home page counted 557 certified services, 38 of them through 20x.39 Agencies and vendors should watch the program's consolidated rules for 2026, published in June 2026, rather than older guides.
GovRAMP (formerly StateRAMP)
GovRAMP, a nonprofit formerly called StateRAMP, offers a similar verification program for state, local, tribal and education governments, built on NIST SP 800-53 controls. Its tiers run from a Security Snapshot (an assessment of a top-40 control set) through Core, Ready and Authorized or Provisional verification, the last based on a third-party assessment of more than 300 controls with monthly monitoring. On Nov. 13, 2026 its site reported more than 1,200 member organizations and more than 330 products in the program, and on Nov. 2, 2026 it opened comment on a proposed "20x Delta Assessment" to align with FedRAMP 20x.40 Its home page does not mention Idaho; Idaho buyers should ask the Office of Information Technology Services what cloud security evidence the state requires.
COBIT 2019
COBIT, from ISACA, is an information and technology governance framework rather than a security standard. COBIT 2019 has 40 governance and management objectives covering how an enterprise directs, plans, builds, runs and monitors its technology, and is common in internal audit departments, banks and public agencies. ISACA's page, checked Nov. 13, 2026, still describes COBIT 2019 as current.41 Its publications are sold. Organizations use COBIT to frame IT governance and audit, and the CSF or ISO 27001 for security within it.
Sector frameworks that sit on top
Several sectors add their own layer, usually mapped back to the CSF:
- Health care: the HIPAA Security Rule, HHS's 405(d) Health Industry Cybersecurity Practices, and HHS's voluntary health care Cybersecurity Performance Goals. See module 109 lesson 3.
- Industrial and critical infrastructure: ISA/IEC 62443 (paid) and NIST SP 800-82 Rev. 3 for operational technology; NERC CIP for the bulk electric system; TSA security directives for pipelines and rail. See module 111 lesson 6.
- All critical infrastructure: CISA's Cross-Sector Cybersecurity Performance Goals, a short list of high-impact practices. CISA released CPG 2.0 on Dec. 10, 2025, adding "a new component focused on the essential role of governance" and aligning with CSF 2.0.42
- Financial services: the Cyber Risk Institute's CRI Profile, a financial-sector version of the CSF used by many banks; NIST lists a CRI Profile 2.0 to CSF 2.0 mapping.2 Bank examiners use their own procedures; lesson 4 covers NYDFS Part 500.
- Professional firms: the FTC Safeguards Rule and IRS Publication 4557 for tax and accounting firms, covered in module 110 lesson 4.
How the standards fit together
Put the five kinds of documents in layers and the map becomes readable. Laws and regulators set the duty. Contract and program rules decide who may sell to whom. Frameworks and catalogs say what to do, with the CSF as the index on top. Evidence shows whether it was done. Crosswalks connect the frameworks row so that one control, run well and tested once, can answer every layer above it.
Crosswalks and informative references
A crosswalk, which NIST calls an informative reference, is a mapping that shows how parts of one document relate to parts of another. NIST defines a CSF Informative Reference as "a mapping that indicates a relationship between a CSF Core outcome and an existing standard, guideline, regulation, or other content."1 Its new Informative References Quick-Start Guide (SP 1347, final Aug. 25, 2026) explains that each reference "indicates one or more parts of another document in which readers can find additional information on the topic (known as a crosswalk)," and walks through three ways to get them: a single Excel download of all CSF 2.0 references, the CSF 2.0 Reference Tool for browsing and filtering, and the Online Informative References (OLIR) program catalog, which can generate comparison reports between documents and export them to Excel or JSON.43
The OLIR catalog on Nov. 13, 2026 listed CSF 2.0 mappings to, among others, NIST SP 800-53 Release 5.2.0, SP 800-171 Rev. 3, ISO/IEC 27001:2022, CIS Controls v8.1, PCI DSS v4.0.1, the Cloud Security Alliance's Cloud Controls Matrix v4.0, the CRI Profile 2.0, the NICE workforce framework and the UK's Cyber Governance Code of Practice, plus newer mappings for artificial intelligence and the OWASP Top 10 for large language model applications.2 Two cautions from NIST's own page belong in every compliance office: NIST "does not conduct correctness testing on non-NIST submitted mappings," and listing a non-NIST mapping "does not imply NIST endorsement." A mapping says two items are related. It does not say they are the same, that meeting one meets the other, or that an auditor for one will accept evidence prepared for the other.
One control set, many reports
Large organizations that handle several standards well usually do the same thing: they build a single internal control library (often called a common control framework), map each control once to every obligation, give each control one owner, test it on one calendar, and collect evidence once in a form every reviewer can use. The CSF sits on top for reporting; one detailed catalog (SP 800-53 for government-facing organizations, ISO Annex A for global ones, CIS for organizations that want a short, prioritized list) sits underneath as the source of truth. When the HITRUST assessor, the SOC 2 auditor, the PCI assessor and the internal auditor arrive, they draw from the same evidence store.
This approach has three practical rules. First, write controls in the organization's own words, with the mapping beside them, so a change in one standard does not force a rewrite of the program. Second, keep the version and date of every standard in the mapping, because versions change: an organization mapped to CSF 1.1, ISO 27001:2013 or PCI DSS v3.2.1 is mapped to documents that no longer govern anything. Third, compliance automation software can track evidence and mappings, but it does not decide whether a control works, and its prebuilt mappings carry the same caution NIST applies to non-NIST mappings. Where a framework gap leads to changes in production systems, such as turning on multifactor sign-in for every administrator or segmenting a network, plan each change, test it, and keep a way back.
How to pick: a method for large and regulated organizations
- List every obligation, with its source. Laws and regulators, contracts and clauses, customer requirements, card agreements, insurance applications, grant terms. Name the document and version each one cites. The general counsel's office and procurement usually hold half this list; the CISO holds the other half.
- Sort each by kind and consequence. Is it a duty (law), a gate (contract or program), a request (customer), or a price factor (insurer)? What happens on failure, and who checks?
- Choose the index. For nearly every U.S. organization, CSF 2.0. Write a Current Profile and a Target Profile, and present both to the board.
- Choose one detailed catalog as the source of truth. SP 800-53 if you serve or are government, run critical infrastructure, or need the most detail; ISO/IEC 27001 Annex A if you sell globally or customers want a certificate; CIS Controls if you need a short, prioritized technical list. Map the others to it.
- Decide which evidence you must buy. SOC 2 Type 2, ISO certificate, HITRUST, PCI Report on Compliance, CMMC assessment, FedRAMP or GovRAMP: pick only what a real customer, contract or program requires, and schedule each so the evidence periods line up.
- Set the calendar and the owners. One owner per control, test dates, revision watch (who checks NIST, ISO, AICPA, PCI SSC, DoD and FedRAMP for changes each quarter), and the dates any safe harbor clock or certificate expires.
- Report one way to the board. CSF Functions, Current against Target, top gaps with owners and dates, and the status of every external certificate or report. Lesson 4 covers board reporting in detail.
The table shows stacks that commonly result. They are starting points for analysis, not legal conclusions about any particular organization.
| Organization | Typical duties and gates | Common index and catalog | Evidence commonly bought |
|---|---|---|---|
| Hospital or health system | HIPAA Security Rule; PCI DSS for cards; SP 800-171 for some federally funded research involving CUI | CSF 2.0 with HHS 405(d) practices; SP 800-53 or ISO Annex A | HITRUST for payer and partner demands; PCI Report on Compliance or questionnaire |
| Bank or credit union | GLBA and examiner expectations; NYDFS Part 500 if licensed in New York; PCI DSS | CSF or the CRI Profile; SP 800-53 or ISO Annex A | SOC 1 and SOC 2 from key vendors; PCI validation |
| Software or cloud provider | Customer contracts; FedRAMP or GovRAMP for government sales | CSF; ISO Annex A or SP 800-53 | SOC 2 Type 2; ISO/IEC 27001 (and 27017, 27018, 42001); FedRAMP or GovRAMP |
| Defense manufacturer | DFARS 252.204-7012; CMMC as named in solicitations; ISA/IEC 62443 on the plant floor | SP 800-171 Rev. 2 now, watching Rev. 3; CSF | SPRS self-assessment; CMMC Level 2 C3PAO when required |
| State agency, city or county | State policy (in Idaho, ITA P4140 and Idaho Code 67-827A); CJIS rules for criminal justice data; PCI DSS for payments | CSF 2.0; SP 800-53 or CIS IG1 and IG2 | GovRAMP or FedRAMP evidence from cloud vendors; audits |
| University | GLBA for student financial aid; HIPAA for a medical center; SP 800-171 for research CUI; PCI DSS | CSF; SP 800-53 or CIS | SOC 2 from vendors; CMMC for defense research where required |
| Public company (any sector) | SEC disclosure of cybersecurity processes in Form 10-K Item 1C; sector rules | CSF for board and disclosure language; a detailed catalog underneath | Whatever customers and sector rules require; internal audit testing |

Pictures, Numbers and Infographics
The numbers below are the ones most often asked for in board meetings, audits and procurement reviews. Each comes from the publisher's or regulator's own document, read on the date shown in its note.
| Item | Number or date | Source |
|---|---|---|
| NIST CSF 2.0 published | Feb. 26, 2024; 6 Functions, 22 Categories, 106 Subcategories | NIST CSWP 291 |
| NIST SP 800-53 Rev. 5 | 20 control families; Release 5.2.0 on Aug. 27, 2025, with 3 new controls (SA-15(13), SA-24, SI-02(07)) | NIST17 |
| NIST SP 800-171 | Rev. 2: 110 requirements in 14 families; Rev. 3 (May 14, 2024): 97 requirements in 17 families | NIST18 |
| CMMC program rule and DFARS rule | Effective Dec. 16, 2024 and Nov. 10, 2025; Phase 2 (planned Nov. 10, 2026) suspended July 13, 2026 | Federal Register; DoW202122 |
| DoD estimate of entities needing Level 2 C3PAO assessments | 8,350 medium and large entities | 89 FR 8309220 |
| DoD cost estimate, Level 2 C3PAO assessment, other-than-small entity | About $117,768 per three-year cycle, not counting implementation | 89 FR 8309220 |
| CMMC assessment capacity, late September 2026 | 117 C3PAOs; 2,362 final and 71 conditional Level 2 certificates | Cyber AB figures as reported24 |
| ISO/IEC 27002:2022 controls | 93 (37 organizational, 8 people, 14 physical, 34 technological), down from 114; 11 new | Certification body summary28 |
| End of ISO/IEC 27001:2013 certificates | Oct. 31, 2025 | Accreditation body notice29 |
| CIS Controls v8.1 | 18 Controls, 153 Safeguards; IG1 = 56 Safeguards (v8 count) | CIS31 |
| PCI DSS v4.0.1 | Published June 11, 2024; 12 principal requirements; future-dated requirements mandatory March 31, 2025 | PCI SSC35 |
| HITRUST validated assessments | e1: 43 controls, 1 year; i1: 182 requirements, 1 year; r2: 2 years | HITRUST36 |
| FedRAMP marketplace | 557 certified services, 38 through 20x (Nov. 13, 2026); new Rev5 certifications end June 11, 2027 (planned) | FedRAMP3938 |
| GovRAMP | More than 1,200 member organizations; more than 330 products | GovRAMP40 |
| COBIT 2019 | 40 governance and management objectives | ISACA41 |
| Ohio safe harbor | Effective Nov. 2, 2018; one year to conform after a framework revision | Ohio Rev. Code 1354.0310 |
| HITECH recognized security practices | At least 12 months in place before HHS must consider them; law signed Jan. 5, 2021 | Public Law 116-3218 |
| Idaho agencies and the CSF | ITA P4140 established Oct. 17, 2001; NIST CSF adopted 2016; "current" CSF required since Aug. 20, 2024 | ITA7 |
| SolarWinds internal NIST assessment, Sept. 2019 (SEC allegation) | "program/practice in place" for 21 of 325 controls (6 percent) | SEC complaint44 |
| MORSECORP SPRS score (DOJ, admitted facts) | Reported 104 in January 2021; consultant found -142 in July 2022; settlement $4.6 million (March 26, 2025) | DOJ45 |
Common mistakes
Claiming to "follow" a framework you have not met
In October 2023 the SEC sued SolarWinds and its chief information security officer, alleging that the company's public Security Statement misled investors. The complaint quotes the statement as saying "SolarWinds follows the NIST Cybersecurity Framework with layered security controls," and alleges that the company's own internal assessments, run against the SP 800-53 moderate baseline, found a "program/practice in place" for only 21 of 325 controls (6 percent) in September 2019, and that a January 2021 assessment found 60 percent of controls unmet.4446 These are allegations, and the case's later rulings and outcome are covered in lesson 4. The lesson for every compliance office is the same whatever the outcome: a framework claim on a website, in a questionnaire or in a filing is a statement of fact, and the organization's own assessments are the evidence that will be used to test it.
Reporting a score you know is wrong, or not updating it
MORSECORP, a Massachusetts defense contractor, agreed on March 26, 2025, to pay $4.6 million to settle False Claims Act allegations. In facts it admitted, the company had reported an SP 800-171 score of 104 (the scale runs from -203 to 110) in January 2021; a consultant told it in July 2022 that its actual score was -142; and it did not update the score in the government's system until June 2023, three months after being served with a subpoena.45 The settlement is one of a line of cases under the Justice Department's Civil Cyber-Fraud Initiative. A self-assessment is not a private document once it is submitted: it must be kept current when the facts change.
Scoping fiction
Georgia Tech Research Corporation agreed on Sept. 30, 2025, to pay $875,000 to resolve allegations that a lab doing sensitive Defense Department cyber research ran without antivirus or anti-malware tools until December 2021, had no system security plan until at least February 2020, and that the institution submitted a campus-wide score of 98 in December 2020 even though there was no campus-wide system; the government called the assessed environment "fictitious" or "virtual." There was no determination of liability.47 A score or a certificate is only as meaningful as its scope, and the scope must match the systems that actually handle the data.
Assuming the cloud vendor is covered
The same MORSECORP settlement included the admitted fact that, from January 2018 to September 2022, the company used a third-party email host without ensuring it met security requirements equivalent to the FedRAMP Moderate baseline, as DFARS 252.204-7012 requires for cloud services handling covered defense information.45 A vendor's general security reputation is not the evidence a rule asks for. Check the specific authorization, certificate or report the rule names.
Paperwork that does not hold up
Aerojet Rocketdyne agreed on July 8, 2022, to pay $9 million to resolve a whistleblower's allegations that it misrepresented its compliance with federal contract cybersecurity requirements. The whistleblower, a former employee, received $2.61 million, and the case settled on the second day of trial; there was no determination of liability.48 Employees who know the gap between the compliance documents and reality can bring these cases themselves, and the law rewards them for it.
Letting a version or certificate lapse
ISO/IEC 27001:2013 certificates ended Oct. 31, 2025.29 PCI DSS v4.0 ended Dec. 31, 2024.35 Ohio's safe harbor requires conformity to a framework's revision within one year of its publication.10 Contracts that say "NIST CSF" without a version now arguably mean 2.0. A program that does not track versions will discover the lapse when a customer, an auditor or a court does.
Treating a mapping as equivalence
NIST's catalog warns that it does not test non-NIST mappings for correctness and that listing them does not imply endorsement.2 An organization certified to ISO/IEC 27001 has not thereby met SP 800-171, and a SOC 2 report does not satisfy a HIPAA risk analysis. Use mappings to find overlap and reuse evidence, then check each obligation's own wording.
Questions people ask
Is the NIST Cybersecurity Framework mandatory?
Not for private organizations in general. NIST describes it as a framework that can be used voluntarily or through government policies. It becomes mandatory by adoption: Idaho state agencies under ITA Policy P4140, for example, or a company whose contract names it.7 It is also the framework most often named in board reporting, insurance applications and state safe harbor laws, which makes it the default index even where no one requires it.
Which detailed catalog should a large organization use underneath the CSF?
Pick by your heaviest obligation. Government-facing organizations and critical infrastructure usually choose SP 800-53, because federal, FedRAMP, GovRAMP and many state rules are written in its terms. Organizations that sell globally or are asked for certificates choose ISO/IEC 27001 Annex A. Organizations that need a short, prioritized technical list, or that are starting late, choose CIS Controls. Most large programs end up using one as the source of truth and mapping the others.
Is ISO/IEC 27001 better than SOC 2?
They answer different questions. ISO certifies that a management system for security exists and runs, across a stated scope, and is recognized worldwide. A SOC 2 Type 2 report gives a CPA's opinion on whether specific controls operated over a period, with the tests and exceptions listed, and is the report U.S. enterprise buyers usually ask for. Many service providers maintain both and run them from one control set.
We are ISO certified. Does that satisfy CMMC or HIPAA?
No. CMMC requires the specific requirements of SP 800-171 (and FAR 52.204-21 at Level 1), assessed by the method the rule sets. HIPAA requires a risk analysis and the safeguards in 45 CFR Part 164 Subpart C. A good ISO program will already cover much of the ground, and mappings will show where, but each obligation must be met and documented in its own terms.
Our contracts still say "NIST CSF 1.1." What do we do?
Read the clause. If it names version 1.1, you can meet it as written while building to 2.0; the mapping NIST publishes between versions helps. If it says "current" or names no version, assume 2.0. Ohio and Iowa safe harbors expect conformity to a revision within a year of publication, so organizations relying on them should already be on 2.0.11
What should the board see about framework status?
One page, quarterly: the CSF Functions with Current against Target, the organization's chosen Tier and whether practice matches it, the top gaps with owners and due dates, and a list of every external certificate or report with its scope, period and expiry. Detail stays with the risk or audit committee. Lesson 4 covers what boards owe and what public companies must disclose.
With CMMC Phase 2 suspended, should defense suppliers stop preparing?
The duty to implement SP 800-171 under DFARS 252.204-7012 did not pause, and self-assessments and SPRS scores are still required where the contract calls for them.19 False Claims Act exposure depends on what a contractor certified, not on whether a third party checked it. Preparation for a third-party assessment is also preparation for that exposure. The schedule may change; the requirement has not.
Hard questions
Should the federal government require private companies to follow one framework?
The case for a mandate: voluntary adoption is uneven, attackers exploit the weakest firms in a supply chain, and the patchwork of sector rules, contract clauses and state laws costs large organizations heavily in duplicate audits. One required baseline, such as the CSF with a minimum control set, would raise the floor and let one assessment count everywhere. The case against: security needs differ widely by size and sector; a mandated framework turns into a checklist that lags threats; the CSF's value comes partly from being flexible and voluntary; and agencies already have sector authority. What the evidence shows: the trend in 2025 and 2026 has been mixed rather than toward one mandate. CISA's CPG 2.0 remains voluntary, DoD paused a third-party mandate on cost grounds, and FedRAMP rebuilt its process around measured security indicators rather than longer documents.422238 This lesson found no rigorous study showing that mandated frameworks, as opposed to specific required controls such as multifactor authentication, reduce breaches.
Third-party certification or self-attestation?
For third-party checks: self-assessed scores have been wrong in documented cases, by large margins (104 reported against -142 found at MORSECORP), and buyers cannot audit every supplier themselves.45 For self-attestation: third-party assessments are expensive (DoD estimated about $104,670 to $117,768 per three-year Level 2 cycle before any remediation), assessor capacity is limited, and small suppliers may leave the market.20 What the evidence shows: by late September 2026, 2,362 final Level 2 certificates had been issued against DoD's estimate that 8,350 entities would need them, which supports the capacity concern; the documented false-score cases support the accuracy concern.24 A middle path some programs use is self-assessment with personal affirmation, backed by targeted government audits and False Claims Act enforcement.
Do certificates make organizations safer, or just better documented?
Skeptics' case: certified organizations are breached; audits sample rather than test everything; scope can be drawn to exclude what matters; and a market of compliance tools rewards evidence collection over security. Defenders' case: the management discipline of ISO, the testing of SOC 2 and the third-party review of CMMC force organizations to find and fix gaps they would otherwise ignore, and the evidence trail matters when regulators judge reasonableness. What the evidence shows: public outcome studies comparing certified and uncertified organizations are scarce, and this lesson found none it would rely on. The documented enforcement cases point to a narrower conclusion: harm comes most often from claims that outrun reality, which certification can either expose or conceal depending on scope and honesty.
Should states give breach-lawsuit safe harbors to companies that follow frameworks?
For: safe harbors reward investment before a breach, give companies a clear target, and reduce lawsuits against organizations that acted reasonably but were still attacked. Against: "reasonably conforms" is hard for a consumer to test, the defense can shift the cost of a breach to the people whose data was taken, and a written program can look better than practice. What the evidence shows: Ohio's law has been in force since 2018 and Iowa's since 2023, and both limit the defense to tort claims and require keeping up with revisions.911 How often courts have applied these defenses is not well documented in public sources; this lesson did not survey case law, so the effect on breach rates or litigation remains an open question.
For reporters and advocates
What public records exist.
- SEC filings. Since the 2023 rules, public companies describe their cybersecurity risk management processes in Form 10-K Item 1C, and many name the framework they "use" or are "guided by." EDGAR full-text search lets you find every filer that names NIST CSF, ISO 27001 or CIS. Compare those words with any later Form 8-K Item 1.05 incident report. SEC complaints, such as the SolarWinds complaint, quote internal assessments.44
- Justice Department releases. Civil Cyber-Fraud Initiative settlements (MORSECORP, Georgia Tech, Aerojet and others) describe what contractors claimed and what was true.4547
- Program listings. The FedRAMP Marketplace and GovRAMP's product list show which cloud services are certified and at what level.3940 The Cyber AB publishes authorized C3PAOs. ISO certificates can often be checked through the certification body or the accreditation community's certificate search; ask a company for its certificate number and certification body.
- Federal oversight. Agency inspectors general report each year on agency information security programs under FISMA, and GAO reports on federal cybersecurity, CMMC and FedRAMP.
- State records. Idaho ITA policies are public at ita.idaho.gov.49 Ask state agencies, through a request under the Idaho Public Records Act (Idaho Code Title 74, chapter 1), for the date and scope of their most recent CSF assessment under P4140 and the existence of a plan to close gaps. Expect detailed vulnerability information to be withheld for security reasons; summaries, dates, vendor contracts and audit findings are often obtainable. Idaho legislative audit reports on agencies are also public.
- Court dockets. Breach lawsuits in Ohio and Iowa may raise the safe harbor defense; search PACER, CourtListener and state dockets for the statute numbers.
Questions to ask any organization that claims a standard. Which standard, which version, and for what scope? Who assessed it, when, and was the assessor independent and accredited? Can you see the certificate, the Statement of Applicability, the SOC 2 report or the CSF profile? What were the exceptions or open items, and when will they close? If the claim appears in a public filing or a contract, does it match the latest internal assessment? For a public agency: which framework does state policy require, when was the last assessment, and who on the governing body has seen it?
The Idaho angle. Idaho requires its state agencies to use the current NIST CSF (ITA P4140, revised Aug. 20, 2024) and requires multifactor sign-in across state government (Idaho Code 67-827A, as amended in 2025).712 Idaho companies and universities that hold defense contracts or subcontracts live under DFARS 252.204-7012 and CMMC like everyone else. This lesson did not find a private-sector safe harbor statute of the Ohio or Iowa kind in Idaho. Good questions for legislators and county commissioners: Have cities, counties and school districts adopted any framework, and who checks? Should Idaho consider a safe harbor, and with what limits? How are state cloud purchases verified?
Where to go next
- NIST Cybersecurity Framework portal: Free. The CSF 2.0 document, Quick-Start Guides, Community Profiles, translations and the CSF 2.0 Reference Tool. Start with the Organizational Profiles and Enterprise Risk Management guides to build Current and Target Profiles.
- NIST CSF 2.0 Informative References and OLIR catalog: Free. Download every CSF 2.0 mapping in one spreadsheet or generate comparison reports between documents; use with SP 1347 to build a crosswalk for a common control framework.
- NIST SP 800-53 Rev. 5 and SP 800-53B: Free. The master control catalog and baselines, also available as spreadsheets and machine-readable OSCAL files. For organizations that serve government or need the most detail.
- CIS Critical Security Controls v8.1: Free with registration for the document; the online control finder and mappings are on the CIS site. Use IG1 as the minimum test for every business unit.
- AICPA Trust Services Criteria: Free with a free AICPA account. The criteria SOC 2 reports measure against; also check the October 2026 exposure drafts for the proposed 2027 criteria.
- FedRAMP Marketplace and 20x: Free. Shows which cloud services are certified for federal use and how the 20x classes work; useful for any public agency evaluating cloud vendors.
- Idaho Technology Authority policies: Free. Idaho's statewide IT security policies, including P4140 (NIST CSF), P4502 (privileged access MFA) and P4520 (patching). For Idaho agencies, their vendors and anyone asking how the state manages its own security.
- PCI Security Standards Council document library: Free with license acceptance. PCI DSS v4.0.1, self-assessment questionnaires and FAQs for any organization that takes payment cards.
Still being checked (10 items)
These points could not be fully confirmed against a primary source when this lesson was written and fact checked in November 2026. The text above states each one as uncertain.
- No official CMMC announcement made between Oct. 28 and Nov. 13, 2026 could be confirmed; the latest independent trackers read were dated Oct. 12 to Oct. 19, 2026. The web search budget ran out during research, so later news may exist.
- The contents, comment deadline and effective date of the AICPA's Oct. 26, 2026 exposure drafts of proposed 2027 SOC 2 criteria were not read (they require an account).
- CIS Implementation Group counts (56 in IG1, 130 cumulative in IG2) come from CIS's v8 handout; CIS confirms the 153 total for v8.1 but the per-group counts were not rechecked against the v8.1 workbook.
- ISO's own catalogue page for ISO/IEC 27001 could not be retrieved; the edition date, Amd 1:2024 and the Oct. 31, 2025 transition are from a certification body summary, an accreditation body notice and a standards reseller's catalogue.
- The SEC v. SolarWinds court rulings and final outcome were not rechecked for this lesson; the text relies on the 2023 complaint and press release and refers to lesson 04.
- GovRAMP's rename from StateRAMP is described from general knowledge and the site's branding; the exact rename date was not confirmed.
- NIST SP 800-172 Rev. 3 (May 13, 2026), DoD Class Deviation 2024-O0013 (May 2024) and the status of the FAR CUI rule were taken from the module 111 fact sheet verified Oct. 28, 2026 and not rechecked.
- The Department of War name's basis (a September 2025 executive order) was not rechecked.
- This lesson did not search for an Idaho private-sector cybersecurity safe harbor statute exhaustively, and did not survey case law applying the Ohio or Iowa safe harbors.
- Some states besides Ohio and Iowa (for example Utah and Connecticut) are reported to have similar safe harbor laws; their texts were not read and they are not named in the lesson.
Last verified November 14, 2026. General education, not legal, compliance, audit or other professional advice; rule versions and dates are stated in the text, and the sources used are listed in the Notes and Sources below. Check the regulator's current text before relying on any point.
Notes
- National Institute of Standards and Technology, The NIST Cybersecurity Framework (CSF) 2.0, NIST CSWP 29, Feb. 26, 2024: abstract, Sections 2 to 4 (Functions, Tiers, Profiles, online resources), Appendix A (Core) and glossary; counts of 22 Categories and 106 Subcategories tallied from Appendix A (read Nov. 13, 2026). Read it online. ↩
- NIST, "CSF 2.0 Informative References" (catalog of mappings, recent additions, and the statement that NIST "does not conduct correctness testing on non-NIST submitted mappings") (read Nov. 13, 2026). Read it online. ↩
- NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations, September 2020 (updated Dec. 10, 2020), publication page with Release 5.2.0 notes and the 20 control families; abstract quoted from the PDF (read Nov. 13, 2026). Read it online. ↩
- AICPA and CIMA, "System and Organization Controls: SOC Suite of Services" (read Nov. 13, 2026). Read it online. ↩
- PCI Security Standards Council, "PCI Data Security Standard (PCI DSS)" standards page, last modified April 8, 2026 (read Nov. 13, 2026). Read it online. ↩
- Jeff A. Pierson, "The HIPAA Security Rule and the Proposed Update," module 109, lesson 3 (status of the Jan. 6, 2025 proposal, 90 FR 898, as of Oct. 28, 2026) (read Nov. 13, 2026). Read it online. ↩
- Idaho Technology Authority, Enterprise Policy P4140, "Cybersecurity Framework," established Oct. 17, 2001, revision history through Aug. 20, 2024 (authority: Idaho Code 67-831 to 67-833) (read Nov. 13, 2026). Read it online. ↩
- Public Law 116-321, 134 Stat. 5072 (Jan. 5, 2021), adding section 13412, "Recognition of Security Practices," to the HITECH Act (42 U.S.C. 17941) (read Nov. 13, 2026). Read it online. ↩
- Ohio Revised Code 1354.02, "Safe harbor requirements," effective Nov. 2, 2018 (Senate Bill 220, 132nd General Assembly) (read Nov. 13, 2026). Read it online. ↩
- Ohio Revised Code 1354.03, "Reasonable conformance," effective Nov. 2, 2018 (Senate Bill 220, 132nd General Assembly) (read Nov. 13, 2026). Read it online. ↩
- Iowa Code chapter 554G, "Tort Liability: Cybersecurity Programs," sections 554G.1 to 554G.4 (2023 Acts, ch. 63), Iowa Code 2026 text (read Nov. 13, 2026). Read it online. ↩
- Idaho Code 67-827A, "Powers and duties" of the Office of Information Technology Services, subsections (5) to (11), as amended through 2025 (read Nov. 13, 2026). Read it online. ↩
- NIST, "Cybersecurity Framework: Updates Archive" (2024 to 2026 entries, including IR 8374 Rev. 1, SP 800-61 Rev. 3 of April 3, 2025, IR 8576, SP 1308, the Dec. 18, 2025 IR 8286 updates and the Nov. 17, 2025 CSF 2.0 to SP 800-53 Release 5.2.0 mapping) (read Nov. 13, 2026). Read it online. ↩
- NIST Computer Security Resource Center, "NIST Releases Two New CSF 2.0 Quick-Start Guides" (SP 1308 final and SP 1347 draft), March 23, 2026 (read Nov. 13, 2026). Read it online. ↩
- NIST SP 800-53B, Control Baselines for Information Systems and Organizations (October 2020, as updated), and SP 800-53 Rev. 5, Section 1 on changes from Revision 4 (read Nov. 13, 2026). Read it online. ↩
- NIST SP 800-37 Rev. 2, Risk Management Framework for Information Systems and Organizations, December 2018 (read Nov. 13, 2026). Read it online. ↩
- NIST Computer Security Resource Center, "NIST Releases Revision to SP 800-53 Controls" (Release 5.2.0, responding to Executive Order 14306), Aug. 27, 2025 (read Nov. 13, 2026). Read it online. ↩
- NIST SP 800-171 Rev. 3, Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations, May 14, 2024 (supersedes Rev. 2 of Jan. 28, 2021); count of 97 requirements made for this lesson from Chapter 3, excluding withdrawn items (read Nov. 13, 2026). Read it online. ↩
- Office of the Assistant Secretary of War for Acquisition and Sustainment, DFARS Class Deviation 2026-O0025, Revision 3 (FAR Part 40 and DFARS Part 240), signed by John M. Tenaglia, Sept. 3, 2026, paragraph (b), implementing the DoW CIO memo of July 13, 2026 (read from the saved PDF) (read Nov. 13, 2026). Read it online. ↩
- Department of Defense, "Cybersecurity Maturity Model Certification (CMMC) Program," final rule, 89 FR 83092, Oct. 15, 2024 (32 CFR Part 170, effective Dec. 16, 2024), including Table 1 (levels), the phased plan, the 8,350-entity estimate and cost Tables 9 and 10 (read Nov. 13, 2026). Read it online. ↩
- Department of Defense, "Defense Federal Acquisition Regulation Supplement: Assessing Contractor Implementation of Cybersecurity Requirements," final rule, 90 FR 43560, Sept. 10, 2025 (effective Nov. 10, 2025) (read Nov. 13, 2026). Read it online. ↩
- U.S. Department of War, "War Department Changes Cybersecurity Maturity Model Certification Requirements," July 13, 2026 (read Nov. 13, 2026). Read it online. ↩
- ISI Defense, "CMMC Status" tracker, last reviewed Oct. 19, 2026 (a private compliance firm's summary, used here for status only); see also CMMCMap, "The November 2026 CMMC deadline was suspended," updated Oct. 16, 2026 (read Nov. 13, 2026). Read it online. ↩
- The Defense Compliance Report, "CMMC Deadlines 2026: Phase 2 Status Tracker," checked Oct. 12, 2026, reporting Cyber AB Town Hall figures of Sept. 29, 2026 (issuer-reported, not a census) (read Nov. 13, 2026). Read it online. ↩
- Bright Defense, "ISO 27001: What Changed in 2026?" (2026), on the October 2022 third edition, Amd 1:2024 and the 2025 transition (a consultancy summary; ISO's own pages could not be retrieved) (read Nov. 13, 2026). Read it online. ↩
- International Organization for Standardization, catalogue entry for ISO/IEC 27000:2026, Information security, cybersecurity and privacy protection: Information security management systems: Overview, edition 6, July 2026 (the sixth edition drops "and vocabulary" from the title; ISO states it is no longer a terminology document) (read Nov. 13, 2026). Read it online. ↩
- ISO/IEC 27001:2022/Amd 1:2024, "Climate action changes," catalogue summary (published February 2024), via iTeh Standards (read Nov. 13, 2026). Read it online. ↩
- DQS (certification body), "Revision of ISO 27002: These are the changes" (93 controls in four themes, 11 new controls) (read Nov. 13, 2026). Read it online. ↩
- Irish National Accreditation Board, "Transition requirements for ISO/IEC 27001:2022," applying IAF MD 26 (clients to be transitioned by Oct. 31, 2025) (read Nov. 13, 2026). Read it online. ↩
- Center for Internet Security, "Center for Internet Security (CIS) Releases CIS Controls v8.1 with New Governance Recommendations," press release, June 25, 2024 (read Nov. 13, 2026). Read it online. ↩
- Center for Internet Security, "CIS Critical Security Controls Implementation Groups" (153 Safeguards in v8 and v8.1; IG1 as "essential cyber hygiene"); IG counts of 56 and 130 from CIS's published v8 Implementation Groups handout (read Nov. 13, 2026). Read it online. ↩
- Center for Internet Security, CIS Critical Security Controls Version 8.1 guide, June/August 2024, list of Controls and license (CC BY-NC-ND 4.0); copy hosted by Indiana University ResearchSOC (read Nov. 13, 2026). Read it online. ↩
- AICPA, "2017 Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy (with Revised Points of Focus, 2022)" download page (read Nov. 13, 2026). Read it online. ↩
- AICPA Assurance Services Executive Committee, "AICPA Exposure Drafts: Proposed 2027 SOC 2 Trust Services Criteria and Description Criteria," Oct. 26, 2026 (landing page; the drafts require a free account and were not read) (read Nov. 13, 2026). Read it online. ↩
- PCI Security Standards Council, "Just Published: PCI DSS v4.0.1," June 11, 2024 (read Nov. 13, 2026). Read it online. ↩
- HITRUST Alliance, "Assessments and Certifications" page (e1, i1, r2, AI assessments, NIST CSF 2.0 add-on), copyright 2026 (read Nov. 13, 2026). Read it online. ↩
- FedRAMP, blog index, including "Realizing the FedRAMP Authorization Act" (Jan. 13, 2026), "Propelling Change: FedRAMP Launches Consolidated Rules for 2026" (June 25, 2026) and "Memo to Milestone: FedRAMP Grants the First Full FedRAMP 20x Class C Certification" (Nov. 2, 2026) (read Nov. 13, 2026). Read it online. ↩
- FedRAMP, "FedRAMP 20x" program page (phases, certification classes A to D, and the plan to "stop accepting new Rev5 Certifications on June 11, 2027") (read Nov. 13, 2026). Read it online. ↩
- FedRAMP home page, marketplace counts (557 certified services, 38 through 20x) and notices dated Nov. 2 and Nov. 10, 2026 (read Nov. 13, 2026). Read it online. ↩
- GovRAMP home page (verification levels, member and product counts, Nov. 2, 2026 comment period on a proposed 20x Delta Assessment) (read Nov. 13, 2026). Read it online. ↩
- ISACA, "COBIT" resources page (COBIT 2019, 40 governance and management objectives) (read Nov. 13, 2026). Read it online. ↩
- Cybersecurity and Infrastructure Security Agency, bulletin announcing Cross-Sector Cybersecurity Performance Goals 2.0, Dec. 10, 2025 (sent Dec. 11, 2025) (read Nov. 13, 2026). Read it online. ↩
- NIST SP 1347, NIST Cybersecurity Framework 2.0: Informative References Quick-Start Guide, final, Aug. 25, 2026; see also NIST news release of the same date (read Nov. 13, 2026). Read it online. ↩
- Complaint, SEC v. SolarWinds Corp. and Timothy G. Brown (S.D.N.Y., filed Oct. 30, 2023), paragraphs 45 to 57 (allegations, not findings) (read Nov. 13, 2026). Read it online. ↩
- U.S. Department of Justice, "Defense Contractor MORSECORP Inc. Agrees to Pay $4.6 Million to Settle Cybersecurity Fraud Allegations," March 26, 2025 (updated April 29, 2025) (read Nov. 13, 2026). Read it online. ↩
- U.S. Securities and Exchange Commission, press release 2023-227, "SEC Charges SolarWinds and Chief Information Security Officer with Fraud, Internal Control Failures," Oct. 30, 2023 (read Nov. 13, 2026). Read it online. ↩
- U.S. Department of Justice, "Georgia Tech Research Corporation Agrees to Pay $875,000 to Resolve Civil Cyber-Fraud Litigation," Sept. 30, 2025 (read Nov. 13, 2026). Read it online. ↩
- U.S. Attorney's Office, Eastern District of California, "Aerojet Rocketdyne Agrees to Pay $9 Million to Resolve False Claims Act Allegations of Cybersecurity Violations in Federal Government Contracts," July 8, 2022 (read Nov. 13, 2026). Read it online. ↩
- Idaho Technology Authority, "Policies" index (security series P4000 to P4500, including P4140) (read Nov. 13, 2026). Read it online. ↩
Check yourself
1. Which of these produces an internationally recognized certificate of conformity issued by an accredited certification body?
ISO/IEC 27001 sets requirements for an information security management system and accredited certification bodies certify against it. NIST CSWP 29 says the CSF does not prescribe how outcomes are achieved, and there is no CSF or SP 800-53 certificate for private organizations.
2. What function did NIST CSF 2.0 (Feb. 26, 2024) add to the five in version 1.1?
NIST CSWP 29 lists six Functions: Govern, Identify, Protect, Detect, Respond and Recover. Govern is new in 2.0 and includes Cybersecurity Supply Chain Risk Management (GV.SC).
3. As of November 2026, which revision of NIST SP 800-171 does DFARS 252.204-7012 require defense contractors to meet?
DFARS Class Deviation 2026-O0025, Revision 3 (Sept. 3, 2026) requires "baseline compliance with NIST SP 800-171 Rev 2" under DFARS 252.204-7012, even though Rev. 3 was published May 14, 2024.
4. What happened to CMMC Phase 2 on July 13, 2026?
The Department of War suspended the Phase 2 transition planned for Nov. 10, 2026 and created a 60-day review and reform task force (DoW release, July 13, 2026; Class Deviation 2026-O0025 Rev. 3). No court was involved, and 32 CFR Part 170 was not rescinded.
5. Under Ohio Revised Code 1354.03, how long does a business relying on a listed framework have to conform to a newly published final revision of it?
Ohio Rev. Code 1354.03(A)(2) requires reasonable conformance to the revised framework "not later than one year after the publication date stated in the revision." Iowa Code 554G.3 has a similar limit.
6. A SOC 2 Type 2 report differs from a Type 1 report because it:
Type 1 addresses the design of controls as of a date; Type 2 adds operating effectiveness over a period. SOC 2 reports are issued by licensed CPA firms measured against the AICPA Trust Services Criteria (2017, revised points of focus 2022).
7. What does the HITECH Act's section 13412 (Public Law 116-321, 2021) require HHS to do?
Section 13412 says the Secretary "shall consider" whether the entity adequately demonstrated recognized security practices for not less than the previous 12 months when making determinations on fines, audits and agreed remedies. It does not excuse breaches.
8. What does NIST say about non-NIST mappings listed in its informative references catalog?
NIST's CSF 2.0 Informative References page states that NIST "does not conduct correctness testing on non-NIST submitted mappings" and that listing them "does not imply NIST endorsement."
9. Which Idaho rule requires state agencies to use the current NIST Cybersecurity Framework as the basis for assessing their cybersecurity programs?
ITA Enterprise Policy P4140, revised Aug. 20, 2024, says state agencies "shall adopt the current NIST Cybersecurity Framework as the basis for assessing their cybersecurity programs." P4530 covers cleansing surplus equipment; 28-51-105 is breach notice.
10. In the MORSECORP settlement of March 26, 2025, what did the company admit about its NIST SP 800-171 score?
The Justice Department release says MORSECORP reported 104 in January 2021, was told in July 2022 its score was -142, and did not update the government system until June 2023, three months after a subpoena. It paid $4.6 million.
Terms in this lesson
- Outcome framework
- A document that describes desired security results without prescribing how to achieve them, such as the NIST Cybersecurity Framework.
- Control catalog
- A detailed list of specific safeguards, such as NIST SP 800-53 or the CIS Controls, usually with baselines or groups that match controls to risk levels.
- Govern Function
- The sixth Function added in NIST CSF 2.0, covering organizational context, risk strategy, roles, policy, oversight and supply chain risk management.
- CSF Tier
- One of four levels (Partial, Risk Informed, Repeatable, Adaptive) describing the rigor of an organization's cybersecurity risk governance and management practices.
- Organizational Profile
- A description of an organization's Current and Target cybersecurity posture in terms of CSF outcomes; the gap between the two becomes the improvement plan.
- Community Profile
- A published CSF baseline for a sector, technology or threat, such as NIST's ransomware profile, that organizations can adapt as a Target Profile.
- Informative reference (crosswalk)
- A mapping that shows how a CSF outcome relates to parts of another standard, guideline or regulation; published by NIST and others through the OLIR program.
- OLIR
- NIST's Online Informative References program, a catalog of mappings between documents with tools to compare them and export results.
- Statement of Applicability
- The ISO/IEC 27001 document listing which Annex A controls an organization applies, which it excludes, and why.
- Controlled Unclassified Information (CUI)
- Sensitive government information that is not classified but must be protected under law, regulation or policy; NIST SP 800-171 sets requirements for protecting it in nonfederal systems.
- C3PAO
- Certified Third-Party Assessment Organization, an assessor authorized to conduct CMMC Level 2 certification assessments.
- SPRS
- The Supplier Performance Risk System, where defense contractors post NIST SP 800-171 assessment scores on a scale from 110 down to -203.
- Complementary user entity controls
- Controls a service organization's SOC report says its customers must operate themselves for the service's controls to work as described.
- Safe harbor (cybersecurity)
- A state law, such as Ohio's or Iowa's, giving a business that maintains a written program reasonably conforming to a recognized framework an affirmative defense in data breach tort suits.
- Common control framework
- An organization's single internal library of controls, each mapped once to every law, contract and standard it must meet, tested once and reported many ways.
Sources
- NIST CSWP 29, The NIST Cybersecurity Framework (CSF) 2.0 (2024-02-26) checked 2026-11
- NIST SP 800-53 Rev. 5 publication page (Release 5.2.0) (2025-08-27) checked 2026-11
- NIST SP 800-171 Rev. 3 (2024-05-14) checked 2026-11
- NIST SP 1347, CSF 2.0 Informative References Quick-Start Guide (2026-08-25) checked 2026-11
- CMMC Program final rule, 89 FR 83092 (32 CFR Part 170) (2024-10-15) checked 2026-11
- DFARS CMMC acquisition rule, 90 FR 43560 (2025-09-10) checked 2026-11
- DFARS Class Deviation 2026-O0025, Revision 3 (2026-09-03) checked 2026-11
- Public Law 116-321 (HITECH recognized security practices) (2021-01-05) checked 2026-11
- Ohio Revised Code 1354.03, Reasonable conformance (2018-11-02) checked 2026-11
- Iowa Code chapter 554G (2025-12-09) checked 2026-11
- Idaho Technology Authority Policy P4140, Cybersecurity Framework (2024-08-20) checked 2026-11
- FedRAMP 20x program page (2026-11-13) checked 2026-11
- SEC v. SolarWinds Corp. complaint (2023-10-30) checked 2026-11
- DOJ, MORSECORP settlement release (2025-03-26) checked 2026-11