How would you ensure secure media sanitization SSD?

Domain 7: Operations Security

Eric Conrad, ... Joshua Feldman, in Eleventh Hour CISSP (Second Edition), 2014

Shredding

A simple form of media sanitization is shredding, a type of physical destruction. Though this term is sometimes used in relation to overwriting of data, here shredding refers to the process of making data printed on hard copy, or on smaller objects such as floppy or optical disks, unrecoverable. Sensitive information such as printed information needs to be shredded prior to disposal in order to thwart a dumpster diving attack. Dumpster diving is a physical attack in which a person recovers trash in hopes of finding sensitive information that has not been securely erased or destroyed.

Read full chapter

URL: https://www.sciencedirect.com/science/article/pii/B9780124171428000078

Domain 2: Asset Security (Protecting Security of Assets)

Eric Conrad, ... Joshua Feldman, in CISSP Study Guide (Third Edition), 2016

Shredding

A simple form of media sanitization is shredding, a type of physical destruction. Though this term is sometimes used in relation to overwriting of data, here shredding refers to the process of making data printed on hard copy, or on smaller objects such as floppy or optical disks, unrecoverable. Sensitive information such as printed information needs to be shredded prior to disposal in order to thwart a dumpster diving attack.

Paper shredders cut paper to prevent object reuse. Strip-cut shredders cut the paper into vertical strips. Cross-cut shredders are more secure than strip-cut, and cut both vertically and horizontally, creating small paper “confetti”. Given enough time and access to all of the shredded materials, attackers can recover shredded documents, though it is more difficult with cross-cut shredders.

Dumpster diving is a physical attack in which a person recovers trash in hopes of finding sensitive information that has been merely discarded in whole rather than being run through a shredder, incinerated, or otherwise destroyed. Figure 3.1 shows locked shred bins that contain material that is intended for shredding. The locks are intended to ensure that dumpster diving is not possible during the period prior to shredding.

How would you ensure secure media sanitization SSD?

Figure 3.1. Locked Shred Bins

Source: http://commons.wikimedia.org/wiki/File:Confidential_shred_bins.JPG

Photograph by: © BrokenSphere / Wikimedia Commons. Image under permission of Creative Commons Attribution ShareAlike 3.0

Read full chapter

URL: https://www.sciencedirect.com/science/article/pii/B9780128024379000035

Microsoft Vista: Trusted Platform Module Services

In Microsoft Vista for IT Security Professionals, 2007

Encryption as a Countermeasure

Let’s start by first mentioning cryptography in a general sense. After all, the TPM device and TPM services in Windows Vista are obviously focused on encryption. The TPM is mainly designed to create, store, and protect encryption keys, password hashes, and digital certificates.

The first thing we should say here is that no single countermeasure will fully protect digital assets from attack. In fact, there is probably not a combination of countermeasures that can ensure 100 percent protection from attack. Cryptography is no exception to that rule. Consider this as you read vendor product claims, white papers, and other industry articles that tout TPM as the end of your search for a secure enterprise.

Several sources are currently touting media sanitization as a feature of the TPM. The argument goes that you can clear the TPM in a matter of seconds, and your data is gone. No more spending money on and waiting hours for National Security Agency (NSA) media sanitization procedures to work. Just clear the TPM and your data is gone forever. There are two important points here:

1.

When you clear the TPM your data is not gone. Only the key that was used to wrap the key that was used to encrypt that data is gone. The data, in encrypted form, still exists on the drive.

2.

Encryption can be defeated by brute force attacks.

This is not meant to argue that encryption is insecure. The fact of the matter is that with current computing power, it would take a state-of-the-art desktop machine more than 100 trillion years to brute force your data if it is encrypted using the 128-bit Advanced Encryption Standard (AES)! Obviously, if it takes trillions of years to crack into your data, it’s safe. We raise this issue only because a lot of talk is circulating about using the clearing of the TPM as a media sanitization method, when technically speaking, the data is not destroyed and it can be attacked using brute force. Now those brute force attacks may very well remain infeasible for the next 2,000 years. However, there is a chance that leaps in the power of computers over the next two decades or a flaw discovered in the AES algorithm could make brute forcing a 128-bit AES encryption seem as easy as cracking the Data Encryption Standard (DES) is today.

Tools & Traps…

Media Sanitization

