(j) the term “Software Bill of Materials” or “SBOM” means a formal record containing
the details and supply chain relationships of various components used in building
software. Software developers and vendors often create products by assembling existing
open source and commercial software components. The SBOM enumerates these
components in a product. It is analogous to a list of ingredients on food packaging. An
SBOM is useful to those who develop or manufacture software, those who select or
purchase software, and those who operate software. Developers often use available open
source and third-party software components to create a product; an SBOM allows the
builder to make sure those components are up to date and to respond quickly to new
vulnerabilities. Buyers can use an SBOM to perform vulnerability or license analysis, both
of which can be used to evaluate risk in a product. Those who operate software can use
SBOMs to quickly and easily determine whether they are at potential risk of a newly
discovered vulnerability. A widely used, machine-readable SBOM format allows for
greater benefits through automation and tool integration. The SBOMs gain greater value
when collectively stored in a repository that can be easily queried by other applications
and systems. Understanding the supply chain of software, obtaining an SBOM, and using
it to analyze known vulnerabilities are crucial in managing risk.
(k) the term “Zero Trust Architecture” means a security model, a set of system design
principles, and a coordinated cybersecurity and system management strategy based on an
acknowledgement that threats exist both inside and outside traditional network
boundaries. The Zero Trust security model eliminates implicit trust in any one element,
node, or service and instead requires continuous verification of the operational picture via
real-time information from multiple sources to determine access and other system
responses. In essence, a Zero Trust Architecture allows users full access but only to the
bare minimum they need to perform their jobs. If a device is compromised, zero trust can
ensure that the damage is contained. The Zero Trust Architecture security model assumes
that a breach is inevitable or has likely already occurred, so it constantly limits access to
only what is needed and looks for anomalous or malicious activity. Zero Trust
Architecture embeds comprehensive security monitoring; granular risk-based access
controls; and system security automation in a coordinated manner throughout all aspects
of the infrastructure in order to focus on protecting data in real-time within a dynamic
threat environment. This data-centric security model allows the concept of leastprivileged access to be applied for every access decision, where the answers to the
questions of who, what, when, where, and how are critical for appropriately allowing or
denying access to resources based on the combination of sever.
Sec. 11. General Provisions.
(a) Upon the appointment of the National Cyber Director (NCD) and the establishment
of the related Office within the Executive Office of the President, pursuant to section 1752
of Public Law 116-283, portions of this order may be modified to enable the NCD to fully
execute its duties and responsibilities.
(b) Nothing in this order shall be construed to impair or otherwise affect:
(i) the authority granted by law to an executive department or agency, or the head
thereof; or
(ii) the functions of the Director of the Office of Management and Budget relating to
16/18
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents