TheArtOfService
Cross-Framework Mapping

AWS Well-Architected Security PillarvsOpen Banking Security

See exactly how AWS Well-Architected Security Pillar controls map to Open Banking Security. 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 Open Banking Security 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 4 domains. Sign up to explore all 819K+ mappings across 693 frameworks.

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

AWS-WA-01Shared responsibility model definition
→OBIE-05Roles and responsibilities definition

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

AWS-WA-12Encryption of cloud-stored data
→OBIE-09Encryption and key management
AWS-WA-14Data backup and recovery in cloud
→OBIE-12Disaster recovery procedures

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

AWS-WA-16Virtual network segmentation
→OBIE-06Network security and segmentation
AWS-WA-19Image and template hardening
→OBIE-10Secure configuration standards
AWS-WA-20Cloud configuration management
→OBIE-10Secure configuration standards

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

AWS-WA-22Incident response in cloud3 targets
→OBIE-22Incident response and containment
→OBIE-23Regulatory reporting requirements
→OBIE-25Post-incident review and improvement

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 Open Banking Security comparisons

APRA CPS 234 vs Open Banking Security16 mappingsGLBA vs Open Banking Security16 mappingsDORA vs Open Banking Security16 mappingsHKMA SPM vs Open Banking Security16 mappingsFFIEC IT Examination Handbook vs Open Banking Security16 mappingsBCBS 239 vs Open Banking Security16 mappingsMAS TRM vs Open Banking Security16 mappingsSWIFT CSP vs Open Banking Security16 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 Open Banking Security?

AWS Well-Architected Security Pillar has 25 controls across its framework, while Open Banking Security covers 25 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 Open Banking Security equivalent.

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

Of 25 total AWS Well-Architected Security Pillar controls, 7 map directly to Open Banking Security 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 Open Banking Security?

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

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.