Data remanence

From Wikipedia, the free encyclopedia

Data remanence is the residual representation of digital data that remains even after attempts have been made to remove or erase the data. This residue may result from data being left intact by a nominal file deletion operation, by reformatting of storage media that does not remove data previously written to the media, or through physical properties of the storage media that allow previously written data to be recovered. Data remanence may make inadvertent disclosure of sensitive information possible should the storage media be released into an uncontrolled environment (e.g., thrown in the bin (trash) or lost).

Various techniques have been developed to counter data remanence. These techniques are classified as clearing, purging/sanitizing, or destruction. Specific methods include overwriting, degaussing, encryption, and media destruction.

Effective application of countermeasures can be complicated by several factors, including media that are inaccessible, media that cannot effectively be erased, advanced storage systems that maintain histories of data throughout the data's life cycle, and persistence of data in memory that is typically considered volatile.

Several standards exist for the secure removal of data and the elimination of data remanence.

Causes[edit]

Many operating systems, file managers, and other software provide a facility where a file is not immediately deleted when the user requests that action. Instead, the file is moved to a holding area (i.e. the "trash"), making it easy for the user to undo a mistake. Similarly, many software products automatically create backup copies of files that are being edited, to allow the user to restore the original version, or to recover from a possible crash (autosave feature).

Even when an explicit deleted file retention facility is not provided or when the user does not use it, operating systems do not actually remove the contents of a file when it is deleted unless they are aware that explicit erasure commands are required, like on a solid-state drive. (In such cases, the operating system will issue the Serial ATA TRIM command or the SCSI UNMAP command to let the drive know to no longer maintain the deleted data.) Instead, they simply remove the file's entry from the file system directory because this requires less work and is therefore faster, and the contents of the file—the actual data—remain on the storage medium. The data will remain there until the operating system reuses the space for new data. In some systems, enough filesystem metadata are also left behind to enable easy undeletion by commonly available utility software. Even when undelete has become impossible, the data, until it has been overwritten, can be read by software that reads disk sectors directly. Computer forensics often employs such software.

Likewise, reformatting, repartitioning, or reimaging a system is unlikely to write to every area of the disk, though all will cause the disk to appear empty or, in the case of reimaging, empty except for the files present in the image, to most software.

Finally, even when the storage media is overwritten, physical properties of the media may permit recovery of the previous contents. In most cases however, this recovery is not possible by just reading from the storage device in the usual way, but requires using laboratory techniques such as disassembling the device and directly accessing/reading from its components.

The section on complications gives further explanations for causes of data remanence.

Countermeasures[edit]

Main article: Data erasure

There are three levels commonly recognized for eliminating remnant data:

Clearing[edit]

Clearing is the removal of sensitive data from storage devices in such a way that there is assurance that the data may not be reconstructed using normal system functions or software file/data recovery utilities. The data may still be recoverable, but not without special laboratory techniques.[1]

Clearing is typically an administrative protection against accidental disclosure within an organization. For example, before a hard drive is re-used within an organization, its contents may be cleared to prevent their accidental disclosure to the next user.

Purging[edit]

Purging or sanitizing is the physical rewrite of sensitive data from a system or storage device with the intent that the data cannot be recovered.[2] Purging, proportional to the sensitivity of the data, is generally done before releasing media beyond control, such as before discarding old media, or moving media to a computer with different security requirements.

Destruction[edit]

The storage media is made unusable for conventional equipment. Effectiveness of destroying the media varies by medium and method. Depending on recording density of the media, and/or the destruction technique, this may leave data recoverable by laboratory methods. Conversely, destruction using appropriate techniques is the most secure method of preventing retrieval.

Specific methods[edit]

Overwriting[edit]

A common method used to counter data remanence is to overwrite the storage media with new data. This is often called wiping or shredding a file or disk, by analogy to common methods of destroying print media, although the mechanism bears no similarity to these. Because such a method can often be implemented in software alone, and may be able to selectively target only part of the media, it is a popular, low-cost option for some applications. Overwriting is generally an acceptable method of clearing, as long as the media is writable and not damaged.

The simplest overwrite technique writes the same data everywhere—often just a pattern of all zeros. At a minimum, this will prevent the data from being retrieved simply by reading from the media again using standard system functions.

