Ready reckoner
ISO 22301 clauses 8.5 and 8.6
| Clause | Requirement |
|---|---|
| 8.5 | Programme that over time validates all strategies and solutions · consistent with BC objectives · appropriate scenarios with clear aims · builds teamwork, competence, confidence, knowledge · minimises disruption · formal post-exercise reports (outcomes, recommendations, actions) · reviewed for improvement · planned intervals + significant change · act on results |
| 8.6 | Evaluate suitability, adequacy, effectiveness of BIA, risk assessment, strategies, solutions, plans · via reviews, analysis, exercises, tests, post-incident reports, performance evaluation · evaluate partners and suppliers · evaluate legal/regulatory compliance, good practice, own policy · update promptly · at planned intervals, after incident/activation, on change |
Exercise types
Walkthrough → tabletop → simulation → functional test → full-scale/live (realism, cost and risk rise). Build up gradually.
Regulatory frequencies (check current instrument)
| Source | Frequency |
|---|---|
| RBI critical systems | DR drill ≥ half-yearly |
| RBI op. resilience | Scenario testing vs tolerance |
| SEBI MIIs | DR drill quarterly · live from DR twice a year · near-site switchover |
| SEBI CSCRF | Periodic drills by category |
| IRDAI | BCP/DR ≥ annually → ISRMC |
| DORA | Annual programme · TLPT ≥ every 3 years |
| Contracts | Often annual DR report or joint test |
Programme: list every strategy/solution → map frequencies → assign type + interval → vary scenarios and timing → include alternates, suppliers, customers → test after change → avoid peaks for live tests.
Design
Objectives: 3–6, measurable, tied to BC objectives/tolerances ("CMT convenes within 30 min via out-of-band bridge").
Scenario: from the library · specific (what, unknowns, what works, when) · stressful timing · realistic complications · plausible.
MSEL: time · source · content · expected response · objective; spare injects; realistic artefacts.
Roles: director · controllers · players · evaluators · safety officer · scribe. "EXERCISE EXERCISE EXERCISE" · real-incident code word · rollback and stop criteria.
Tabletop: briefing → 3 phases → hot debrief → evaluator notes.
DR drills
Plan: scope + scenario · objectives · type · prerequisites · roles · go/no-go · stop/rollback · timing · comms.
Live switchover: planned change · verify backups · real runbook, real operators, alternates · timestamps · rollback · business validation with real transactions.
Measure: time to decision · technical recovery · business validation · total (from incident start and from declaration) · RPO achieved · fail-back.
Drills that prove little: no business validation · pre-warmed DR · one expert · clock starts late · partner interfaces untested · same scenario · no fail-back · findings "noted". Keep a drill pack.
Cyber exercises
| Type | Tests |
|---|---|
| Executive tabletop | Ransom, disclosure, regulators, DR safety |
| Technical tabletop | Playbooks, containment |
| Simulation | Reporting clock, comms, coordination |
| Red team | Real detection and response (blind) |
| Purple team | Joint detection tuning |
| TLPT | Intelligence-led red team on live critical functions (control team, scoping, rules of engagement, board/regulator) |
| Ransomware recovery | Vault without prod creds · recovery point · clean room · validation · service up · timed |
| Sector/national | CERT-In drills, sector exercises, exchange mock sessions |
Reporting and closure
Post-exercise report: summary · timeline · results by objective with evidence · findings + root causes · actions (owner, date, priority) · plan updates. Hot + cold debrief; issue in 2–4 weeks; systems not people.
Actions → corrective action log → steering review → closure with evidence → re-test. Metric: actions closed on time.
Suitable = fits now · Adequate = complete · Effective = works.