TheArtOfService
AWS Well-Architected Security PillarCloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1

AWS Well-Architected Security Pillar covers 23.9% of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1

47 of the 197 controls in Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 are already satisfied by evidence you collected for AWS Well-Architected Security Pillar. 150 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.

23.9%
of the target already covered
47
controls evidenced
150
genuine gaps
0
claims rejected in review

This number is directional. It says how much of Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 your AWS Well-Architected Security Pillar 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.

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

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.

IAM - Identity & Access Management11 of 16 evidenced, 5 to do
IVS - Infrastructure & Virtualization Security6 of 9 evidenced, 3 to do
AIS - Application & Interface Security4 of 7 evidenced, 3 to do
CCC - Change Control & Configuration Management4 of 9 evidenced, 5 to do
TVM - Threat & Vulnerability Management4 of 10 evidenced, 6 to do
SEF - Security Incident Management, E-Discovery & Cloud Forensics3 of 8 evidenced, 5 to do
LOG - Logging & Monitoring4 of 13 evidenced, 9 to do
DSP - Data Security & Privacy Lifecycle Management5 of 19 evidenced, 14 to do
IPY - Interoperability & Portability1 of 4 evidenced, 3 to do
CEK - Cryptography, Encryption & Key Management4 of 21 evidenced, 17 to do
GRC - Governance, Risk & Compliance1 of 8 evidenced, 7 to do
A&A - Audit & Assurance0 of 6 evidenced, 6 to do
BCR - Business Continuity Management & Operational Resilience0 of 11 evidenced, 11 to do
DCS - Datacenter Security0 of 15 evidenced, 15 to do
HRS - Human Resources Security0 of 13 evidenced, 13 to do
STA - Supply Chain Management, Transparency & Accountability0 of 14 evidenced, 14 to do
UEM - Universal Endpoint Management0 of 14 evidenced, 14 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.

SEC 11: How do you incorporate and validate the security properties of applications? | SEC11-BP02CCM-AIS-04argued against and upheld
Secure Application Design and Development

Security testing embedded across build and release is direct secure development lifecycle evidence.

SEC 1: How do you securely operate your workload? | SEC01-BP07CCM-AIS-04argued against and upheld
Secure Application Design and Development

Per workload threat modelling evidences security requirements applied at design stage.

SEC 11: How do you incorporate and validate the security properties of applications? | SEC11-BP02CCM-AIS-05argued against and upheld
Automated Application Security Testing

SAST, SCA, DAST and image scanning gating the pipeline is exactly pre release automated testing.

SEC 11: How do you incorporate and validate the security properties of applications? | SEC11-BP06CCM-AIS-06argued against and upheld
Automated Secure Application Deployment

Automated pipeline deployment with approvals and no direct human push evidences standardised secure release.

SEC 6: How do you protect your compute resources? | SEC06-BP01CCM-AIS-07argued against and upheld
Application Vulnerability Remediation

Continuous scanning with risk prioritised remediation SLAs is the defined vulnerability fix process.

SEC 11: How do you incorporate and validate the security properties of applications? | SEC11-BP06CCM-CCC-02argued against and upheld
Quality Testing

Pipeline approvals, separation of duties and audit trail evidence the controlled path to production.

SEC 3: How do you manage permissions for people and machines? | SEC03-BP05CCM-CCC-04argued against and upheld
Unauthorized Change Protection

Service control policies enforce non negotiable boundaries preventing unauthorised asset administration.

SEC 1: How do you securely operate your workload? | SEC01-BP06CCM-CCC-06argued against and upheld
Change Management Baseline

Version controlled infrastructure as code is the recorded configuration baseline for authorised changes.

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