In an attempt to counter more advanced data recovery techniques, specific overwrite patterns and multiple passes have often been prescribed. These may be generic patterns intended to eradicate any trace signatures, for example, the seven-pass pattern: 0xF6, 0x00, 0xFF, random, 0x00, 0xFF, random; sometimes erroneously attributed to the US standard DOD 5220.22-M.

One challenge with overwriting is that some areas of the disk may be inaccessible, due to media degradation or other errors. Software overwrite may also be problematic in high-security environments, which require stronger controls on data commingling than can be provided by the software in use. The use of advanced storage technologies may also make file-based overwrite ineffective (see the discussion below under Complications).

There are specialized machines and software that are capable of doing overwriting. The software can sometimes be a standalone operating system specifically designed for data destruction. There are also machines specifically designed to wipe hard drives to the department of defense specifications DOD 5220.22-M.[3]

Feasibility of recovering overwritten data[edit]

Peter Gutmann investigated data recovery from nominally overwritten media in the mid-1990s. He suggested magnetic force microscopy may be able to recover such data, and developed specific patterns, for specific drive technologies, designed to counter such.[4] These patterns have come to be known as the Gutmann method.

Daniel Feenberg, an economist at the private National Bureau of Economic Research, claims that the chances of overwritten data being recovered from a modern hard drive amount to "urban legend".[5] He also points to the "18+1⁄2-minute gap" Rose Mary Woods created on a tape of Richard Nixon discussing the Watergate break-in. Erased information in the gap has not been recovered, and Feenberg claims doing so would be an easy task compared to recovery of a modern high density digital signal.

As of November 2007, the United States Department of Defense considers overwriting acceptable for clearing magnetic media within the same security area/zone, but not as a sanitization method. Only degaussing or physical destruction is acceptable for the latter.[6]

On the other hand, according to the 2014 NIST Special Publication 800-88 Rev. 1 (p. 7): "For storage devices containing magnetic media, a single overwrite pass with a fixed pattern such as binary zeros typically hinders recovery of data even if state of the art laboratory techniques are applied to attempt to retrieve the data."[7] An analysis by Wright et al. of recovery techniques, including magnetic force microscopy, also concludes that a single wipe is all that is required for modern drives. They point out that the long time required for multiple wipes "has created a situation where many organizations ignore the issue [altogether] – resulting in data leaks and loss."[8]

Degaussing[edit]

Degaussing is the removal or reduction of a magnetic field of a disk or drive, using a device called a degausser that has been designed for the media being erased. Applied to magnetic media, degaussing may purge an entire media element quickly and effectively.

Degaussing often renders hard disks inoperable, as it erases low-level formatting that is only done at the factory during manufacturing. In some cases, it is possible to return the drive to a functional state by having it serviced at the manufacturer. However, some modern degaussers use such a strong magnetic pulse that the motor that spins the platters may be destroyed in the degaussing process, and servicing may not be cost-effective. Degaussed computer tape such as DLT can generally be reformatted and reused with standard consumer hardware.

In some high-security environments, one may be required to use a degausser that has been approved for the task. For example, in US government and military jurisdictions, one may be required to use a degausser from the NSA's "Evaluated Products List".[9]

Encryption[edit]

Encrypting data before it is stored on the media may mitigate concerns about data remanence. If the decryption key is strong and carefully controlled, it may effectively make any data on the media unrecoverable. Even if the key is stored on the media, it may prove easier or quicker to overwrite just the key, versus the entire disk. This process is called crypto-shredding.

Encryption may be done on a file-by-file basis, or on the whole disk. Cold boot attacks are one of the few possible methods for subverting a full-disk encryption method, as there is no possibility of storing the plain text key in an unencrypted section of the medium. See the section Complications: Data in RAM for further discussion.

Other side-channel attacks (such as keyloggers, acquisition of a written note containing the decryption key, or rubber-hose cryptanalysis) may offer a greater chance of success, but do not rely on weaknesses in the cryptographic method employed. As such, their relevance for this article is minor.

Media destruction[edit]

The pieces of a physically destroyed hard disk drive.
Hard drive mechanically broken by a data destroying device (after degaussing)

