FedRAMP Moderate SA-3: System Development Life Cycle

What else in your programme already covers this

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

ISO 27001:2022 · 6 controls

5.8 Information security in project management
8.25 Secure development life cycle
8.26 Application security requirements
8.29 Security testing in development and acceptance
8.31 Separation of development, test and production environments
8.32 Change management

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.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
6.5.3 Pre-production environments are separated from production environments and the separation is enforced with access controls

ISO 27002:2022 · 3 controls

5.8 Information security in project management
8.25 Secure development life cycle
8.31 Separation of development, test and production environments

NIST SP 800-218 · 3 controls

SP800-218-PO.1.1 Define Security Requirements for Software Development
SP800-218-PO.2.1 Roles and Responsibilities for Secure Development
SP800-218-PO.4.1 Criteria for Software Security

Azure Security Benchmark · 2 controls

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

C5 (Germany) · 2 controls

C5-DEV-01 Policies for the development/procurement of information systems
C5-DEV-10 Separation of environments

CIS Controls v8 · 2 controls

CIS-16.1 Establish and Maintain a Secure Application Development Process
CIS-16.8 Separate Production and Non-Production Systems

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

ISO/IEC 42001:2023 · 2 controls

A.6 AI system life cycle
A.6.1.3 Processes for responsible design and development of AI systems

NIST Cybersecurity Framework 2.0 · 2 controls

NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle

AWS Well-Architected Security Pillar · 1 control

SEC11-BP06 Deploy software programmatically

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

AUCDR-IS-3 Securely manage information assets over their lifecycle

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

CFTC-SS-5 Systems Development and Quality Assurance Category

CMMC 2.0 · 1 control

SC.L2-3.13.2 Security Engineering

GDPR · 1 control

GDPR-Art.25 Data protection by design and by default

ISO 27701:2019 · 1 control

6.11.2 Security in development and support processes

NIS2 Directive · 1 control

Art.21.2.e Security in acquisition, development and maintenance, including vulnerability handling and disclosure

NIST SP 800-161 Rev 1 · 1 control

161R1-SA-3 System Development Life Cycle

NIST SP 800-171 Rev 3 · 1 control

03.16.01 Security Engineering Principles

NIST SP 800-53 Rev 5 · 1 control

NIST800-SA-3 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.

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

FedRAMP Moderate SA-3 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 gaps If you hold PCI DSS 4.051.1% covered · 158 gaps If you hold ISO 27001:202249.8% covered · 162 gaps If you hold NIST SP 800-171 Rev 345.5% covered · 176 gaps If you hold C5 (Germany)37.2% covered · 203 gaps If 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 each Browse the graph free