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

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 covers 57.4% of SOC 2

35 of the 61 controls in SOC 2 are already satisfied by evidence you collected for Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1. 26 are genuine gaps. Every claim below was judged against both control sets and then argued against; the ones that did not survive are published further down with the reason each failed.

57.4%
of the target already covered
35
controls evidenced
26
genuine gaps
0
claims rejected in review

What this leaves you to do

SOC 2 has 61 controls. Holding Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 already evidences 35 of them, so the work in front of you is 26 controls, not 61, which is 43% of the standard rather than all of it.

That is the whole claim. Every number in that sentence comes from the two counts above it and can be re-derived from the free tools without taking our word for any of it.

In money, using only our numbers. The full report is $299 and names 35 controls of SOC 2 you do not have to implement again, which is $8.54 per control identified. That arithmetic uses our price and our count and assumes nothing about you.

In your hours, using your assumption. We do not know what a control costs you to implement, so pick the column that looks like your organisation. These are your figures, not our claim.

If a control takes you4 hours8 hours16 hours
the 35 already evidenced are140 hours280 hours560 hours
and the 26 remaining are104 hours208 hours416 hours

Multiply by your own rate. We publish no rate because we have not measured yours, and a number built on an invented rate is the kind of claim this platform exists to argue against.

This number is directional. It says how much of SOC 2 your Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 evidence satisfies. The reverse pair is a different number, often very different, because a security standard has enormous depth for access control and almost none for lawful basis or data subject rights.

121 candidate mappings were examined and 0 were removed. Signed off 2026-08-19, review level machine verified. Mappings were judged by Claude Code rather than read line by line by a practitioner. Every claim shows its reasoning so you can check it. Ask and a practitioner will review this pair. This pair was additionally re-checked after CSA CCM v4.0.1 was rebuilt from the CAIQ v4.0.1 source on 2026-08-19: its mappings were originally judged when CCM carried no requirement text, a sample of 70 across the 21 CCM pairs found about 80 percent holding cleanly, and the two identified errors were corrected before release.

Where the gaps are

Coverage is never evenly spread. A source standard usually satisfies one part of a target almost completely and barely touches another, and which part is which is the thing worth knowing before you plan the work.

A - Availability3 of 3 evidenced
C - Confidentiality2 of 2 evidenced
CC - Common Criteria (Security)21 of 33 evidenced, 12 to do
P - Privacy9 of 18 evidenced, 9 to do
PI - Processing Integrity0 of 5 evidenced, 5 to do

Theme level, not control level, deliberately. The per-control list of what is evidenced and what is a gap is the report itself, so publishing it here would be publishing the thing being sold.

Claims that held

A sample. Each one names the control whose evidence does the work, the control it satisfies, and why.

CCM-IVS-02SOC2-A1.1argued against and upheld
Maintains capacity to meet availability commitments

Capacity and resource planning is the same availability capacity requirement.

CCM-DCS-13SOC2-A1.2argued against and upheld
Environmental protections, data backups, and recovery infrastructure support availability

Environmental systems control is the environmental protection element.

CCM-BCR-08SOC2-A1.2argued against and upheld
Environmental protections, data backups, and recovery infrastructure support availability

Backup control is the data backup element of this requirement.

CCM-BCR-10SOC2-A1.3argued against and upheld
Recovery plan procedures support system recovery from failures

Response plan exercises are the recovery plan testing requirement.

CCM-BCR-06SOC2-A1.3argued against and upheld
Recovery plan procedures support system recovery from failures

Business continuity exercises test recovery procedures.

CCM-DSP-17SOC2-C1.1argued against and upheld
Confidential information is identified and protected during receipt, processing, storage

Sensitive data protection is the safeguarding requirement.

CCM-DSP-04SOC2-C1.1argued against and upheld
Confidential information is identified and protected during receipt, processing, storage

Data classification identifies information requiring confidentiality.

CCM-DSP-02SOC2-C1.2argued against and upheld
Confidential information is disposed of securely

Secure disposal of data is the same requirement.

Claims that did not hold

Nothing proposed for this pair was rejected in review. That is unusual and worth knowing rather than hiding: it means the candidate set was small and every candidate held.

The full report

Everything above is a sample. The report is every evidenced control and every gap, with the reasoning and the source document behind each one, in a form you can hand to an assessor. $299, emailed immediately.

Buy this crosswalk