TheArtOfService
Cross-Framework Mapping

API 1164vsOpen Banking Security

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

19
Controls Mapped
5
Gaps Found
29%
Coverage

According to the TheArtOfService Compliance Knowledge Graph:

API 1164 maps to Open Banking Security with 29% coverage across 13 directly mapped controls. Analysis of 24 API 1164 controls identifies 32 compliance gaps — primarily concentrated in API 1164: Access Management.

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

Control Mappings

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

Resilience(1 mappings)

API1164-13Business Continuity and Recovery
→OPENBANK-3Mutual TLS, Token Binding, Request Signing (JWS), Key Management

API 1164: Systems Security(2 mappings)

API1164-13Business Continuity and Recovery
→OPENBANK-3Mutual TLS, Token Binding, Request Signing (JWS), Key Management
API1164-14Physical Security
→OPENBANK-3Mutual TLS, Token Binding, Request Signing (JWS), Key Management

Physical(1 mappings)

API1164-14Physical Security
→OPENBANK-3Mutual TLS, Token Binding, Request Signing (JWS), Key Management

Communications(2 mappings)

API1164-17Wireless and Field Communications2 targets
→OPENBANK-7Logging, Monitoring, Regulatory Reporting, SLA, Availability
→OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

API 1164: Incident Response & Recovery(6 mappings)

API1164-17Wireless and Field Communications2 targets
→OPENBANK-7Logging, Monitoring, Regulatory Reporting, SLA, Availability
→OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM
API1164-18Field Device Security2 targets
→OPENBANK-7Logging, Monitoring, Regulatory Reporting, SLA, Availability
→OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM
API1164-19Safety Instrumented Systems Interface2 targets
→OPENBANK-7Logging, Monitoring, Regulatory Reporting, SLA, Availability
→OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

Endpoint(2 mappings)

API1164-18Field Device Security2 targets
→OPENBANK-7Logging, Monitoring, Regulatory Reporting, SLA, Availability
→OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

Safety(2 mappings)

API1164-19Safety Instrumented Systems Interface2 targets
→OPENBANK-7Logging, Monitoring, Regulatory Reporting, SLA, Availability
→OPENBANK-8Incident Detection, Response, Customer Notification, Post-Incident Review, BCM

Regulatory(1 mappings)

API1164-21TSA Pipeline Security Directive Alignment
→OPENBANK-4Third Party Provider (TPP) Onboarding, Directory Integration, Due Diligence

API 1164: Supply Chain & Configuration(2 mappings)

API1164-21TSA Pipeline Security Directive Alignment
→OPENBANK-4Third Party Provider (TPP) Onboarding, Directory Integration, Due Diligence
API1164-22Configuration management for OT systems
→OPENBANK-3Mutual TLS, Token Binding, Request Signing (JWS), Key Management

Related Comparisons

Other API 1164 comparisons

API 1164 vs NIST SP 800-53 Rev 522 mappingsAPI 1164 vs NIST SP 800-82 Revision 3: Guide to Industrial Control Systems (ICS) Security17 mappingsAPI 1164 vs NIS2 Directive16 mappingsAPI 1164 vs IEEE 168616 mappingsAPI 1164 vs IEC 6244316 mappingsAPI 1164 vs NIST SP 1800-3216 mappingsAPI 1164 vs ISO 2701916 mappingsAPI 1164 vs CISA Cross-Sector Cybersecurity Performance Goals (CPG) 2.013 mappings

Other Open Banking Security comparisons

NIST Cybersecurity Framework 2.0 vs Open Banking Security5 mappingsAPRA CPS 234 vs Open Banking Security5 mappingsFFIEC IT Examination Handbook vs Open Banking Security5 mappingsNIST SP 800-171A Rev 3 - Assessing CUI Security Requirements vs Open Banking Security5 mappingsAnnex 11 to EU GMP - Computerised Systems vs Open Banking Security5 mappingsNIST AI Risk Management Framework (AI RMF 1.0) vs Open Banking Security5 mappingsISO 28001:2007 Supply Chain Security Management vs Open Banking Security5 mappingsISO 27019 vs Open Banking Security4 mappings

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 →

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 API 1164 and Open Banking Security?

API 1164 has 24 controls across its framework, while Open Banking Security covers 8 controls. Direct mapping analysis identifies 13 overlapping controls (29% coverage). The frameworks diverge most significantly in API 1164: Access Management, where 5 API 1164 controls have no direct Open Banking Security equivalent.

How many controls map between API 1164 and Open Banking Security?

Of 24 total API 1164 controls, 13 map directly to Open Banking Security controls — representing 29% coverage. The remaining 32 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.

What are the compliance gaps when mapping API 1164 to Open Banking Security?

32 API 1164 controls have no direct equivalent in Open Banking Security. The highest concentration of gaps is in API 1164: Access 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 API 1164 and Open Banking Security?

The domain with the highest gap count is API 1164: Access Management (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.