The most important thing to consider when using encryption is how long the data you are protecting needs to remain confidential. If you have information on your hard drive that you expect to remain sensitive for the next six months (maybe it is a proposal you are working on, and you must turn it in within that six-month time frame), you can expect the AES algorithm with a 128-bit key to do the job for you. On the other hand, if you are storing a full portfolio of personal information which you need to keep confidential for the next 50 years, you might want to consider how quickly a computer can chug through those keys 35 years down the road. What is the shelf life of your data?

Even the good folks at the National Institute of Standards and Technology (NIST) seem to be riding the fence on this media sanitization issue. In the recently released Special Publication 800–88, “Guidelines for Media Sanitization,” found at http://csrc.nist.gov/publications/nistpubs/800-88/NISTSP800-88_rev1.pdf, NIST added and then removed the following text:

“Encryption is not a generally accepted means of sanitization. The increasing power of computers decreases the time needed to crack cipher text and therefore the inability to recover the encrypted data [cannot] be assured.”

You’ll also find a lot of good debate on the topic throughout the Internet. We don’t usually disagree with what comes out of NIST, and we won’t start here. Just remember that this method of sanitization does not destroy the data or the media. Encryption is a method of ensuring that it takes a long time to get to sensitive data, and for most data this method of sanitization will probably buy us enough time. However, in some applications, this will not be an adequate sanitization method. The important point is that you know how sensitive your data is and how long it must remain confidential before it becomes useless, and that you apply the proper methods given those facts.

You should also note that NIST did not go so far as to add cryptographic destruction anywhere in its list of sanitization methods.

Now that we’ve addressed that caveat, let’s look at the power at our fingertips. Where the TPM and its capability to give us a more robust encryption platform help the most is simply in the fact that the data we are protecting is increasingly moving outside the walls of the enterprise. As we mentioned before, employees are going ever more mobile, with laptops replacing desktops, and cell phones, PDAs, and even MP3 players providing more and more storage and remote connectivity features. Those firewalls, proxies, DMZs, and other layered perimeter protection rings we designed and built in the past are doing a great job at keeping the bad stuff out. What we have increasingly less ability to do is keep the assets we protect in.

This is where encryption and the trusted platform come to the rescue. Encrypting data, especially when we utilize full-disk encryption technologies such as BitLocker Drive Encryption, allows us to create an environment where employees are carrying our security perimeter with them wherever they go. That encryption creates a boundary wherever the device and the data are between the data and the outside world. There are, of course, already software-only solutions for full-disk encryption, but the TPM provides better protection of encryption keys because key recovery techniques that may have worked fairly well against keys held in software are not likely to work against keys protected by the TPM.

Our protection is strengthened even more by the fact that many normal attacks which involve subverting the system software will not work. As soon as part of the system has been modified, the chain of trust will cease to extend to that part of the system. The platform will not load, and the data will not be able to be recovered by simply creating a backdoor in some poorly coded software. The only piece of software we have to rely upon is the tiny bit of code known as the CRTM. Because this code is small and relatively simple, it is easier to ensure that there are no vulnerabilities in it. Buffer overflows and backdoors tend to get lost in a program of tens of thousands of lines of code.

Either brute force cracking methods or attacks on the hardware itself will be required. As long as the data was encrypted using large keys and a secure algorithm, brute force attacks will prove to be a fruitless endeavor, and hardware attacks require a lot more skill and resources than running the canned attack code available on the Internet which is used against software.

Notes from the Underground…

Mandating Full-Disk Encryption

On June 23, 2006, the Office of Management and Budget (OMB) issued Memoranda M-06-16, “Protection of Sensitive Agency Information.” This was a direct response to many of the data loss problems that afflicted the federal government during the first half of 2006. The memoranda requires a blend of technical, management, and operational controls defined in the NIST Special Publication (SP) 800–53, “Recommended Security Controls for Federal Information Systems,” to be implemented, but one specific requirement leading off the memoranda requires that all sensitive data on mobile devices be encrypted.

In rapid response to the memoranda, the U.S. Air Force posted a request for a full-disk encryption solution on the Federal Business Opportunity Web site. The U.S. Department of Agriculture (USDA) also posted a request for quotes (RFQ) on www.fbo.gov in relation to mobile device encryption. In an article for Government Computer News found at www.gcn.com/online/vol1_no1/42640-1.html?topic=mobile-wireless, Mary Mosquera wrote that the USDA’s requirements for the encryption solution include the following:

