Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-CCC-02: Quality Testing

What else in your programme already covers this

This control maps to 38 controls across 20 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 · 4 controls

11.3.1.3 11.3.1.3 Internal scans after significant change
6.2.3 6.2.3 Code review before release
6.5.1 6.5.1 Change control procedure for production
6.5.2 6.5.2 Confirm PCI DSS controls after significant change

C5 (Germany) · 3 controls

C5-AM-03 Commissioning of Hardware
C5-DEV-06 Testing changes
C5-DEV-09 Approvals for provision in the production environment

NIST SP 800-171 Rev 3 · 3 controls

03.04.01 Baseline Configuration
03.04.03 Configuration Change Control
03.04.04 Impact Analyses

NIST SP 800-218 · 3 controls

SP800-218-PO.4.1 Criteria for Software Security
SP800-218-PS.1.1 Protect All Forms of Code from Unauthorized Modification
SP800-218-PW.8.2 Execute Security Testing

AWS Well-Architected Security Pillar · 2 controls

SEC11-BP02 Automate testing throughout the development and release lifecycle
SEC11-BP06 Deploy software programmatically

Azure Security Benchmark · 2 controls

ASBv3-DS-4 Integrate static application security testing into DevOps pipeline
ASBv3-DS-5 Integrate dynamic application security testing into DevOps pipeline

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 2 controls

CFTC-SS-12 Capacity and Performance Planning Category
CFTC-SS-5 Systems Development and Quality Assurance Category

FedRAMP High · 2 controls

CM-3(2) Testing, Validation, and Documentation of Changes
CM-4 Impact Analyses

FedRAMP Moderate · 2 controls

CM-3(2) Testing, Validation, and Documentation of Changes
CM-4 Impact Analyses

ISO 27001:2022 · 2 controls

8.29 Security testing in development and acceptance
8.32 Change management

ISO 27002:2022 · 2 controls

8.29 Security testing in development and acceptance
8.32 Change management

NIST SP 800-161 Rev 1 · 2 controls

161R1-CM-4 Impact Analysis
161R1-SA-11 Developer Testing and Evaluation

NIST SP 800-53 Rev 5 · 2 controls

NIST800-CM-3 CM-3 Configuration Change Control
NIST800-CM-4 CM-4 Impact Analyses

CIS Controls v8 · 1 control

CIS-16.12 Implement Code-Level Security Checks

CMMC 2.0 · 1 control

CM.L2-3.4.4 Security Impact Analysis

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

CCC-02 Quality Testing

EU AI Act · 1 control

EUAI-Art.43 Conformity assessment

NIST Cybersecurity Framework 2.0 · 1 control

NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked

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 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 have you already done?

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 CCM-CCC-02 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 140 of 197 Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 controls already carry evidence.

If you hold NIST SP 800-53 Rev 571.1% covered · 57 gaps If you hold FedRAMP Moderate60.4% covered · 78 gaps If you hold PCI DSS 4.060.4% covered · 78 gaps If you hold C5 (Germany)58.4% covered · 82 gaps If you hold ISO 27001:202256.3% covered · 86 gaps If you hold ISO 27002:202256.3% covered · 86 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. 12 were rejected on the NIST SP 800-53 Rev 5 pair alone.

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