FedRAMP High
SA - System and Services Acquisition

FedRAMP High SA-11: Developer Testing and Evaluation

Require developer to test at FedRAMP-defined depth and coverage; document; correct flaws.

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

What else in your programme already covers this

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

CIS Controls v8 · 6 controls

  • CIS-16.1 Establish and Maintain a Secure Application Development Process
  • CIS-16.12 Implement Code-Level Security Checks
  • CIS-16.13 Conduct Application Penetration Testing
  • CIS-16.2 Establish and Maintain a Process to Accept and Address Software Vulnerabilities
  • CIS-16.8 Separate Production and Non-Production Systems
  • CIS-18.3 Remediate Penetration Test Findings

NIST SP 800-218 · 6 controls

  • ASBv3-DS-4 Integrate static application security testing into DevOps pipeline
  • ASBv3-DS-5 Integrate dynamic application security testing into DevOps pipeline
  • DS-6 Enforce security of workload throughout DevOps lifecycle

PCI DSS 4.0 · 3 controls

  • 6.2.3 Custom software reviewed prior to production
  • 6.2.3.1 Code review findings corrected
  • 6.3.1 Security vulnerabilities are identified and managed as follows: • New security vulnerabilities are identified using industry-recognized sources for security vulnerability information, including alerts from international and national computer emergency response teams (CERTs). • Vulnerabilities
  • SEC11-BP02 Automate testing throughout the development and release lifecycle
  • SEC11-BP04 Conduct code reviews

C5 (Germany) · 2 controls

ISO 27001:2022 · 2 controls

  • 8.26 Application security requirements
  • 8.29 Security testing in development and acceptance

ISO 27002:2022 · 2 controls

  • 8.25 Secure development life cycle
  • 8.29 Security testing in development and acceptance
  • AUCDR-IS-4 Formal vulnerability management program
  • CFTC-SS-5 Systems Development and Quality Assurance Category

DORA · 1 control

ISO 27701:2019 · 1 control

  • 6.11.2 Security in development and support processes

ISO/IEC 42001:2023 · 1 control

  • A.6.2.4 AI system verification and validation
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
  • 53A-2.1 Assessments Within the System Development Life Cycle

SOC 2 · 1 control

  • SOC2-CC8.1 Change management processes are in place

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 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 38 it maps to, and the evidence behind each claim, over MCP and REST.