Ransomware recovery plan: before and after an attack

Key takeaways

  • A ransomware recovery plan should name decision-makers, rank critical services, protect backups, and set recovery time and recovery point objectives validated by timed exercises.
  • Keep multiple backup copies including an offline, immutable one, use separate administrative accounts, and test restores, since attackers may target the backups themselves.
  • After discovering ransomware, isolate affected systems in a coordinated way and preserve evidence such as logs, memory captures and ransom notes before rebuilding.
  • Restore services through gates: build a clean recovery environment, choose and validate a restore point, rebuild and remove attacker access, then test the business service.

A ransomware recovery plan defines how an organization will protect its recovery options before an attack, contain damage during an incident, and restore trusted business services afterward. It connects people, decisions, backups, security controls, and business priorities—not just the steps for restoring files. This guide explains how to build and exercise that plan, then use it without rushing compromised systems back into production. (csrc.nist.gov)

What should a ransomware recovery plan include?

A ransomware recovery plan should include named decision-makers, critical service priorities, protected backups, containment procedures, evidence preservation, clean rebuilding instructions, communication responsibilities, and measurable conditions for returning services to operation. It must remain accessible when normal systems are unavailable. NIST recommends defined recovery roles, a tested backup and restoration strategy, and an up-to-date list of internal and external contacts. (csrc.nist.gov)

The plan should connect three activities without treating them as interchangeable:

  • Incident response: Investigate the compromise, contain the attacker, preserve evidence, and remove unauthorized access.
  • Disaster recovery: Rebuild infrastructure and restore applications, configurations, and data.
  • Business continuity: Keep essential work operating through approved alternatives while technology remains unavailable.

These activities need coordinated ownership. Restoring a database, for example, does not establish that its contents are trustworthy or that the business can safely use the application connected to it. Recovery planning should account for both technical restoration and the validation needed to resume operations. (csrc.nist.gov)

Ransomware also creates a confidentiality problem when attackers steal information. Recovering encrypted files does not resolve potential exposure of customer records, employee information, or intellectual property. Backup protection therefore belongs within a broader cyber resilience strategy that also addresses unauthorized access, investigation, and communication. (ncsc.gov.uk)

For practical use, organize your documentation into two layers. Keep a short operational checklist for the incident commander, with contacts, immediate actions, and decision authority. Support it with technical runbooks that explain how individual services are rebuilt, tested, and released. This is a suggested structure: adapt it to your team rather than producing a document too large to navigate under pressure.

Before an attack: establish business priorities and dependencies

Start with the services your organization must deliver, then identify the technology supporting them. A list of servers alone cannot explain which outage creates a safety issue, stops customer transactions, or prevents employees from working. NIST’s contingency planning guidance uses business impact analysis to connect recovery priorities with operational needs. (csrc.nist.gov)

Define the minimum acceptable operation

For each essential service, describe the smallest safe and useful operation you could sustain during recovery. This is a planning recommendation, not a universal technical standard. The description should be concrete enough that a business owner can approve it and a recovery team can build toward it.

For an order-processing service, your planning record might specify which transactions must remain possible, which customers require priority handling, and which activities can wait. For a public-facing service, it might identify an alternative intake channel and the information staff need to operate it. Do not label a workaround acceptable until its owner has considered access restrictions, recordkeeping, and later reconciliation.

Use a service worksheet with these fields:

Planning field What to record
Business owner The person authorized to accept reduced service and approve its return
Essential outcome The work that must continue, expressed in business terms
Technology dependencies Identity, networking, applications, databases, devices, and external providers
Recovery target Approved restoration timing and acceptable data loss
Temporary procedure An authorized alternative, including its limitations
Acceptance evidence Tests and records required before normal use resumes

Keep the worksheet focused on decisions. “Restore the finance server” leaves unanswered whether staff can authenticate, reach the application, produce accurate records, or complete the next business task. Documenting the service outcome makes those missing dependencies easier to challenge during an exercise.

Set recovery objectives that can be tested

A recovery time objective, or RTO, defines the recovery period your organization is targeting before disruption negatively affects its mission or business processes. A recovery point objective, or RPO, identifies the point in time to which data must be recovered. In practical planning, RPO expresses the amount of recent data loss the business can tolerate. (csrc.nist.gov)

Treat both as requirements to validate, not promises created by a backup schedule. As an illustrative example, a business might request a four-hour RTO and a one-hour RPO for an application. That request should lead to a timed exercise covering access, infrastructure, data restoration, application startup, and business testing—not simply confirmation that hourly backups exist.

