Back to glossary

National Institute of Standards and Technology (NIST)

NIST is the U.S. agency behind the Cybersecurity Framework, SP 800-53, the SSDF, and FIPS, and the operator of the National Vulnerability Database.

NIST, the National Institute of Standards and Technology, is a non-regulatory U.S. Commerce Department agency that writes the security baselines federal agencies follow and auditors test companies against: the Cybersecurity Framework, the SP 800-53 controls, the Secure Software Development Framework, and FIPS. Each defines outcomes or controls, not tools. NIST also runs the National Vulnerability Database.

Every NIST security document follows one design rule: say what must be true, never how. The Cybersecurity Framework (CSF) 2.0 puts it in one line: "The CSF does not prescribe how outcomes should be achieved." That rule is why one framework fits a bank and a hospital. It is also why a clean NIST audit says little about your dependencies. We searched the machine-readable text of SP 800-53 Release 5.2.0, nearly 10,000 prose fields, and found zero mentions of "SBOM" or "package manager." The catalog's guidance on inspecting components for tampering lists "changes in packaging, specifications, factory location" as the warning signs.

Our position: use NIST as the vocabulary and the contract for a security program, and never mistake it for a detection spec. NIST's supply chain guidance assumes a supplier you can contract with, assess, and inspect. Open source arrives as an anonymous publish to a public registry. The control that works there is reading what each new version's code does before it runs. NIST's own vulnerability database adds a second warning: in April 2026 it stopped routinely enriching most CVEs.

What is NIST?

#

NIST is a federal measurement and standards laboratory inside the U.S. Department of Commerce. It was founded in 1901 as the National Bureau of Standards and renamed NIST in 1988. Its security publications are released through the Computer Security Resource Center at csrc.nist.gov.

NIST is non-regulatory. It cannot fine a company or force anyone outside government to adopt its documents. NIST's security mandate comes from the Federal Information Security Modernization Act (FISMA), which makes it responsible for the security standards and guidelines that protect federal information systems. Private companies meet NIST documents mostly through contracts: a federal sale, a defense subcontract, a cloud authorization, or a customer's security questionnaire.

NIST does not certify organizations as "NIST compliant." A claim of NIST compliance is a self-assessment or a third-party audit against a specific NIST document. Cryptography is the main exception: the Cryptographic Module Validation Program, run jointly with Canada's Cyber Centre, validates cryptographic modules against FIPS 140-3 and publishes the list of validated modules.

What are NIST standards?

#

NIST standards are documents in a handful of publication series, and the series tells you how binding each one is.

  • FIPS (Federal Information Processing Standards) are the only true standards in the set. Each FIPS states its own applicability, and for mandatory FIPS, NIST notes that FISMA "does not include a statutory provision allowing federal agencies to waive" them. FIPS 203, 204, and 205, the first post-quantum cryptography standards, were approved on August 13, 2024.
  • SP 800 documents (Special Publications in computer security) are guidelines: SP 800-53 for controls, SP 800-37 for risk management, SP 800-161 for cyber supply chain risk management, and SP 800-218, the Secure Software Development Framework. Federal agencies apply them under FISMA. Everyone else adopts them by choice or by contract.
  • SP 1800 documents are practice guides from NIST's National Cybersecurity Center of Excellence. Each one documents a working example build, down to product configuration, that another organization can reproduce.
  • NIST IR reports, formerly NISTIRs, carry research and supporting detail.
  • CSWP documents are Cybersecurity White Papers, and they include the CSF itself. CSF 2.0 is not a Special Publication. It is NIST CSWP 29.

How do you read a NIST publication identifier?

#

A NIST publication identifier encodes the series, number, revision, update, and draft stage in one string. NIST publishes the identifier syntax, and every citation in a contract or audit should use the full form.

In text form, the figure breaks NIST.SP.800-161r1-upd1 into five parts: the publisher NIST (NBS before 1988), the series SP, the report number 800-161, the revision r1, and the update upd1, which is an errata release to the same revision. Draft identifiers add a stage: ipd for the initial public draft, 2pd for a second draft, and fpd for the final public draft. Prefixing the machine-readable form with https://doi.org/10.6028/ resolves the document. More examples:

