# Vulnerability disclosure policy requirements compared

**In short:** CISA's BOD 20-01, issued September 2, 2020, requires federal executive branch agencies to publish a vulnerability disclosure policy that authorizes good-faith research and to bring all internet-accessible systems into scope within two years. Under section 524B of the FD&C Act, effective for premarket submissions from March 29, 2023, sponsors of cyber devices must give FDA a plan that includes coordinated vulnerability disclosure. The IoT Cybersecurity Improvement Act of 2020 required NIST to publish disclosure guidelines for agencies and their contractors (NIST SP 800-216, May 2023) and bars agencies from buying or using IoT devices that prevent compliance with them, and Executive Order 14412 (June 22, 2026) directs the FAR Council to propose a rule, within 270 days, under which covered contractors implement VDPs.

Cross-sector · Security & Resilience. Published November 14, 2026. Last reviewed November 14, 2026.

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. <https://creativecommons.org/licenses/by/4.0/>. Attribution: "Moraph Insights", <https://insights.moraph.com/compare/vulnerability-disclosure-policies>.

## The table

Each cell ends with the number of its source in "Sources". Cells were checked on November 14, 2026 unless the cell gives another date. Data: <https://insights.moraph.com/compare/vulnerability-disclosure-policies.csv> (CSV), <https://insights.moraph.com/compare/vulnerability-disclosure-policies.json> (JSON).

| Instrument | Who | Duty | Date |
|---|---|---|---|
| CISA Binding Operational Directive 20-01, Develop and Publish a Vulnerability Disclosure Policy [1] | Federal executive branch departments and agencies [1] | Keep a monitored security contact for each .gov domain; publish a VDP at /vulnerability-disclosure-policy on the agency's primary .gov website stating scope, allowed testing, how to report (anonymously if wished), a commitment not to recommend or pursue legal action over research the agency concludes was a good-faith effort to follow the policy, and when reporters can expect acknowledgment; set handling procedures; widen scope until all internet-accessible systems are covered. Bug bounties are not required. [1] | Issued September 2, 2020. Security contacts within 30 days; policy and procedures within 180 days; all internet-accessible systems in scope 2 years after issuance. [1] |
| FD&C Act section 524B(b)(1), with FDA guidance Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions [2] | Sponsors of 510(k), PMA, PDP, De Novo or HDE submissions for cyber devices: devices that include software validated, installed or authorized by the sponsor, can connect to the internet and could be vulnerable to cybersecurity threats [2] | Statute: submit a plan to monitor, identify and address postmarket vulnerabilities and exploits in a reasonable time, including coordinated vulnerability disclosure and related procedures. The guidance, which is nonbinding, says CVD could include coordinated disclosure of vulnerabilities found by outside parties such as researchers and third-party software suppliers. [2] | Section 524B applies to premarket submissions from March 29, 2023. Current guidance issued February 3, 2026, superseding the June 27, 2025 version. [2] |
| Executive Order 14412, Securing the Nation Against Advanced Cryptographic Attacks, section 6(d) [3] | The FAR Council, in consultation with CISA and NIST; the rule would apply to covered contractors [3] | Publish a proposed rule amending FAR requirements and contract clauses for contractor vulnerability disclosure programs, so that covered contractors implement VDPs consistent with NIST guidelines and those VDPs take reports of cryptographic vulnerabilities, including testing for lack of encryption and use of non-FIPS approved algorithms [3] | Signed June 22, 2026 (91 FR 38483, June 25, 2026). Proposed rule due within 270 days of the order. [3] |
| NIST SP 800-216, Recommendations for Federal Vulnerability Disclosure Guidelines [4] | NIST says the framework should apply to all software, hardware and digital services under federal control. NIST lists the IoT Cybersecurity Improvement Act as the related law. [4] | Guidance: a federal vulnerability disclosure framework, handling of vulnerability reports, and communication of mitigation or remediation [4] | Final published May 2023 (May 24, 2023 in the document history); draft June 7, 2021 [4] |
| IoT Cybersecurity Improvement Act of 2020, 15 U.S.C. 278g-3c [5] | NIST, for agencies and for contractors and subcontractors at any tier that provide information systems, including IoT devices, to an agency [5] | NIST must publish guidelines on reporting, coordinating, publishing and receiving information about security vulnerabilities and their resolution, including example content for contractors. The Director of OMB oversees implementation. [5] | Enacted December 4, 2020 (Pub. L. 116-207, section 5); guidelines due within 180 days [5] |
| IoT Cybersecurity Improvement Act of 2020, 15 U.S.C. 278g-3e [6] | Heads of federal agencies, through chief information officer contract reviews [6] | An agency may not procure, renew a contract for, or use an IoT device if its CIO determines the device prevents compliance with the NIST guidelines under 278g-3c or the standards under 278g-3b. Waivers for national security, research, or alternative and effective security methods. [6] | Prohibition took effect 2 years after December 4, 2020 [6] |

