Ransomware continuity planning answers a narrow operational question: how will priority business services continue while technology is unavailable, isolated or untrusted? It is not the malware-removal plan and it is not the technical restore runbook. The continuity team must define minimum service, safe workarounds, decision authority and the evidence required before operations move back to restored technology.
Start with minimum service, not systems
For each priority service, define the minimum outcome that must still be delivered, the maximum period it can operate in degraded mode, the people and information required, and the point at which the workaround becomes unsafe or unsustainable. Avoid generic instructions such as “work manually.” Name the transaction, queue, approval, customer commitment or regulatory obligation that must continue.
Assume the normal digital workplace may be untrusted
Ransomware can remove more than applications. Identity, email, collaboration, telephony, file shares, endpoint management and privileged administration may be unavailable or intentionally isolated. Maintain an out-of-band contact method, an offline authority list, clean-device access for essential roles and a controlled source for approved instructions. Do not copy potentially compromised files into the clean coordination environment merely to restore convenience.
Define containment-versus-continuity decision rights
Business pressure must not silently override cyber containment. Document who may approve a degraded workaround, who can stop it, which security controls cannot be bypassed, and which exceptional controls require executive risk acceptance. A useful playbook names the cyber incident lead, continuity lead, service owner, legal/privacy contacts and recovery authority and states how disagreements are escalated.
Design workarounds with reconciliation built in
Every manual or alternate-channel process should capture a unique transaction reference, time, originator, approver, value or quantity where relevant, and the system of record that must eventually be updated. Define duplicate detection and backlog ownership before an incident. A workaround that keeps service moving but creates an unreconcilable financial, safety or customer record is not a viable continuity strategy.
Set explicit stop conditions
Manual processing may fail because queues grow, staffing becomes exhausted, fraud controls weaken or source information becomes stale. Set measurable stop or escalation conditions such as backlog age, transaction volume, error rate, cash exposure, safety risk or regulatory deadline. These thresholds tell leaders when to ration service, suspend a process or invoke an alternate provider.
Use trusted recovery gates
“The server is back” is not sufficient. Before reconnecting a recovered service, confirm the recovery source is trusted, required security controls are active, identities and privileged access have been reviewed, integrations are understood, business data has been reconciled and the service owner accepts the residual risk. Reconnection order should follow business dependency and containment constraints rather than technical convenience.
Exercise the degraded operating period
Test a scenario in which normal identity, email and one critical application are unavailable at the same time. Require teams to activate clean communications, process real work samples through the workaround, record decisions, manage a growing backlog and demonstrate the handoff to recovery. Measure time to minimum service, sustainable throughput, exception/error rate and reconciliation completeness.
Evidence to retain
- priority-service minimum operating requirements and tolerances;
- clean communication and contact arrangements;
- approved workaround procedures and control exceptions;
- decision/authority matrix and stop conditions;
- exercise evidence, throughput results and unresolved actions;
- reconciliation records and trusted-recovery acceptance criteria.
Use this article when the question is how the business continues during ransomware. For recovery architecture and extended restoration sequencing, use the related ransomware business continuity planning guide.
Separate continuity decisions from technical eradication
Ransomware continuity planning must define how the organization continues priority services while cyber teams contain, investigate and eradicate the threat. Establish decision points for isolating networks, disabling identity services, suspending integrations, moving to clean communications and activating manual or alternate processing. Each decision should identify who can authorize it, what evidence is required and what business consequence is accepted.
Pre-design clean minimum-service patterns that do not depend on potentially compromised identity, endpoints or shared administration tooling. Protect emergency contact data, essential records, recovery credentials and approved offline procedures. Manual workarounds need transaction numbering, approval limits, privacy controls and a reconciliation method so temporary operations do not create a second incident when systems return.
Prove clean recovery and controlled re-entry
Recovery acceptance must cover more than server availability. Define gates for trusted identity, known-good backups, malware scanning, privileged-access reset, application integrity, data consistency, integration validation, monitoring and business-owner acceptance. Prioritize services by business dependency rather than by whichever system is easiest to restore first.
Exercise a scenario in which the preferred recovery point is unusable and a secondary point must be selected. Measure decision time, data-loss exposure, minimum operating capacity, backlog growth and reconciliation effort. Re-entry to normal operations should be staged, with explicit stop conditions if indicators of compromise reappear or recovered data fails validation.
After exercises or incidents, convert failed assumptions into owned corrective actions with due dates and retesting. Evidence should show that continuity, cyber response, disaster recovery, communications and executive crisis management can operate as one coordinated recovery system under ransomware conditions.
Coordinate external dependencies and communications
Include critical suppliers, cyber-response partners, insurers where applicable, regulators, customers and law-enforcement interfaces in the communication plan. Pre-agree what can be shared, who approves messages and how updates will continue if corporate email or collaboration tools are unavailable. Recovery estimates should be labelled as assumptions until validated by technical and business owners.
Define business stop conditions as carefully as restart criteria. If manual processing creates unsafe decisions, uncontrolled financial exposure, privacy risk or irreconcilable records, leaders need authority to suspend that activity even when demand is high. This prevents continuity pressure from overriding essential controls during a cyber crisis.
Related BCM.Center resources: Ransomware Business Continuity Planning · Immutable Backups and Ransomware Recovery.
Ransomware Continuity Planning: operational continuity playbook for keeping priority services running while systems, identities or data are unavailable or untrusted during ransomware. Consult NIST SP 800-34 Rev. 1 for its published scope in federal information-system contingency planning.
CISA’s ransomware guidance addresses preparation, incident response and recovery. In practice, reopening access before validating identity controls, malicious persistence and data integrity may restore throughput while reintroducing the attacker’s path. CISA #StopRansomware Guide.