Record the result honestly. If the test takes longer than the approved objective, either improve the recovery capability or have the business reconsider its requirement. Avoid leaving an ambitious target in the plan while everyone informally expects a slower recovery.

Map the foundations needed for restoration

Include identity services, name resolution, network configurations, virtualization management, cloud administration, certificates, and access to recovery tools in your dependency review. Microsoft’s ransomware response guidance emphasizes identifying application dependencies and available backups of applications, configurations, and data. (learn.microsoft.com)

A useful exercise is to ask a technician to explain how recovery begins when the normal sign-in service is unavailable. Then repeat the question for the password vault, backup console, and network documentation. Store protected copies of essential network and asset information separately from production systems so responders can access them during a major disruption. (ncsc.gov.uk)

Build backup and recovery capabilities that withstand compromise

Backups need protection from the same attacker who may control production systems. MITRE recommends hardening backup systems, isolating backup copies, using secure storage, and testing restoration. Design backup and recovery around the loss of normal administrative access, not only an accidental deletion or failed disk. (attack.mitre.org)

Separate copies, access, and administration

The FBI recommends maintaining multiple copies of critical data, including an offline, immutable copy, alongside separate administrative accounts and secured backup consoles. The practical objective is to prevent one compromised account or environment from eliminating every usable recovery option. (fbi.gov)

Review separation at several levels:

  • Data: Identify which copies remain available if production storage is encrypted or deleted.
  • Identity: Establish recovery access that does not depend entirely on the affected corporate sign-in system.
  • Administration: Restrict who can change backup settings, retention, and access policies.
  • Location: Account for loss of a facility or region as well as malicious activity.
  • Recovery material: Protect the configurations, installation resources, and documentation required to rebuild services.

Use those categories as review prompts, not as proof that a design is secure. Cloud architecture guidance from CISA recommends considering separate regions, tenancies, least privilege, and separation of duties when protecting backup data. Have your technical team explain how those boundaries work in your actual environment. (cisa.gov)

For example, storing another copy elsewhere is helpful, but your review should still ask who can delete it and how responders will retrieve it. Require a demonstration using the access method intended for an emergency. A diagram showing separation is not a substitute for a successful restore.

Verify what immutable storage actually protects

Immutable storage limits alteration or deletion, but its protection depends on the service and configuration. Amazon S3 Object Lock, for example, uses a write-once-read-many model and applies protection to specified object versions. Its retention modes provide different controls, so a product label alone does not explain what an administrator can change. (docs.aws.amazon.com)

Ask the person responsible for backup storage to document the applicable retention settings, privileged exceptions, and account-level dependencies. Test a permitted, nonproduction scenario in which an administrator attempts a destructive change. Keep the result with your recovery evidence, including any permissions that allowed the change or controls that prevented it.

Also confirm how you will read the stored data. The UK National Cyber Security Centre warns that destroying or modifying encryption keys can prevent access to encrypted backups even when the backup data itself remains intact. Protect key management and emergency access as part of the recovery design. (ncsc.gov.uk)

Retain versions and monitor destructive changes

Your recovery team needs a choice of restore points, not just the most recent copy. The NCSC recommends version history and retention arrangements that allow recovery from an earlier backup when later versions become corrupted. Select retention based on your organization’s risk and recovery requirements rather than assuming the newest version will always be usable. (ncsc.gov.uk)

Build a monitoring checklist around changes that could undermine recovery:

  • Backup jobs stopping unexpectedly or repeatedly failing.
  • Attempts to delete large amounts of backup data.
  • Changes to retention periods or encryption policies.
  • Changes to privileged accounts or administrative access.
  • Alerts that no longer reach the people responsible for responding.

The NCSC identifies these kinds of significant changes as reasons to raise alerts, including unsuccessful attempts. It also stresses that alerts need a follow-on incident management process. Assign an owner and escalation route rather than relying on a message that someone might eventually read. (ncsc.gov.uk)

For software-as-a-service applications, check exactly what the provider’s recovery mechanisms cover. Do not assume that built-in retention or recovery features constitute a complete backup of your critical information. Document coverage, limitations, and the steps needed to recover the records your organization depends on. (ncsc.gov.uk)

Assign authority, communications, and outside support

Recovery decisions should not depend on discovering who has authority during an outage. Name the people who can declare an incident, approve disruptive containment, authorize external help, prioritize restoration, and accept a service back into operation. NIST recommends integrating incident response responsibilities throughout cybersecurity risk management rather than treating response as an isolated technical activity. (csrc.nist.gov)

