Cross-Framework Mapping

AWS Well-Architected Security PillarvsGLBA

See exactly how AWS Well-Architected Security Pillar controls map to GLBA. Pre-computed mappings, identified gaps, and coverage analysis.

8
Controls Mapped
81
Gaps Found
8%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

AWS Well-Architected Security Pillar maps to GLBA with 8% coverage across 7 directly mapped controls. Analysis of 89 AWS Well-Architected Security Pillar controls identifies 82 compliance gaps — primarily concentrated in Identity & Access Management.

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

Control Mappings

Showing 8 of 8 mapped controls across 4 domains. Sign up to explore all 415K+ mappings across 715 frameworks.

Cloud Security Overview(1 mappings)

AWS-WA-01Shared responsibility model definition
GLBA-Sec6801-PolicyDuty-SafeguardingStandardGLBA Section 6801 - Privacy Obligation Policy and Safeguarding Standard

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

AWS-WA-12Encryption of cloud-stored data
GLBA-Subordinate-Rules-OperationalisationGLBA Operationalisation through FTC Safeguards Rule, Privacy Rule, SEC Reg S-P and Banking-Agency Guidelines
AWS-WA-14Data backup and recovery in cloud
GLBA-Subordinate-Rules-OperationalisationGLBA Operationalisation through FTC Safeguards Rule, Privacy Rule, SEC Reg S-P and Banking-Agency Guidelines

AWS Well-Architected Security Pillar: Cloud Infrastructure Security(3 mappings)

AWS-WA-16Virtual network segmentation
GLBA-Subordinate-Rules-OperationalisationGLBA Operationalisation through FTC Safeguards Rule, Privacy Rule, SEC Reg S-P and Banking-Agency Guidelines
AWS-WA-19Image and template hardening
GLBA-Subordinate-Rules-OperationalisationGLBA Operationalisation through FTC Safeguards Rule, Privacy Rule, SEC Reg S-P and Banking-Agency Guidelines
AWS-WA-20Cloud configuration management
GLBA-Subordinate-Rules-OperationalisationGLBA Operationalisation through FTC Safeguards Rule, Privacy Rule, SEC Reg S-P and Banking-Agency Guidelines

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

AWS-WA-22Incident response in cloud2 targets
GLBA-Implementation-Roadmap-ExaminationGLBA Implementation Roadmap, Examination Readiness, Roles and Tooling
GLBA-Status-FTC-CFPB-SEC-NAIC-EnforcementGLBA Status, Enforcement Activity, FTC + CFPB + SEC + NAIC Recent Actions

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 715 framework browser
  • Cross-framework mappings (415K+)
  • 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 GLBA?

AWS Well-Architected Security Pillar has 89 controls across its framework, while GLBA covers 12 controls. Direct mapping analysis identifies 7 overlapping controls (8% coverage). The frameworks diverge most significantly in Identity & Access Management, where 15 AWS Well-Architected Security Pillar controls have no direct GLBA equivalent.

How many controls map between AWS Well-Architected Security Pillar and GLBA?

Of 89 total AWS Well-Architected Security Pillar controls, 7 map directly to GLBA controls — representing 8% coverage. The remaining 82 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 GLBA?

82 AWS Well-Architected Security Pillar controls have no direct equivalent in GLBA. 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 GLBA?

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.