IdentifierWhat it means
NIST SP 800-53r5Special Publication 800-53, Revision 5
NIST SP 800-161r1-upd1SP 800-161, Revision 1, Update 1, an errata release dated November 1, 2024
NIST SP 800-218r1 ipdSP 800-218 Revision 1, initial public draft: SSDF 1.2, published December 17, 2025
NIST CSWP 29Cybersecurity White Paper 29: the CSF 2.0
NIST FIPS 140-3FIPS 140, third version; older series keep a hyphenated version number for historical reasons
NIST.SP.800-161r1-upd1Machine-readable form, used in DOIs and PDF file names

The revision number matters more than most audit reports admit. "NIST 800-53 compliant" without a revision is ambiguous: Revision 5 created the Supply Chain Risk Management (SR) control family, while Revision 4 covered supply chain protection in one control, SA-12, and its enhancements. SP 800-53 also versions its catalog data inside a revision. Release 5.2.0, issued August 27, 2025, strengthened software update and patch controls without becoming Revision 6.

What is the NIST Cybersecurity Framework?

#

The NIST Cybersecurity Framework is a taxonomy of security outcomes, arranged as Functions, Categories, and Subcategories. CSF 2.0, published February 26, 2024, has 6 Functions, 22 Categories, and 106 Subcategories. The first version appeared in 2014 and had five Functions.

The six CSF Functions are Govern, Identify, Protect, Detect, Respond, and Recover. Govern is new in 2.0. It covers organizational context, risk strategy, roles, policy, oversight, and Cybersecurity Supply Chain Risk Management (GV.SC), which replaced the old Identify category ID.SC. GV.SC has ten Subcategories, from GV.SC-01 to GV.SC-10.

A CSF Subcategory is one outcome sentence. GV.SC-04 reads, in full: "Suppliers are known and prioritized by criticality." Nothing in it says how to know them, how to rank them, or what counts as a supplier.

NIST publishes the CSF 2.0 Core as machine-readable OSCAL JSON in its oscal-content repository, which makes these counts reproducible:

Bash
curl -sL https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/CSF/v2.0/json/NIST_CSF_v2.0_catalog.json -o csf.json

# Categories still in force (CSF 1.1 categories stay in the file, marked withdrawn)
jq '[.catalog.groups[].controls[] | select([.props[]?.value] | index("withdrawn") | not)] | length' csf.json
22

# Subcategories still in force
jq '[.catalog.groups[].controls[].controls[]? | select([.props[]?.value] | index("withdrawn") | not)] | length' csf.json
106

Open source appears once in that file. The implementation examples for ID.AM-02, the software inventory outcome, say to inventory "commercial-off-the-shelf, open-source, custom applications, API services." The closest CSF outcome to a pre-install check is ID.RA-09: "The authenticity and integrity of hardware and software are assessed prior to acquisition and use."

How do you implement the NIST Cybersecurity Framework?

#

You implement the NIST Cybersecurity Framework by writing two Organizational Profiles, a Current Profile and a Target Profile, and closing the gap between them. CSF 2.0 describes five steps: scope the profile, gather inputs such as policies and risk priorities, create the profile, analyze gaps and build a prioritized action plan, then execute the plan and update the profile.

CSF Tiers grade how rigorous the process behind a profile is. The four Tiers are Partial, Risk Informed, Repeatable, and Adaptive. Tier 1 means strategy is applied "in an ad hoc manner." Tiers are optional, and Tier 4 is not everyone's goal. CSF 2.0 encourages progression to higher Tiers "when risks or mandates are greater," and where a cost-benefit analysis supports it. NIST's quick-start guide for Tiers, SP 1302, covers how to apply them to a profile.

The hard part of a profile is translating outcome sentences into evidence. Here is a Target Profile for open source dependencies, built from real CSF 2.0 Subcategories:

SubcategoryTarget outcome for open sourceEvidenceWhat it misses
ID.AM-02, software inventoryEvery package that executes, including CI toolsSBOMs generated from lockfiles, plus logs of what CI fetchedTools run through npx or global installs never enter the lockfile
GV.SC-04, suppliers known and prioritizedPublishing accounts known, ranked by where their code runsRegistry publisher metadata for each resolved versionA test dependency in CI runs beside cloud and registry credentials
GV.SC-05, requirements in contractsNot achievable with volunteer maintainersAn install-time admission policy in place of a contractThere is no upstream party to enforce anything against
ID.RA-09, integrity assessed before useEach new version's behavior checked before installAnalysis of package contents at resolution timeThe first minutes after a malicious publish, before analysis finishes
GV.SC-07, risk monitored over the relationshipOwnership and publish-rights changes trackedAlerts on new maintainers and unusual publishesAn account takeover publishes as a trusted maintainer

