Cyber Resilience

NIST 800-53 r5 · Controls catalogue · Family SA

SA-4Acquisition Process

Include the following requirements, descriptions, and criteria, explicitly or by reference, using {{ insert: param, sa-04_odp.01 }} in the acquisition contract for the system, system component, or system service: Security and privacy functional requirements; Strength of mechanism requirements; Security and privacy assurance requirements; Controls needed to satisfy the security and privacy requirements. Security and privacy documentation requirements; Requirements for protecting security and privacy documentation; Description of the system development environment and environment in which the system is intended to operate; Allocation of responsibility or identification of parties responsible for information security, privacy, and supply chain risk management; and Acceptance criteria.

Last updated: 20 August 2026 13:14 UTC

Cumulative inbound coverage

How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.

Collective: partial · 1 mapping(s) from 1 framework(s): OWASP-Web 1 (partial)

See the full cumulative-coverage rollup →

Implementations targeting this control (0)

ATT&CK techniques this control mitigates (6)

Weaknesses this control addresses (7)AI-assisted

CWEs ranked by how often they appear in real CVEs. The rationale describes how this control reduces exploitability of each weakness class.

CWE Name CVEs Why this control addresses it
CWE-798Use of Hard-coded Credentials2,000+Requiring security functional requirements and acceptance criteria allows contracts to prohibit hard-coded credentials in delivered systems or components.
CWE-1188Initialization of a Resource with an Insecure Default300+Mandating secure configuration and initialization requirements in the acquisition process prevents delivery of products that initialize resources with insecure defaults.
CWE-829Inclusion of Functionality from Untrusted Control Sphere300+Allocation of supply-chain risk management responsibilities and vetting of the development/operational environment reduce inclusion of functionality from untrusted control spheres.
CWE-321Use of Hard-coded Cryptographic Key300+Functional and assurance requirements specified in acquisition can prohibit hard-coded cryptographic keys in delivered products.
CWE-494Download of Code Without Integrity Check200+Requiring integrity-protection mechanisms and assurance requirements in contracts prevents acquisition of code-download features lacking integrity checks.
CWE-1392Use of Default Credentials100+Security functional requirements and acceptance criteria can stipulate that acquired systems must not use default credentials.
CWE-1104Use of Unmaintained Third Party Components26Explicit supply-chain risk management and acceptance criteria in acquisition contracts directly reduce procurement of unmaintained third-party components.

Top CVEs where this control is the strongest mitigation

CVE Risk CVSS EPSS Match
CVE-2024-36912 6.99.60.0096partial
CVE-2025-15480 6.89.10.0031partial
CVE-2024-36913 6.69.30.0065partial
CVE-2025-14551 6.08.10.0028partial
CVE-2026-664325.87.50.0040partial
CVE-2026-526965.77.50.0024partial
CVE-2025-32257 4.65.30.0080partial
CVE-2025-26482 3.94.90.0029partial
CVE-2026-269483.94.90.0029partial

Other controls in family SA

SA-1 SA-10 SA-11 SA-12 SA-13 SA-14 SA-15 SA-16 SA-17 SA-18 SA-19 SA-2 SA-20 SA-21 SA-22 SA-23 SA-24 SA-3 SA-5 SA-6 SA-7 SA-8 SA-9