SA-4(3) Development Methods, Techniques, and Practices

Control enhancement of SA-4 Acquisition Process

Control

Require the developer of the system, system component, or system service to demonstrate the use of a system development life cycle process that includes:

(a)

[Assignment: systems engineering methods];

(b)

[Assignment: Selection (one-or-more): [sa-04.03_odp.03] | [sa-04.03_odp.04] ] ; and

(c)

[Assignment: Selection (one-or-more): [sa-04.03_odp.06] | [sa-04.03_odp.07] | [sa-04.03_odp.08] ].

Discussion

Following a system development life cycle that includes state-of-the-practice software development methods, systems engineering methods, systems security and privacy engineering methods, and quality control processes helps to reduce the number and severity of latent errors within systems, system components, and system services. Reducing the number and severity of such errors reduces the number of vulnerabilities in those systems, components, and services. Transparency in the methods and techniques that developers select and implement for systems engineering, systems security and privacy engineering, software development, component and system assessments, and quality control processes provides an increased level of assurance in the trustworthiness of the system, system component, or system service being acquired.

Need SA-4(3) implemented and evidenced?

We assess where you stand against this control, document the gap, and build the remediation plan your auditor and your board will both accept.

Request an assessment

Control catalog and framework text on this page is reproduced from official NIST publications — a public-domain work of the U.S. Government (17 U.S.C. §105). Maverc commentary, groupings, and readiness guidance are our own and are not part of any NIST publication.