Ready reckoner
ISO 22301 clause 8.4
| Sub-clause | Requirement |
|---|---|
| 8.4.1 | Plans and procedures from strategies; response structure enabling timely warning and communication; plans specific, precise, actionable |
| 8.4.2 | Teams with roles, authority, competence, alternates; able to assess · use thresholds · activate · plan · prioritise (life safety first) · monitor · activate solutions · communicate; procedures incl. activation and stand-down |
| 8.4.3 | Warning + communication: what/when/whom/how · receive + respond (incl. risk advisories) · means available in disruption · emergency responders · media · record disruption, actions, decisions · alerting · interoperability · exercised |
| 8.4.4 | BC plans collectively: actions within timeframes + monitoring · thresholds + activation · delivery at agreed capacity · immediate consequences (welfare, further loss, environment). Each: purpose/scope/objectives · roles · actions · activation info · interdependencies · resources · reporting · stand-down. Usable and available |
| 8.4.5 | Documented processes to return from temporary measures to normal |
Response levels
| Level | Team | Focus |
|---|---|---|
| Strategic (gold) | Crisis management team | Strategy, regulators, media, ransom, funding |
| Tactical (silver) | Incident management team | Priorities, resources, sitreps |
| Operational (bronze) | Recovery teams | Plans and runbooks |
Separate purposes; incident manager links levels; scale to the event. Guidance: ISO 22320 (incident management), ISO 22361 (crisis management).
Thresholds in judgeable terms: service down X min · near tolerance · suspected cyber compromise · safety · media/regulator inquiry. Named activators + deputies. Bridge independent of corporate systems.
Running it: fixed agenda · sitreps on schedule · decision log (time, decision, options, rationale, owner) · shift rotation · stand-down criteria.
Communication
Matrix: staff · customers · regulators · operators/exchanges · partners · corporate customers · media · board · emergency services → owner · template · approval · timing · fallback.
Make it work: notification tool + status page outside your infrastructure · out-of-band voice · pre-approved templates · trained spokespeople · regional languages · social media monitoring.
Principles: early · accurate · tell people what to do · promise next update and keep it · consistent · empathetic · close the loop.
BC plans
Plan set: crisis plan + CCMP · IR plan · comms plan · emergency plans · BC plan per critical operation · IT DR plan per service. Cross-reference; don't duplicate contacts.
Usable: 5–10 pages · time-phased checklists (0–1 h, 1–4 h, 4–24 h, 24 h+) · roles not names · explicit decision points · step-by-step workarounds · resource-loss based + cyber annex · version/date/owner · offline.
IT DR
SP 800-34 ISCP: supporting info → activation + notification → recovery → reconstitution → appendices. ISO/IEC 27031:2025: ICT readiness (requirements, design, implement, test, monitor).
Runbook: preconditions · numbered steps · estimated times · owners · verification · rollback · links to break-glass process.
Declaring a disaster: who + deputies · criteria · max decision time (SEBI MII: declare 30 min, restore 45 min) · cyber precondition (DR clean) · log the time.
Sequence by dependencies (identity, DNS, keys → DB → apps → feeds → monitoring). Sum of steps vs RTO → report gaps. Keep current: change management · IaC + drift detection · test after change.
Return to BAU
Stabilise → restore → fail back as planned change (reverse replication, freeze, rollback, clean primary) → backlog + reconciliation (order, all channels, control totals) → customers (correct, waive, explain) → stand down.
Regulators: follow-up and final reports with RCA within set periods; record tolerance breaches.
Post-incident review: blameless + rigorous · timeline from log · actual vs plan · root causes · actions with owners/dates · update BIA/risk/strategies/plans.