Thorough destruction of the underlying storage media is the most certain way to counter data remanence. However, the process is generally time-consuming, cumbersome, and may require extremely thorough methods, as even a small fragment of the media may contain large amounts of data.

Specific destruction techniques include:

Complications[edit]

Inaccessible media areas[edit]

Storage media may have areas which become inaccessible by normal means. For example, magnetic disks may develop new bad sectors after data has been written, and tapes require inter-record gaps. Modern hard disks often feature reallocation of marginal sectors or tracks, automated in a way that the operating system would not need to work with it. The problem is especially significant in solid-state drives (SSDs) that rely on relatively large relocated bad block tables. Attempts to counter data remanence by overwriting may not be successful in such situations, as data remnants may persist in such nominally inaccessible areas.

Advanced storage systems[edit]

Data storage systems with more sophisticated features may make overwrite ineffective, especially on a per-file basis. For example, journaling file systems increase the integrity of data by recording write operations in multiple locations, and applying transaction-like semantics; on such systems, data remnants may exist in locations "outside" the nominal file storage location. Some file systems also implement copy-on-write or built-in revision control, with the intent that writing to a file never overwrites data in-place. Furthermore, technologies such as RAID and anti-fragmentation techniques may result in file data being written to multiple locations, either by design (for fault tolerance), or as data remnants.

Wear leveling can also defeat data erasure, by relocating blocks between the time when they are originally written and the time when they are overwritten. For this reason, some security protocols tailored to operating systems or other software featuring automatic wear leveling recommend conducting a free-space wipe of a given drive and then copying many small, easily identifiable "junk" files or files containing other nonsensitive data to fill as much of that drive as possible, leaving only the amount of free space necessary for satisfactory operation of system hardware and software. As storage and system demands grow, the "junk data" files can be deleted as necessary to free up space; even if the deletion of "junk data" files is not secure, their initial nonsensitivity reduces to near zero the consequences of recovery of data remanent from them.[citation needed]

Optical media[edit]

As optical media are not magnetic, they are not erased by conventional degaussing. Write-once optical media (CD-R, DVD-R, etc.) also cannot be purged by overwriting. Rewritable optical media, such as CD-RW and DVD-RW, may be receptive to overwriting. Methods for successfully sanitizing optical discs include delaminating or abrading the metallic data layer, shredding, incinerating, destructive electrical arcing (as by exposure to microwave energy), and submersion in a polycarbonate solvent (e.g., acetone).

Data on solid-state drives[edit]

Research from the Center for Magnetic Recording and Research, University of California, San Diego has uncovered problems inherent in erasing data stored on solid-state drives (SSDs). Researchers discovered three problems with file storage on SSDs:[10]

First, built-in commands are effective, but manufacturers sometimes implement them incorrectly. Second, overwriting the entire visible address space of an SSD twice is usually, but not always, sufficient to sanitize the drive. Third, none of the existing hard drive-oriented techniques for individual file sanitization are effective on SSDs.[10]: 1 

Solid-state drives, which are flash-based, differ from hard-disk drives in two ways: first, in the way data is stored; and second, in the way the algorithms are used to manage and access that data. These differences can be exploited to recover previously erased data. SSDs maintain a layer of indirection between the logical addresses used by computer systems to access data and the internal addresses that identify physical storage. This layer of indirection hides idiosyncratic media interfaces and enhances SSD performance, reliability, and lifespan (see wear leveling), but it can also produce copies of the data that are invisible to the user and that a sophisticated attacker could recover. For sanitizing entire disks, sanitize commands built into the SSD hardware have been found to be effective when implemented correctly, and software-only techniques for sanitizing entire disks have been found to work most, but not all, of the time.[10]: section 5  In testing, none of the software techniques were effective for sanitizing individual files. These included well-known algorithms such as the Gutmann method, US DoD 5220.22-M, RCMP TSSIT OPS-II, Schneier 7 Pass, and Secure Empty Trash on macOS (a feature included in versions OS X 10.3-10.9).[10]: section 5 

The TRIM feature in many SSD devices, if properly implemented, will eventually erase data after it is deleted[11][citation needed], but the process can take some time, typically several minutes. Many older operating systems do not support this feature, and not all combinations of drives and operating systems work.[12]

