GRA · Banking Nexus
Spatial financeWhere capital meets hazard, exposure and transition
Bank operational resilience
Operational resilience is a bank’s ability to keep delivering critical services through disruption, whether from a cyber attack, a failed technology change, a third-party outage or a pandemic. Supervisors now ask banks to identify their important business services, set impact tolerances and show they can stay within them. This page explains how operational disruption develops and spreads, how resilience is measured and tested, and who decides what level of disruption is tolerable.
Bank operational resilience on the record.
Bank operational resilience: how the risk develops.
Third-party, cyber and process continuity. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.
Dependencies are hidden
A single payment or lending service rests on people, processes, data, technology and external providers. Mapping these dependencies end to end often reveals single points of failure that no one clearly owns.
Third parties concentrate risk
Many banks rely on the same cloud, software and data providers. An outage or compromise at one provider can hit many institutions at once, turning an operational event at one firm into a sector-wide one.
Cyber incidents escalate
Intrusion, ransomware or data corruption can disable services and damage the integrity of records. Recovery is slower when backups are compromised or when an attack spreads through shared networks and supply chains.
Disruption becomes financial
An outage blocks payments, delays settlement and erodes customer confidence. Prolonged disruption can trigger deposit outflows, sanctions and compensation costs, and at a market utility it can cause knock-on failures elsewhere.
How a shock to assets becomes a system loss.
بین البینک متعدی اثر کے بعد نظام کا کھویا ہوا سرمایہ، ابتدائی دھچکے کے مقابلے میں، جب قرض کا تناسب، باہمی ربط اور بحالی کی شرحیں بدلتی ہیں: کلی احتیاطی دباؤ کی جانچکا مرکزی حصہ۔ بیان کردہ مثالی اقدار کے ساتھ تدریسی ماڈل، پیش گوئی نہیں۔
کنٹرولز
- Fall in external assets
- 2.0%
- Leverage (assets over equity)
- 10 times
- Interbank share of assets
- 10%
- Recovery on interbank claims
- 40%
- Banks in the system
- 20
- Core banks
- 20% of banks
ریڈنگز
- Equity lost to the initial shock
- 18.0%
- Equity lost after contagion
- 45.0%
- Added by contagion (DebtRank)
- 27.0 points
- Banks in default
- 0
اعداد، طریقے اور ماخذات
| Round | System equity lost (%) | Banks in default |
|---|---|---|
| 0 | 18.00 | 0 |
| 1 | 28.80 | 0 |
| 2 | 35.28 | 0 |
| 3 | 39.17 | 0 |
| 4 | 41.50 | 0 |
| 5 | 42.90 | 0 |
| 6 | 43.74 | 0 |
| 7 | 44.24 | 0 |
| 8 | 44.55 | 0 |
| 9 | 44.73 | 0 |
| 10 | 44.84 | 0 |
| 11 | 44.90 | 0 |
| 12 | 44.94 | 0 |
| 13 | 44.96 | 0 |
| 14 | 44.98 | 0 |
| 15 | 44.99 | 0 |
| 16 | 44.99 | 0 |
| 17 | 45.00 | 0 |
| 18 | 45.00 | 0 |
| 19 | 45.00 | 0 |
| 20 | 45.00 | 0 |
| 21 | 45.00 | 0 |
| 22 | 45.00 | 0 |
| 23 | 45.00 | 0 |
| 24 | 45.00 | 0 |
| 25 | 45.00 | 0 |
| 26 | 45.00 | 0 |
| 27 | 45.00 | 0 |
| 28 | 45.00 | 0 |
| 29 | 45.00 | 0 |
| 30 | 45.00 | 0 |
طریقے
- DebtRank Battiston and others (2012), Scientific Reports 2:541
- Differential DebtRank Bardoscia and others (2015), PLOS ONE 10
- Contagion in financial networks Gai and Kapadia (2010), Proc. R. Soc. A 466
- Clearing in financial networks Eisenberg and Noe (2001), Management Science 47
- غیر یقینی کا پنکھا (پیرامیٹر Monte Carlo) Spiegelhalter، Pearson and Short (2011)، Visualising uncertainty about the future، Science 333
- ایک وقت میں ایک کی حساسیت (ٹورنیڈو) Saltelli and others (2008)، Global Sensitivity Analysis: The Primer، Wiley
ڈیٹا
No observed data enters this model: it runs on the teaching values set by the controls, to be replaced with a programme’s own evidence.
چھ ستونوں میں، Nexus Consortium کی قیادت میں
- تجربات تجربہ گاہیں
- Built in Banking Nexus in Foundry
- Tested at Banking Nexus in Universe
- میں مدون معیارات میں مالیات، بیمہ اور معیشت
- Published in Banking Nexus in Reports
- میں پڑھایا جاتا ہے اکیڈمی میں مالیات اور معاشیات کی فیکلٹی
What is measured, and how well.
Each indicator carries its unit, its cadence, the kind of source behind it and the evidence label a value would carry. No values are shown: a programme supplies them under its own authority.
| Indicator | Unit | Cadence | Source type | لیبل |
|---|---|---|---|---|
| Important business services within impact tolerance in testing | count of services tested and count passing | annual | Scenario testing records | رپورٹ شدہ |
| Major ICT-related incidents | count by severity class | quarterly | Incident reports to supervisors | Published statistics |
| Service downtime | minutes per incident | per event | Incident logs | مشاہدہ شدہ |
| Recovery time against objective | hours | per event | Continuity tests and incident records | مشاہدہ شدہ |
| Critical third-party concentration | count of important services per provider | annual | Register of third-party arrangements | رپورٹ شدہ |
| Operational risk losses | currency units by Basel event type | quarterly | Internal loss data | رپورٹ شدہ |
| Critical vulnerabilities past remediation deadline | count | monthly | Security management records | مشاہدہ شدہ |
What bank operational resilience means for exposure, loss and capital.
The exposure, loss, scenario and capital views a risk officer, supervisor or ministry of finance would ask for, with the frameworks they report against. Structures follow supervisory and actuarial practice. Values are illustrative: never prices, ratings or advice.
Scenario pathways
How bank operational resilience could be stressed under the scenario families central banks and supervisors use.
| Scenario family | Transition risk | Physical risk | What a stress test asks |
|---|---|---|---|
| Orderly | Early, gradual policy | کم تر | Can the book absorb a steady repricing? |
| Disorderly | Late, abrupt policy | Lower to medium | What breaks under a sudden repricing and credit migration? |
| Hot house world | Limited policy | High and rising | Where do physical losses concentrate in collateral and insurance? |
Where the evidence comes from.
Named public datasets and institutional records, each with its licence class. Sources by agreement are used only under their terms and never republished.
| ماخذ | What it gives | Licence class |
|---|---|---|
| Registers and critical provider designations under the EU Digital Operational Resilience Act | Registers of ICT third-party arrangements held by authorities and the public list of designated critical ICT providers | Registers restricted to authorities; designation list public |
| ECB cyber resilience stress test and supervisory publications | Supervisory findings on cyber response and recovery capabilities | Free, attribution |
| Bank of England and PRA operational resilience publications | Policy statements, thematic findings and CBEST threat-led testing reports | Free, Bank of England terms of use |
| ORX operational risk loss data | Pooled loss events by event type and business line from member banks | Licensed, membership |
| ENISA threat landscape for the finance sector | Analysis of cyber threats and incident patterns affecting financial institutions | Free, attribution |
| Pillar 3 operational risk disclosures | Operational risk capital and loss summaries published by banks | Public, bank terms |
Who decides, and what the evidence serves.
Banking Nexus prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| کون فیصلہ کرتا ہے | The question | Evidence this page serves |
|---|---|---|
| Bank board | Which business services are important and what impact tolerance each should carry | Service maps, scenario test results and incident history |
| Chief operating officer and chief information security officer | Where to invest in redundancy, recovery and exit plans for third parties | Dependency maps, recovery tests, vulnerability and incident data |
| Prudential supervisor | Whether a bank’s self-assessment and testing are credible, and when to intervene | Incident reports, test evidence and thematic reviews |
| Authorities overseeing critical third parties | Which providers to designate and what oversight to apply | Concentration across the sector and the substitutability of each provider |
Outputs this topic produces
- Guides to mapping important business services and their dependencies
- Severe but plausible disruption scenarios for tabletop and live testing
- Research on concentration in cloud and critical technology providers
- Briefings on incident patterns, with sources and evidence labels
Shared questions the industry asks.
- 01
Which services matter most?
Which business services, if disrupted, would harm customers or market integrity.
- 02
What do they depend on?
The people, processes, technology, facilities and third parties behind each service.
- 03
Where are shared dependencies?
Providers and systems that many banks rely on at once.
- 04
How fast can services recover?
Whether banks can stay within impact tolerances in severe scenarios.
How the risk arises and transmits.
Modern banking runs on technology chains. A payment may depend on core banking systems, cloud infrastructure, network providers, card schemes and settlement systems, many operated by third parties.
Concentration in technology providers creates shared exposure. An outage or compromise at a major cloud, software or data provider can affect many banks simultaneously, a systemic risk that no single bank’s contract can address.
Cyber threats are persistent and adaptive. Ransomware, data theft and destructive attacks target banks and their suppliers. Recovery depends on segmentation, trusted backups and rehearsed response.
Physical hazards affect operations too. Floods, heat and power outages can disable data centres, branches and staff access, often in the same region as borrower losses.
The shift from preventing failure to assuming it will occur has reshaped the discipline: banks now map services end to end and test whether they can recover within set tolerances.
How evidence is gathered, and where it stops.
| Method or data | What it shows | Its limit |
|---|---|---|
| Service mapping | Dependencies behind each service | Maps age quickly as systems change |
| Scenario testing | Recovery within tolerances | Scenarios may not capture novel failures |
| Incident data | Causes and duration of disruptions | Under-reporting and confidentiality |
| Third-party registers | Shared provider concentration | Visibility beyond direct suppliers is limited |
How it is studied, and what the methods cannot say.
- 01Network science and contagionInterbank and counterparty contagion · Overlapping portfolios and fire salesApplied here
- 02Probability and statisticsEstimating default and loss parameters · Operational loss modellingApplied here
- 03Financial and risk engineeringExpected credit loss modelling · Counterparty exposure and valuation adjustmentsApplied here
- 04Artificial intelligence and machine learningCredit decisioning with explainability · Early warning and transaction monitoringApplied here
سوالات و جوابات۔
What is an impact tolerance?
How is operational resilience different from business continuity?
Why are cloud providers a supervisory concern?
Does GRA test banks’ resilience?
Can banks share incident information through GRA?
Why include physical hazards in operational resilience?
اس صفحے سے شواہد فراہم کریں۔
Reports کنسورشیم کی سہ ماہی اشاعت ہے۔ اس موضوع کے بارے میں آپ کا علم اگلے شمارے میں شواہد، کیس یا تصحیح بن سکتا ہے، جو آپ کے نام سے منسوب ہوگا اور اگر یہ آپ کا اپنا کام ہو تو CC BY 4.0 کے تحت شائع ہوگا۔
- EmailGateway GW-GRASend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGlobal Risks AllianceSee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
کبھی بھی ذاتی ڈیٹا، حساس بنیادی ڈھانچے کی تفصیل یا کوئی ایسی چیز نہ بھیجیں جسے شیئر کرنے کا آپ کو حق نہ ہو۔ ہر شراکت استعمال سے پہلے جانچی جاتی ہے؛ اسے بھیجنے سے کوئی تصنیفی یا ادارتی حق حاصل نہیں ہوتا، اور سرپرستی کبھی کوئی نتیجہ نہیں خریدتی۔
Bring an exposure or capital question to the Alliance.
معلومات اور استفسارات آج کھلے ہیں۔ استفسار کو ایک حوالہ نمبر ملتا ہے اور اگلے مرحلے کی نشاندہی ہوتی ہے؛ درخواستیں، ادائیگیاں، کمپیوٹنگ کی تخصیص اور رجسٹریشن صرف اس وقت کھلتی ہیں جب ان کی ٹیم، شرائط اور جائزے کی استعداد موجود ہو۔
قانونی دستاویزات۔
اس سائٹ کے نقشے، ڈیٹا اور اشکال سیاق اور عمومی معلومات کے لیے دکھائے جاتے ہیں۔ یہ مشورہ، پیش گوئیاں یا انتباہات نہیں؛ معلومات کی حدود دستبرداریوں اور ڈیٹا سے متعلق اطلاعات میں بیان کی گئی ہیں۔