NIST SP 800-88 Rev. 1 — Clear

Under Rev. 1, Clear was one of three sanitization categories:

• Clear
• Purge
• Destroy

Clear was intended to sanitize user-accessible data while preserving the usability of the storage media.

For applicable storage technologies, Rev. 1 specified overwriting using an organizationally approved and tested overwriting technology, methodortool. For magnetic disks such as ATA HDDs, the minimum Clear pattern was generally at least one write pass using a fixed data value, such as all zeros. Multiple passes or more complex patterns could also be used. Verification of the overwritten data was required.

This made Rev. 1 Clear fundamentally different from simply deleting files or formatting a drive.

Clear was primarily concerned with making target data inaccessible through normal user interfaces while keeping the storage device usable.

For supported magnetic storage, the Rev. 1 approach centered on overwriting addressable storage with an approved sanitization pattern.

A typical workflow was:

1. 01Identify
2. 02Select Clear
3. 03Overwrite
4. 04Verify
5. 05Document

The actual technique depended on the storage technology.

Deleting a file normally removes or changes filesystem references to the file. The underlying sectors may still contain recoverable information.

Similarly, quick formatting generally changes filesystem structures rather than sanitizing every location containing previous data.

A proper sanitization operation addresses the target data according to the selected sanitization methodology.

File deletion≠Formatting≠Data Sanitization

NIST SP 800-88 Rev. 1 treated sanitization as a security process intended to make recovery of target data infeasible for the applicable level of effort.

For ATA hard disk drives, including PATA, SATA and eSATA devices, Rev. 1 specified overwriting with an organizationally approved and validated technology, method or tool.

The Clear pattern was required to consist of at least one write pass using a fixed value such as zeros. Additional passes or more complex patterns could optionally be used.

1. Identify HDD Model, serial number, capacity and interface are identified.

2. Assess Device DSP can inspect available device information and storage health indicators.

Clear under Rev. 1 requires greater care when applied to flash-based storage.

NIST specifically warned that overwriting flash media can:

• reduce the effective lifetime of the media;
• fail to sanitize data residing in unmapped physical locations;
• leave previous data in areas not directly accessible through the normal logical interface.

This is an important distinction between traditional magnetic HDDs and modern SSD/NVMe storage.

HDD

Traditional overwrite can address the magnetic storage surface through the drive's logical addressing system.

Flash storage uses technologies such as:

• Flash Translation Layers
• Wear Leveling
• Spare Cells
• Over-Provisioning
• Garbage Collection
• Controller-Managed Physical Mapping

Consequently, a conventional overwrite should not automatically be treated as equivalent to a complete physical sanitization of every underlying flash cell.

For higher assurance requirements, the appropriate Purge technique or another technology-specific sanitization approach should be evaluated.

Rev. 1 provided technology-specific recommendations.

For USB removable media, the Clear procedure called for at least two passes: a pattern followed by its complement, with additional passes permitted.

For memory cards, including SD, SDHC, MMC, CompactFlash and similar flash media, Rev. 1 likewise specified a minimum two-pass Clear pattern consisting of an initial pattern followed by its complement.

These historical requirements are important when maintaining compatibility with legacy sanitization procedures.

NIST Rev. 1 explicitly treated Clear, Purge and Destroy as different sanitization categories, with the appropriate choice depending on information sensitivity, media characteristics, risk and intended disposition.

Data Sanitization Pro provides a dedicated NIST SP 800-88 Rev. 1 Clear Method within its DSP Sanitization Engine.

IDENTIFY DEVICE ↓ ASSESS STORAGE TECHNOLOGY ↓ SELECT NIST SP 800-88 REV. 1 CLEAR ↓ DSP SANITIZATION ENGINE ↓ EXECUTE CLEAR METHOD ↓ MONITOR PROCESS ↓ VERIFY RESULT ↓ DOCUMENT OPERATION ↓ AUDIT-READY CERTIFICATE

The method is designed for organizations that specifically require a Rev. 1 Clear workflow for historical, contractual, operational or internal policy reasons.

Verification is an important part of the Rev. 1 process.

NIST Rev. 1 states that the goal of sanitization verification is to determine whether target data was effectively sanitized. The publication also discusses verification of the sanitization equipment, personnel competency and sanitization results.

DSP can document the sanitization operation together with relevant verification information.

Depending on the device and selected method, the workflow can record:

• Device Identification
• Manufacturer
• Model
• Serial Number
• Capacity
• Storage Technology
• Selected Sanitization Method
• Sanitization Status
• Verification Status
• Start Time
• Completion Time
• Operator Information
• System Information
• Process Events
• Verification Results

A reliable data erasure workflow should not treat every storage device as identical.

Before sanitization, DSP can provide relevant device information such as:

• SMART Health Information
• Temperature
• Power-On Hours
• Firmware
• Model
• Serial Number
• Storage Capacity
• Device Errors
• Sector-Related Information

This can help identify devices that may require additional assessment before executing a sanitization operation.

Bad sectors can affect the ability of an overwrite-based sanitization process to address storage locations.