It must be Federal Information Processing Standards (FIPS) 140–2 compliant.

It must integrate with a Microsoft Active Directory infrastructure.

It must be invisible to users.

It must be scalable.

It must provide automated deployment tools.

It must provide adequate recovery processes.

As we have seen throughout this chapter, devices containing version 1.2 TPM chips and Windows Vista TPM services fulfill all of these requirements. They go beyond the requirements by securing encryption keys with TPM hardware instead of relying on a software-only solution. Whether Windows Vista becomes the solution of choice for most federal agencies remains to be seen.

This is the leading edge of a widespread change in the way that both the public and the private sectors protect their digital assets on mobile devices. As the federal government leads this process of carefully identifying all PII, controlling which mobile devices that the PII. It is just unfortunate that the compromise of the PII of millions of people has been the impetus required to effect this change.

Here are some references for more information on this issue:

You can find OMB Memoranda M-06-16 at www.whitehouse.gov/omb/memoranda/fy2006/m06-16.pdf.

You can find information about the U.S. Air Force procurement at www.fbo.gov/spg/USAF/AFMC/ESC/FA8771-07-R-0001/Attachments.html.

You can find NIST SP 800–53 Revision 1 at http://csrc.nist.gov/publications/nistpubs/800-53-Rev1/800-53-rev1-final-clean-sz.pdf.

Read full chapter

URL: https://www.sciencedirect.com/science/article/pii/B978159749139650008X

Security component fundamentals for assessment

Leighton Johnson, in Security Controls Evaluation, Testing, and Assessment Handbook (Second Edition), 2020

Media sanitation

The information security concern regarding information disposal and media sanitization resides not in the media but in the recorded information. The issue of media disposal and sanitization is driven by the information placed intentionally or unintentionally on the media.

Information systems capture, process, and store information using a wide variety of media. This information is located not only on the intended storage media but also on devices used to create, process, or transmit this information. These media may require special disposition in order to mitigate the risk of unauthorized disclosure of information and to ensure its confidentiality. Efficient and effective management of information that is created, processed, and stored by an information technology (IT) system throughout its life, from inception through disposition, is a primary concern of an information system owner and the custodian of the data.

With the use of increasingly sophisticated encryption, an attacker wishing to gain access to an organization's sensitive information is forced to look outside the system itself for that information. One avenue of attack is the recovery of supposedly deleted data from media. These residual data may allow unauthorized individuals to reconstruct data and thereby gain access to sensitive information. Sanitization can be used to thwart this attack by ensuring that deleted data cannot be easily recovered.

When storage media are transferred, become obsolete, or are no longer useable or required by an information system, it is important to ensure that residual magnetic, optical, electrical, or other representation of data that has been deleted is not easily recoverable. Sanitization refers to the general process of removing data from storage media, such that there is reasonable assurance that the data may not be easily retrieved and reconstructed.

Information disposition and sanitization decisions occur throughout the system life cycle. Critical factors affecting information disposition and media sanitization are decided at the start of a system's development. The initial system requirements should include hardware and software specifications as well as interconnections and data flow documents that will assist the system owner in identifying the types of media used in the system.

How would you ensure secure media sanitization SSD?

Read full chapter

URL: https://www.sciencedirect.com/science/article/pii/B9780128184271000112

Security Component Fundamentals for Assessment

Leighton Johnson, in Security Controls Evaluation, Testing, and Assessment Handbook, 2016

Media Sanitation

The information security concern regarding information disposal and media sanitization resides not in the media but in the recorded information. The issue of media disposal and sanitization is driven by the information placed intentionally or unintentionally on the media.

Information systems capture, process, and store information using a wide variety of media. This information is located not only on the intended storage media but also on devices used to create, process, or transmit this information. These media may require special disposition in order to mitigate the risk of unauthorized disclosure of information and to ensure its confidentiality. Efficient and effective management of information that is created, processed, and stored by an IT system throughout its life, from inception to disposition, is a primary concern of an information system owner and the custodian of the data.

With the use of increasingly sophisticated encryption, an attacker wishing to gain access to an organization’s sensitive information is forced to look outside the system itself for that information. One avenue of attack is the recovery of supposedly deleted data from media. These residual data may allow unauthorized individuals to reconstruct data and thereby gain access to sensitive information. Sanitization can be used to thwart this attack by ensuring that deleted data cannot be easily recovered.

