[P2] [S2] Chapter 17
Case Study – Banking Sector CBS Mapping
Introduction

To translate theory into practice, this chapter presents a banking sector case study illustrating how to map interconnections and interdependencies for Critical Business Services (CBS). The objective is to demonstrate how mapping moves from high-level identification to end-to-end dependency visibility, enabling actionable operational resilience outcomes.![[OR] [P2] [S2] [MII] [C17] Case Study – Banking Sector CBS Mapping](https://no-cache.hubspot.com/cta/default/3893111/5a846fed-f810-4f6b-a1d8-0c2100f0eeac.png)
The case study focuses on two commonly identified CBS in banks:
- CBS-1: Deposit & Account Services
- CBS-2: Payments & Funds Transfer Services
These services are foundational to banking operations and are typically prioritised by regulators and institutions due to their customer impact, systemic importance, and regulatory significance.
Purpose of the Chapter
The purpose of this chapter is to:
- Provide a practical illustration of CBS mapping
- Demonstrate end-to-end dependency mapping
- Show how interconnections span people, processes, technology, and third parties
- Highlight how mapping supports operational resilience analysis
Overview of Selected CBS
CBS-1: Deposit & Account Services
This CBS includes services related to:
- Customer onboarding and account opening
- Deposit and withdrawal transactions
- Account maintenance and servicing
- Balance reporting and statements
Key Characteristics:
- High customer dependency
- Continuous availability expectations
- Regulatory reporting requirements
CBS-2: Payments & Funds Transfer Services
This CBS includes services related to:
- Domestic and cross-border payments
- Fund transfers between accounts
- Bill payments and standing instructions
- Clearing and settlement processes
Key Characteristics:
- Time-critical processing
- Integration with external payment networks
- High systemic importance
End-to-End Mapping Approach
For both CBS, mapping follows an end-to-end service delivery approach, covering:
- Service initiation
- Processing and validation
- Execution and settlement
- Completion and reporting
Each stage is supported by:
- Processes
- People
- Technology
- Data
- Third-party providers
CBS-1: Deposit & Account Services – Dependency Mapping
Sub-CBS Structure
|
Sub-CBS Code |
Sub-CBS |
|
1.1 |
Customer Onboarding & Account Application |
|
1.2 |
Customer Identification & Verification (KYC/CDD) |
|
1.3 |
Account Approval & Opening |
|
1.4 |
Deposit Transactions Processing |
|
1.5 |
Withdrawal & Funds Access Processing |
|
1.6 |
Account Servicing & Maintenance |
|
1.7 |
Statement & Balance Reporting |
Sample Dependency Mapping
|
Sub-CBS |
Dependency Type |
Dependency Detail |
Connectivity |
|
Customer Onboarding |
Process |
Customer data collection workflow |
Initiates onboarding process |
|
KYC Verification |
Technology |
KYC System |
Validates customer identity via API |
|
Account Opening |
People |
Operations Officer |
Approves and activates account |
|
Deposit Processing |
Technology |
Core Banking System |
Processes deposit transactions |
|
Withdrawal Processing |
Third Party |
ATM Network |
Enables cash withdrawal |
|
Account Servicing |
Data |
Customer Database |
Supports updates and maintenance |
|
Reporting |
Technology |
Reporting System |
Generates statements |
Key Observations
- Heavy reliance on core banking systems (shared dependency)
- Integration with external networks (ATM, KYC providers)
- Sequential dependencies across onboarding → approval → activation
- Potential concentration risk in centralised systems and data platforms
CBS-2: Payments & Funds Transfer – Dependency Mapping
Sub-CBS Structure
|
Sub-CBS Code |
Sub-CBS |
|
2.1 |
Payment Initiation |
|
2.2 |
Authentication & Authorisation |
|
2.3 |
Fraud Detection & Risk Screening |
|
2.4 |
Funds Availability Check |
|
2.5 |
Payment Routing & Processing |
|
2.6 |
Clearing & Settlement |
|
2.7 |
Transaction Posting & Notification |
Sample Dependency Mapping
|
Sub-CBS |
Dependency Type |
Dependency Detail |
Connectivity |
|
Payment Initiation |
Technology |
Mobile Banking App |
Captures customer request |
|
Authentication |
Technology |
Authentication System |
Verifies user identity |
|
Fraud Screening |
Technology |
Fraud Detection Engine |
Screens transactions |
|
Funds Check |
Data |
Account Balance Database |
Validates funds availability |
|
Payment Processing |
Technology |
Payment Engine |
Executes transactions |
|
Clearing & Settlement |
Third Party |
Payment Network |
Processes interbank settlement |
|
Notification |
Technology |
Notification System |
Sends transaction alerts |
Key Observations
- Strong reliance on external payment networks (external dependency)
- Multiple real-time system integrations (API connectivity)
- Sequential dependencies with high time sensitivity
- Concentration risk in authentication and payment processing systems
End-to-End Interdependency Illustration
Combined Dependency Flow
An example of end-to-end interconnection for a payment transaction:
- Customer initiates payment via mobile app
- Authentication system verifies identity
- Fraud detection engine screens transaction
- Core banking system checks funds
- Payment engine processes transaction
- External payment network performs clearing
- Settlement occurs between banks
- Notification system confirms transaction
Interdependency Characteristics
- Sequential Dependencies: Each step must occur in order
- Shared Dependencies: Core banking and authentication systems support multiple CBS
- External Dependencies: Payment networks and third-party providers
- Data Dependencies: Continuous data flow across systems
Key Risks Identified
Single Points of Failure
- Core banking system
- Authentication platform
Critical Dependencies
- Payment processing engine
- KYC system
- Customer database
Concentration Risks
- Single cloud or infrastructure provider
- Centralised data centres
- Shared third-party vendors
Link to Operational Resilience
Impact Tolerance
- Mapping identifies critical points affecting downtime thresholds
- Helps define acceptable disruption levels
Scenario Testing
- Enables design of realistic scenarios such as:
- Payment network outage
- Core banking system failure
- Cyberattack on authentication systems
Recovery Planning
- Supports prioritisation of recovery actions
- Ensures restoration of end-to-end service delivery
Lessons Learned
1. Service-Centric Mapping is Critical
Focusing on CBS ensures alignment with customer outcomes and regulatory expectations.
2. Interdependencies are Complex and Multi-Layered
Dependencies span across internal systems, external providers, and data flows.
3. External Dependencies Drive Risk Exposure
Third-party and ecosystem dependencies significantly influence resilience.
4. Mapping Enables Actionable Insights
Identifies vulnerabilities, concentration risks, and recovery priorities.
This case study demonstrates how interconnection and interdependency mapping can be applied in a banking context to provide end-to-end visibility of Critical Business Services.
By mapping:
- CBS-1: Deposit & Account Services
- CBS-2: Payments & Funds Transfer Services
organisations can clearly understand how services are delivered, where dependencies exist, and how disruptions may propagate.
The outcome is a comprehensive and actionable view of operational resilience, enabling:
- Better risk identification
- More effective scenario testing
- Stronger recovery planning
Ultimately, this practical illustration reinforces the central theme of this eBook—moving from complexity to clarity, ensuring that interconnections and interdependencies are not only mapped, but fully understood and effectively managed.








![[OR] [P2] [S2] [MII] [C1] Introduction to Interconnections and Interdependencies](https://no-cache.hubspot.com/cta/default/3893111/8cbaf41b-9671-404d-83b3-9a20c9fd69f7.png)
![[OR] [P2] [S2] [MII] [C2] Why Mapping is Critical for Operational Resilience](https://no-cache.hubspot.com/cta/default/3893111/a7625fb5-1205-4fc5-97d4-4b7492c2b25f.png)
![[OR] [P2] [S2] [MII] [C3] Core Components of Interconnections and Dependencies](https://no-cache.hubspot.com/cta/default/3893111/38a3cbd4-322a-41bd-974f-5090a2ce52aa.png)
![[OR] [P2] [S2] [MII] [C4] Step 1 – Define Scope of Mapping](https://no-cache.hubspot.com/cta/default/3893111/69cc922b-c86c-4242-b85b-315a3f941e12.png)
![[OR] [P2] [S2] [MII] [C5] Step 2- Identify Data Sources](https://no-cache.hubspot.com/cta/default/3893111/622d0fcc-71bf-4c3b-a569-213cb48bd1db.png)
![[OR] [P2] [S2] [MII] [C6] Step 3 – Develop Mapping Framework](https://no-cache.hubspot.com/cta/default/3893111/95581d69-3824-4acd-accf-03c2cab43765.png)
![[OR] [P2] [S2] [MII] [C7] Step 4 – Map Processes and Resources](https://no-cache.hubspot.com/cta/default/3893111/a4ffedf2-c795-41e9-9a8b-c5e24eea7159.png)
![[OR] [P2] [S2] [MII] [C8] Step 5 – Map Interconnections and Interdependencies](https://no-cache.hubspot.com/cta/default/3893111/10f06848-f21f-457d-aa80-ca4e3b20ce9e.png)
![[OR] [P2] [S2] [MII] [C9] Step 6 – Validate Mapping](https://no-cache.hubspot.com/cta/default/3893111/57d7a65a-a462-4919-9324-53e0bb207f3e.png)
![[OR] [P2] [S2] [MII] [C10] Step 7 – Analyse Mapping Outputs](https://no-cache.hubspot.com/cta/default/3893111/44bbb252-fdf5-4026-90ba-cbbdbe9c099a.png)
![[OR] [P2] [S2] [MII] [C11] Mapping Tools and Techniques](https://no-cache.hubspot.com/cta/default/3893111/d2fab757-0d78-42dd-8553-044eead7390e.png)
![[OR] [P2] [S2] [MII] [C12] Standard Templates and Data Structures](https://no-cache.hubspot.com/cta/default/3893111/4f04214c-3a0f-4bed-b2f8-6352c6d3cda0.png)
![[OR] [P2] [S2] [MII] [C13] Integration with Operational Resilience Framework](https://no-cache.hubspot.com/cta/default/3893111/c9628dd2-bbcb-4b54-b5b5-490066640d6d.png)
![[OR] [P2] [S2] [MII] [C14] Mapping Third-Party and Supply Chain Dependencies](https://no-cache.hubspot.com/cta/default/3893111/0c13b720-3d3e-4452-91e4-b9533260b3a4.png)
![[OR] [P2] [S2] [MII] [C15] Mapping for Digital and Cloud Environments](https://no-cache.hubspot.com/cta/default/3893111/1c90de74-af6b-44d3-ae4f-26d01eac3cf7.png)
![[OR] [P2] [S2] [MII] [C16] Common Challenges and Pitfalls](https://no-cache.hubspot.com/cta/default/3893111/32bbd8d7-f947-42ac-9db9-b88b0b156813.png)
![[OR] [P2] [S2] [MII] [C18] Governance and Ownership of Mapping](https://no-cache.hubspot.com/cta/default/3893111/44ed11f0-5263-4485-98db-725a423c5fd6.png)
![[OR] [P2] [S2] [MII] [C19] Using Mapping for Scenario Testing](https://no-cache.hubspot.com/cta/default/3893111/b7bf0bc8-b382-4892-821d-c7c867303f14.png)
![[OR] [P2] [S2] [MII] [C20] Maintaining and Updating Mapping](https://no-cache.hubspot.com/cta/default/3893111/41d34d1f-78bd-4346-845e-b0b86232cfa6.png)
![[OR] [P2] [S2] [MII] [C21] Key Takeaways and Future Direction](https://no-cache.hubspot.com/cta/default/3893111/d8414f6b-4b4e-4a50-adb3-963546f13951.png)
![[OR] [P2] [S2] [MII] [C22] Back Cover](https://no-cache.hubspot.com/cta/default/3893111/0f96fecf-9a98-4404-8377-d37c1233df10.png)





![[BL-OR] [3-4-5] View Schedule](https://no-cache.hubspot.com/cta/default/3893111/d0d733a1-16c0-4b68-a26d-adbfd4fc6069.png)
![[BL-OR] [3] FAQ OR-300](https://no-cache.hubspot.com/cta/default/3893111/f20c71b4-f5e8-4aa5-8056-c374ca33a091.png)
![Email to Sales Team [BCM Institute]](https://no-cache.hubspot.com/cta/default/3893111/3c53daeb-2836-4843-b0e0-645baee2ab9e.png)