DSP can identify and report relevant storage errors and bad-sector conditions as part of the device assessment and reporting workflow.

Where a device cannot reliably address the required storage area organizations should not automatically assume that a successful software completion message represents complete sanitization.

For higher-risk situations, the organization may need to select a stronger or technology-appropriate sanitization method or move to physical destruction.

Rev. 1 also included guidance concerning Cryptographic Erase (CE).

Cryptographic Erase can be appropriate where the storage device uses encryption and the necessary cryptographic conditions and implementation characteristics provide sufficient assurance.

However, CE should not simply be assumed to be effective because a device supports encryption. The device's encryption architecture, key management and implementation characteristics must be considered.

DSP can separately support applicable sanitization methods rather than treating every storage device as a conventional overwrite target.

NIST SP 800-88 Rev. 1 included Appendix G — Sample "Certificate of Sanitization" Form for documenting organizational sanitization activities.

DSP extends this operational concept with its own audit-ready sanitization certificate.

A DSP certificate can document information such as:

The DSP certificate documents the sanitization operation actually performed by Data Sanitization Pro.

It does not mean:

• NIST Has Certified DSP;
• NIST Has Approved DSP;
• The Certificate Was Issued By NIST;
• The Device Has Received An External NIST Certification.

The certificate is DSP's audit documentation showing the selected sanitization method, device information, execution details and verification information.

Secure data erasure is an important part of the IT Asset Disposition (ITAD) lifecycle.

Before computers, servers, HDDs, SSDs and removable media are:

• Reused;
• Refurbished;
• Resold;
• Transferred;
• Recycled;
• Returned To Inventory;

organizations need a controlled process for handling residual data.

A documented Rev. 1 Clear workflow can support legacy ITAD policies where this methodology remains specified by contract or organizational procedure.

DSP combines:

DEVICE IDENTIFICATION+SANITIZATION+VERIFICATION+REPORTING

into one software-controlled workflow.

For enterprise environments, DSP can support controlled sanitization of multiple devices and storage technologies.

Typical use cases include:

• Corporate IT Asset Retirement
• Data-Center Hardware Decommissioning
• Laptop And Desktop Refurbishment
• HDD Retirement
• SSD Retirement
• USB Media Sanitization
• Memory-Card Sanitization
• ITAD Operations
• Electronics Recycling Workflows
• Hardware Resale And Refurbishment
• Internal Media Reuse

Multiple devices can be processed according to the organization's selected workflow and licensing configuration.

DSP can also be used in environments where sanitization systems should operate without depending on public internet connectivity.

This is particularly relevant for:

• High-Security Environments
• Government Facilities
• Enterprise IT Departments
• Restricted Networks
• Air-Gapped Environments
• Controlled ITAD Facilities

Offline operation allows sanitization activities to be performed within the organization's controlled infrastructure.

NIST states that Rev. 2 supersedes Rev. 1 and substantially changes the publication's focus toward establishing an enterprise or agency media sanitization program.

Although Rev. 1 is withdrawn organizations may still encounter it in:

• Legacy Security Policies
• Existing ITAD Contracts
• Historical Procurement Specifications
• Internal SOPs
• Customer Requirements
• Older Compliance Documentation
• Existing Sanitization Workflows
• Archived Audit Requirements

DSP's dedicated Rev. 1 Clear method allows such organizations to maintain a documented workflow where continued use of the historical methodology is specifically required.

For new sanitization programs organizations should evaluate NIST SP 800-88 Rev. 2 and current technology-specific standards and organizational requirements.

The DSP Sanitization Engine provides a controlled execution layer for supported sanitization methodologies.

For NIST SP 800-88 Rev. 1 Clear, the workflow is:

1. 01Select Method
2. 02Select Device
3. 03Execute Clear
4. 04Verify
5. 05Document
6. 06Certify

The same DSP platform can provide separate dedicated methods for other supported sanitization methodologies.

This prevents different standards from being treated as a single generic "wipe" operation.

DSP brings multiple sanitization methodologies into a single data erasure software environment.

Depending on the selected method, DSP can provide:

Each certificate identifies the sanitization method actually executed by DSP.

• 01DSP-DPDP India
• 02NIST SP 800-88 Rev. 1 Clear
• 03NIST SP 800-88 Rev. 1 Purge
• 04NIST SP 800-88 Rev. 2 Clear
• 05NIST SP 800-88 Rev. 2 Purge
• 06IEEE 2883-2022
• 07ISO/IEC 27040:2024
• 08Random Overwrite
• 09DoD 5220.22-M
• 10DoD 5220.22-M ECE
• 11NSA/CSS Policy Manual 9-12
• 12HMG IS5 Baseline
• 13HMG IS5 Enhanced
• 14CSEC ITSG-06
• 15BSI-GSE
• 16BSI VSITR
• 17Gutmann Method
• 18Schneier Algorithm
• 19Pfitzner Method
• 20AFSSI-5020
• 21AR 380-19
• 22GOST R 50739-95
• 23NZISM
• 24NAVSO P-5239-26
• 25RCMP TSSIT OPS-II