requirements issued pursuant to subsections (g) through (k) of this section.
(o) After receiving the recommendations described in subsection (n) of this section,
the FAR Council shall review the recommendations and, as appropriate and consistent
with applicable law, amend the FAR.
(p) Following the issuance of any final rule amending the FAR as described in
subsection (o) of this section, agencies shall, as appropriate and consistent with applicable
law, remove software products that do not meet the requirements of the amended FAR
from all indefinite delivery indefinite quantity contracts; Federal Supply Schedules;
Federal Government-wide Acquisition Contracts; Blanket Purchase Agreements; and
Multiple Award Contracts.
(q) The Director of OMB, acting through the Administrator of the Office of Electronic
Government within OMB, shall require agencies employing software developed and
procured prior to the date of this order (legacy software) either to comply with any
requirements issued pursuant to subsection (k) of this section or to provide a plan
outlining actions to remediate or meet those requirements, and shall further require
agencies seeking renewals of software contracts, including legacy software, to comply with
any requirements issued pursuant to subsection (k) of this section, unless an extension or
waiver is granted in accordance with subsection (l) or (m) of this section.
(r) 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 Defense acting through the
Director of the NSA, shall publish guidelines recommending minimum standards for
vendors’ testing of their software source code, including identifying recommended types
of manual or automated testing (such as code review tools, static and dynamic analysis,
software composition tools, and penetration testing).
(s) The Secretary of Commerce acting through the Director of NIST, in coordination
with representatives of other agencies as the Director of NIST deems appropriate, shall
initiate pilot programs informed by existing consumer product labeling programs to
educate the public on the security capabilities of Internet-of-Things (IoT) devices and
software development practices, and shall consider ways to incentivize manufacturers and
developers to participate in these programs.
(t) Within 270 days of the date of this order, the Secretary of Commerce acting through
the Director of NIST, in coordination with the Chair of the Federal Trade Commission
(FTC) and representatives of other agencies as the Director of NIST deems appropriate,
shall identify IoT cybersecurity criteria for a consumer labeling program, and shall
consider whether such a consumer labeling program may be operated in conjunction with
or modeled after any similar existing government programs consistent with applicable
law. The criteria shall reflect increasingly comprehensive levels of testing and assessment
that a product may have undergone, and shall use or be compatible with existing labeling
schemes that manufacturers use to inform consumers about the security of their
products. The Director of NIST shall examine all relevant information, labeling, and
incentive programs and employ best practices. This review shall focus on ease of use for
consumers and a determination of what measures can be taken to maximize manufacturer
participation.
(u) Within 270 days of the date of this order, the Secretary of Commerce acting
through the Director of NIST, in coordination with the Chair of the FTC and
9/18
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents