FedRAMP Moderate
SA - System and Services Acquisition

FedRAMP Moderate SA-11(1): Developer Testing and Evaluation | Static Code Analysis. Require the developer of the system, system component, or system service to employ static code analysis tools to identify common flaws and document the results of

Developer Testing and Evaluation | Static Code Analysis. Require the developer of the system, system component, or system service to employ static code analysis tools to identify common flaws and document the results of

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

What else in your programme already covers this

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

PCI DSS 4.0 · 6 controls

  • 6.2.1 Bespoke and custom software are developed securely, as follows: • Based on industry standards and/or best practices for secure development. • In accordance with PCI DSS (for example, secure authentication and logging). • Incorporating
  • 6.2.3 Custom software reviewed prior to production
  • 6.2.3.1 Code review findings corrected
  • 6.2.4 Coding practices prevent common attacks
  • 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
  • 6.5.1 Changes to all system components in the production environment are made according to established procedures that include: • Reason for, and description of, the change. • Documentation of security impact. • Documented change approval

ISO 27002:2022 · 3 controls

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

NIST SP 800-218 · 3 controls

  • 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.28 Secure coding
  • 8.29 Security testing in development and acceptance
  • AUCDR-IS-4 Formal vulnerability management program
  • ASBv3-DS-4 Integrate static application security testing into DevOps pipeline

CIS Controls v8 · 1 control

  • CIS-16.12 Implement Code-Level Security Checks
  • NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

NIST SP 800-172 · 1 control

  • 3.14.7e Verify Correctness of Security Functions

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 Moderate have you already done?

FedRAMP Moderate SA-11(1) is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP Moderate your existing evidence covers. Hold ISO 27002:2022 and 182 of 323 FedRAMP Moderate 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. 348 were rejected on the ISO 27002:2022 pair alone.

Query this from an agent

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