When storage media are transferred, become obsolete, or are no longer usable or required by an information system, it is important to ensure that residual magnetic, optical, electrical, or other representation of data that has been deleted is not easily recoverable. Sanitization refers to the general process of removing data from storage media, such that there is reasonable assurance that the data may not be easily retrieved and reconstructed.

Information disposition and sanitization decisions occur throughout the system life cycle. Critical factors affecting information disposition and media sanitization are decided at the start of a system’s development. The initial system requirements should include hardware and software specifications as well as interconnections and data flow documents that will assist the system owner in identifying the types of media used in the system.

How would you ensure secure media sanitization SSD?

Read full chapter

URL: https://www.sciencedirect.com/science/article/pii/B9780128023242000117

Domain 2

Eric Conrad, ... Joshua Feldman, in Eleventh Hour CISSP® (Third Edition), 2017

Memory and Remanence

The 2015 exam update added timely topics such as remanence properties of SSDs, discussed next, followed by a discussion of computer memory itself.

Data Remanence

It is important to understand data remanence when discussing media sanitization and data destruction. Data remanence is data that persists beyond noninvasive means to delete it. Though data remanence is sometimes used specifically to refer to residual data that persists on magnetic storage, remanence concerns go beyond just that of magnetic storage media.

Memory

Memory is a series of on/off switches representing bits: 0s (off) and 1s (on). Memory may be chip based, disk based, or tape based. RAM is random-access memory: “random” means the CPU may randomly access or jump to any location in memory. Sequential memory, such as tape, must sequentially read memory, beginning at offset zero, to the desired portion of memory. Volatile memory, such as RAM, loses integrity after a power loss; nonvolatile memory (such as read-only memory (ROM), disk, or tape) maintains integrity without power.

Real or primary memory, such as RAM, is directly accessible by the CPU and is used to hold instructions and data for currently executing processes. Secondary memory, such as disk-based memory, is not directly accessible.

Cache memory

Cache memory is the fastest system memory, required to keep up with the CPU as it fetches and executes instructions. The data most frequently used by the CPU is stored in cache memory. The fastest portion of the CPU cache is the register file, which contains multiple registers. Registers are small storage locations used by the CPU to store instructions and data.

The next fastest form of cache memory is Level 1 cache, located on the CPU itself. Finally, Level 2 cache is connected to (but outside of) the CPU. Static random-access memory (SRAM) is used for cache memory.

RAM and ROM

RAM is volatile memory used to hold instructions and data of currently running programs. It loses integrity after loss of power.

ROM is nonvolatile; data stored in ROM maintains integrity after loss of power. A computer basic input/output system (BIOS) firmware is stored in ROM. While ROM is “read only,” some types of ROM may be written to via flashing.

DRAM and SRAM

SRAM is fast, expensive memory that uses small latches called “flip-flops” to store bits. Dynamic random-access Memory (DRAM) stores bits in small capacitors (like small batteries), and is slower and cheaper than SRAM. The capacitors used by DRAM leak charge, and so they must be continually refreshed to maintain integrity, typically every few to a few hundred milliseconds, depending on the type of DRAM. Refreshing reads and writes the bits back to memory. SRAM does not require refreshing and maintains integrity as long as power is supplied.

Firmware

Firmware stores programs that do not change frequently, such as a computer’s BIOS (discussed below) or a router’s operating system and saved configuration. Various types of ROM chips may store firmware, including programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), and EEPROM, defined next.

PROM can be written to once, typically at the factory. EPROM and EEPROM may be “flashed,” or erased and written to multiple times.

A programmable logic device (PLD) is a field-programmable device, which means it is programmed after it leaves the factory. EPROMs, EEPROMs, and flash memory are examples of PLDs.

Flash memory

Flash memory, such as a USB thumb drive, is a specific type of EEPROM that is used for storage. The difference is that any byte of an EEPROM may be written, while flash drives are written by larger sectors.

Solid-state drives

A SSD is a combination of flash memory (EEPROM) and DRAM. Degaussing (destroying data via a strong magnetic field, which we will discuss shortly) has no effect on SSDs. While physical disks have physical blocks (eg, Block 1 is on a specific physical location on a magnetic disk), blocks on SSDs are logical and are mapped to physical blocks. Also, SSDs do not overwrite blocks that contain data; the device will instead write data to an unused block and mark the previous block unallocated.

