SA-11 (02)—Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses

Moderate

High

>Control Description

Require the developer of the system, system component, or system service to perform threat modeling and vulnerability analyses during development and the subsequent testing and evaluation of the system, component, or service that: (a) Uses the following contextual information: ⚙organization-defined information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels; (b) Employs the following tools and methods: ⚙organization-defined tools and methods; (c) Conducts the modeling and analyses at the following level of rigor: ⚙organization-defined breadth and depth of modeling and analyses; and (d) Produces evidence that meets the following acceptance criteria: ⚙organization-defined acceptance criteria.

>FedRAMP Baseline Requirements

No FedRAMP-specific parameter values or requirements for this baseline.

>Discussion

Systems, system components, and system services may deviate significantly from the functional and design specifications created during the requirements and design stages of the system development life cycle. Therefore, updates to threat modeling and vulnerability analyses of those systems, system components, and system services during development and prior to delivery are critical to the effective operation of those systems, components, and services. Threat modeling and vulnerability analyses at this stage of the system development life cycle ensure that design and implementation changes have been accounted for and that vulnerabilities created because of those changes have been reviewed and mitigated.

>Assessment Interview Topics

Questions assessors commonly ask

Process & Governance:

•What acquisition policies and procedures address the requirements of SA-11(2)?
•How are security and privacy requirements integrated into the acquisition process?
•Who is responsible for ensuring that acquisitions comply with SA-11(2)?
•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.