GRA · Payments and Market Infrastructure
Spatial financeWhere capital meets hazard, exposure and transition
Operational test methods
Infrastructures and participants test their resilience through scenario tests, failover and recovery tests, threat-led penetration tests and market-wide exercises. Testing shows whether plans work under severe but plausible disruption. This page sets out the main test methods, what each can and cannot show, the records they produce, and who decides what is tested.
Operational test methods on the record.
Operational test methods: how the risk develops.
Failure exercises and recovery assumptions. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.
Scenario tests check tolerances
Severe but plausible scenarios test whether important services stay within impact tolerances. Scenarios that are too mild give false comfort.
Red teams test defences
Threat-led penetration tests use realistic attacker techniques against live systems, under controlled conditions, to find weaknesses.
Market-wide exercises test coordination
Exercises across many institutions and authorities test communication, decisions and shared dependencies that single-firm tests miss.
Findings must close
Testing produces findings. Without remediation tracked to closure, the same weaknesses appear in the next test.
RTGS operations console.
وہ اسکرین جو ایک ٹیم اس موضوع کی پیروی کے لیے استعمال کرے گی: اس کے پیمانے، حالتیں اور فیصلے۔ نام مثالیں ہیں اور اقدار توضیحی ہیں۔
RTGS operations console
Operational test methods · RTGS system · Business day 193
- Value settled today107local bnActive
- Payments queued11624نگرانی کریں
- Availability, % this month99.9معمول
- Participants below liquidity floor2Alert
Intraday liquidity, system
Incident and failover log
- 09:26INCParticipant P-12 message delay
- 10:43LSMLiquidity saving cycle released 64 payments
- 14:00CUTCustomer payment cut-off
- Q1TESTContingency site failover in 93 min
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 | لیبل |
|---|---|---|---|---|
| Threat-led penetration tests completed | count | annual | Public records | Published statistics |
| Failover tests to secondary sites | count and success rate | annual | Operator records | DECLARED |
| Market-wide exercises held | count | annual | Authority publications | Published statistics |
| Findings remediated within deadline | share of findings | periodic | Remediation tracking | DECLARED |
| Services tested against impact tolerance | share of important services | annual | Self-assessments | DECLARED |
| Recovery time achieved in tests | hours | per test | Test reports | مشاہدہ شدہ |
What operational test methods 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.
Transmission channels
How a shock in operational test methods reaches credit, market, underwriting, liquidity and operational risk, and feeds back.
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 |
|---|---|---|
| ECB TIBER-EU framework and annual reports | Red-team testing framework and summary findings | Free, ECB terms |
| Bank of England CBEST and SIMEX reports | Threat-led testing and market-wide exercises | Free, Bank of England terms |
| DORA regulatory technical standards on threat-led penetration testing | EU testing requirements | Free, EU reuse terms |
| G7 Cyber Expert Group fundamental elements | Principles for threat-led testing and third-party risk | Free to read, terms to check |
| Hamilton series exercise reports and similar public summaries | Cross-sector exercise findings | Free to read, terms to check |
Who decides, and what the evidence serves.
Payments and Market Infrastructure 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 |
|---|---|---|
| Authorities | Which institutions must run threat-led tests and exercises | Test frameworks and sector risk evidence |
| Boards | Which services and scenarios to test and how to fix findings | Test results and remediation status |
| Testing teams and providers | How to design and conduct tests safely | Framework requirements and methods |
| Exercise coordinators | Which scenarios to run across the market | Threat evidence and previous findings |
Outputs this topic produces
- Guide to operational resilience test types
- Method note on severe but plausible scenario design
- Brief on market-wide exercises and their lessons
- Questions for boards on remediation tracking
What the industry asks.
Plans and recovery targets are only as reliable as the tests that verify them. Many infrastructures meet their recovery objectives in planned tests but have never faced a realistic, destructive scenario involving several institutions at once. Credible testing exposes assumptions, such as that backups are clean, that providers will be available or that staff can work from alternate sites, before a real crisis tests them.
- Do tests use severe but plausible scenarios, including destructive cyber attacks and provider failures?
- Do tests cover the whole chain, including participants, providers and linked infrastructures, rather than one system in isolation?
- Which recovery assumptions have been tested, and which remain untested?
- How are lessons from tests turned into changes, and how is progress tracked?
How the infrastructure works and fails.
Testing ranges from single-system checks to sector-wide simulations.
Failover and recovery
Switching to backup sites and systems to check recovery times. Planned tests may not reflect real conditions.
Simulated attacks
Testing by teams that simulate real attackers’ techniques, under frameworks established by authorities in several jurisdictions.
Many institutions together
Exercises that simulate disruption across infrastructures, participants and authorities, revealing interdependencies.
A common weakness revealed by exercises is the gap between technical recovery and business recovery. Systems may be restored within target, but reconciling positions, communicating with participants and resuming normal operations can take much longer. Tests that measure the full return to service, including data reconciliation across institutions, give a more honest picture of resilience.
How the evidence is built, and its limits.
- 01
Test design
Scenario selection, scope and success criteria. Test results depend heavily on design.
- 02
Recovery metrics
Measurement of recovery time and data loss against objectives, applying reliability and resilience engineering.
- 03
کارروائی کے بعد کا جائزہ
Structured review of what worked and what failed, with tracked follow-up.
- 04
Simulation models
Models of payment flows under disruption, applying network science and contagion, to complement live tests.
How it is studied, and what the methods cannot say.
- 01Reliability and resilience engineeringImpact tolerance setting · Recovery design · Learning from incidentsApplied here
- 02Cybersecurity and cryptographyEndpoint control frameworks · Threat-led testing · Destructive attack recoveryApplied here
- 03Network science and contagionPayment flow networks · Shared provider mapping · CCP membership networksApplied here
- 04Payment and financial market technologyLiquidity-saving mechanisms · ISO 20022 data quality · Settlement cycle designApplied here
سوالات و جوابات۔
What is threat-led penetration testing?
What is a market-wide exercise?
What is an impact tolerance?
Does GRA run tests on payment systems?
Why are sector-wide exercises important?
What is the Universe payment outage exercise?
اس صفحے سے شواہد فراہم کریں۔
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.
معلومات اور استفسارات آج کھلے ہیں۔ استفسار کو ایک حوالہ نمبر ملتا ہے اور اگلے مرحلے کی نشاندہی ہوتی ہے؛ درخواستیں، ادائیگیاں، کمپیوٹنگ کی تخصیص اور رجسٹریشن صرف اس وقت کھلتی ہیں جب ان کی ٹیم، شرائط اور جائزے کی استعداد موجود ہو۔
قانونی دستاویزات۔
اس سائٹ کے نقشے، ڈیٹا اور اشکال سیاق اور عمومی معلومات کے لیے دکھائے جاتے ہیں۔ یہ مشورہ، پیش گوئیاں یا انتباہات نہیں؛ معلومات کی حدود دستبرداریوں اور ڈیٹا سے متعلق اطلاعات میں بیان کی گئی ہیں۔