Data in RAM[edit]

Data remanence has been observed in static random-access memory (SRAM), which is typically considered volatile (i.e., the contents degrade with loss of external power). In one study, data retention was observed even at room temperature.[13]

Data remanence has also been observed in dynamic random-access memory (DRAM). Modern DRAM chips have a built-in self-refresh module, as they not only require a power supply to retain data, but must also be periodically refreshed to prevent their data contents from fading away from the capacitors in their integrated circuits. A study found data remanence in DRAM with data retention of seconds to minutes at room temperature and "a full week without refresh when cooled with liquid nitrogen."[14] The study authors were able to use a cold boot attack to recover cryptographic keys for several popular full disk encryption systems, including Microsoft BitLocker, Apple FileVault, dm-crypt for Linux, and TrueCrypt.[14]: 12 

Despite some memory degradation, authors of the above described study were able to take advantage of redundancy in the way keys are stored after they have been expanded for efficient use, such as in key scheduling. The authors recommend that computers be powered down, rather than be left in a "sleep" state, when not in physical control of the owner. In some cases, such as certain modes of the software program BitLocker, the authors recommend that a boot password or a key on a removable USB device be used.[14]: 12  TRESOR is a kernel patch for Linux specifically intended to prevent cold boot attacks on RAM by ensuring that encryption keys are not accessible from user space and are stored in the CPU rather than system RAM whenever possible. Newer versions of the disk encryption software VeraCrypt can encrypt in-RAM keys and passwords on 64-bit Windows.[15]

Standards[edit]

Australia
  • ASD ISM 2014, Australian Government Information Security Manual, 2014 [16]
Canada
New Zealand
  • GCSB NZISM 2016, New Zealand Information Security Manual v2.5, July 2016 [19]
  • NZSIS PSM 2009, Protective Security Manual
United Kingdom
United States
  • NIST Special Publication 800-88, Guidelines for Media Sanitization, September 2006 [1]
  • DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), February 2006 [21]
    • Current editions no longer contain any references to specific sanitization methods. Standards for sanitization are left up to the Cognizant Security Authority.[21]
    • Although the NISPOM text itself never described any specific methods for sanitization, past editions (1995 and 1997)[22] did contain explicit sanitization methods within the Defense Security Service (DSS) Clearing and Sanitization Matrix inserted after Section 8-306. The DSS still provides this matrix and it continues to specify methods.[6] As of the Nov 2007 edition of the matrix, overwriting is no longer acceptable for sanitization of magnetic media. Only degaussing (with an NSA approved degausser) or physical destruction is acceptable.
  • Army AR380-19, Information Systems Security, February 1998 [23] replaced by AR 25-2 https://armypubs.army.mil/epubs/DR_pubs/DR_a/pdf/web/ARN17503_AR25_2_Admin_FINAL.pdf (Army Publishing Directorate, 2009)
  • Air Force AFSSI 8580, Remanence Security, 17 November 2008[24]
  • Navy NAVSO P5239-26, Remanence Security, September 1993 [25]
  • IEEE 2883, IEEE Standard for Sanitizing Storage, August 2022 [26] [27] [28]

See also[edit]

