← SA-11
SA-11(2) SA · System and Services Acquisition

Threat Modeling and Vulnerability Analyses

LOW MODERATE HIGH
1 Overlay 3 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

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:

Discussion (NIST 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.

Implementation Guidance

Engineering Interpretation

Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.

No engineering interpretation has been authored for SA-11(2) yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.

Assessment

NIST SP 800-53A REV 5.2.0

Assessment Objectives

  1. information concerning impact, environment of operations, known or assumed threats, and acceptable risk levels to be used as contextual information for threat modeling and vulnerability analyses is defined;
  2. the tools and methods to be employed for threat modeling and vulnerability analyses are defined;
  3. the breadth and depth of threat modeling to be conducted is defined;
  4. the breadth and depth of vulnerability analyses to be conducted is defined;
  5. acceptance criteria to be met by produced evidence for threat modeling are defined;
  6. acceptance criteria to be met by produced evidence for vulnerability analyses are defined;
  7. the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that uses <SA-11(02)_ODP[01] information>;
  8. the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that uses <SA-11(02)_ODP[01] information>;
  9. the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that uses <SA-11(02)_ODP[01] information>;
  10. the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that uses <SA-11(02)_ODP[01] information>;
  11. the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that employs <SA-11(02)_ODP[02] tools and methods>;
  12. the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that employs <SA-11(02)_ODP[02] tools and methods>;
  13. the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that employs <SA-11(02)_ODP[02] tools and methods>;
  14. the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that employs <SA-11(02)_ODP[02] tools and methods>;
  15. the developer of the system, system component, or system service is required to perform threat modeling at <SA-11(02)_ODP[03] breadth and depth> during development of the system, component, or service;
  16. the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that conducts modeling and analyses at <SA-11(02)_ODP[04] breadth and depth>;
  17. the developer of the system, system component, or system service is required to perform threat modeling during development of the system, component, or service that produces evidence that meets <SA-11(02)_ODP[05] acceptance criteria>;
  18. the developer of the system, system component, or system service is required to perform threat modeling during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets <SA-11(02)_ODP[05] acceptance criteria>;
  19. the developer of the system, system component, or system service is required to perform vulnerability analyses during development of the system, component, or service that produces evidence that meets <SA-11(02)_ODP[06] acceptance criteria>;
  20. the developer of the system, system component, or system service is required to perform vulnerability analyses during the subsequent testing and evaluation of the system, component, or service that produces evidence that meets <SA-11(02)_ODP[06] acceptance criteria>.

Examine

[SELECT FROM: System and services acquisition policy; procedures addressing system developer security testing; solicitation documentation; acquisition documentation; service level agreements; acquisition contracts for the system, system component, or system service; system developer security test plans; records of developer security testing results for the system, system component, or system service; vulnerability scanning results; system risk assessment reports; threat and vulnerability analysis reports; system security plan; supply chain risk management plan; other relevant documents or records].

Interview

[SELECT FROM: Organizational personnel with system and service acquisition responsibilities; organizational personnel with information security responsibilities; organizational personnel with developer security testing responsibilities; system developers; organizational personnel with supply chain risk management responsibilities].

Test

[SELECT FROM: Organizational processes for monitoring developer security testing and evaluation; mechanisms supporting and/or implementing the monitoring of developer security testing and evaluation].

Overlays

Showing the OT/ICS overlay for the parent control SA-11 — see the SA-11(2) entries within each baseline below.

OT/ICS Overlay SP 800-82r3

NIST SP 800-82r3 Appendix F, Table 22. Blank baseline means the control/control enhancement is not selected in that initial OT baseline.

LOW

Not applicable at this tier.

MODERATE

  • Base control: Included (matches standard baseline)

HIGH

  • Base control: Included (matches standard baseline)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for SA-11(2). This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.

Learn more about STIG/CCI integration →

Evidence

Potential Evidence — Derived

Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.

Policy

  • System and services acquisition policy
  • system security plan
  • supply chain risk management plan

Testing

  • Organizational processes for monitoring developer security testing and evaluation
  • mechanisms supporting and/or implementing the monitoring of developer security testing and evaluation

Other Records

  • procedures addressing system developer security testing
  • solicitation documentation
  • acquisition documentation
  • service level agreements
  • acquisition contracts for the system, system component, or system service
  • system developer security test plans
  • records of developer security testing results for the system, system component, or system service
  • vulnerability scanning results
  • system risk assessment reports
  • threat and vulnerability analysis reports
  • other relevant documents or records