Cross-Framework Mapping

AWS Well-Architected Security PillarvsProtective Security Policy Framework (PSPF) Release 2024

See exactly how AWS Well-Architected Security Pillar controls map to Protective Security Policy Framework (PSPF) Release 2024. Pre-computed mappings, identified gaps, and coverage analysis.

3
Controls Mapped
86
Gaps Found
3%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

AWS Well-Architected Security Pillar maps to Protective Security Policy Framework (PSPF) Release 2024 with 3% coverage across 3 directly mapped controls. Analysis of 89 AWS Well-Architected Security Pillar controls identifies 86 compliance gaps — primarily concentrated in Identity & Access Management.

Source: TheArtOfService Knowledge Graph | 89 controls analysed | 718 frameworks | 332K+ cross-framework mappings

Control Mappings

Showing 3 of 3 mapped controls across 3 domains. Sign up to explore all 332K+ mappings across 718 frameworks.

Cloud Security Overview(1 mappings)

AWS-WA-01Shared responsibility model definition
PSPF24-1Security Culture, Governance, Risk Management

AWS Well-Architected Security Pillar: Data Protection in Cloud(1 mappings)

AWS-WA-11Data classification for cloud
PSPF24-2Information Security, Cybersecurity Maturity, Essential Eight

AWS Well-Architected Security Pillar: Cloud Operations & Monitoring(1 mappings)

AWS-WA-22Incident response in cloud
PSPF24-1Security Culture, Governance, Risk Management

Stop Paying Consultants to Read Spreadsheets

AI-powered compliance intelligence across 718 frameworks — at a fraction of consulting costs.

$0/forever

Free

  • 718 framework browser
  • Cross-framework mappings (332K+)
  • 824 compliance assessments
  • 3 AI queries & searches per day
Get Started Free
Recommended
$49/month

Professional

  • Unlimited AI Compliance Advisory
  • Unlimited full-text search
  • Framework self-assessment
  • PDF, Excel & CSV exports
Start 7-Day Free Trial →

What are the key differences between AWS Well-Architected Security Pillar and Protective Security Policy Framework (PSPF) Release 2024?

AWS Well-Architected Security Pillar has 89 controls across its framework, while Protective Security Policy Framework (PSPF) Release 2024 covers 5 controls. Direct mapping analysis identifies 3 overlapping controls (3% coverage). The frameworks diverge most significantly in Identity & Access Management, where 15 AWS Well-Architected Security Pillar controls have no direct Protective Security Policy Framework (PSPF) Release 2024 equivalent.

How many controls map between AWS Well-Architected Security Pillar and Protective Security Policy Framework (PSPF) Release 2024?

Of 89 total AWS Well-Architected Security Pillar controls, 3 map directly to Protective Security Policy Framework (PSPF) Release 2024 controls — representing 3% coverage. The remaining 86 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping AWS Well-Architected Security Pillar to Protective Security Policy Framework (PSPF) Release 2024?

86 AWS Well-Architected Security Pillar controls have no direct equivalent in Protective Security Policy Framework (PSPF) Release 2024. The highest concentration of gaps is in Identity & Access Management with 15 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.

Which control domains have the most gaps between AWS Well-Architected Security Pillar and Protective Security Policy Framework (PSPF) Release 2024?

The domain with the highest gap count is Identity & Access Management (15 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.