FedRAMP Moderate SA-8: Security and Privacy Engineering Principles

What else in your programme already covers this

This control maps to 36 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.

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

CCM-AIS-01 Application and Interface Security Policy and Procedures
CCM-AIS-04 Secure Application Design and Development
CCM-DSP-07 Data Protection by Design and Default
CCM-DSP-08 Data Privacy by Design and Default

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

SOC 2 · 4 controls

SOC2-CC5.2 COSO principle 11: Selects and develops general controls over technology
SOC2-CC6.1 Implements logical access security software, infrastructure and architectures over protected information assets
SOC2-CC8.1 Change management processes are in place
SOC2-P3.1 Personal information is collected consistent with privacy commitments

ISO 27001:2022 · 3 controls

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

ISO 27002:2022 · 3 controls

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

NIST SP 800-218 · 3 controls

SP800-218-PW.1.1 Design Software to Meet Security Requirements
SP800-218-PW.1.3 Support Standardized Security Features
SP800-218-PW.2.1 Qualified Review of Software Design

CIS Controls v8 · 2 controls

CIS-16.10 Apply Secure Design Principles in Application Architectures
CIS-16.11 Leverage Vetted Modules or Services for Application Security Components

NIST SP 800-53 Rev 5 · 2 controls

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-8 Security and privacy engineering principles

APEC Cross-Border Privacy Rules (CBPR) System · 1 control

CBPR-09 Preventing Harm

AWS Well-Architected Security Pillar · 1 control

SEC01-BP05 Reduce security management scope

Azure Security Benchmark · 1 control

ASBv3-DS-1 Conduct threat modeling

C5 (Germany) · 1 control

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

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

CFTC-SS-7 Generally Accepted Standards and Best Practices

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

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

161R1-SA-8 Security and Privacy Engineering Principles

NIST SP 800-171 Rev 3 · 1 control

03.16.01 Security Engineering Principles

NIST SP 800-172 · 1 control

3.13.2e Introduce Unpredictability into System Operations

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-8 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