+SA-15(03) [H] Criticality Analysis

SA-15(03) [H] Criticality Analysis

Control

Require the developer of the system, system component, or system service to perform a criticality analysis:
  1. At the following decision points in the system development life cycle: [Assignement: decision points] ; and
  2. At the following level of rigor: [Assignement: 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.

Assessment Objective

  1. the developer of the system, system component, or system service is required to perform a criticality analysis at [Assignement: decision points] in the system development life cycle;
    1. the developer of the system, system component, or system service is required to perform a criticality analysis at the following rigor level: [Assignement: breadth];
    2. the developer of the system, system component, or system service is required to perform a criticality analysis at the following rigor level: [Assignement: depth] .

Assessment Method

Examine

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

Interview

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

1. Panoramica

1.1 Riferimenti

1.2 Requisiti identificati

1.3 Regolamentazioni correlate

2. Requisiti identificati

Requisiti

3. Regolamentazioni correlate

Regolamentazioni

Ticket collegati

Collegamenti
is blocked by SA-15(03) [H] Criticality Analysis – Assessment Procedure
is blocked by Criticality Analysis During Development