2nd Line of Defence — Operational Resilience

Operational Resilience
Toolkit

A framework for mapping critical functions, testing resilience against severe-but-plausible scenarios, and scoring maturity across DORA, FINMA, PRA and BCBS.

Built by Saranne Ndamba · LinkedIn · GitHub
Critical Functions
5
Dependencies Mapped
21
Single Points of Failure
3
Concentration Risks
2
DORA Maturity
2.5/5.0
Tolerance Coverage
100%
⚠️ Top Risks
RiskTypeImpactStatus
Core Banking SystemSPOFAll 5 critical functionsCritical
Cloud Provider A (AWS)Concentration4 critical functionsHigh
Primary DatabaseSPOFCascading via Core BankingCritical
SWIFT GatewaySingle-pathPayments Processing onlyMedium
📊 Impact Tolerances
Critical FunctionMax DisruptionRTOFinancial LimitCustomer ImpactReg. Reporting
Payments Processing4 hours2 hoursCHF 5,000,000CriticalYes
Client Digital Channels2 hours1 hourCHF 2,000,000CriticalYes
Client Portfolio Mgmt8 hours4 hoursCHF 10,000,000HighYes
Client Onboarding & KYC24 hours12 hoursCHF 1,000,000MediumNo
Regulatory Reporting48 hours24 hours—LowYes
🔗 Critical Function Dependency Map

End-to-end mapping of critical functions, technology dependencies, third-party providers, and infrastructure — with single-point-of-failure and concentration risk analysis.

📋 Full Dependency Register
Critical FunctionDependencyTypeCriticalitySPOF?
⚡ Scenario Testing Framework

Severe-but-plausible disruption scenarios aligned with DORA Art. 26-27 and FINMA Cm 50-55. Click a scenario to run the simulation.

📈 Resilience Maturity Assessment

Maturity scoring across DORA, FINMA, PRA, and BCBS frameworks. Scale: 1 (Initial) → 5 (Optimised).

DORA
2.5
FINMA
2.7
PRA
2.6
BCBS
2.5
📋 DORA Pillar Assessment
🗺️ Regulatory Mapping
CapabilityDORAFINMAPRABCBS
Critical Function IDArt. 8Cm 31-35SS1/21 5.1-5.3P3
Dependency MappingArt. 8-9Cm 36-40SS1/21 5.4-5.6P4
Impact TolerancesArt. 11Cm 41-45SS1/21 6.1-6.4P5
Scenario TestingArt. 26-27Cm 50-55SS1/21 7.1-7.5P7
Incident ManagementArt. 17-23Cm 60-65SS1/21 8.1-8.3P9
Third-Party OversightArt. 28-44Cm 70-75SS1/21 9.1-9.4P10
🚨 Incident Management & Lessons Learned
Total Incidents (Q1)
7
P1/P2 Incidents
3
Total Downtime
14.5h
Open Remediation Actions
5
📋 Recent Incidents
IDTitleSeverityCategoryDowntimeRoot CauseStatus
INC-0001Core Banking System OutageP1Technology3.5hDB connection pool exhaustionResolved
INC-0002Cloud Provider Latency SpikeP2Third Party4.0hAWS EU region degradationResolved
INC-0003SWIFT Gateway TimeoutP2Technology2.0hHSM certificate expiryResolved
INC-0004KYC Screening DegradationP3Third Party1.5hRefinitiv API rate limitingClosed
INC-0005E-Banking Login FailuresP1Technology1.5hAuth service memory leakInvestigating
INC-0006Market Data Feed DelayP3Third Party1.0hBloomberg feed latencyClosed
INC-0007Batch Reporting FailureP4Process1.0hETL job configuration errorResolved
💡 Key Messages for Board Reporting
7 operational incidents recorded in Q1 2026, with 3 classified as P1/P2.
2 incidents involved Cloud Provider A — recurring dependency warrants diversification review.
Core Banking System SPOF validated: INC-0001 confirmed cascading impact to Payments Processing.
5 remediation actions remain open. Recommend escalation of overdue items to ORCO.