Core ideas
Disruption is inevitable. The question regulators ask: which critical operations must continue, how much disruption can they tolerate, what do they depend on, can you stay within tolerance under severe but plausible scenarios, and is the board accountable?
| Concept |
One line |
| Operational resilience |
Outcome: deliver critical operations through disruption, within tolerance |
| BCMS |
Management system that plans, runs, checks and improves continuity (ISO 22301) |
| BCM |
Ongoing work of understanding impacts and building response capability |
| Cyber resilience |
Anticipate · withstand · recover · adapt (NIST SP 800-160 Vol. 2) |
| DR / ICT continuity |
Restore technology and data to meet continuity objectives |
| Crisis management |
Lead decisions and communication when strategy or reputation is threatened |
Time and data objectives
| Term |
Question |
Rule |
| MTPD |
When does impact become unacceptable? |
Set by top management |
| RTO |
By when must it resume? |
RTO < MTPD |
| MBCO |
Minimum service while recovering? |
From the BIA |
| RPO |
How much data loss is tolerable? |
Looks back from disruption |
| RTC |
What have we demonstrated? |
RTC > RTO = gap |
- Tech RTO ≤ activity RTO minus work recovery time (verify, reconcile, clear backlog).
- Tolerance for disruption (Basel, RBI) / impact tolerance (UK) ≈ MTPD for a critical operation; may use time, volume or service level.
- Equivalent terms: critical operations (Basel, RBI) · important business services (UK) · critical or important functions (DORA).
Standards
| Document |
Use |
| ISO 22301:2019 + Amd 1:2024 |
Certifiable BCMS requirements; Amd adds climate to 4.1 / 4.2 |
| Clause 8 |
8.1 planning · 8.2 BIA + risk · 8.3 strategies & solutions · 8.4 plans · 8.5 exercises · 8.6 evaluation |
| ISO 22313 · TS 22317 · TS 22318 |
Guidance · BIA · supply chain |
| ISO 22316 · 22361 · 22320 |
Org. resilience · crisis management · incident command |
| ISO/IEC 27031:2025 |
ICT readiness for BC |
| NIST SP 800-34 Rev. 1 |
7-step contingency planning; plan family (BCP, DRP, ISCP, CIRP…) |
| NIST CSF 2.0 |
Govern + Identify, Protect, Detect, Respond, Recover |
| NIST SP 800-61 Rev. 3 (2025) |
Incident response organised around CSF 2.0 |
| NIST SP 800-160 Vol. 2 · SP 800-184 |
Cyber-resilient design · cyber event recovery |
Indian regulation (as of November 2026)
| Regulator |
Instrument |
Key numbers and themes |
| RBI |
Cybersecurity, technology risk & resilience Directions, 31 Jul 2026, entity-wise |
DR drills half-yearly (critical systems) · DAKSH within 6 h · ITSC · CISO · C-SOC · CCMP |
| RBI |
Op. risk & operational resilience guidance (2024) |
17 principles, 3 pillars · critical operations · tolerance for disruption · mapping · severe-but-plausible testing · immutable backups |
| RBI |
IT outsourcing Directions (2023) |
RE accountable · provider BCP tested · audit/regulator access · concentration · exit |
| SEBI |
CSCRF (Aug 2024; clarified Aug 2025) |
Graded categories · RTO 2 h / RPO 15 min · 6 h reporting · Market SOC · CCI · audits twice yearly (MII, Qualified) · ISO 27001 mandatory MII, recommended Qualified |
| SEBI |
MII BCP-DR (2021, 2024) |
Declare 30 min · restore 45 min · RPO 15 min · quarterly drills · live from DR twice a year · near site, near-zero RPO |
| IRDAI |
Info & cyber security guidelines (Apr 2026) |
BCP/DR test annually → ISRMC · CERT-In 6 h with copy to IRDAI |
| CERT-In |
Directions (2022) |
6 h reporting · 180-day logs in India · NTP sync |
| DPDP |
Act 2023 + Rules 2025 |
Safeguards incl. continued processing · breach intimation |
Flow-down: TSPs inherit customers' rules through contracts: RTO/RPO, 2–4 h incident notice, testing, audit and regulator access, exit support.
International
| Regime |
Remember |
| BCBS 2021 |
7 principles: governance · ORM · BCP + testing · mapping · third parties · incident mgmt · resilient ICT |
| EU DORA (from 17 Jan 2025) |
ICT risk · major incident reporting · testing incl. TLPT ≥ every 3 years · ICT third-party register + contract terms · CTPP oversight |
| UK |
Important business services · impact tolerances · mapping · testing · self-assessment · within tolerance by 31 Mar 2025 |
Integrated map: themes × sources → one process, owner and evidence per theme. Strictest applicable requirement wins; record the decision.
Programme phases (year 1)
Mobilise (1–2) → Analyse (2–4) → Design (4–7) → Document (5–8) → Exercise (7–11) → Assure (10–12).
Lessons from incidents
| Incident |
Lesson |
| Bank data-centre outage (2020) |
Repeated outages → regulator restricts growth |
| Exchange halt (2021) |
Pre-agree fast DR invocation |
| Ransomware at bank's broker (2023) |
Plan safe manual workarounds |
| Ransomware at banking TSP (2024) |
Concentration risk across many REs |
| Faulty security update (2024) |
Trusted supplier = possible single point of failure |