AWS Well-Architected Security PillarNIST Cybersecurity Framework 2.0

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

37 of the 106 controls in NIST Cybersecurity Framework 2.0 are already satisfied by evidence you collected for AWS Well-Architected Security Pillar. 69 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.9%
of the target already covered
37
controls evidenced
69
genuine gaps
0
claims rejected in review

This number is directional. It says how much of NIST Cybersecurity Framework 2.0 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.

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.

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.

DE - Detect7 of 11 evidenced, 4 to do
RS - Respond8 of 13 evidenced, 5 to do
PR - Protect12 of 22 evidenced, 10 to do
ID - Identify10 of 21 evidenced, 11 to do
GV - Govern0 of 28 evidenced, 28 to do
Govern0 of 3 evidenced, 3 to do
RC - Recover0 of 8 evidenced, 8 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 4: How do you detect and investigate security events? | SEC04-BP03NIST-CSF-DE.AE-02argued against and upheld
Potentially adverse events are analyzed to better understand associated activities

Alert enrichment and correlation across findings is the analysis of adverse events tested.

SEC 4: How do you detect and investigate security events? | SEC04-BP03NIST-CSF-DE.AE-03argued against and upheld
Information is correlated from multiple sources

Correlating signals across GuardDuty, Security Hub and other tools is multi source correlation.

SEC 4: How do you detect and investigate security events? | SEC04-BP02NIST-CSF-DE.AE-03argued against and upheld
Information is correlated from multiple sources

Aggregating telemetry into a central SIEM enables the cross source correlation required.

SEC 4: How do you detect and investigate security events? | SEC04-BP03NIST-CSF-DE.AE-07argued against and upheld
Cyber threat intelligence and contextual information are integrated into analysis

Threat intelligence enrichment of findings is exactly the integration this subcategory requires.

SEC 1: How do you securely operate your workload? | SEC01-BP04NIST-CSF-DE.AE-07argued against and upheld
Cyber threat intelligence and contextual information are integrated into analysis

Emerging threat feeds incorporated into detection rules evidence intelligence driving analysis.

SEC 5: How do you protect your network resources? | SEC05-BP03NIST-CSF-DE.CM-01argued against and upheld
Networks and network services are monitored to find potentially adverse events

Network firewall and inspection appliances actively monitor traffic for threats.

SEC 4: How do you detect and investigate security events? | SEC04-BP01NIST-CSF-DE.CM-01argued against and upheld
Networks and network services are monitored to find potentially adverse events

VPC flow logs and service logs across all accounts evidence network monitoring.

SEC 4: How do you detect and investigate security events? | SEC04-BP01NIST-CSF-DE.CM-03argued against and upheld
Personnel activity and technology usage are monitored to find potentially adverse events

CloudTrail across all accounts records personnel activity and technology usage for review.

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