For a smaller organization, one person may hold several responsibilities. The important distinction is between making a technical recommendation, approving its business consequences, and recording the decision. Use the following allocation as a starting point, then assign named people and alternates.

Responsibility Suggested accountable role Decision to document
Incident coordination Incident commander Activation, priorities, assignments, and escalation
Containment and investigation Security lead Isolation, evidence collection, and remediation recommendations
Technical restoration Recovery lead Rebuild sequence, restore points, and technical testing
Operational acceptance Business service owner Workarounds, reduced service, and return to normal use
External obligations Legal or privacy lead Notification assessment and approved disclosures
Stakeholder updates Communications lead Audience, message, approval, and next update

Maintain an offline contact list covering internal leaders, technical providers, incident response specialists, relevant authorities, and other support your organization expects to use. NIST specifically recommends keeping internal and external ransomware contacts current and understanding each contact’s recovery role. Test the list rather than assuming a saved number reaches an available responder. (csrc.nist.gov)

Agree on an alternative communication method before corporate email or chat becomes unavailable. CISA’s ransomware guidance recommends out-of-band communication during coordinated isolation because attackers may monitor normal organizational communications. Keep sensitive response details within approved channels and make sure participants know which channel to use. (cisa.gov)

Prepare a simple update template: confirmed impact, actions underway, current service availability, decisions required, and the next update time. Treat estimates as estimates. This format gives leaders something useful to communicate without pressuring technical staff to invent a restoration deadline.

Before an incident, also review how outside help will be engaged. Record any internal procurement steps, contract contacts, access arrangements, and approvals that could delay assistance. This is an operational preparation task: the plan should tell the incident commander how to activate support, not merely name a provider.

Exercise the plan under realistic failure conditions

Test decision-making and technical recovery separately, then bring them together. A discussion exercise can expose unclear authority or missing communication procedures; it cannot demonstrate that an application actually restores. CISA provides tabletop exercise resources, while NIST recommends regularly exercising incident recovery plans and testing restoration strategies. (cisa.gov)

Run a decision-focused tabletop

Use a hypothetical scenario that challenges your own assumptions. Start with a suspicious encryption alert, then introduce missing corporate email, an unavailable administrator, and uncertainty about the latest backup. Ask participants to use the plan and record where they have to improvise.

Suggested discussion prompts include:

  1. Who can approve network isolation when it interrupts an essential service?
  2. How will the incident commander reach responders without corporate messaging?
  3. Who decides which business service returns first?
  4. What information is needed before issuing an external update?
  5. What happens if the preferred recovery provider cannot assist immediately?

Keep the exercise focused on actions and decisions rather than testing individual memory. Give each unresolved issue an owner and a practical next step. A shorter exercise that produces corrected contacts and clarified authority is more useful than an elaborate scenario whose findings are never addressed.

Restore an entire service, not just a sample file

Technical exercises should establish whether the recovery procedure can restore the intended business capability. The FBI recommends measuring restoration time and addressing gaps. NIST’s data integrity recovery work also emphasizes confidence in recovered information, not merely the availability of restored files. (fbi.gov)

For a suggested test record, capture the starting assumptions, backup version, access method, infrastructure steps, dependencies, elapsed time, and acceptance results. Include a business task such as opening a record, completing a transaction, or generating an expected output. Have the relevant owner identify what would make that output trustworthy.

Test an older restore point as well as the preferred recent one. Include a scenario in which normal production access cannot be used. Record any undocumented credential, missing configuration, or specialist knowledge needed to complete the exercise; those discoveries should become runbook improvements.

For organizations with operational technology, involve the appropriate engineering and safety teams in exercise design. NIST’s OT backup guidance calls for integrating backups with change management, creating and testing them regularly, and reviewing them during recovery exercises. Do not extend an office IT test procedure to industrial equipment without suitable review. (csrc.nist.gov)

What should you do immediately after discovering ransomware?

Activate your incident response plan, isolate affected systems in a coordinated way, protect remaining recovery options, and engage qualified responders. Preserve evidence while establishing the scope of the compromise and the services affected. CISA recommends disconnecting impacted systems from networks; powering them down is a fallback when disconnection is not possible because shutdown can destroy evidence held in memory. (cisa.gov)

Treat the following sequence as a planning checklist, not a substitute for incident-specific technical judgment. Safety-critical operations and complex environments require coordination with the people responsible for their safe operation. Avoid uncontrolled changes by multiple teams working from different assumptions.

