Ready reckoner
ISO 22301 clause 8.2
| Sub-clause | Must do |
|---|---|
| 8.2.1 | Systematic processes for BIA and risk assessment; review at planned intervals and on significant change |
| 8.2.2 BIA | Define impact types and criteria · identify activities · assess impacts over time · find when impact becomes unacceptable · set prioritised timeframes at minimum capacity · determine prioritised activities · resources · dependencies (incl. suppliers) |
| 8.2.3 Risk | Identify risks of disruption to prioritised activities and resources · analyse + evaluate · decide which need treatment → strategies (8.3) |
Running a BIA (ISO/TS 22317)
Plan → collect → assess impact → set priorities → dependencies → validate + approve → repeat.
| Level | Question |
|---|---|
| Product / service | Which services matter; MTPD per service |
| Process | Which processes, in what order |
| Activity | RTOs, minimum staff, systems, suppliers |
Start at product level; go deeper only where priority is high.
Impact categories: customer harm · financial · regulatory/legal · reputation · market/partners · backlog. Time buckets matched to the business. Use worst credible timing (EMI dates, month-end, expiry days).
Errors: everything critical · RTO = current IT capability · ignoring peaks · missing upstream/downstream · stale BIA.
The numbers
| Term | How to set |
|---|---|
| MTPD | First time bucket where any category hits "unacceptable" |
| RTO | Inside MTPD, with margin for detection, problems, work recovery (often ≤ ½–⅔ MTPD for critical) |
| MBCO | Minimum acceptable service while recovering; enables cheaper strategies |
| RPO | From what data can be recreated; zero RPO needs replication plus protection from replicated corruption |
| Tolerance | Per critical operation, from end user's view, board-approved; time · volume · service level · data integrity; may be stricter than analysis |
Regulatory numbers (e.g. SEBI RTO 2 h / RPO 15 min) = minimum constraints. BIA shorter → keep BIA. Not critical in regulator's sense → document reasoning.
Consistency test: tolerance ↔ supporting RTOs ↔ achieved drill times.
Recovery tiers (example)
| Tier | RTO | RPO |
|---|---|---|
| 1 | ≤ 4 h | near-zero – 15 min |
| 2 | ≤ 8 h | ≤ 1 h |
| 3 | ≤ 24 h | ≤ 4 h |
| 4 | ≤ 5 days | ≤ 24 h |
Dependency mapping
Critical operation → activities → people · technology · information · premises · suppliers. Sources: interviews, CMDB, architecture (incl. identity, DNS, certificates, secrets), contract register, incident history. Walk the customer journey.
Look for SPOFs · shared · hidden · concentrated dependencies · mismatched RTO/RPO. Recovery profile = resources needed over time. Keep maps alive via change management.
Scenarios
Severe but plausible: happened or nearly happened in the sector, or threat intel says it could.
Library must cover: all resource families · cyber that defeats failover (ransomware reaching backups, compromised admin) · third-party and concentration · peak timing · combinations. Review yearly and after major sector incidents.
For each breach of tolerance: why · fix · decision (treat with date, or board-accepted with remediation). Knowing where you would breach is the point.
Third parties
| Tier | Test | Do |
|---|---|---|
| Critical | Tier 1 support or no substitute in tolerance | Deep assessment · contract RTO/RPO · joint DR test · notice · exit plan |
| Important | Tier 2–3; substitute exists | Questionnaire + evidence · contract terms |
| Standard | No priority impact | Standard terms |
Tier by impact and replaceability, not spend. Ask critical suppliers for: BIA extract for your service · DR test results · ransomware recovery design · nth parties · incident notice (2–4 h) · test participation · exit support.
Concentration: firm-level (one provider, many critical ops or most volume) · sector-level (many REs, one provider; regulators watch). Substitutability: active · warm · manual/degraded · planned exit. Exit plan: triggers · data retrieval · steps + timeline · roles · service during transition · cost · tested (tabletop).
Regulatory hooks: RBI IT outsourcing Directions · RBI op. resilience guidance (third/nth party, substitutability) · SEBI CSCRF supply chain · DORA register, contract terms, exit, concentration.