NIST 800-53 REV 5 • SYSTEM AND SERVICES ACQUISITION

SA-8(9)Trusted Components

Implement the security design principle of trusted components in {{ insert: param, sa-08.09_odp }}.

CMMC Practice Mapping

No direct CMMC mapping

NIST 800-171 Mapping

No direct NIST 800-171 mapping

Related Controls

No related controls listed

Supplemental Guidance

The principle of trusted components states that a component is trustworthy to at least a level commensurate with the security dependencies it supports (i.e., how much it is trusted to perform its security functions by other components). This principle enables the composition of components such that trustworthiness is not inadvertently diminished and the trust is not consequently misplaced. Ultimately, this principle demands some metric by which the trust in a component and the trustworthiness of a component can be measured on the same abstract scale. The principle of trusted components is particularly relevant when considering systems and components in which there are complex chains of trust dependencies. A trust dependency is also referred to as a trust relationship and there may be chains of trust relationships. The principle of trusted components also applies to a compound component that consists of subcomponents (e.g., a subsystem), which may have varying levels of trustworthiness. The conservative assumption is that the trustworthiness of a compound component is that of its least trustworthy subcomponent. It may be possible to provide a security engineering rationale that the trustworthiness of a particular compound component is greater than the conservative assumption. However, any such rationale reflects logical reasoning based on a clear statement of the trustworthiness objectives as well as relevant and credible evidence. The trustworthiness of a compound component is not the same as increased application of defense-in-depth layering within the component or a replication of components. Defense-in-depth techniques do not increase the trustworthiness of the whole above that of the least trustworthy component.

Practitioner Notes

Trusted components means using components (hardware, software, firmware) whose integrity and security properties can be verified. You need to trust but verify the building blocks of your systems.

Example 1: Maintain an approved components list that identifies trusted hardware and software sources. Verify software integrity using vendor-provided checksums or digital signatures before installation. For critical systems, use only components from verified supply chains.

Example 2: In your development environment, use signed packages from trusted registries (NuGet, npm, PyPI) and lock dependency versions. Implement tools like Dependabot or Snyk to alert you when a dependency has known vulnerabilities or has been tampered with.