The inventory row is where most programs overstate their coverage. During the axios compromise, CI jobs that ran tools through npx resolved the malicious version at execution time, outside any lockfile (our blast-radius analysis has examples). An SBOM built from that lockfile would be accurate and would still not list the package that ran.

SP 800-53 and the Risk Management Framework

#

SP 800-53 is NIST's catalog of security and privacy controls, and it is the document federal systems are assessed against. Revision 5 was published September 23, 2020. As of Release 5.2.0, the catalog holds 20 control families, 300 base controls, and 714 control enhancements still in force.

The Risk Management Framework (RMF), defined in SP 800-37 Revision 2 (December 2018), is the process wrapped around those controls. Its seven steps are Prepare, Categorize, Select, Implement, Assess, Authorize, and Monitor. In the Select step, an organization picks a control baseline and tailors it. Tailoring includes filling in organization-defined parameters, which the catalog writes as assignments.

SP 800-53's software supply chain controls are mostly assignments waiting to be filled in. CM-10(1), "Open-source Software," says in full: "Establish the following restrictions on the use of open-source software: [Assignment]." CM-14 blocks installation of designated components unless their digital signatures are verified. The SR family has 12 controls, including SR-4 Provenance, SR-10 Inspection of Systems or Components, and SR-11 Component Authenticity.

The catalog's language shows which supply chain it was written for. We counted every prose field in the controls still in force in NIST's OSCAL release of SP 800-53, and did the same for the CSF 2.0 Core:

TermSP 800-53 Rel. 5.2.0 (9,982 prose fields)CSF 2.0 Core (491 prose fields)
"SBOM"00
"bill of materials"1, in an SR-4 assessment evidence list1, in a GV.SC-05 contract example
"package manager"00
"open-source software"70
"counterfeit"350
"tamper"404
"malicious code"1010
Bash
curl -sL https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json -o 800-53.json

# Prose fields that mention an SBOM or a package manager
jq '[.. | .prose? // empty | select(test("SBOM|package manager"; "i"))] | length' 800-53.json
0

# Guidance for SR-10, the control that tells you to inspect components
jq -r '.catalog.groups[] | select(.id=="sr") | .controls[] | select(.id=="sr-10") | .parts[] | select(.name=="guidance") | .prose' 800-53.json
The inspection of systems or systems components for tamper resistance and detection addresses physical and logical tampering and is applied to systems and system components removed from organization-controlled areas. Indications of a need for inspection include changes in packaging, specifications, factory location, or entity in which the part is purchased, and when individuals return from travel to high-risk locations.

"Malicious code" appears 101 times, and 45 of those mentions sit in SI-3 and its enhancements. SI-3 places malware protection "at system entry and exit points," the model of an antivirus gateway, not a package resolver. Nothing in the catalog names the event that matters most for open source: a new version, published by an account you never contracted with, that your build accepts automatically.

SCAP, OSCAL, STIGs, and CIS Benchmarks

#

Several acronyms travel with NIST and are often confused with it.

  • OSCAL (Open Security Controls Assessment Language) is NIST's machine-readable format for control catalogs, baselines, and system security plans, in XML, JSON, and YAML. The files queried above are OSCAL.
  • SCAP (Security Content Automation Protocol) is NIST's suite of specifications for automated configuration and vulnerability checking. SCAP 1.3, defined in SP 800-126 Revision 3, bundles XCCDF 1.2, OVAL 5.11.2, CPE 2.3, and CVSS version 3, among others.
  • STIGs (Security Technical Implementation Guides) come from the Defense Information Systems Agency (DISA), not NIST. Each STIG check traces to an SP 800-53 control through a DISA Control Correlation Identifier (CCI).
  • CIS Controls and CIS Benchmarks come from the Center for Internet Security, which is independent of NIST. CIS Controls v8.1, released June 2024, updated its mappings to CSF 2.0 and added a governance function.

NIST's software supply chain documents, compared

#

No single NIST document covers software supply chain security. Five of them divide the job, and they differ in who they address and how binding they are.

