Two engineers at a desk reviewing code together on a large monitor

PSIRT & disclosure

NIST SP 800-216 (federal vulnerability disclosure guidelines), explained

Last updated:

NIST SP 800-216, "Recommendations for Federal Vulnerability Disclosure Guidelines," is a free NIST Special Publication (May 2023) that tells U.S. federal agencies how to receive, triage, verify, remediate and publicly advise on vulnerability reports against their own software, hardware and IoT devices. It exists because Section 5 of the IoT Cybersecurity Improvement Act of 2020 directed NIST to write exactly this guidance, aligned "to the maximum extent practicable" with ISO/IEC 29147 and 30111 — the international coordinated-vulnerability-disclosure standards. SP 800-216 does not replace those standards; its own text says it "augments rather than replaces the requirements and recommendations provided in" them, adding a federal-government-specific organizational layer on top.

Key takeaways

  • NIST SP 800-216, "Recommendations for Federal Vulnerability Disclosure Guidelines," is a free NIST Special Publication (May 2023) that tells U.S.
  • Most agencies "will leverage the services provided by an FCB member, will not themselves be part of the FCB, and will instead establish their own VDPOs" (Section 1).
  • Because the law behind SP 800-216 reaches contractors and can block IoT purchases.
  • Monitoring of the reporting mechanism and of public sources/support channels likely to surface a report informally.

Who are the two actors, the FCB and the VDPO?

The whole framework runs on two defined roles (Executive Summary; Sections 2-3):

Actor Role
Federal Coordination Body (FCB) "A group of cooperating government entities that operate at the federal level to ensure vulnerability disclosure coordination services for all government agencies." Receives source vulnerability reports, coordinates investigation to identify vulnerable systems, routes findings reports, and produces advisories. Expected to have few members, each covering a distinct slice of government (e.g. military vs. civilian).
Vulnerability Disclosure Program Office (VDPO) "The operational unit that is responsible for information technology (IT) systems and coordinating with other actors to identify, resolve, and issue advisories on reported vulnerabilities." Ideally part of an existing information technology security office (ITSO), closest to the affected product or service.

Most agencies "will leverage the services provided by an FCB member, will not themselves be part of the FCB, and will instead establish their own VDPOs" (Section 1). Other actors in the flow are the reporter (anyone submitting a report, inside or outside government), the public (whoever needs to act on or is affected by a vulnerability), and the external coordinator — a non-government CVD entity, another VDPO, or the upstream software vendor.

Why should a device maker selling to agencies care?

Because the law behind SP 800-216 reaches contractors and can block IoT purchases. The IoT Cybersecurity Improvement Act of 2020 (Public Law 116-207, enacted 4 December 2020) contains three provisions that matter to a vendor:

  • Section 5(a)(2) asks for guidelines for "a contractor providing to an agency an information system (including an Internet of Things device) and any subcontractor thereof at any tier" on receiving vulnerability information and disseminating information about its resolution. SP 800-216's Executive Summary quotes this mandate in full.
  • Section 6(d) states that the Federal Acquisition Regulation "shall be revised as necessary" to implement agency disclosure policies.
  • Section 7(a) prohibits an agency head from procuring, renewing or using an IoT device if the agency CIO determines that its use "prevents compliance with" the IoT device standards under section 4 (published by NIST as SP 800-213, November 2021) or the disclosure guidelines under section 5. The prohibition applies even below the simplified acquisition threshold and took effect two years after enactment, on 4 December 2022.

Section 7(b) lets the agency head waive the prohibition when the CIO finds the waiver is needed for national security, for research, or because the device "is secured using alternative and effective methods appropriate to the function of such device." For a vendor, the practical reading is simple: if you cannot receive a report and ship a fix, an agency may be unable to buy your device without a waiver.

