SA-15(3) Criticality Analysis
Control enhancement of SA-15 Development Process, Standards, and Tools
Control
Require the developer of the system, system component, or system service to perform a criticality analysis:
At the following decision points in the system development life cycle: [Assignment: decision points] ; and
At the following level of rigor: [Assignment: organization-defined breadth and depth of criticality analysis].
Discussion
Criticality analysis performed by the developer provides input to the criticality analysis performed by organizations. Developer input is essential to organizational criticality analysis because organizations may not have access to detailed design documentation for system components that are developed as commercial off-the-shelf products. Such design documentation includes functional specifications, high-level designs, low-level designs, source code, and hardware schematics. Criticality analysis is important for organizational systems that are designated as high value assets. High value assets can be moderate- or high-impact systems due to heightened adversarial interest or potential adverse effects on the federal enterprise. Developer input is especially important when organizations conduct supply chain criticality analyses.
Related controls
Need SA-15(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.
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.