DocumentQuestion it answersHow bindingWhat it says about a malicious package version
CSF 2.0 (CSWP 29, 2024)Which outcomes does our program commit to?VoluntaryID.RA-09 asks for authenticity and integrity checks before use, with no method
SP 800-53r5 (Release 5.2.0, 2025)Which controls does this system implement?Applied to federal systems under FISMACM-10(1), CM-14, SR-4, SR-11; inspection guidance written for physical parts
SP 800-161r1-upd1 (2022, updated 2024)How do we run a supply chain risk program?GuidanceSupplier-centric; acknowledges that open source can escape supplier processes
SP 800-218 SSDF 1.1 (2022); 1.2 draft (2025)What must a software producer do?Federal attestation optional since January 2026PW.4.4 says keep verifying components; the 1.2 draft adds scanning supplier artifacts for malicious content as an example
SP 800-204D (2024)How do we protect a CI/CD pipeline?GuidancePipeline integrity: attestations, provenance, and SBOMs for what the pipeline builds

Verdict: commit to CSF 2.0 outcomes at the program level, and use the SP 800-53 SR and CM controls as the evidence trail for each system. Use SP 800-161 to structure supplier management for vendors you can actually contract with. If you sell software to federal or regulated buyers, the SSDF is where their questions come from, even though OMB memo M-26-05 made the federal attestation optional on January 23, 2026. As of November 2026, SSDF 1.2 is still a draft. None of the five documents tells you whether the next version of a dependency is malicious. That check has to come from analyzing the package itself.

The National Vulnerability Database is NIST's most strained product

#

The National Vulnerability Database (NVD) is NIST's enrichment layer on top of the CVE list. NVD analysts add CVSS severity scores, CWE weakness types, and CPE product matches, which are what let scanners match a CVE to installed software. Security products have been built on that enrichment for decades.

NIST abandoned the goal of enriching every CVE on April 15, 2026. The NVD now prioritizes CVEs in CISA's Known Exploited Vulnerabilities catalog, software used by the federal government, and critical software under Executive Order 14028. NIST attributed the change to CVE submissions growing 263% between 2020 and 2025. NIST enriched nearly 42,000 CVEs in 2025, and that was still not enough to keep pace.

On August 17, 2026, the NVD dashboard listed 42,353 CVEs as "Not Scheduled," against 2,426 "Awaiting Enrichment" and 623 "Undergoing Enrichment." Unscheduled records outnumbered the two active queues combined by nearly 14 to 1. We captured those figures while covering NIST's request for information on an AI-enabled NVD, which named an AI enrichment tool, V-etalon, that NIST had not yet released. A Commerce Department Inspector General audit found the backlog grew from about 13,000 vulnerabilities in June 2024 to more than 27,000 by the end of 2025. The same audit found NIST had no strategic plan for the NVD when auditors asked for one.

A shrinking NVD is a reason to stop treating any single CVE feed as the source of truth. Pull severity and affected-version data from CVE records, CISA's Vulnrichment data, OSV, and GitHub Security Advisories, and prioritize by whether the vulnerable code is reachable. The larger gap is structural. A malicious package version is not a vulnerability report, so it usually never receives a CVE, and no amount of NVD capacity would catch it.

Where NIST guidance should go next

#

NIST's supply chain model is a supplier model. GV.SC-05 puts requirements in contracts. SR-6 assesses suppliers. SR-10 triggers inspection on a change of factory. Each control assumes a counterparty who signed something and a shipment that crossed a dock.

In open source, the shipment is a publish event. On May 11, 2026, the TanStack compromise put 84 malicious artifacts into the @tanstack namespace, as one wave of Mini Shai-Hulud. The attacker published through TanStack's own trusted publishing binding, so the versions came out of the project's real release pipeline. The worm's code can also attach valid Sigstore provenance to what it publishes. Supplier assessments and provenance checks had nothing to flag. Socket AI Scanner flagged all 84 artifacts within six minutes of publication by analyzing what the new code did: it was an obfuscated credential stealer targeting CI secrets.

That is the check NIST's documents gesture at and never name. SR-11 should treat a malicious package version the way it treats a counterfeit part. ID.RA-09's examples should spell out what assessing a new open source version before use involves: install scripts, obfuscation, network and credential access, and unexpected new dependencies. The SSDF 1.2 draft's suggestion to scan supplier artifacts for malicious content should become a task. Until then, organizations will keep passing NIST audits with dependency programs built for the risk that gets a CVE, while the risk without one runs at install time.