SA-15(3)—Development Process, Standards, and Tools | Criticality Analysis

IL4 Mod

IL4 High

IL5

IL6

>Control Description

Require the developer of the system, system component, or system service to perform a criticality analysis: (a) At the following decision points in the system development life cycle: ⚙organization-defined decision points in the system development life cycle; and (b) At the following level of rigor: ⚙organization-defined breadth and depth of criticality analysis.

>DoD Impact Level Requirements

No specific parameter values or requirements for this impact level.

>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.

>Programmatic Queries

Beta

Related Services

AWS CodePipeline

AWS CodeBuild

AWS Systems Manager

CLI Commands

Create pipeline with criticality gates

aws codepipeline create-pipeline --cli-input-json file://criticality-pipeline.json

Create build project for criticality analysis

aws codebuild create-project --name criticality-analysis --source type=GITHUB,location=https://github.com/repo --artifacts type=S3,location=s3://bucket/artifacts --service-role arn:aws:iam::123456789012:role/CodeBuildRole

Create Systems Manager automation for criticality gates

aws ssm create-document --content file://criticality-analysis.json --name criticality-analysis-doc --document-type Automation

Track criticality metrics

aws cloudwatch put-metric-alarm --alarm-name criticality-score --metric-name CriticalityScore --namespace CustomMetrics --statistic Average --period 300 --threshold 8 --comparison-operator GreaterThanThreshold

Open AWS Console Documentation

>Related Controls

RA-9

>Assessment Interview Topics

Questions assessors commonly ask

Process & Governance:

•What acquisition policies and procedures address the requirements of SA-15(3)?
•How are security and privacy requirements integrated into the acquisition process?
•Who is responsible for ensuring that acquisitions comply with SA-15(3)?
•How is security integrated throughout your system development lifecycle (SDLC)?

Technical Implementation:

•How are security requirements defined and documented in acquisition contracts?
•What mechanisms ensure that acquired systems and services meet security requirements?
•How do you validate that vendors and service providers comply with specified security controls?
•What security practices are required at each phase of the SDLC?
•What secure coding practices and standards are required for developers?

Evidence & Documentation:

•Can you provide examples of acquisition documentation that includes security requirements?
•What evidence demonstrates that acquired systems meet security specifications?
•Where is acquisition security documentation maintained throughout the system lifecycle?
•Can you show evidence of security activities performed during development?
•Can you provide code review or static analysis results?

Ask AI

Configure your API key to use AI features.