TheArtOfService
Cross-Framework Mapping

AWS Well-Architected Security PillarvsUS OFAC Sanctions Compliance Framework

See exactly how AWS Well-Architected Security Pillar controls map to US OFAC Sanctions Compliance Framework. Pre-computed mappings, identified gaps, and coverage analysis.

9
Controls Mapped
16
Gaps Found
28%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

AWS Well-Architected Security Pillar maps to US OFAC Sanctions Compliance Framework with 28% coverage across 7 directly mapped controls. Analysis of 25 AWS Well-Architected Security Pillar controls identifies 18 compliance gaps — primarily concentrated in AWS Well-Architected Security Pillar: Identity & Access in Cloud.

Source: TheArtOfService Knowledge Graph | 25 controls analysed | 693 frameworks | 819K+ cross-framework mappings

Control Mappings

Showing 9 of 9 mapped controls across 3 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

AWS Well-Architected Security Pillar: Cloud Governance(4 mappings)

AWS-WA-01Shared responsibility model definition
→TA-3Remediation of Findings
AWS-WA-03Cloud risk assessment3 targets
→DMF-4.1Impact Assessment
→DMF-4.3Regulatory Risk Assessment
→RA-1Security Risk Assessment

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

AWS-WA-11Data classification for cloud
→DMF-4.2Risk Categorization
AWS-WA-12Encryption of cloud-stored data
→DMF-4.3Regulatory Risk Assessment
AWS-WA-14Data backup and recovery in cloud
→DMF-4.3Regulatory Risk Assessment
AWS-WA-15Secure data deletion in cloud
→DMF-4.3Regulatory Risk Assessment

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

AWS-WA-23Cloud vulnerability management
→TA-3Remediation of Findings

Related Comparisons

Other AWS Well-Architected Security Pillar comparisons

AWS Well-Architected Security Pillar vs Azure Security Benchmark19 mappingsAWS Well-Architected Security Pillar vs NIST SP 800-19019 mappingsAWS Well-Architected Security Pillar vs CAIQ (CSA)19 mappingsAWS Well-Architected Security Pillar vs ISO 2701719 mappingsAWS Well-Architected Security Pillar vs MTCS (Singapore)19 mappingsAWS Well-Architected Security Pillar vs ISO 2701819 mappingsAWS Well-Architected Security Pillar vs NIST SP 800-14519 mappingsAWS Well-Architected Security Pillar vs C5 (Germany)19 mappings

Other US OFAC Sanctions Compliance Framework comparisons

SQF Code Edition 9 — Safe Quality Food vs US OFAC Sanctions Compliance Framework10 mappingsILO Nursing Personnel Convention C149 (1977) vs US OFAC Sanctions Compliance Framework9 mappingsILO Tripartite Declaration of Principles concerning Multinational Enterprises (MNE Declaration) vs US OFAC Sanctions Compliance Framework9 mappingsNIST SP 800-53 Rev 5 vs US OFAC Sanctions Compliance Framework9 mappingsNIST AI Risk Management Framework (AI RMF 1.0) vs US OFAC Sanctions Compliance Framework8 mappingsNIST AI 600-1 Generative AI Profile vs US OFAC Sanctions Compliance Framework8 mappingsChile Personal Data Protection Law (Law No. 21.719) vs US OFAC Sanctions Compliance Framework8 mappingsEU NIS2 Directive — Transport Sector Requirements vs US OFAC Sanctions Compliance Framework8 mappings

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • ✓ 693 framework browser
  • ✓ Cross-framework mappings (819K+)
  • ✓ 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 →

Popular framework comparisons

NIST CSF vs NIST 800-53ISO 27001 vs NIST CSFCMMC vs NIST 800-53FedRAMP vs NIST 800-53NIST CSF vs SOC 2HIPAA vs NIST 800-53ISO 27001 vs SOC 2ISO 27001 vs ISO 27701

What are the key differences between AWS Well-Architected Security Pillar and US OFAC Sanctions Compliance Framework?

AWS Well-Architected Security Pillar has 25 controls across its framework, while US OFAC Sanctions Compliance Framework covers 35 controls. Direct mapping analysis identifies 7 overlapping controls (28% coverage). The frameworks diverge most significantly in AWS Well-Architected Security Pillar: Identity & Access in Cloud, where 5 AWS Well-Architected Security Pillar controls have no direct US OFAC Sanctions Compliance Framework equivalent.

How many controls map between AWS Well-Architected Security Pillar and US OFAC Sanctions Compliance Framework?

Of 25 total AWS Well-Architected Security Pillar controls, 7 map directly to US OFAC Sanctions Compliance Framework controls — representing 28% coverage. The remaining 18 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 OFAC Sanctions Compliance Framework?

18 AWS Well-Architected Security Pillar controls have no direct equivalent in US OFAC Sanctions Compliance Framework. The highest concentration of gaps is in AWS Well-Architected Security Pillar: Identity & Access in Cloud 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 OFAC Sanctions Compliance Framework?

The domain with the highest gap count is AWS Well-Architected Security Pillar: Identity & Access in Cloud (5 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.

Related Resources

How to Map Controls Across Frameworks|Multi-Framework Compliance Guide|Compliance Glossary

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.