[OR] [Pillar] [E4] [C6] Scenario Testing for Third-Party Failures

eBook 4: Chapter 6

Scenario Testing for Third-Party Failures

Introduction

As organisations become increasingly dependent on third parties, the ability to withstand and recover from third-party failures becomes a defining element of Operational Resilience.

Scenario testing is a critical tool that enables financial institutions to simulate disruptions and assess whether their Critical Business Services (CBS) can continue operating within defined impact tolerances.

Regulators such as the Bangko Sentral ng Pilipinas (BSP) and Bank Negara Malaysia (BNM) require financial institutions to conduct severe but plausible scenario testing, including scenarios involving third-party failures.

These tests must validate whether the organisation can continue to deliver essential services despite disruptions to outsourced or externally supported operations.

Purpose of This Chapter

This chapter provides structured approaches and CBS-aligned templates for conducting scenario testing focused on third-party failures. By the end of this chapter, readers will:

• Understand the role of scenario testing in TPRM and Operational Resilience
• Develop third-party failure scenarios aligned to CBS
• Use standardised templates for scenario testing
• Evaluate resilience against impact tolerances (MTD, MTDL)
• Strengthen recovery and response strategies

Types of Third-Party Failure Scenarios

Third-party failure scenarios should reflect realistic and severe disruptions, including:

• Vendor system outage (cloud, core banking, payment gateway)
• Cyberattack on third-party provider
• Third-party financial failure or insolvency
• Supply chain disruption (fourth-party failure)
• Data breach or data loss
• Service performance degradation
• Regulatory non-compliance by the vendor

Scenario Testing Framework

Key Components of Scenario Testing

Section 1: CBS-Level Scenario Testing Table

Template: Scenario Testing for CBS (High-Level)

Example: CBS-1 Deposit and Account Services

Section 2: Sub-CBS Scenario Testing (Detailed Processes)

Template: Scenario Testing for Sub-CBS

Example: CBS-1 Detailed Processes

Section 3: Severe but Plausible Scenarios

Template: Severe Scenario Testing

Example Scenarios

Section 4: Scenario Testing Evaluation Template

Template: Test Results and Evaluation

Example

Section 5: Integration with Operational Resilience

Mapping Scenario Testing to OR Framework

Section 6: Best Practices for Scenario Testing

1. Use Severe but Plausible Scenarios

Focus on realistic disruptions with significant impact.

2. Include Third and Fourth Parties

Test extended supply chain dependencies.

3. Align with Impact Tolerance

Validate against MTD and MTDL thresholds.

4. Conduct Regular Testing

At least annually for critical vendors.

5. Involve Cross-Functional Teams

Include IT, Risk, Business Units, and Vendors.

6. Capture Lessons Learned

Continuously improve resilience strategies.

Section 7: Implementation Roadmap

Step-by-Step Approach

Key Takeaways

• Scenario testing validates real-world resilience capability
• Third-party failures must be explicitly tested
• CBS alignment ensures business-focused resilience
• Severe scenarios reveal hidden vulnerabilities
• Continuous testing improves preparedness and response

Scenario testing is a critical component of Third-Party Risk Management and Operational Resilience. It transforms theoretical risk assessments into practical insights by simulating real-world disruptions and evaluating organisational readiness.

By aligning scenario testing with Critical Business Services and incorporating third-party failure scenarios, financial institutions can ensure that they are prepared not only for internal disruptions but also for failures across their extended ecosystem.

This capability is essential for meeting regulatory expectations under BSP Circular No. 1203 and BNM guidelines, and for maintaining customer trust and service continuity in an increasingly interconnected world.