Contain the incident and establish control

Use your approved isolation methods to restrict affected devices and compromised access. Microsoft’s incident response guidance recommends assessing impacted accounts, devices, and applications, isolating compromised systems, and protecting critical systems that may still be unaffected. Qualified responders should adapt those actions to the environment and evidence available. (learn.microsoft.com)

The incident commander should establish a working record immediately. Suggested fields include the discovery time, reporting source, affected services, containment actions, action owners, and outstanding decisions. Distinguish confirmed facts from suspicions so later teams can understand why an action was taken.

Create a separate status for systems whose condition is unknown. For planning purposes, “not known to be affected” should not mean “approved for reconnection.” Require investigation or validation before moving a system into the trusted recovery environment.

Engage the technical teams and outside support identified in your plan. Provide a concise account of what was observed and what has already changed. The Canadian Centre for Cyber Security’s ransomware playbook emphasizes coordinated response, backup protection, and tested restoration rather than treating an incident as a simple file-recovery task. (cyber.gc.ca)

Preserve useful evidence before rebuilding

Responders may need system images, memory captures, security logs, ransom notes, malware samples, and records of suspicious activity. CISA advises preserving volatile or short-retention evidence that could otherwise be lost. Coordinate collection with containment so evidence handling does not become an excuse to leave ongoing damage unaddressed. (cisa.gov)

Avoid asking general staff to investigate malware or experiment with encrypted files. Have qualified personnel specify what to preserve and where to store it. CISA’s technical remediation guidance warns that premature or poorly coordinated actions can lose evidence or alert an attacker to the investigation. (content.govdelivery.com)

As an internal recordkeeping practice, document who collected each item, when it was collected, and where it is held. Keep the decision log separate from public communications. It should help responders reconstruct actions without becoming a source of unapproved speculation.

Assess recovery options without assuming payment works

Ask law enforcement or qualified responders whether a reputable decryptor exists for the identified ransomware variant. CISA notes that researchers have produced decryption tools for some variants. Any proposed tool still needs technical review and controlled testing before use on important data. (cisa.gov)

The FBI does not support paying a ransom and warns that payment does not guarantee recovery. In the United States, facilitating a ransomware payment can also create sanctions risks under Treasury guidance. Escalate payment-related questions to leadership, legal counsel, law enforcement, and other relevant advisers rather than allowing an individual administrator to make the decision. (fbi.gov)

Keep restoration work and the assessment of stolen information as separate workstreams. An organization may regain access to its systems while still needing to investigate a confidentiality breach. Do not let successful decryption or restoration close questions it cannot answer. (cisa.gov)

Restore trusted services through controlled recovery gates

Recovery should proceed through evidence-based decisions, not a race to reconnect the most systems. NIST’s cybersecurity recovery guidance emphasizes recovery planning, testing, metrics, and continuous improvement. Translate that approach into gates that your security, recovery, and business owners can apply to each service. (nvlpubs.nist.gov)

The following gates are a suggested operating model. Adjust their evidence requirements to the affected service and incident. A gate should make a decision clearer; it should not become paperwork that conceals unresolved risk.

Gate 1: establish a controlled recovery environment

Prepare a recovery environment separated from systems still under investigation. Use approved administrative access, documented network connections, and the monitoring needed to observe restored services. CISA advises taking care not to reinfect clean systems and ensuring that only clean systems enter a recovery network. (cdfifund.gov)

Record who can authorize new connections into this environment. For each exception, note why it is necessary and what safeguards apply. This gives the incident commander a way to resolve urgent business requests without allowing informal reconnections to undermine the recovery effort.

Gate 2: select and validate a restore point

Choose a backup version using the investigation, available records, and integrity checks. NIST’s recovery guidance stresses that organizations must be able to trust the accuracy and completeness of recovered data. A backup that can be read is not, by itself, evidence that its contents represent an acceptable recovery state. (nvlpubs.nist.gov)

Have the recovery team record why the selected version is appropriate and what uncertainty remains. Identify the gap between that version and the point of disruption. Ask the business owner to approve how missing work will be reconstructed or handled before the service resumes.

Where practical, test restoration in isolation before releasing the service. Include application-specific checks rather than relying entirely on a general malware scan. The acceptance record should explain both what was tested and what the tests could not establish.

Gate 3: rebuild and address unauthorized access

Rebuild affected systems using trusted installation material or approved images, and address the vulnerabilities and persistence mechanisms identified during response. Microsoft recommends coordinated remediation of compromised identities and infrastructure; system restoration alone does not establish that attacker access has been removed. (learn.microsoft.com)

