AWS Well-Architected Security PillarvsUS ITAR and EAR — Export Control and Data Security
See exactly how AWS Well-Architected Security Pillar controls map to US ITAR and EAR — Export Control and Data Security. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
AWS Well-Architected Security Pillar maps to US ITAR and EAR — Export Control and Data Security with 48% coverage across 12 directly mapped controls. Analysis of 25 AWS Well-Architected Security Pillar controls identifies 13 compliance gaps — primarily concentrated in AWS Well-Architected Security Pillar: Cloud Infrastructure Security.
Source: TheArtOfService Knowledge Graph | 25 controls analysed | 693 frameworks | 819K+ cross-framework mappings
Control Mappings
Showing 18 of 18 mapped controls across 4 domains. Sign up to explore all 819K+ mappings across 693 frameworks.
AWS Well-Architected Security Pillar: Cloud Governance(8 mappings)
AWS Well-Architected Security Pillar: Identity & Access in Cloud(1 mappings)
AWS Well-Architected Security Pillar: Data Protection in Cloud(4 mappings)
AWS Well-Architected Security Pillar: Cloud Operations & Monitoring(5 mappings)
Related Comparisons
Other AWS Well-Architected Security Pillar comparisons
Other US ITAR and EAR — Export Control and Data Security comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 693 frameworks — at a fraction of consulting costs.
Free
- ✓ 693 framework browser
- ✓ Cross-framework mappings (819K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between AWS Well-Architected Security Pillar and US ITAR and EAR — Export Control and Data Security?
AWS Well-Architected Security Pillar has 25 controls across its framework, while US ITAR and EAR — Export Control and Data Security covers 41 controls. Direct mapping analysis identifies 12 overlapping controls (48% coverage). The frameworks diverge most significantly in AWS Well-Architected Security Pillar: Cloud Infrastructure Security, where 5 AWS Well-Architected Security Pillar controls have no direct US ITAR and EAR — Export Control and Data Security equivalent.
How many controls map between AWS Well-Architected Security Pillar and US ITAR and EAR — Export Control and Data Security?
Of 25 total AWS Well-Architected Security Pillar controls, 12 map directly to US ITAR and EAR — Export Control and Data Security controls — representing 48% coverage. The remaining 13 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 US ITAR and EAR — Export Control and Data Security?
13 AWS Well-Architected Security Pillar controls have no direct equivalent in US ITAR and EAR — Export Control and Data Security. The highest concentration of gaps is in AWS Well-Architected Security Pillar: Cloud Infrastructure Security with 5 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 US ITAR and EAR — Export Control and Data Security?
The domain with the highest gap count is AWS Well-Architected Security Pillar: Cloud Infrastructure Security (5 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
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.