RA · Foundations
Operational risk and business continuity: what to learn, in what order, and why
A learning guide to operational risk and business continuity: operational resilience, contingency planning, key texts, an order of study and expertise.
- As of
- 17 November 2026
- படித்தல்
- 11 minutes
- சான்றுகள்
- 10 sources, cited in order
- நிலை
- Introductory to intermediate
- Study time
- 15 minutes
What you will be able to do
- Distinguish operational risk, business continuity and operational resilience.
- Describe the steps of contingency planning.
- Explain why third-party dependencies are treated as a risk.
- Write a short note on what a desk exercise found.
- நிலை
- Introductory to intermediate
- Study time
- 15 minutes
- Before you start
- The learning guide to the Faculty of Risk Science and Methods, or equivalent background
01What operational risk and business continuity covers
What operational risk and business continuity covers
Operational risk and business continuity is the Academy discipline of operational risk and business continuity, one of the disciplines of the Faculty of Risk Science and Methods. In plain terms, operational risk is the risk of loss from failed processes, people or systems, or from external events. Business continuity is the capacity to keep critical activities going, or restore them quickly, when something goes wrong.
Standard setters treat the two as linked. The Basel Committee on Banking Supervision published its Principles for operational resilience and its revisions to the principles for the sound management of operational risk, both dated 31 March 2021 1 2. The Prudential Regulation Authority (PRA) considers that firms are operationally resilient when they can do four things. They prevent disruption to the extent practicable and adapt systems and processes to continue services during an incident. They return to normal running promptly and learn from incidents and near misses 3.
The discipline sits beside enterprise risk management and risk frameworks, assurance, internal control and risk culture and preparedness and crisis management.
02Why resilience is now a supervised outcome
Why resilience is now a supervised outcome
Disruption is no longer treated as a rare exception. Cyber incidents, supplier failures, outages and extreme weather all interrupt services that people rely on. Regulators have moved from asking whether a firm has a plan to asking whether it can keep important services within limits it has set.
The PRA's operational resilience policy was first published on 29 March 2021 and took effect from 31 March 2022 3. The European Insurance and Occupational Pensions Authority describes the Digital Operational Resilience Act, Regulation (EU) 2022/2554 of 14 December 2022, as strengthening the digital resilience of financial entities. It says the Act entered into application on 17 January 2025 and applies to 20 types of financial entities and to ICT third-party service providers 4.
The same logic reaches beyond finance. The Sendai Framework calls on business, professional associations and private sector financial institutions to integrate disaster risk management, including business continuity, into business models and practices 6. One of its targets is to substantially reduce disaster damage to critical infrastructure and disruption of basic services 6.
03Risk, continuity and resilience
Risk, continuity and resilience
The three ideas answer different questions. Operational risk management asks what could go wrong and how to reduce the chance and the loss. Business continuity asks how to keep going, or restore critical activities, when something does go wrong. Operational resilience asks whether the organisation can deliver its most important services within agreed limits through severe but plausible disruption. The PRA notes that operational resilience is an outcome that is supported by several parts of the PRA's regulatory framework 3. Its Supervisory Statement 1/21, first published on 29 March 2021, sets out expectations for the operational resilience of firms' important business services, for which they are required to set impact tolerances 7.
Planning is the classic continuity tool. The NIST Contingency Planning Guide for Federal Information Systems, Revision 1, published in May 2010, defines contingency planning as interim measures to recover information system services after a disruption, and information system contingency planning as a coordinated strategy involving plans, procedures and technical measures 5. Although written for US federal information systems, its steps are widely read as a worked method: analyse impact, choose recovery strategies, write plans, test and maintain them.
Technology risk is part of operational risk. NIST says in its interagency report on cybersecurity and enterprise risk management that all enterprises should ensure that cybersecurity risk receives appropriate attention within their ERM programmes 8. Figure 2 shows how the three ideas fit.
The United Nations expert working group on terminology defines resilience for hazards in general. It is the ability of a system, community or society exposed to hazards to resist, absorb, accommodate, adapt to, transform and recover from the effects of a hazard in a timely and efficient manner 9. The wording is broader than the version used by financial supervisors, but the shape is the same: resilience is judged by how a system behaves under stress and how fast it recovers, not by whether it ever fails.
A worked habit helps here. For any critical service, a learner should be able to say who depends on it, what it depends on, how long a disruption can last before harm becomes unacceptable and who decided that limit. If any of those four answers is missing, the service is not yet understood well enough to be called resilient.
Fig. 02Risk, continuity and resilience
Figure 2 in words
Three layers stacked from top to bottom. Operational resilience, highlighted: whether important services stay within agreed limits through severe but plausible disruption. Business continuity: how to keep critical activities going or restore them. Operational risk management: what could go wrong and how to reduce the chance and loss. The PRA describes resilience as an outcome supported by several parts of its regulatory framework.
04A suggested learning order in four stages
A suggested learning order in four stages
The Academy describes study at four levels: introductory, intermediate, advanced and integrative. The four stages below follow the same arc for operational risk and business continuity. They are a suggestion, and a learner can enter at any stage.
Stage one: the language of operational risk. Start with the loss events that operational risk covers: process failure, people, systems and external events. Read the Basel revised principles as a statement of what sound management looks like 2. Write a short list of operational risk events from public news and classify each.
Stage two: continuity and contingency planning. Next, study how plans are made. Work through the steps of NIST contingency planning guide, Revision 1 5. Learn the difference between an impact analysis, a recovery strategy and a plan, and why plans must be tested.
Stage three: resilience and impact tolerance. Then study the shift to outcomes. Read the PRA operational resilience policy 3 and the Basel principles for operational resilience 1. Note how each frames important services and limits on disruption.
Stage four: testing, dependencies and learning. Finally, study dependencies and testing. Read how the EIOPA page on DORA treats ICT third-party providers 4. Read the NIST report on cybersecurity in ERM 8. Practise running a short desk exercise on a plausible disruption and writing what was learned.
The order is a suggestion. A practitioner may begin at stage three and return to stage one later. What matters is that each new idea has the ideas beneath it in place.
Fig. 01Four stages of study in operational risk and business continuity
Figure 1 in words
Four steps rise from left to right. Step one, the language of operational risk: the Basel revised principles. Step two, continuity and contingency planning: the NIST contingency planning guide. Step three, resilience and impact tolerance: the PRA policy and the Basel resilience principles. Step four, highlighted, testing, dependencies and learning: DORA and the NIST report on cybersecurity in ERM.
Fig. 03The four parts of operational resilience
Figure 3 in words
Four stages run from left to right: prevent, adapt, return and learn. Prevent disruption occurring to the extent practicable. Adapt systems and processes to continue to provide services during an incident. Return to normal running promptly when the disruption is over. Learn and evolve from both incidents and near misses.
05Six core ideas every learner should hold
Six core ideas every learner should hold
Six ideas carry most of the weight in this discipline. Each is simple to state and takes practice to use.
Operational risk has a defined scope. The Basel Committee describes it as the risk of loss resulting from inadequate or failed internal processes, people and systems or from external events 2.
Resilience is an outcome. The PRA frames it as the ability to prevent, adapt, return and learn 3.
Plans are only as good as their testing. Contingency planning is a cycle of analysis, planning, testing and maintenance 5.
Dependencies are risks. DORA extends rules to ICT third-party service providers because financial entities depend on them 4.
Technology risk belongs in the whole. Cybersecurity risk should be visible in ERM 8.
Continuity is a private and public concern. Sendai asks business to integrate continuity into practice and aims to reduce disruption of basic services 6.
06Canonical references and data to know
Canonical references and data to know
A learner should know a short list of primary texts. Read the originals first and treat summaries as an aid.
For standards: the Basel principles for operational resilience 1 and for sound management of operational risk 2. For supervisory policy: the PRA operational resilience page 3 and the EIOPA DORA page 4. For method: the NIST contingency planning guide 5 and NIST IR 8286 8. For the wider context: the Sendai Framework 6, and the IIA Three Lines Model 10 on roles. These are documents, not datasets. Learners should record the edition and date of each text and note where rules have changed since.
07Skills that make the knowledge usable
Skills that make the knowledge usable
Knowledge becomes useful through a small set of skills. The discipline treats these as its practical core.
Mapping a service. Trace what a critical service depends on: people, processes, technology, premises and suppliers. Analysing impact. Say how long a disruption can last before harm is unacceptable. Setting tolerance. Agree limits and record who accepted them. Planning recovery. Write steps that a team can follow under stress. Testing. Run exercises and record gaps. Learning from incidents. Record causes and near misses, and show what changed.
08Open courses and pathways
Open courses and pathways
No open course on this subject was opened at its provider and confirmed as open to the public for this edition, so none is listed.
The primary texts are a pathway. The Basel principles, the PRA policy page, the EIOPA page and the NIST publications are free to read at their issuers, as confirmed on 17 November 2026 1 2 3 4 5. A suggested order is the Basel texts, then one planning method such as the NIST guide, then a supervisory policy page.
None of these is a course with assessment, and none is described here as leading to a qualification. Professional bodies publish their own standards and training, and this guide did not open them.
09How expertise is shown
How expertise is shown
Expertise in this field is shown by work that others can check. The Academy records learning, not credentials.
Finishing a course gives a completion record. It is not a certificate, an accreditation or a qualification, and it does not state that a person is competent in a profession. Achievements on the Academy recognise assessed learning only.
The Academy catalogue lists two courses for this discipline: Operational risk and business continuity: foundations and practice, at the intermediate level, and Operational risk and business continuity: frontier methods, at the advanced level. On 17 November 2026 the catalogue page shows the first as in authoring and the second as planned. Nothing is open for enrolment until it is published in the NXS Learning catalogue, so this guide does not point to an Academy course as a place to enrol.
Outside the Academy, the strongest evidence of expertise is a body of work: a service map with dependencies and tolerances, a tested continuity plan with exercise findings, or a short comparison of two resilience policies. Learners are encouraged to keep such a record from their first course.
10Emerging areas to watch
Emerging areas to watch
Several areas are changing what a continuity and operational risk professional needs to know. Each is a place to read on once the core is in place.
Digital operational resilience. DORA has applied since 17 January 2025 and covers ICT third-party providers 4. Resilience as an outcome. Supervisors such as the PRA keep updating policy on important business services and impact tolerances 3. Technology in ERM. NIST continues to link cybersecurity and enterprise risk 8. Continuity in development finance and policy. Sendai places business continuity in the integration of disaster risk management into business models 6.
Related work across the Nexus network gives wider context. See infrastructure dependencies at the Global Centre for Risk and Innovation, cyber and operational risk at the Global Risks Alliance, disaster and crisis governance at the Global Risks Forum and the proposed Nexus Standards on cyber and digital operational resilience. These pages describe programmes and proposals. A link to them implies no endorsement of the sources this guide cites.
What this guide does not claim: it is suggested learning, not a curriculum that anyone must follow, and it is not professional, legal, medical or technical advice. It names programmes, courses and bodies as places to learn and implies no partnership with any of them. It reports figures as their issuers published them and draws no new estimates from them. Risk Academy does not certify competence, and a completion record is not a professional qualification. The Academy records no partners, cohorts or learner outcomes for this faculty, and this guide implies none. The Nexus Standards are proposed and in draft; nothing here treats them as adopted.
கேள்விகள்
Questions and answers
Where should a complete beginner start in operational risk and business continuity?
Start with stage one and a list of public operational risk events, then work through the steps of the NIST contingency planning guide.
What is the difference between business continuity and operational resilience?
Continuity concerns plans to keep critical activities going or restore them. Resilience concerns whether important services stay within agreed limits through severe but plausible disruption.
Does DORA apply to every organisation?
No. EIOPA describes it as applying to 20 types of financial entities and to ICT third-party service providers in the EU.
Do I need technical skills to follow this guide?
Not for stages one and three. Stage two and four are easier with some knowledge of information systems.
Do courses in this discipline lead to a qualification?
No. A completion record shows that you finished a course. It is not a certificate or a professional qualification.
விதிமுறைகள்
Glossary
- Operational risk
- The risk of loss from failed processes, people and systems or from external events.
- Business continuity
- The capability to keep critical activities running, or to restore them, during and after disruption.
- Operational resilience
- The ability to prevent, adapt to, recover from and learn from operational disruption.
- Contingency plan
- A plan for recovering a service after a disruption.
- Impact tolerance
- The maximum disruption an organisation accepts for an important service.
- Third-party dependency
- Reliance on an outside supplier for something the organisation needs to operate.
தொடர்புடையவை
Further reading across the network
- இயக்க இடரும் வணிகத் தொடர்ச்சியும்
- Core course of the discipline
- Frontier course of the discipline
- இடர் அறிவியல் மற்றும் முறைகள் புலம்
- Learning guide: risk science and methods
- Learning guide: enterprise risk management and risk frameworks
- Learning guide: assurance, internal control and risk culture
- Learning guide: model risk and validation
- The Global Centre for Risk and Innovation (GCRI): infrastructure dependencies
- The Global Risks Alliance (GRA): cyber and operational risk
- The Global Risks Forum (GRF): disaster and crisis governance
- Nexus Standards: cyber resilience and digital operational resilience (proposed)
Check your understanding
What four abilities does the PRA associate with operational resilience?
Prevent disruption as far as practicable, adapt to keep services going, return to normal promptly and learn from incidents and near misses.
What is contingency planning in the NIST guide?
Interim measures to recover information system services after a disruption.
Why does DORA cover ICT third-party providers?
Financial entities depend on them, and failures can spread across borders and sectors.
Continue with a course
- Operational risk and business continuity: foundations and practice operational-risk-continuity.core
- Operational risk and business continuity: frontier methods operational-risk-continuity.frontier
மூலங்கள்
References
10 sources, numbered in the order they are first cited
- Basel Committee on Banking Supervision (2021-03). Principles for operational resilience. www.bis.org. Accessed 2026-11-17.
- Basel Committee on Banking Supervision (2021-03). Revisions to the principles for the sound management of operational risk. www.bis.org. Accessed 2026-11-17.
- Bank of England, Prudential Regulation Authority (2021-03). SoP1/21: Operational resilience. www.bankofengland.co.uk. Accessed 2026-11-17.
- European Insurance and Occupational Pensions Authority (2026). Digital Operational Resilience Act (DORA). www.eiopa.europa.eu. Accessed 2026-11-17.
- U.S. National Institute of Standards and Technology (2010-05). Contingency Planning Guide for Federal Information Systems. nvlpubs.nist.gov. Accessed 2026-11-17.
- United Nations General Assembly (2015-06). Sendai Framework for Disaster Risk Reduction 2015–2030 (A/RES/69/283). documents.un.org. Accessed 2026-11-17.
- Prudential Regulation Authority, Bank of England (2021-03). SS1/21: Operational resilience: Impact tolerances for important business services. www.bankofengland.co.uk. Accessed 2026-11-17.
- U.S. National Institute of Standards and Technology (2020-10). NIST IR 8286: Integrating Cybersecurity and Enterprise Risk Management (ERM). csrc.nist.gov. Accessed 2026-11-17.
- United Nations General Assembly (2016-12). Report of the open-ended intergovernmental expert working group on indicators and terminology relating to disaster risk reduction (A/71/644). digitallibrary.un.org. Accessed 2026-11-17.
- Institute of Internal Auditors (2020-09). The IIA's Three Lines Model: An update of the Three Lines of Defense. www.theiia.org. Accessed 2026-11-17.
பதிவு
Editorial record
Facts and course states are given as of 17 November 2026. This guide is reviewed at least every 270 days and whenever a cited report publishes a new edition or a course of the faculty opens.
Published by the Academy desk of Risk Academy. To report an error or request a correction, write through the Risk Academy contact page; corrections are dated and listed with the page. The Academy's statement on AI use explains how AI assistance is used and reviewed. Text, visuals and data are licensed CC BY 4.0, except where a cited source states other terms.
Cite this article
Academy desk, Risk Academy (2026, November 17). Operational risk and business continuity: a guide. Risk Academy. https://risksacademy.com/risk-science/learning-operational-risk-and-business-continuity-guide/
@online{academy2026learningoperationalris,
author = {{Academy desk, Risk Academy}},
title = {{Operational risk and business continuity: a guide}},
publisher = {Risk Academy},
year = {2026},
month = {11},
url = {https://risksacademy.com/risk-science/learning-operational-risk-and-business-continuity-guide/},
language = {en}
} TY - ELEC AU - Academy desk, Risk Academy TI - Operational risk and business continuity: a guide PB - Risk Academy PY - 2026 DA - 2026/11/17 UR - https://risksacademy.com/risk-science/learning-operational-risk-and-business-continuity-guide/ LA - en ER -
Republish
Republish or translate this article free of charge, in print or online, under CC BY 4.0: keep the byline and Risk Academy, link to the original and note any change. Figures, maps and twins made by the institutions carry the same licence; third-party data keeps its own credit line.
Attribution to paste
<p>Operational risk and business continuity: what to learn, in what order, and why — Academy desk, Risk Academy, Risk Academy. First published 17 November 2026 at <a href="https://risksacademy.com/risk-science/learning-operational-risk-and-business-continuity-guide/">https://risksacademy.com/risk-science/learning-operational-risk-and-business-continuity-guide/</a>. Republished under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/).</p>