U.S. flag   An unofficial archive of your favorite United States government website
Dot gov

Official websites do not use .rip
We are an unofficial archive, replace .rip by .gov in the URL to access the official website. Access our document index here.

Https

We are building a provable archive!
A lock (Dot gov) or https:// don't prove our archive is authentic, only that you securely accessed it. Note that we are working to fix that :)

This is an archive
(replace .gov by .rip)

SP 1800-11 (Draft)

Data Integrity: Recovering from Ransomware and Other Destructive Events

Date Published: September 2017
Comments Due: November 6, 2017 (public comment period is CLOSED)
Email Questions to: di-nccoe@nist.gov

Author(s)

Timothy McBride (NIST), Michael Ekstrom (MITRE), Lauren Lusty (MITRE), Julian Sexton (MITRE), Anne Townsend (MITRE)

Announcement

Constant threats of destructive malware, ransomware, malicious insider activity, and even honest mistakes create the imperative for organizations to be able to quickly recover from an event that alters or destroys data. Businesses must be confident that recovered data is accurate and safe. The National Cybersecurity Center of Excellence (NCCoE)—in collaboration with members of the business community and vendors of cybersecurity solutions—created an example solution to address these complex data integrity challenges.

Multiple systems need to work together to prevent, detect, notify, and recover from events that corrupt data. This project explores methods to effectively recover operating systems, databases, user files, applications, and software/system configurations. It also explores issues of auditing and reporting (user activity monitoring, file system monitoring, database monitoring, and rapid recovery solutions) to support recovery and investigations. To address real-world business challenges around data integrity, the example solution is composed of open-source and commercially available components.  

The goal of this building block effort is to help organizations confidently identify: 

  • Altered data, as well as the date and time of alteration
  • The identity/identities of those who alter data
  • Other events that coincide with data alteration
  • Any impact of the data alteration
  • The correct backup version (free of corrupted data) for data restoration

Abstract

Keywords

data recovery; malware; ransomware; data integrity; business continuity
Control Families

None selected

Documentation

Publication:
Draft SP 1800-11 files

Supplemental Material:
None available

Document History:
09/06/17: SP 1800-11 (Draft)
09/22/20: SP 1800-11 (Final)

Topics

Security and Privacy
malware