Open Banking Security
Open Banking Implementation Entity security profile
Framework summaries on this platform are AI-assisted interpretations for educational and compliance planning purposes. They do not reproduce or replace the official standards. Refer to the authoritative source for the definitive text. Framework names and trademarks belong to their respective organisations.
Framework Domains (5)
Open Banking Security: Cybersecurity Controls
Technical cybersecurity measures (Open Banking Security)
| Code | Title |
|---|---|
| OBIE-06 | Network security and segmentation |
| OBIE-07 | Endpoint protection and detection |
| OBIE-08 | Application security controls |
| OBIE-09 | Encryption and key management |
| OBIE-10 | Secure configuration standards |
Open Banking Security: Incident Management & Reporting
Incident handling for financial services (Open Banking Security)
| Code | Title |
|---|---|
| OBIE-21 | Incident detection and classification |
| OBIE-22 | Incident response and containment |
| OBIE-23 | Regulatory reporting requirements |
| OBIE-24 | Customer notification procedures |
| OBIE-25 | Post-incident review and improvement |
Open Banking Security: Information Security Governance
IT governance for financial institutions (Open Banking Security)
| Code | Title |
|---|---|
| OBIE-01 | Information security program management |
| OBIE-02 | Board and management oversight |
| OBIE-03 | Risk appetite and tolerance for IT risk |
| OBIE-04 | Security policy framework |
| OBIE-05 | Roles and responsibilities definition |
Open Banking Security: Operational Resilience
Business continuity and resilience (Open Banking Security)
| Code | Title |
|---|---|
| OBIE-11 | Business continuity planning and testing |
| OBIE-12 | Disaster recovery procedures |
| OBIE-13 | Third-party dependency management |
| OBIE-14 | Critical service identification |
| OBIE-15 | Communication and escalation procedures |
Open Banking Security: Third-Party Risk Management
Managing vendor and supplier risks (Open Banking Security)
| Code | Title |
|---|---|
| OBIE-16 | Due diligence and onboarding |
| OBIE-17 | Contractual security requirements |
| OBIE-18 | Ongoing monitoring and assessment |
| OBIE-19 | Concentration risk management |
| OBIE-20 | Exit strategy and transition planning |
Maps to 606 other frameworks
Frequently Asked Questions
What is Open Banking Security?
Open Banking Security is a compliance framework from United Kingdom with 5 domains and 25 controls. Open Banking Implementation Entity security profile It is used by organisations to establish and maintain compliance with industry standards and regulatory requirements.
How many controls does Open Banking Security have?
Open Banking Security has 25 controls organised across 5 domains. The largest domains are Open Banking Security: Cybersecurity Controls (5 controls), Open Banking Security: Incident Management & Reporting (5 controls), Open Banking Security: Information Security Governance (5 controls). Each control defines specific requirements that organisations must implement to achieve compliance.
What frameworks does Open Banking Security map to?
Open Banking Security maps to 606 other compliance frameworks. The top mapping partners are APRA CPS 234 (64% coverage), GLBA (64% coverage), DORA (64% coverage). Use our comparison tool to explore control-level mappings between frameworks.
How do I get started with Open Banking Security compliance?
Start your Open Banking Security compliance journey by running a self-assessment on our platform to identify your current compliance posture. Our AI advisory can answer specific questions about Open Banking Security requirements, and cross-framework mapping helps you leverage existing controls from other frameworks you may already comply with. Create a free account to access all 25 controls and track your progress.
Start Your Compliance Journey
Create a free account to run self-assessments, get AI advisory, and track your compliance progress across 692 frameworks.
Get Started Free →Free forever — no credit card required