NIST Cybersecurity Framework 2.0AWS Well-Architected Security Pillar

NIST Cybersecurity Framework 2.0 covers 49.2% of AWS Well-Architected Security Pillar

31 of the 63 controls in AWS Well-Architected Security Pillar are already satisfied by evidence you collected for NIST Cybersecurity Framework 2.0. 32 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.

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

This number is directional. It says how much of AWS Well-Architected Security Pillar your NIST Cybersecurity Framework 2.0 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.

70 candidate mappings were examined and 1 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.

Detection3 of 4 evidenced, 1 to do
Infrastructure Protection6 of 9 evidenced, 3 to do
Data Protection6 of 11 evidenced, 5 to do
Incident Response4 of 8 evidenced, 4 to do
Identity & Access Management7 of 15 evidenced, 8 to do
Security Foundations3 of 8 evidenced, 5 to do
Application Security2 of 8 evidenced, 6 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.

NIST-CSF-ID.IM-04SEC 10: How do you anticipate, respond to, and recover from incidents? | SEC10-BP02argued against and upheld
Develop incident management plans

Incident response plans established and maintained is the same requirement.

NIST-CSF-ID.IM-04SEC 10: How do you anticipate, respond to, and recover from incidents? | SEC10-BP04argued against and upheld
Develop and test security incident response playbooks

Maintained response plans include the prescriptive playbooks for anticipated scenarios.

NIST-CSF-ID.IM-01SEC 10: How do you anticipate, respond to, and recover from incidents? | SEC10-BP07argued against and upheld
Run simulations

Improvements drawn from exercise results require the exercises to be run.

NIST-CSF-ID.IM-03SEC 10: How do you anticipate, respond to, and recover from incidents? | SEC10-BP08argued against and upheld
Establish a framework for learning from incidents

Improvements identified from incidents is the learning framework.

NIST-CSF-PR.AT-02SEC 11: How do you incorporate and validate the security properties of applications? | SEC11-BP01argued against and upheld
Train for application security

Training for individuals in specialised roles covers developer application security.

NIST-CSF-PR.PS-06SEC 11: How do you incorporate and validate the security properties of applications? | SEC11-BP02argued against and upheld
Automate testing throughout the development and release lifecycle

Secure development practices integrated throughout the life cycle is pipeline testing.

NIST-CSF-GV.OC-03SEC 1: How do you securely operate your workload? | SEC01-BP03argued against and upheld
Identify and validate control objectives

Understood legal, regulatory and contractual requirements are the control objectives.

NIST-CSF-ID.RA-02SEC 1: How do you securely operate your workload? | SEC01-BP04argued against and upheld
Stay up to date with security threats and recommendations

Threat intelligence received from sharing forums is the same practice.

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