Make credential and access remediation an assigned workstream. Document which accounts, secrets, and integrations were assessed, what was changed, and who approved exceptions. Avoid a vague instruction to “reset everything” without a sequence that accounts for application dependencies and emergency access.

Keep the remediation record connected to the investigation. If responders discover another affected account or management system, revisit the relevant recovery decisions. Do not assume an earlier approval remains valid when the underlying evidence changes.

Gate 4: validate the business service

Test the complete workflow with the business owner. Suggested checks include authorized sign-in, access to required records, a representative transaction, expected outputs, and confirmation that integrations behave as intended. Record the result against the acceptance criteria established before the incident.

Also reconcile information created through temporary procedures. The NCSC advises planning how newly generated data will be validated and integrated with restored data to establish a single correct dataset. Assign responsibility for duplicates, missing transactions, and conflicting versions rather than leaving each department to resolve them independently. (ncsc.gov.uk)

Gate 5: reconnect gradually and confirm ownership

Use a documented release decision for each service. Identify its business owner, technical owner, monitoring arrangements, known limitations, and escalation route. Where appropriate, begin with a controlled group of users before widening access; treat that rollout pattern as a design choice to test in your exercises.

Record any conditions that would pause restoration or reverse a release. Those conditions might include unexplained activity, failed integrity checks, or unacceptable business results. Make sure someone is available to act on them rather than interpreting initial availability as the end of recovery.

Manage communications, obligations, and ongoing business work

Provide updates that distinguish service availability from investigation findings. NIST recommends coordinating recovery communications with internal and external parties, updating senior leadership, following applicable information-sharing arrangements, and using approved public messaging. A service can return before every incident question has been resolved. (nvlpubs.nist.gov)

Use audience-specific messages. Employees need approved workarounds and instructions for reporting suspicious activity. Customers need accurate information about service access and any actions they should take. Leadership needs unresolved risks, resource requirements, and decisions—not an unfiltered stream of technical observations.

A practical update can follow this structure:

  • Confirmed impact: Services or information known to be affected.
  • Current operation: What is available, restricted, or operating through a workaround.
  • Recovery activity: The stage reached and the next validation step.
  • Uncertainty: Questions still under investigation, clearly identified as such.
  • Next update: A scheduled communication point, even if recovery is incomplete.

Have legal or privacy counsel assess notification duties and contractual requirements for the actual incident. Requirements vary, and operational recovery does not eliminate the need to assess information exposure. For example, HHS provides ransomware-specific guidance for organizations subject to HIPAA, including contingency planning and breach-related considerations. (hhs.gov)

Keep broader emergency planning connected but distinct. The supplied search phrase “breathitt county ky fema dr-4860 recovery plan ransomware megaproject” should not be treated as evidence of a ransomware project. FEMA-4860-DR concerns Kentucky severe storms, winds, flooding, landslides, and mudslides, declared on February 24, 2025, and includes Breathitt County—not a ransomware recovery declaration. (public-inspection.federalregister.gov)

For organizations managing both physical disaster recovery and cyber attack recovery, use separate incident records, technical procedures, and obligation assessments. Coordinate shared resources and leadership decisions through the broader continuity plan. This keeps similar terminology from obscuring very different recovery tasks.

How should you evaluate data recovery solutions?

Evaluate data recovery solutions by whether they can restore your essential services under your expected attack conditions, not by feature lists alone. Assess protection against destructive changes, independent recovery access, usable version history, key management, and tested restoration. The NCSC’s ransomware-resistant backup principles provide a basis for questioning suppliers about these capabilities. (ncsc.gov.uk)

Turn procurement discussions into demonstrations. Give prospective providers a representative service and a failure scenario, then ask them to show the recovery process. Use the same scenario when reviewing an existing service so comparisons reflect your requirements rather than different sales presentations.

A suggested evaluation checklist includes:

  • Coverage: Identify the applications, configurations, identities, and data included—and excluded.
  • Access: Demonstrate recovery when normal corporate sign-in is unavailable.
  • Protection: Show how deletion, retention changes, and privileged exceptions are controlled.
  • Restoration: Demonstrate the required recovery granularity and complete service workflow.
  • Evidence: Provide test results, timestamps, limitations, and responsibilities.
  • Support: Explain how incident assistance is activated and what the customer must supply.

Ask for documented boundaries between the supplier’s work and yours. A provider may operate storage while your team remains responsible for application validation, business reconciliation, or recovery decisions. Write those assignments into the runbook so an emergency does not become a debate about scope.

