AWS Well-Architected Security Pillar SEC11-BP04: Conduct code reviews

What else in your programme already covers this

This control maps to 32 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 · 4 controls

SP800-218-PS.1.1 Protect All Forms of Code from Unauthorized Modification
SP800-218-PW.7.1 Code Review
SP800-218-PW.7.2 Perform Code Review and Analysis
SP800-218-RV.1.2 Review and Analyze Code for Vulnerabilities

C5 (Germany) · 3 controls

C5-DEV-06 Testing changes
C5-DEV-09 Approvals for provision in the production environment
C5-PSS-02 Identification of Vulnerabilities of the Cloud Service

FedRAMP High · 3 controls

CM-4 Impact Analyses
SA-11 Developer Testing and Evaluation
SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))

FedRAMP Moderate · 3 controls

CM-4 Impact Analyses
SA-11 Developer Testing and Evaluation
SA-11(1) Developer Testing and Evaluation | Static Code Analysis (SA-11(1))

NIST SP 800-53 Rev 5 · 3 controls

NIST800-CM-4 CM-4 Impact Analyses
NIST800-SA-11 SA-11 Developer Testing and Evaluation
NIST800-SA-15 SA-15 Development Process, Standards, and Tools

CIS Controls v8 · 2 controls

CIS-16.1 Establish and Maintain a Secure Application Development Process
CIS-16.12 Implement Code-Level Security Checks

CMMC 2.0 · 2 controls

CM.L2-3.4.3 System Change Management
CM.L2-3.4.4 Security Impact Analysis

ISO 27001:2022 · 2 controls

8.25 Secure development life cycle
8.28 Secure coding

NIST SP 800-161 Rev 1 · 2 controls

161R1-SA-11 Developer Testing and Evaluation
161R1-SA-15 Development Process, Standards, and Tools

PCI DSS 4.0 · 2 controls

6.2.3 6.2.3 Code review before release
6.2.3.1 6.2.3.1 Manual code review independence and approval

Azure Security Benchmark · 1 control

DS-6 Enforce security of workload throughout DevOps lifecycle

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

CCM-AIS-04 Secure Application Design and Development

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-171 Rev 3 · 1 control

03.16.01 Security Engineering Principles

SOC 2 · 1 control

SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

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 AWS Well-Architected Security Pillar have you already done?

AWS Well-Architected Security Pillar SEC11-BP04 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of AWS Well-Architected Security Pillar your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 52 of 63 AWS Well-Architected Security Pillar controls already carry evidence.

If you hold NIST SP 800-53 Rev 582.5% covered · 11 gaps If you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.174.6% covered · 16 gaps If you hold ISO 27002:202273% covered · 17 gaps If you hold FedRAMP Moderate69.8% covered · 19 gaps If you hold Azure Security Benchmark65.1% covered · 22 gaps If you hold PCI DSS 4.063.5% covered · 23 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. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.

See the released pairs, $299 each Browse the graph free