Vulnerability disclosure policy requirements compared
| Instrument | Who | Duty | Date |
|---|---|---|---|
| CISA Binding Operational Directive 20-01, Develop and Publish a Vulnerability Disclosure Policy1 | WhoFederal executive branch departments and agencies1 | DutyKeep 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 | DateIssued 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 Submissions2 | WhoSponsors 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 threats2 | DutyStatute: 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 | DateSection 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 | WhoThe FAR Council, in consultation with CISA and NIST; the rule would apply to covered contractors3 | DutyPublish 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 algorithms3 | DateSigned 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 Guidelines4 | WhoNIST 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 | DutyGuidance: a federal vulnerability disclosure framework, handling of vulnerability reports, and communication of mitigation or remediation4 | DateFinal published May 2023 (May 24, 2023 in the document history); draft June 7, 20214 |
| IoT Cybersecurity Improvement Act of 2020, 15 U.S.C. 278g-3c5 | WhoNIST, for agencies and for contractors and subcontractors at any tier that provide information systems, including IoT devices, to an agency5 | DutyNIST 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 | DateEnacted December 4, 2020 (Pub. L. 116-207, section 5); guidelines due within 180 days5 |
| IoT Cybersecurity Improvement Act of 2020, 15 U.S.C. 278g-3e6 | WhoHeads of federal agencies, through chief information officer contract reviews6 | DutyAn 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 | DateProhibition took effect 2 years after December 4, 20206 |
License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.
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
What was left out, and why.
- 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
- Cybersecurity and Infrastructure Security Agency. BOD 20-01: Develop and Publish a Vulnerability Disclosure Policy. Checked .
- U.S. Food and Drug Administration. Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions (February 3, 2026). Checked .
- 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). Checked .
- National Institute of Standards and Technology. NIST SP 800-216, Recommendations for Federal Vulnerability Disclosure Guidelines. Checked .
- 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). Checked .
- 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). Checked .
How we source and check every fact: Editorial standards · Corrections
Last reviewed .
Spotted an error? Tell us and we will check it and correct the table where needed.