FedRAMP High
SA - System and Services Acquisition

FedRAMP High SA-11(2): Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses (SA-11(2))

Developer Testing and Evaluation | Threat Modeling and Vulnerability Analyses. Require the developer of the system, system component, or system service to perform threat modeling and vulnerability analyses during development and the subsequent testing

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 23 controls across 12 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

SOC 2 · 4 controls

  • SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)
  • SOC2-CC5.1 CC5.1 Selecting control activities that mitigate risk (COSO principle 10)
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • SOC2-CC9.1 CC9.1 Mitigating risks of business disruption

ISO 27001:2022 · 3 controls

  • 8.25 Secure development life cycle
  • 8.27 Secure system architecture and engineering principles
  • 8.29 Security testing in development and acceptance

NIST SP 800-53 Rev 5 · 3 controls

PCI DSS 4.0 · 3 controls

  • 6.2.1 6.2.1 Secure development of bespoke and custom software
  • 6.2.4 6.2.4 Engineering techniques against common software attacks
  • 6.3.1 6.3.1 Vulnerability identification and risk ranking

ISO 27002:2022 · 2 controls

  • 8.25 Secure development life cycle
  • 8.29 Security testing in development and acceptance

NIST SP 800-218 · 2 controls

  • SEC01-BP07 Identify threats and prioritize mitigations using a threat model

C5 (Germany) · 1 control

  • C5-PSS-02 Identification of Vulnerabilities of the Cloud Service

CIS Controls v8 · 1 control

NIST SP 800-172 · 1 control

  • 3.11.1e Threat-Aware Risk Assessment

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in SA - System and Services Acquisition

You are reading one control. How much of FedRAMP High have you already done?

FedRAMP High SA-11(2) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP High your existing evidence covers. Hold C5 (Germany) and 119 of 410 FedRAMP High controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 6 were rejected on the C5 (Germany) pair alone.

Query this from an agent

The graph holds this control, the 23 it maps to, and the evidence behind each claim, over MCP and REST.