SA-11(2): Threat Modeling and Vulnerability Analyses

CSF v1.1 References:

CSF v2.0 References:


(Not part of any baseline)

Previous Version:

Info icon.

Incorporates the following control from the previous version of the control set: SA-15(4): Threat Modeling / Vulnerability Analysis.

Control Statement

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:

  1. Uses the following contextual information: [Assignment: organization-defined information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels];
  2. Employs the following tools and methods: [Assignment: organization-defined tools and methods];
  3. Conducts the modeling and analyses at the following level of rigor: [Assignment: organization-defined breadth and depth of modeling and analyses]; and
  4. Produces evidence that meets the following acceptance criteria: [Assignment: organization-defined acceptance criteria].

Supplemental Guidance

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.