What must a VDPO stand up (Section 3.2)?

  1. Report acceptance policies and receipt capability— both a public external policy (report methods, acknowledgement/resolution expectations, no-legal-action commitment for researchers following the rules — aligned with CISA's BOD 20-01) and an internal policy covering response/remediation timelines.
  2. Monitoringof the reporting mechanism and of public sources/support channels likely to surface a report informally.
  3. Processing and resolution— identifying which systems/software a report concerns, verifying the vulnerability exists, and overseeing or supporting the system owner's mitigation or remediation.
  4. Internal handling procedures— who is responsible at each stage, safeguards against premature disclosure, and a target remediation schedule.

How does a report move end to end?

SP 800-216's Section 2 walks the FCB-level process in sequence: prepare receipt capability and contacts (2.1) → receive the source vulnerability report (2.2) → triage and prioritize using "a documented vulnerability scoring methodology (e.g., the Common Vulnerability Scoring System [CVSS])" plus government-exposure and user-impact factors (2.3) → determine the affected system (2.4) and software (2.5) → verify and remediate, with the VDPO closest to the system leading resolution (2.6) → decide whether to publish an advisory (2.7). Note 6 under Section 2.3 flags a deliberate deviation from ISO/IEC 30111: SP 800-216 prioritizes using the highest calculated severity across configurations, rather than ISO/IEC 30111's "severity of the most common configuration," because this guidance targets specific deployed government systems rather than widely-configured commercial products.

What happens when a report about your product reaches an agency?

It is forwarded to you as the software owner, and you are expected to help fix it. The SP 800-216 full text treats a commercial vendor as an external coordinator and sets out what happens at each stage:

Stage (section) What the agency side does What the vendor should have ready
Scope and contacts (2.1.2) FCB members "may engage with industry-tied vulnerability coordination entities" such as CERT/CC A security contact that CERT/CC and agencies can find
Identify software (2.5) If the software is commercial or open source, the FCB or VDPO "should identify the software owner and forward the report to that EC"; if that fails, to an industry-focused handling organization An intake channel that accepts forwarded reports, with credit for the original reporter
Track progress (2.5) The FCB monitors verification and remediation and updates the reporter and affected VDPOs Status updates on a stated cadence
Remediate (3.2.5.4) The VDPO may notify the product owner directly through existing support channels A patch or update; per the guidance, the owner "should assist stakeholders in dealing with vulnerabilities until a product has reached the end of service" and offer "a reasonable upgrade path" if not every supported version gets a fix
Contracts (3.3.4) Disclosure handling and resolution terms "should be included in any contracts that support a federal information system" Contract language you can accept: timelines, contacts, advisory coordination

What should a vulnerability report to you contain?

Ask for the same fields SP 800-216 tells agencies to collect. Section 2.1.1 lists the information a source vulnerability report could include, and it doubles as a vendor intake form:

  • product or service name and affected versions;
  • an identified host or its network interface;
  • class or type of vulnerability, optionally using a taxonomy like CWE;
  • possible root cause, or the CVE if known;
  • proof-of-concept code or other substantial evidence;
  • tools and steps to reproduce;
  • impact and severity estimate;
  • other products, components, services or vendors thought to be affected;
  • disclosure plans, specifically embargo and publication timelines.

Add a firmware build number and hardware revision for devices, since the same model name often spans several images.

How does SP 800-216 decide whether to publish an advisory?

Section 2.7.1 lists conditions favoring public disclosure: the vulnerability has no CVE yet, the affected system is public-facing, PII or sensitive data exposure is possible, the flaw could affect users outside the VDPO's own agency, or the public needs to take action (patch, update, change a password). Section 2.7.2 then specifies what a good advisory contains: a stable identifier (ideally a CVE), affected product/version detail "without... too much detail to avoid enabling exploitation," an ISO 8601-formatted publication date, a documented severity rating (CVSS recommended), remediation or mitigation steps, contact information, and reporter credit if requested. Section 2.7.3 names the two standing government advisory channels: CISA's National Cyber Awareness System (five products — Current Activity, Alerts, Bulletins, Analysis Reports, and an Industrial Control Systems feed) and NIST's own National Vulnerability Database (NVD).

How does this fit with ISO/IEC 29147/30111 and CISA's own process?

SP 800-216 is built directly on top of ISO/IEC 29147 and 30111: a VDPO "will implement the vulnerability disclosure standard [ISO/IEC 29147]" and "provide oversight and support for system owners who perform the vulnerability handling duties described in [ISO/IEC 30111]." It separately notes alignment with CISA's Binding Operational Directive 20-01 (2020), which already requires federal agencies to publish a vulnerability disclosure policy enabling external reports. SP 800-216 does not itself describe CISA's own internal CVD workflow for non-federal reports — that is covered by CISA's published CVD process page, a related but distinct process. NIST keeps further agency examples on its vulnerability disclosure guidelines project page.

What does a forwarded report look like in practice?

Worked example, synthetic: "Example Controls Co.", the product and the agency are invented for illustration. A researcher reports an authentication bypass in the web interface of a building-automation controller to a civilian agency's VDPO. The agency runs 40 of the controllers.

  1. Day 0, agency sideThe VDPO checks the report against Section 2.1.1's fields, confirms the controllers are in scope and sees the software is commercial, so it forwards the report to Example Controls Co.'s published security contact and copies its FCB member.
  2. Day 1, vendor intakeThe vendor's PSIRT acknowledges receipt, asks for the firmware build seen on the agency's units and agrees embargo terms with the reporter.
  3. Days 2–5, triageEngineers reproduce the issue on firmware 4.2 and 4.3, score it with CVSS, and check which other models share the web component by searching their firmware SBOMs.
  4. Days 6–30, fixA fixed 4.3.1 build ships. Model 4.1 hardware is past end of service, so the advisory points owners to a supported upgrade path, as Section 3.2.5.4 suggests.
  5. PublicationThe vendor, as a CNA or through one, assigns a CVE and publishes an advisory with affected versions, CVSS, remediation, contact and reporter credit; the agency's VDPO confirms its 40 units are updated.

The timeline above is illustrative; SP 800-216 leaves remediation targets to each VDPO's internal policy.

What are the common pitfalls?

  • No findable contact. If an FCB or CERT/CC cannot reach you, the report goes to a third party and you lose time.
  • Reports routed to sales or general support. Section 3.2.5.4 expects owners to be reachable "through existing support channels," so those channels need a hand-off to the security team.
  • Silence about end of service. Without a support end date, you cannot offer the "reasonable upgrade path" the guidance asks for.
  • No CVE route. Advisories should carry a stable identifier; see CNA rules for becoming one or working through one.
  • Contract terms seen for the first time at award. Section 3.3.4 puts disclosure handling into contracts; review the wording before you bid.

What is a workable starting point?

  1. Decide your FCB relationship firstMost agencies are not FCB members — identify which FCB member covers your sector and use its templates and advisory channel rather than building one from scratch.
  2. Write the external policy to BOD 20-01's shape, even outside the federal government: clear report channel, acknowledgement timescale, and an explicit no-legal-action commitment for good-faith researchers. Our vulnerability disclosure policy template and the free security.txt generator cover the vendor version.
  3. Pick a documented severity methodology up front— CVSS is what SP 800-216 recommends — so prioritization is consistent across every report your VDPO-equivalent function receives.
  4. Decide your advisory channel before you need oneWhether that's an internal customer bulletin or a public CVE/NVD entry, Section 2.7.2's element list (identifiers, affected versions, severity, remediation, contact, credit) is a usable checklist regardless of audience.

For the vendor side of the process, see setting up a PSIRT at a hardware company and the FIRST PSIRT Services Framework. A federal buyer will often ask about disclosure alongside SP 800-161 supply chain controls and the secure software development attestation form, whose fourth requirement is a vulnerability disclosure program.

SoftWSP's PSIRT engagements can be structured around the FCB/VDPO roles and the report-intake-through-advisory flow SP 800-216 describes, adapted for a device maker rather than a federal agency: see PSIRT as a Service. On the platform side, SoftWSP extracts a CycloneDX 1.6 SBOM from a firmware image, matches it against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, drafts a cited report for engineer review, and sends watchlist alerts on a CVE ID or vendor and product; deciding whether a finding is exploitable and writing the advisory stay with your engineers.

This guide summarises the public NIST SP 800-216 (May 2023) documentation; it is not a substitute for the full text and does not constitute compliance or legal advice.

Put this guide to work

Frequently asked questions

What is NIST SP 800-216?

'Recommendations for Federal Vulnerability Disclosure Guidelines' — a NIST Special Publication by Kim Schaffer, Peter Mell, Hung Trinh and Isabel Van Wyk (NIST Computer Security Division), published in May 2023 and approved by the NIST Editorial Review Board on 2023-05-17. Its Abstract states the goal directly: 'This document recommends guidance for establishing a federal vulnerability disclosure framework, properly handling vulnerability reports, and communicating the mitigation and/or remediation of vulnerabilities,' applied 'to all software, hardware, and digital services under federal control.' It is public-domain U.S. Government work — 'not subject to copyright in the United States,' though NIST asks for attribution — and free to download from https://doi.org/10.6028/NIST.SP.800-216.

Why does this document exist — what law required it?

Section 5 of the IoT Cybersecurity Improvement Act of 2020 (Public Law 116-207) directed NIST to publish guidelines for federal agencies covering 'the reporting, coordinating, publishing, and receiving information about' security vulnerabilities in agency-owned information systems, including IoT devices, and their resolution — and required those guidelines to be aligned, 'to the maximum extent practicable,' with 'Standards 29147 and 30111 of the International Standards Organization (or any successor standard).' SP 800-216 is NIST's response: it explicitly 'leverages the ISO/IEC standards as much as possible' and states it 'augments rather than replaces the requirements and recommendations provided in' ISO/IEC 29147 and 30111.

What are the Federal Coordination Body (FCB) and the Vulnerability Disclosure Program Office (VDPO)?

The two core actors the document defines (Executive Summary and Sections 2-3). The FCB is 'a group of cooperating government entities that operate at the federal level to ensure vulnerability disclosure coordination services for all government agencies,' receiving source vulnerability reports, coordinating investigation, routing findings, and producing advisories; it is expected to have few members, each with a distinct area of responsibility. The VDPO is 'the operational unit that is responsible for information technology (IT) systems and coordinating with other actors to identify, resolve, and issue advisories on reported vulnerabilities,' ideally embedded in an existing information technology security office (ITSO) close to the affected product or service. 'Every government agency is a stakeholder... and each should have at least one VDPO or be supported by a VDPO through an agreement with their parent agency' (Section 2.8).

What must a VDPO actually have in place?

Section 3.2 lists four structural requirements: (1) development of source vulnerability report acceptance policies and the capability to receive reports; (2) monitoring of source vulnerability reports; (3) processing and resolution — identifying potentially vulnerable systems/software, verifying reports, and overseeing or supporting mitigation/remediation; and (4) development of internal vulnerability disclosure handling procedures. Section 3.2.1 requires both a public-facing policy (aligned with CISA's Binding Operational Directive 20-01, covering report methods, acknowledgement/resolution expectations, and a no-legal-action commitment for researchers who follow the rules) and an internal policy governing response/remediation timelines and advisory coordination.

Sources

  1. NIST SP 800-216 (May 2023), Recommendations for Federal Vulnerability Disclosure Guidelines — Schaffer, Mell, Trinh, Van Wyk
  2. NIST SP 800-216 — publication page (abstract, authors, approval date)
  3. NIST SP 800-216 — full-text PDF
  4. IoT Cybersecurity Improvement Act of 2020, Public Law 116-207, Section 5 (NIST guidelines mandate)
  5. CISA Binding Operational Directive 20-01: Develop and Publish a Vulnerability Disclosure Policy
  6. NIST SP 800-213 (November 2021), IoT Device Cybersecurity Guidance for the Federal Government
  7. NIST Vulnerability Disclosure Guidelines (VDG) project page
  8. CERT Coordination Center: report a vulnerability
  9. CVE Program
Was this guide helpful?

In this cluster

NIST SP 800-216 (federal vulnerability disclosure guidelines), explained