Cross-Framework Mapping

AWS Well-Architected Security PillarvsCFTC System Safeguards (17 CFR 37, 38, 39, 49)

See exactly how AWS Well-Architected Security Pillar controls map to CFTC System Safeguards (17 CFR 37, 38, 39, 49). Pre-computed mappings, identified gaps, and coverage analysis.

22
Controls Mapped
3
Gaps Found
40%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

AWS Well-Architected Security Pillar maps to CFTC System Safeguards (17 CFR 37, 38, 39, 49) with 40% coverage across 10 directly mapped controls. Analysis of 25 AWS Well-Architected Security Pillar controls identifies 15 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 20 of 22 mapped controls across 3 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

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

AWS-WA-01Shared responsibility model definition2 targets
38.1051(c)(1)Recovery Time Objectives
EIOPA-GL-10ICT Operations Security
AWS-WA-03Cloud risk assessment3 targets
38.1051(a)General Security Requirements for DCMs
38.1051(h)(5)Enterprise Technology Risk Assessment
39.18(a)General Security Requirements for DCOs

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

AWS-WA-11Data classification for cloud
DSPF-INFO-1Information Classification
AWS-WA-12Encryption of cloud-stored data3 targets
GLI33-4.3Data Protection and Encryption
TISAX-IS-01ISMS Requirements
TSSR-INFO-1Network Data Protection
AWS-WA-14Data backup and recovery in cloud5 targets
38.1051(c)BC-DR Planning
38.1051(c)(1)Recovery Time Objectives
38.1051(c)(2)Geographic Separation of Backup
GLI33-4.3Data Protection and Encryption
TSSR-INFO-1Network Data Protection
AWS-WA-15Secure data deletion in cloud2 targets
GLI33-4.3Data Protection and Encryption
TSSR-INFO-1Network Data Protection

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

AWS-WA-21Cloud security monitoring and logging2 targets
EIOPA-GL-11Security Monitoring
GLI33-4.4Audit Trail and Logging
AWS-WA-22Incident response in cloud
38.1051(h)(4)Security Incident Response Plan Testing
AWS-WA-23Cloud vulnerability management
38.1051(h)(2)Penetration Testing

+2 more mappings

Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 693 frameworks.

Create Free Account →

Free forever — no credit card required

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 →

What are the key differences between AWS Well-Architected Security Pillar and CFTC System Safeguards (17 CFR 37, 38, 39, 49)?

AWS Well-Architected Security Pillar has 25 controls across its framework, while CFTC System Safeguards (17 CFR 37, 38, 39, 49) covers 49 controls. Direct mapping analysis identifies 10 overlapping controls (40% 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 CFTC System Safeguards (17 CFR 37, 38, 39, 49) equivalent.

How many controls map between AWS Well-Architected Security Pillar and CFTC System Safeguards (17 CFR 37, 38, 39, 49)?

Of 25 total AWS Well-Architected Security Pillar controls, 10 map directly to CFTC System Safeguards (17 CFR 37, 38, 39, 49) controls — representing 40% coverage. The remaining 15 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 CFTC System Safeguards (17 CFR 37, 38, 39, 49)?

15 AWS Well-Architected Security Pillar controls have no direct equivalent in CFTC System Safeguards (17 CFR 37, 38, 39, 49). 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 CFTC System Safeguards (17 CFR 37, 38, 39, 49)?

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.

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.