SA-15—Development Process, Standards, and Tools
>Control Description
Require the developer of the system, system component, or system service to follow a documented development process that:
Explicitly addresses security and privacy requirements;
Identifies the standards and tools used in the development process;
Documents the specific tool options and tool configurations used in the development process; and
Documents, manages, and ensures the integrity of changes to the process and/or tools used in development; and
Review the development process, standards, tools, tool options, and tool configurations ⚙organization-defined frequency to determine if the process, standards, tools, tool options and tool configurations selected and employed can satisfy the following security and privacy requirements: ⚙organization-defined security and privacy requirements.
>FedRAMP Baseline Requirements
No FedRAMP-specific parameter values or requirements for this baseline.
>Discussion
Development tools include programming languages and computer-aided design systems. Reviews of development processes include the use of maturity models to determine the potential effectiveness of such processes. Maintaining the integrity of changes to tools and processes facilitates effective supply chain risk assessment and mitigation.
Such integrity requires configuration control throughout the system development life cycle to track authorized changes and prevent unauthorized changes.
>Cross-Framework Mappings
>Programmatic Queries
Related Services
CLI Commands
aws codepipeline list-pipelinesaws codebuild batch-get-projects --names PROJECT_NAMEaws codeguruprofiler list-profiling-groupsaws codeguru-reviewer list-recommendations --code-review-arn CODE_REVIEW_ARN>Relevant Technologies
Technology-specific guidance with authoritative sources and verification commands.
>Assessment Interview Topics
Questions assessors commonly ask
Process & Governance:
- •What acquisition policies and procedures address the requirements of SA-15?
- •How are security and privacy requirements integrated into the acquisition process?
- •Who is responsible for ensuring that acquisitions comply with SA-15?
- •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.