AWS Well-Architected Security PillarISO 27002:2022

AWS Well-Architected Security Pillar covers 34.4% of ISO 27002:2022

32 of the 93 controls in ISO 27002:2022 are already satisfied by evidence you collected for AWS Well-Architected Security Pillar. 61 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.

34.4%
of the target already covered
32
controls evidenced
61
genuine gaps
0
claims rejected in review

This number is directional. It says how much of ISO 27002:2022 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.

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

Technological controls19 of 34 evidenced, 15 to do
Organizational controls13 of 37 evidenced, 24 to do
People controls0 of 8 evidenced, 8 to do
Physical controls0 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 7: How do you classify your data? | SEC07-BP015.12argued against and upheld
Classification of information

Documented classification scheme with handling requirements per class is the evidence assessors test.

SEC 3: How do you manage permissions for people and machines? | SEC03-BP015.15argued against and upheld
Access control

Documented who needs what access under which conditions is the access rule set assessors sample.

SEC 3: How do you manage permissions for people and machines? | SEC03-BP065.16argued against and upheld
Identity management

Joiner mover leaver driven provisioning is direct evidence of identity lifecycle management.

SEC 2: How do you manage identities for people and machines? | SEC02-BP045.16argued against and upheld
Identity management

Central identity provider governs identity creation, change and removal across the estate.

SEC 2: How do you manage identities for people and machines? | SEC02-BP035.17argued against and upheld
Authentication information

Managed secret storage with encryption and rotation is core authentication information handling.

SEC 2: How do you manage identities for people and machines? | SEC02-BP015.17argued against and upheld
Authentication information

MFA and password policy evidence how authentication information is issued and controlled.

SEC 3: How do you manage permissions for people and machines? | SEC03-BP065.18argued against and upheld
Access rights

Access provisioned and revoked on employment change is exactly what this control requires.

SEC 3: How do you manage permissions for people and machines? | SEC03-BP045.18argued against and upheld
Access rights

Unused access findings drive periodic review and removal of access rights.

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