A process called garbage collection later takes care of these old blocks: “Working in the background, garbage collection systematically identifies which memory cells contain unneeded data and clears the blocks of unneeded data during off-peak times to maintain optimal write speeds during normal operations.”3

The TRIM command improves garbage collection by more efficiently marking data “invalid” (requiring garbage collection), and skipping data that can be ignored. “TRIM is an attribute of the ATA Data Set Management Command. The TRIM function improves compatibility, endurance, and performance by allowing the drive to do garbage collection in the background. This collection eliminates blocks of data, such as deleted files.”4 While the TRIM command improves performance, it does not reliably destroy data.

A sector-by-sector overwrite behaves very differently on an SSD versus a magnetic drive, and it does not reliably destroy all data. Also, electronically shredding a file (ie, overwriting the file’s data before deleting it, which we will discuss shortly) is not effective. Data on SSD drives that are not physically damaged may be securely removed via ATA Secure Erase.

The two valid options for destroying data on SSD drives are ATA Secure Erase and destruction. Destruction is the best method for SSD drives that are physically damaged.

Read full chapter

URL: https://www.sciencedirect.com/science/article/pii/B9780128112489000024

Domain 9

Eric Conrad, in Eleventh Hour CISSP, 2011

Media sanitization or destruction of data

It is time to destroy data or its associated media once an organization has identified that it is no longer operationally or legally required. While some data might not be sensitive and so not warrant thorough destruction, an organization will have data that must be verifiably destroyed or otherwise rendered nonusable if the media on which it is housed is recovered by a third party.

Data remanence

The term data remanence is important to understand when discussing media sanitization and data destruction. It refers to data that persists beyond noninvasive means to delete it. Though data remanence sometimes specifically refers to residual data that persists on magnetic storage, its concerns go beyond magnetic storage media. Security professionals must understand and appreciate the steps to make data unrecoverable.

Wiping or overwriting

When a user deletes a file, usually the file system merely removes metadata pointers or references to it. The file allocation table references are gone, but the file data remains. Significant amounts of “deleted data” may be recovered (“undeleted”) by readily available forensic tools. Reformatting a file system may also leave data intact.

Though simple file deletion or hard disk reformatting is not sufficient to render data unrecoverable, files may be securely wiped or overwritten. Wiping, also called overwriting, writes new data over each bit or block of file data. One of the shortcomings of wiping is that physical damage to a hard disk prevents complete overwriting.

Degaussing

By introducing an external magnetic field with a degausser, the data on magnetic storage media can be made unrecoverable. Magnetic storage depends on the magnetization of the media being static unless intentionally changed by the storage device. A degausser destroys the integrity of the magnetization, making the data unrecoverable.

Physical destruction

Physical destruction, when carried out properly, is considered the most secure means of media sanitization. One of the reasons for its higher degree of assurance is the greater likelihood of errors in data remanence with wiping or degaussing. Physical destruction is certainly warranted for the most sensitive data. Common means of destruction include incineration and pulverization.

Shredding

A simple form of media sanitization by physical destruction is shredding. Though sometimes used in relation to data overwriting, here shredding refers to the process of making data printed on hard copy, or on smaller objects such as floppy or optical disks, unrecoverable. Sensitive printed information needs to be shredded prior to disposal in order to thwart dumpster diving. This is a physical attack in which an attacker recovers trash in hopes of finding intact sensitive information.

Read full chapter

URL: https://www.sciencedirect.com/science/article/pii/B9781597495660000096

How do you ensure secure media sanitization for HDD?

The sanitization steps for encrypted Media include: Erasing the key (or re-encrypting with a strong key then erasing the key used for re-encryption.) Clearing the Media as an additional step when key erasure is not verifiable. Removing external markings or labels that indicate government ownership or data sensitivity.

What is the best method to sanitize a solid state drive SSD )?

Sanitize SSD drive. Sanitizing is to remove sensitive data from a system or storage device so that data cannot be recovered by any known technique. Sanitizing SSD using ATA Secure Erase is the most effective. ATA Secure Erase will wipe the entire contents of a drive.

What are the 3 methods of data sanitization?

There are three methods to achieve data sanitization: physical destruction, cryptographic erasure and data erasure.

What is media sanitization?

Media Sanitization Overview “the general process of removing data from storage media, such that there is reasonable assurance that the data may not be easily retrieved and reconstructed.” There are four categories of media sanitization: disposal, clearing, purging and destroying.