markdowneditor

Business Continuity Plan (BCP)

BIA (RTO/RPO) + continuity + comms plan

使い方: BIA first (MTPD/RTO/RPO are derived, not invented). A BCP that's never exercised is a hypothesis, and auditors ask for exercise records.

プレビュー

Business Continuity Plan (BCP)

ISO 22301-aligned + ISO/IEC 27001:2022 A.5.29 (continuity during disruption) + A.5.30 (ICT readiness). Write BEFORE the disaster.

FieldValue
Document IDDOC-BCM-001
OwnerBusiness continuity lead
TestedExercise date
Next reviewYYYY-MM-DD

1. Business impact analysis (BIA)

What breaks, how bad, how fast:

ProcessCritical functionMax tolerable downtime (MTPD)Recovery time objective (RTO)Recovery point objective (RPO)Dependencies
ProcessfunctionN hours/daysN hoursN hours data losssystems/staff
Revenue opsorder processing4h2h15minpayment, DB
Supportcustomer response24h8h1hCRM
Productservice uptime1h30min0infra, data

2. Threat scenarios

ScenarioLikelihoodMTPD impactResponse plan
Office inaccessiblemediumlow – remote workactivate WFH
Cloud region downlowhighfailover region
Key staff unavailablemediummediumcross-training + runbooks
Vendor outagemediumper contractbackup vendor
Cyber incidentmediumhighIR plan DOC-ISMS-020

3. Continuity strategies

Critical functionStrategyRecovery steps
Functionworkaround/alternatestep-by-step

4. Incident roles & activation

RolePersonBackupContact
BC coordinator@namephone
Operations lead@name
Communications@name

Activation: who declares "business continuity mode" – criteria.

5. Recovery procedures per scenario

ScenarioImmediate actionsRecovery stepsValidation
Office lossevacuate, notifyWFH, rerouteops check
System lossdeclare incidentfailover, restoreverify data

6. Communications plan

  • Internal: staff notification tree, status updates
  • External: customer comms, media per PR policy
  • Escalation: when/how to notify clients per contract SLA

7. Exercise & maintenance

  • Tabletop: annually
  • Live test: annually per scenario
  • Review: after every activation + annual

関連テンプレート