shall publish minimum elements for an SBOM.
(g) Within 45 days of the date of this order, the Secretary of Commerce, acting through
the Director of NIST, in consultation with the Secretary of Defense acting through the
Director of the NSA, the Secretary of Homeland Security acting through the Director of
CISA, the Director of OMB, and the Director of National Intelligence, shall publish a
definition of the term “critical software” for inclusion in the guidance issued pursuant to
subsection (e) of this section. That definition shall reflect the level of privilege or access
required to function, integration and dependencies with other software, direct access to
networking and computing resources, performance of a function critical to trust, and
potential for harm if compromised.
(h) Within 30 days of the publication of the definition required by subsection (g) of
this section, the Secretary of Homeland Security acting through the Director of CISA, in
consultation with the Secretary of Commerce acting through the Director of NIST, shall
identify and make available to agencies a list of categories of software and software
products in use or in the acquisition process meeting the definition of critical software
issued pursuant to subsection (g) of this section.
(i) Within 60 days of the date of this order, the Secretary of Commerce acting through
the Director of NIST, in consultation with the Secretary of Homeland Security acting
through the Director of CISA and with the Director of OMB, shall publish guidance
outlining security measures for critical software as defined in subsection (g) of this
section, including applying practices of least privilege, network segmentation, and proper
configuration.
(j) Within 30 days of the issuance of the guidance described in subsection (i) of this
section, the Director of OMB acting through the Administrator of the Office of Electronic
Government within OMB shall take appropriate steps to require that agencies comply
with such guidance.
(k) Within 30 days of issuance of the guidance described in subsection (e) of this
section, the Director of OMB acting through the Administrator of the Office of Electronic
Government within OMB shall take appropriate steps to require that agencies comply
with such guidelines with respect to software procured after the date of this order.
(l) Agencies may request an extension for complying with any requirements issued
pursuant to subsection (k) of this section. Any such request shall be considered by the
Director of OMB on a case-by-case basis, and only if accompanied by a plan for meeting
the underlying requirements. The Director of OMB shall on a quarterly basis provide a
report to the APNSA identifying and explaining all extensions granted.
(m) Agencies may request a waiver as to any requirements issued pursuant to
subsection (k) of this section. Waivers shall be considered by the Director of OMB, in
consultation with the APNSA, on a case-by-case basis, and shall be granted only in
exceptional circumstances and for limited duration, and only if there is an accompanying
plan for mitigating any potential risks.
(n) Within 1 year of the date of this order, the Secretary of Homeland Security, in
consultation with the Secretary of Defense, the Attorney General, the Director of OMB,
and the Administrator of the Office of Electronic Government within OMB, shall
recommend to the FAR Council contract language requiring suppliers of software
available for purchase by agencies to comply with, and attest to complying with, any
8/18
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents