FedRAMP Moderate
SA - System and Services Acquisition

FedRAMP Moderate SA-15: Development Process, Standards, and Tools. a. Require the developer of the system, system component, or system service to follow a documented development process that: 1. Explicitly addresses security and privacy requirements; 2. Identifies the

Development Process, Standards, and Tools. a. Require the developer of the system, system component, or system service to follow a documented development process that: 1. Explicitly addresses security and privacy requirements; 2. Identifies the

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

What else in your programme already covers this

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

NIST SP 800-218 · 9 controls

ISO 27001:2022 · 4 controls

  • 8.25 Secure development life cycle
  • 8.26 Application security requirements
  • 8.27 Secure system architecture and engineering principles
  • 8.28 Secure coding

ISO 27002:2022 · 4 controls

  • 5.8 Information security in project management
  • 8.25 Secure development life cycle
  • 8.28 Secure coding
  • 8.29 Security testing in development and acceptance

NIST SP 800-53 Rev 5 · 4 controls

  • NIST800-SA-15 Development process, standards, and tools
  • NIST800-SA-17 Developer Security and Privacy Architecture and Design. Require the developer of the system, system component, or system service to produce a design specification and security and privacy architecture that: Is consistent with the organization's
  • NIST800-SA-22 Unsupported System Components
  • SP800-53-SA System and Services Acquisition Family

PCI DSS 4.0 · 4 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.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.3 Pre-production environments are separated from production environments and the separation is enforced with access controls

Azure Security Benchmark · 3 controls

  • ASBv3-DS-3 Secure DevOps infrastructure
  • ASBv3-GS-10 Define and implement DevOps security strategy
  • DS-6 Enforce security of workload throughout DevOps lifecycle

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

  • CCM-AIS-01 Application and Interface Security Policy and Procedures
  • CCM-AIS-04 Secure Application Design and Development

AWS Well-Architected Security Pillar · 1 control

Australia Consumer Data Right - Banking (CDR) · 1 control

  • AUCDR-IS-4 Formal vulnerability management program

C5 (Germany) · 1 control

  • C5-DEV-04 Safety training and awareness programme regarding continuous software delivery and associated systems, components or tools

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

  • CFTC-SS-5 Systems Development and Quality Assurance Category

CIS Controls v8 · 1 control

  • CIS-16.1 Establish and Maintain a Secure Application Development Process

ISO 27701:2019 · 1 control

  • 6.11.2 Security in development and support processes

ISO/IEC 42001:2023 · 1 control

  • A.6.1.3 Processes for responsible design and development of AI systems

NIST Cybersecurity Framework 2.0 · 1 control

  • 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-161 Rev 1 · 1 control

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-15 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.

If you hold ISO 27002:202256.3% covered · 141 gapsIf you hold PCI DSS 4.051.1% covered · 158 gapsIf you hold ISO 27001:202249.8% covered · 162 gapsIf you hold NIST SP 800-171 Rev 345.5% covered · 176 gapsIf you hold C5 (Germany)37.2% covered · 203 gapsIf you hold CMMC 2.035% covered · 210 gaps

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.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll FedRAMP Moderate controls