References[edit]

  1. ^ a b "Special Publication 800-88: Guidelines for Media Sanitization Rev. 1" (PDF). NIST. 6 September 2012. Retrieved 2014-06-23. (542 KB)
  2. ^ Encyclopedia of cryptography and security. Tilborg, Henk C. A. van, 1947-, Jajodia, Sushil. ([2nd ed.] ed.). New York: Springer. 2011. ISBN 978-1-4419-5906-5. OCLC 759924624.{{cite book}}: CS1 maint: others (link)
  3. ^ Manual reissues DoD 5220.22-M, "National Industrial Security Program Operating. 2006. CiteSeerX 10.1.1.180.8813.
  4. ^ Peter Gutmann (July 1996). "Secure Deletion of Data from Magnetic and Solid-State Memory". Retrieved 2007-12-10. {{cite journal}}: Cite journal requires |journal= (help)
  5. ^ Daniel Feenberg. "Can Intelligence Agencies Recover Overwritten Data?". Retrieved 2007-12-10. {{cite journal}}: Cite journal requires |journal= (help)
  6. ^ a b "DSS Clearing & Sanitization Matrix" (PDF). DSS. 2007-06-28. Retrieved 2010-11-04.
  7. ^ Kissel, Richard; Regenscheid, Andrew; Scholl, Matthew; Stine, Kevin (December 2014). "Special Publication 800-88 Rev. 1: Guidelines for Media Sanitization". NIST. doi:10.6028/NIST.SP.800-88r1. Retrieved 2018-06-26. {{cite journal}}: Cite journal requires |journal= (help)
  8. ^ Wright, Craig; Kleiman, Dave; Shyaam, Sundhar R.S. (December 2008). "Overwriting Hard Drive Data: The Great Wiping Controversy". Information Systems Security. Lecture Notes in Computer Science. Vol. 5352. Springer Berlin / Heidelberg. pp. 243–257. doi:10.1007/978-3-540-89862-7_21. ISBN 978-3-540-89861-0.
  9. ^ "Media Destruction Guidance". NSA. Archived from the original on 2012-09-28. Retrieved 2009-03-01.
  10. ^ a b c d Michael Wei; Laura M. Grupp; Frederick E. Spada; Steven Swanson (February 2011). "Reliably Erasing Data From Flash-Based Solid State Drives" (PDF). {{cite journal}}: Cite journal requires |journal= (help)
  11. ^ Homaidi, Omar Al (2009). "Data Remanence: Secure Deletion of Data in SSDs". {{cite journal}}: Cite journal requires |journal= (help)
  12. ^ "Digital Evidence Extraction Software for Computer Forensic Investigations". Forensic.belkasoft.com. October 2012. Retrieved 2014-04-01.
  13. ^ Sergei Skorobogatov (June 2002). "Low temperature data remanence in static RAM". University of Cambridge, Computer Laboratory. doi:10.48456/tr-536. {{cite journal}}: Cite journal requires |journal= (help)
  14. ^ a b c J. Alex Halderman; et al. (July 2008). "Lest We Remember: Cold Boot Attacks on Encryption Keys" (PDF). {{cite journal}}: Cite journal requires |journal= (help)
  15. ^ https://www.veracrypt.fr/en/Release%20Notes.html VeraCrypt release notes, version 1.24
  16. ^ "Australia Government Information Security Manual" (PDF). Australian Signals Directorate. 2014. Archived from the original (PDF) on 2014-03-27.
  17. ^ "IT Media Overwrite and Secure Erase Products" (PDF). Royal Canadian Mounted Police. May 2009. Archived from the original (PDF) on 2011-06-15.
  18. ^ "Clearing and Declassifying Electronic Data Storage Devices". Communications Security Establishment. July 2006. Archived from the original (PDF) on 2014-08-07. Retrieved 2016-10-09.
  19. ^ "New Zealand Information Security Manual v2.5" (PDF). Government Communications Security Bureau. July 2016.
  20. ^ "ADISA: ASSET DISPOSAL & INFORMATION SECURITY ALLIANCE". Archived from the original on 2010-11-01.
  21. ^ a b "National Industrial Security Program Operating Manual" (PDF). DSS. February 2006. Archived from the original (PDF) on 2011-05-24. Retrieved 2010-09-22.
  22. ^ "Obsolete NISPOM" (PDF). January 1995. Archived from the original (PDF) on 2003-11-18. Retrieved 2007-12-07. with the Defense Security Service (DSS) Clearing and Sanitization Matrix; includes Change 1, July 31, 1997.
  23. ^ "Information Systems Security" (PDF). February 1998.
  24. ^ AFI 33-106 Archived 2012-10-22 at the Wayback Machine
  25. ^ "Remanence Security Guidebook". September 1993.
  26. ^ "IEEE Standard for Sanitizing Storage".
  27. ^ "IEEE 2883 Standard On Data Sanitization Is A Path To Storage Reuse And Recycling as published on Forbes". Forbes.
  28. ^ "IEEE P2883™ Draft Standard for Sanitizing Storage on SNIA".

Further reading[edit]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Data_remanence&oldid=1195940646"