## Method

We read CISA's BOD 20-01 page, FDA's February 2026 premarket cybersecurity guidance (web page and PDF, which quotes section 524B), Executive Order 14412 in the Federal Register text on govinfo, NIST's SP 800-216 publication page, and 15 U.S.C. 278g-3c and 278g-3e in the U.S. Code on govinfo. A Federal Register search on 2026-11-14 for 'vulnerability disclosure' since June 2026 found no proposed FAR rule under Executive Order 14412. Each cell was checked on 2026-11-14. Sources we could not open or confirm were left out (see Omitted). This table explains the rules; it is not legal advice.

## Omitted

- **IoT Cybersecurity Improvement Act of 2020, 15 U.S.C. 278g-3c · Duty:** The statement that DHS administers the guidelines was removed: 15 U.S.C. 278g-3c names 'the Secretary', whose definition is in 278g-3a, a section this table does not cite.

## Notes

- BOD 20-01 is a compulsory direction to federal executive branch departments and agencies.
- FDA's guidance contains nonbinding recommendations; the duty to submit a plan comes from section 524B of the FD&C Act.

## Sources

1. Cybersecurity and Infrastructure Security Agency. BOD 20-01: Develop and Publish a Vulnerability Disclosure Policy. <https://www.cisa.gov/news-events/directives/bod-20-01-develop-and-publish-vulnerability-disclosure-policy> Checked November 14, 2026.
2. U.S. Food and Drug Administration. Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions (February 3, 2026). <https://www.fda.gov/media/119933/download> Checked November 14, 2026.
3. Executive Office of the President (published by the Office of the Federal Register). Executive Order 14412, Securing the Nation Against Advanced Cryptographic Attacks (91 FR 38483). <https://www.govinfo.gov/content/pkg/FR-2026-06-25/html/2026-12909.htm> Checked November 14, 2026.
4. National Institute of Standards and Technology. NIST SP 800-216, Recommendations for Federal Vulnerability Disclosure Guidelines. <https://csrc.nist.gov/pubs/sp/800/216/final> Checked November 14, 2026.
5. Office of the Law Revision Counsel (published by the U.S. Government Publishing Office). 15 U.S.C. 278g-3c, Guidelines on the disclosure process for security vulnerabilities relating to information systems, including Internet of Things devices (U.S. Code, 2024 edition). <https://www.govinfo.gov/content/pkg/USCODE-2024-title15/html/USCODE-2024-title15-chap7-sec278g-3c.htm> Checked November 14, 2026.
6. Office of the Law Revision Counsel (published by the U.S. Government Publishing Office). 15 U.S.C. 278g-3e, Contractor compliance with coordinated disclosure of security vulnerabilities relating to agency Internet of Things devices (U.S. Code, 2024 edition). <https://www.govinfo.gov/content/pkg/USCODE-2024-title15/html/USCODE-2024-title15-chap7-sec278g-3e.htm> Checked November 14, 2026.

Last reviewed: November 14, 2026
Canonical URL: <https://insights.moraph.com/compare/vulnerability-disclosure-policies>
Publisher: Moraph Insights
