Framework overlap

Does AWS Well-Architected Security Pillar cover Protective Security Policy Framework (PSPF) Release 2024?

You hold AWS Well-Architected Security Pillar and have been told to do Protective Security Policy Framework (PSPF) Release 2024. Here is how much overlaps, control by control.

60% of Protective Security Policy Framework (PSPF) Release 2024 you already have

AWS Well-Architected Security Pillar already covers about 60% of Protective Security Policy Framework (PSPF) Release 2024, leaving 2 of 5 controls as genuinely new work.

Already covered 2 Likely covered 1 New work 2

What is genuinely new work

Nothing in AWS Well-Architected Security Pillar reaches these. This is the list to scope.

PSPF24-3
Personnel Security and Vetting
PSPF24-5
Information and Cyber Incidents
Show the 3 you already have
PSPF24-1
Security Culture, Governance, Risk Management
PSPF24-2
Information Security, Cybersecurity Maturity, Essential Eight
PSPF24-4
Physical Security

How this is calculated

Already covered means a mapping runs from a control in AWS Well-Architected Security Pillar to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition