[P2] [S3] Chapter 12
Testing and Validation of Impact Tolerances
Introduction
Defining impact tolerance is only meaningful if it can be demonstrated, tested, and validated in practice. Regulators increasingly expect organisations to provide evidence that they can operate within defined tolerances under disruption—not just document them.
Testing and validation transform impact tolerance from a theoretical threshold into a proven capability. Through structured exercises and scenario-based testing, organisations can measure actual performance, identify gaps, and refine both their tolerances and resilience strategies.
This chapter focuses on how to test and validate impact tolerances using practical approaches aligned with operational resilience implementation.
Purpose of the Chapter
The purpose of this chapter is to:
- Validate impact tolerances through structured testing and exercises
- Apply scenario testing aligned with Operational Resilience Phase 2 – Stage 4 (OR-P2-S4)
- Use tabletop and simulation exercises to test decision-making and response
- Conduct end-to-end CBS testing to assess real service resilience
- Measure actual performance against defined tolerance thresholds
Scenario Testing (OR-P2-S4)
Scenario testing is the primary mechanism for validating whether an organisation can remain within its defined impact tolerances.
Role of Scenario Testing
Scenario testing enables organisations to:
- Assess whether CBS can operate within tolerance under stress
- Identify weaknesses in dependencies and recovery strategies
- Validate assumptions made during tolerance setting
- Provide evidence for governance, audit, and regulatory review
Alignment with OR-P2-S4
Within the operational resilience methodology:
|
Stage |
Activity |
|
Identify CBS |
Define critical services |
|
Map Dependencies |
Understand supporting resources |
|
Set Impact Tolerance |
Define thresholds |
|
Scenario Testing (OR-P2-S4) |
Validate tolerances |
|
Improve |
Address identified gaps |
Scenario Design Principles
Effective scenario testing should:
- Be severe but plausible
- Reflect realistic operating conditions
- Test end-to-end service delivery
- Include multiple dependencies (technology, people, third parties)
- Simulate time-based escalation of impact
Tabletop and Simulation Exercises
Testing can be conducted at different levels of complexity and realism.
Tabletop Exercises
Tabletop exercises are discussion-based sessions where stakeholders walk through a disruption scenario.
Key Features:
- Facilitated workshops involving cross-functional teams
- Focus on decision-making, escalation, and coordination
- No live system disruption
Benefits:
- Low cost and easy to organise
- Effective for testing governance and communication
- Identifies gaps in roles, responsibilities, and procedures
Simulation Exercises
Simulation exercises are more advanced and may involve:
- Partial system testing
- Simulated data or transaction flows
- Real-time response activities
Key Features:
- Higher realism compared to tabletop
- Tests operational execution and response capability
- May include controlled disruption scenarios
Benefits:
- Provides more accurate validation of capabilities
- Tests both technical and operational resilience
Comparison
|
Exercise Type |
Focus |
Complexity |
Outcome |
|
Tabletop |
Decision-making and coordination |
Low |
Process and governance validation |
|
Simulation |
Operational and technical response |
Medium–High |
Capability validation |
CBS End-to-End Testing
End-to-end testing is critical to validating impact tolerance.
What is End-to-End Testing?
End-to-end testing evaluates the ability of the organisation to deliver a CBS across the full service chain, including:
- Front-end customer interaction
- Internal processing
- Technology systems
- Third-party dependencies
- Output delivery (e.g., transaction completion)
Why It Matters
Testing individual components is insufficient because:
- Failures often occur at integration points
- Dependencies are interconnected
- Recovery of one component does not guarantee service restoration
Example
For Payments and Funds Transfer Services, end-to-end testing may include:
- Payment initiation via digital channel
- Authentication and validation
- Routing through the payment gateway
- Clearing and settlement
- Customer notification
The test must confirm that the entire process can operate within impact tolerance thresholds.
Measuring Actual vs Defined Tolerance
Testing must include quantitative measurement of performance against defined tolerances.
Key Measurement Areas
|
Metric |
Description |
|
Downtime Duration |
Actual service outage vs MTD |
|
Data Loss |
Actual data loss vs MTDL |
|
Transaction Volume |
Number of failed or delayed transactions |
|
Service Capacity |
Percentage of normal operations maintained |
|
Customer Impact |
Number of customers affected |
|
Recovery Time |
Time taken to restore service |
Example Comparison
|
CBS |
Defined Tolerance |
Actual Outcome |
Result |
|
Deposit Services |
4 hours MTD |
3.5 hours recovery |
Within tolerance |
|
Payments Services |
2 hours MTD |
2.5 hours recovery |
Breach |
|
Digital Banking |
3 hours MTD |
2 hours recovery |
Within tolerance |
|
Clearing & Settlement |
1 hour MTD |
1.5 hours recovery |
Breach |
Interpretation
- Within tolerance: Capability validated
- Near tolerance: Risk identified, monitoring required
- Breach: Immediate remediation required
Identifying Gaps and Weaknesses
Testing reveals gaps that may not be visible during planning.
Common Gaps
|
Gap Type |
Example |
|
Technology |
Recovery time longer than expected |
|
Process |
Manual workaround insufficient |
|
People |
Lack of trained backup staff |
|
Third-Party |
Vendor recovery slower than the SLA |
|
Governance |
Delayed escalation or unclear roles |
Root Cause Analysis
Each gap should be analysed to determine:
- Why was the tolerance breached
- Whether assumptions were incorrect
- Whether dependencies were underestimated
- Whether controls are inadequate
Remediation and Improvement
Testing results must lead to actionable improvements.
Example Actions
|
Gap Identified |
Action |
|
System recovery delay |
Implement faster failover solutions |
|
Data recovery gap |
Increase backup frequency |
|
Third-party dependency risk |
Establish an alternate vendor |
|
Manual processing limitation |
Increase automation or staffing |
|
Escalation delay |
Improve incident response procedures |
Continuous Improvement Loop
Testing feeds into a continuous improvement cycle:
- Define impact tolerance
- Test through scenarios
- Measure outcomes
- Identify gaps
- Implement improvements
- Re-test and refine
Governance and Reporting
Testing and validation must be supported by strong governance.
Reporting Requirements
- Test objectives and scope
- Scenario description
- Results vs defined tolerances
- Identified gaps
- Remediation actions
- Timeline and ownership
Escalation
- Breaches must be reported to Senior Management
- Critical issues may require Board-level visibility
- Regulatory reporting may be required in certain cases
Common Challenges
|
Challenge |
Description |
|
Limited scope |
Testing only individual components |
|
Unrealistic scenarios |
Fails to reflect real conditions |
|
Lack of measurement |
Inability to quantify outcomes |
|
Siloed testing |
Lack of cross-functional coordination |
|
Insufficient follow-up |
Gaps identified but not addressed |
Best Practices
- Test end-to-end CBS, not isolated systems
- Use severe but plausible scenarios
- Combine tabletop and simulation exercises
- Measure performance using quantitative metrics
- Involve cross-functional stakeholders
- Document results and maintain audit evidence
- Integrate testing into regular resilience programs
Testing and validation are critical to ensuring that impact tolerances are credible, achievable, and aligned with real-world conditions. Through structured scenario testing, tabletop exercises, simulation activities, and end-to-end CBS validation, organisations can assess whether they can truly operate within defined thresholds.
By measuring actual performance against defined tolerances, organisations gain valuable insights into their resilience capabilities, identify weaknesses, and drive continuous improvement. This process not only strengthens operational resilience but also provides the evidence required to satisfy regulatory expectations.
Ultimately, testing transforms impact tolerance from a static definition into a living, validated capability, ensuring that organisations are prepared to manage disruption effectively and maintain critical services within acceptable limits.





![[OR] [P2] [S3] [ITo] [C12] Testing and Validation of Impact Tolerances](https://no-cache.hubspot.com/cta/default/3893111/9a9cb7eb-1ca3-4790-b39e-f6b0035a1eae.png)
![Banner [Summing] [OR] [E3] Establish Impact Tolerance](https://no-cache.hubspot.com/cta/default/3893111/5e80e50f-5e3e-44ea-8c43-16bf42d4f3b5.png)

![[OR] [P2] [S3] [ITo] [C1] Introduction to Impact Tolerance](https://no-cache.hubspot.com/cta/default/3893111/a2d06a13-c2ac-4e0a-b8ea-c5afcab91844.png)
![[OR] [P2] [S3] [ITo] [C2] Regulatory and Standards Landscape](https://no-cache.hubspot.com/cta/default/3893111/04df8f17-629c-458f-af01-67e3da528b63.png)
![[OR] [P2] [S3] [ITo] [C3] Understanding Impact Tolerance in Context](https://no-cache.hubspot.com/cta/default/3893111/ea66bac0-7b34-4d56-9c93-c33c8f7964bc.png)
![[OR] [P2] [S3] [ITo] [C4] Linking Impact Tolerance to Critical Business Services (CBS)](https://no-cache.hubspot.com/cta/default/3893111/24ceb290-50c2-4af4-be00-41894f00c7cb.png)
![[OR] [P2] [S3] [ITo] [C5] Key Components of Impact Tolerance](https://no-cache.hubspot.com/cta/default/3893111/6e9d8a15-c0a3-4e28-b9a4-c2dcc3e2081e.png)
![[OR] [P2] [S3] [ITo] [C6] Methodology for Setting Impact Tolerance](https://no-cache.hubspot.com/cta/default/3893111/77526e47-fc15-4c7b-bf03-cadd672b40db.png)
![[OR] [P2] [S3] [ITo] [C7] Impact Tolerance Assessment Framework](https://no-cache.hubspot.com/cta/default/3893111/abf28462-aba4-4970-81be-55cf66dc6147.png)
![[OR] [P2] [S3] [ITo] [C8] Scenario-Based Calibration of Impact Tolerance](https://no-cache.hubspot.com/cta/default/3893111/23b3a54d-37ce-494b-acb1-33b3cc5e1655.png)
![[OR] [P2] [S3] [ITo] [C9] Role of Dependency Mapping in Impact Tolerance](https://no-cache.hubspot.com/cta/default/3893111/d35fd8b0-e936-4ab3-9706-4366bfcb8cbe.png)
![[OR] [P2] [S3] [ITo] [C10] Governance, Ownership, and Accountability](https://no-cache.hubspot.com/cta/default/3893111/de12fefd-b6c6-4156-83a9-5d19ca5bc508.png)
![[OR] [P2] [S3] [ITo] [C11] Integration with Operational Resilience Framework](https://no-cache.hubspot.com/cta/default/3893111/84d3d3c4-0647-4ffd-99b4-a20a12526019.png)
![[OR] [P2] [S3] [ITo] [C13] Monitoring, Metrics, and Continuous Improvement](https://no-cache.hubspot.com/cta/default/3893111/1a32f981-3a16-427a-a63f-5a40ab93ea21.png)
![[OR] [P2] [S3] [ITo] [C14] Common Challenges and Pitfalls](https://no-cache.hubspot.com/cta/default/3893111/8831463d-a357-4203-806b-fb31ef71d615.png)
![[OR] [P2] [S3] [ITo] [C15] Practical Case Study (Banking Sector Example)](https://no-cache.hubspot.com/cta/default/3893111/fef15761-14c6-4e2b-b157-554cceb33d14.png)
![[OR] [P2] [S3] [ITo] [C16] Future Trends in Impact Tolerance](https://no-cache.hubspot.com/cta/default/3893111/b6a701db-167e-4630-88ad-de0d43deb322.png)
![[OR] [P2] [S3] [ITo] [C17] Key Takeaways and Call to Action](https://no-cache.hubspot.com/cta/default/3893111/bf49e0c2-33a3-48bc-97d2-eb939aed77bd.png)
![[OR] [P2] [S3] [ITo] [C18] Back Cover](https://no-cache.hubspot.com/cta/default/3893111/3623335d-0b26-4ee7-afbf-0d431358b390.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)









