Cross-Framework Mapping

Azure Security BenchmarkvsOpen Banking Security

See exactly how Azure Security Benchmark controls map to Open Banking Security. Pre-computed mappings, identified gaps, and coverage analysis.

8
Controls Mapped
46
Gaps Found
13%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

Azure Security Benchmark maps to Open Banking Security with 13% coverage across 7 directly mapped controls. Analysis of 54 Azure Security Benchmark controls identifies 47 compliance gaps — primarily concentrated in Identity Management.

Source: TheArtOfService Knowledge Graph | 54 controls analysed | 718 frameworks | 332K+ cross-framework mappings

Control Mappings

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

Azure Security Benchmark: Cloud Governance(1 mappings)

ASB-01Shared responsibility model definition
OPENBANK-2Strong Customer Authentication (SCA), Consent Lifecycle, and Customer UX

Azure Security Benchmark: Data Protection in Cloud(2 mappings)

ASB-12Encryption of cloud-stored data
OPENBANK-3Mutual TLS, Token Binding, Request Signing (JWS), Key Management
ASB-14Data backup and recovery in cloud
OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

Azure Security Benchmark: Cloud Infrastructure Security(3 mappings)

ASB-16Virtual network segmentation
OPENBANK-3Mutual TLS, Token Binding, Request Signing (JWS), Key Management
ASB-19Image and template hardening
OPENBANK-3Mutual TLS, Token Binding, Request Signing (JWS), Key Management
ASB-20Cloud configuration management
OPENBANK-3Mutual TLS, Token Binding, Request Signing (JWS), Key Management

Azure Security Benchmark: Cloud Operations & Monitoring(2 mappings)

ASB-22Incident response in cloud2 targets
OPENBANK-7Logging, Monitoring, Regulatory Reporting, SLA, Availability
OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

Stop Paying Consultants to Read Spreadsheets

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

$0/forever

Free

  • 718 framework browser
  • Cross-framework mappings (332K+)
  • 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 Azure Security Benchmark and Open Banking Security?

Azure Security Benchmark has 54 controls across its framework, while Open Banking Security covers 8 controls. Direct mapping analysis identifies 7 overlapping controls (13% coverage). The frameworks diverge most significantly in Identity Management, where 5 Azure Security Benchmark controls have no direct Open Banking Security equivalent.

How many controls map between Azure Security Benchmark and Open Banking Security?

Of 54 total Azure Security Benchmark controls, 7 map directly to Open Banking Security controls — representing 13% coverage. The remaining 47 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping Azure Security Benchmark to Open Banking Security?

47 Azure Security Benchmark controls have no direct equivalent in Open Banking Security. The highest concentration of gaps is in Identity Management 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 Azure Security Benchmark and Open Banking Security?

The domain with the highest gap count is Identity Management (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.