For managed services, review backup preparation and testing with the provider. NIST’s managed service provider guidance addresses conducting, maintaining, and testing backup files, including considerations when selecting backup services or products. Treat recurring test evidence as part of service oversight, not merely something requested during initial procurement. (csrc.nist.gov)

Finally, assess affordability through a realistic exercise and a clear statement of required resources. Include the staff time, infrastructure, specialist assistance, and operating procedures your chosen design requires. Avoid selecting a recovery target the organization cannot support in practice.

Maintain a practical recovery record and improvement cycle

Keep the plan usable by maintaining a compact control record alongside detailed runbooks. The following template is a suggested starting point. It should point responders to authoritative documents rather than duplicate every technical instruction.

Record Minimum useful content
Plan ownership Named owner, approver, alternates, and review history
Activation Incident triggers, declaration authority, and escalation route
Critical services Business priorities, dependencies, objectives, and owners
Recovery resources Backup locations, access procedure, rebuild material, and provider contacts
Response record Timeline, evidence references, decisions, and assigned actions
Release approval Security checks, business tests, limitations, and acceptance
Improvement log Finding, corrective action, owner, due date, and retest result

After an incident or exercise, compare the plan with what actually happened. Identify missing access, inaccurate documentation, unexpected dependencies, delayed decisions, and failed tests. NIST’s recovery guidance recommends using lessons learned and recovery metrics to improve future capability. (nvlpubs.nist.gov)

Measure outcomes that help someone make a decision. Suggested measures include time to activate the team, time to obtain recovery access, time to restore an essential service, and the number of unresolved acceptance issues. Keep business availability distinct from server startup so reporting does not reward incomplete recovery.

Assign corrective actions and verify them through another test. Updating a paragraph is not enough when the underlying problem is an inaccessible backup or an undocumented application dependency. Close the finding only when the responsible owner can demonstrate that the intended recovery step works.

A workable ransomware recovery plan ultimately answers three practical questions: what must return first, what evidence makes it trustworthy, and who can approve its use. Build around those decisions, protect the resources needed to carry them out, and exercise the process before you depend on it. That turns a disaster recovery plan from stored documentation into a repeatable operational capability.

Sources

  1. csrc.nist.gov: NIST Tips for Preparing for Ransomware Attacks
  2. SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems | CSRC
  3. Ransomware-resistant backups | National Cyber Security Centre
  4. Recovery Time Objective - Glossary | CSRC
  5. Microsoft Incident Response ransomware approach and best practices | Microsoft Learn
  6. Disruptive cyber attacks – reducing their impact, reducing the risk | Preparing for highly disruptive cyber incidents | 3. Prepare your technical recovery capability | National Cyber Security Centre
  7. Data Backup, Mitigation M1053 - Enterprise | MITRE ATT&CK®
  8. fbi.gov: Ten actions to improve cyber resiliency
  9. cisa.gov: Tic 3.0 cloud use case 508c
  10. Locking objects with Object Lock - Amazon Simple Storage Service
  11. Ransomware-resistant backups | Principles for ransomware-resistant cloud backups | National Cyber Security Centre
  12. ncsc.gov.uk: Principles for ransomware resistant cloud backups
  13. Using online services safely | Back up your organisation’s critical data | National Cyber Security Centre
  14. SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management: A CSF 2.0 Community Profile | CSRC
  15. cisa.gov: CISA MS ISAC Ransomware%20Guide S508C
  16. cisa.gov: Ctep fact sheet v. 11 16 2021 final
  17. SP 1339, OT Backup Quick Start Guide | CSRC
  18. Ransomware playbook (ITSM.00.099) - Canadian Centre for Cyber Security
  19. AA20-245A: Technical Approaches to Uncovering and Remediating Malicious Activity
  20. fbi.gov: Ransomware
  21. cisa.gov: CISA Fact Sheet Protecting Sensitive and Personal Information from Ransomware Caused Data Breaches 508C
  22. nvlpubs.nist.gov: NIST.SP.800 184
  23. cdfifund.gov: StopRansomware Guide 508C v3
  24. nvlpubs.nist.gov: NIST.SP.1800 11
  25. nvlpubs.nist.gov: Nist.sp.800 61r3
  26. hhs.gov: Index
  27. public-inspection.federalregister.gov
  28. Protecting Data from Ransomware and Other Data Loss Events: A Guide for Managed Service Providers to Conduct, Maintain, and Test Backup Files | CSRC