id: "SA-15(03)" title: "Criticality Analysis" family: "SA" family_name: "System and Services Acquisition" sort_id: "sa-15.03" priority: "P1" implementation_level: "organization" parent: "SA-15" enhancement: True
Statement
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: {{ insert: param, sa-15.03_odp.01 }} ; and
At the following level of rigor: {{ insert: param, sa-15.3_prm_2 }}.
Guidance
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.
Assessment Objective: the developer of the system, system component, or system service is required to perform a criticality analysis at {{ insert: param, sa-15.03_odp.01 }} in the system development life cycle;
Assessment Objective: the developer of the system, system component, or system service is required to perform a criticality analysis at the following rigor level: {{ insert: param, sa-15.03_odp.02 }};
Assessment Objective: the developer of the system, system component, or system service is required to perform a criticality analysis at the following rigor level: {{ insert: param, sa-15.03_odp.03 }} .
Supply chain risk management plan
system and services acquisition policy
procedures addressing development process, standards, and tools
procedures addressing criticality analysis requirements for the system, system component, or system service
solicitation documentation
acquisition documentation
service level agreements
acquisition contracts for the system, system component, or system service
criticality analysis documentation
business impact analysis documentation
software development life cycle documentation
system security plan
other relevant documents or records
Organizational personnel with system and service acquisition responsibilities
organizational personnel with information security responsibilities
organizational personnel responsible for performing criticality analysis
system developer
organizational personnel with supply chain risk management responsibilities
Organizational processes for performing criticality analysis
mechanisms supporting and/or implementing criticality analysis