NAVSO P-5239-26 Navy — Secure Data Erasure & Media Sanitization Software

NAVSO P-5239-26 is associated with Navy Staff Office Publication 5239 — Information Systems Security (INFOSEC) Program Guidelines.

The publication contains guidance and procedures covering:

• Data Storage Media
• Clearing
• Purging
• Magnetic Storage
• Electronic Storage Technologies
• Storage-Media Release
• Reuse Of Media
• Verification
• Technology-Specific Sanitization Procedures

The original document specifically explains that clearing and purging address different levels of recovery threat and that procedures vary according to the storage technology involved.

This is important because NAVSO P-5239-26 is not simply a generic “three-pass wipe.”

For applicable magnetic storage media, the publication describes a three-stage overwrite concept:

One of the technically distinctive characteristics of NAVSO P-5239-26 is its treatment of magnetic-media encoding.

The original publication provides different pattern considerations for:

• MFM — Modified Frequency Modulation
• RLL — Run Length Limited

The document identifies an RLL pattern where the drive's encoding technique is uncertain and provides specific bit patterns for applicable magnetic storage.

This is one reason NAVSO P-5239-26 should not simply be reduced to:

1. 01“Write Zeros
2. 02Write Ones
3. 03Write Random Data.”

The historical procedure is more media- and encoding-specific.

DSP provides a dedicated NAVSO P-5239-26 Sanitization Method within the DSP Sanitization Engine.

1. 01Identify Device
2. 02Classify Storage Technology
3. 03Assess Device Condition
4. 04Select NAVSO P-5239-26
5. 05Select Applicable Media Profile
6. 06Execute Pass 1
7. 07Execute Pass 2
8. 08Execute Pass 3
9. 09Verify
10. 10Validate
11. 11Document
12. 12Audit-Ready Certificate

This separates NAVSO P-5239-26 from generic custom overwrite operations.

The historical NAVSO procedure is particularly relevant to magnetic storage media.

For supported HDDs, DSP can capture:

• Manufacturer
• Model
• Serial Number
• Capacity
• Interface
• Firmware Information
• SMART Health
• Temperature
• Power-On Hours
• Bad-Sector Information
• Read/write Errors
• Sanitization Progress
• Write Rate
• Pass Status
• Verification Result

This provides operational evidence alongside the actual sanitization process.

The original NAVSO P-5239-26 procedure goes beyond simply overwriting ordinary user files.

For magnetic-media purging, the publication describes writing to areas including:

• File Allocation Structures
• Directories
• Block Maps
• Assigned Space
• Unassigned Space
• Active File Space
• Inactive/unused Space
• Space Between File Data And The End Of Its Sector Or Block
• Bad And Spare Sectors And Tracks, Where Technically Addressable

The publication specifically warns that simply deleting files or formatting a disk does not prevent recovery of information.

A particularly important characteristic of the historical NAVSO procedure is its treatment of bad and spare sectors.

The publication instructs that applicable purge operations should address bad and spare sectors and tracks, including areas removed from standard addressing, where the technology and hardware permit such access.

This is highly relevant when building an audit-ready sanitization workflow.

DSP can identify and report:

• Bad Sectors
• Read Failures
• Write Failures
• Unstable Sectors
• Device Health Warnings
• Inaccessible Regions
• Sanitization Exceptions

If a device contains inaccessible areas that cannot be addressed by the selected technique, the result should not simply be treated as an unconditional successful sanitization.

Verification is an important part of the NAVSO methodology.

The original publication includes verification considerations and specifically notes that read caching should be disabled during verification so that the verification process reflects the storage media rather than cached data.

DSP records the verification outcome as part of the sanitization process.

The report can document:

• Sanitization Completion
• Pass Execution
• Verification Result
• Read/write Errors
• Device Response
• Failed Regions
• Device Status
• Validation Outcome

The original Navy publication explicitly states that simply removing file pointers, such as through delete or format operations, does not prevent recovery.

NAVSO P-5239-26 originated in an era when magnetic storage characteristics were central to media sanitization.

Modern SSD and flash storage behaves differently.

SSD architectures can include:

• Flash Translation Layers
• Wear Leveling
• Spare NAND Blocks
• Over-Provisioning
• Garbage Collection
• Remapping
• Controller-Managed Physical Locations

Consequently, traditional magnetic-media overwrite patterns should not automatically be treated as universal physical sanitization methods for modern SSD or NVMe devices.

For modern solid-state storage, the appropriate technique should be selected according to the storage architecture and current organizational sanitization policy.

Where stronger media sanitization is required organizations may need to use device-specific sanitize capabilities or other modern techniques rather than relying solely on historical multi-pass logical overwriting.

Historical methods such as NAVSO P-5239-26 remain useful when an organization specifically requires the methodology for:

• Legacy Policy Compliance
• Contractual Requirements
• Historical Asset Records
• Compatibility With Existing Procedures
• Specialized Data-Erasure Workflows

However, modern storage should be evaluated according to its actual architecture.

Current frameworks such as NIST SP 800-88 Rev. 2 and IEEE 2883-2022 provide more contemporary approaches to technology-specific media sanitization.

Therefore:

DSP can maintain both approaches as separate selectable methods.

NAVSO P-5239-26 and DoD 5220.22-M are frequently grouped together because both are historical U.S. government-associated media sanitization methodologies.

They are nevertheless separate publications and should not be presented as identical.

DSP therefore treats NAVSO P-5239-26 and DoD 5220.22-M as separate sanitization profiles.

Both methodologies are historically associated with multi-pass data wiping, but they originate from different government environments.

The important difference is method identity, not simply the number of passes.

DSP can perform device assessment before and during sanitization.

• SMART Status
• Temperature
• Power-On Hours
• Read Errors
• Write Errors
• Bad Sectors
• Device Warnings
• Firmware
• Model
• Serial Number

This information can help determine whether the device is suitable for software-based sanitization or requires another disposition decision.

IT Asset Disposition providers may encounter customer or legacy requirements specifying a particular government-associated sanitization method.

DSP can support an ITAD workflow:

1. 01Asset Intake
2. 02Device Identification
3. 03Storage Health Check
4. 04NAVSO P-5239-26 Selection
5. 05Sanitization
6. 06Verification
7. 07Validation
8. 08Certificate
9. 09Asset Release / Reuse / Disposal

This creates a documented relationship between the physical asset and its sanitization result.

DSP can support offline sanitization workflows where internet connectivity is not required.

This can be useful for:

• Government Facilities
• Restricted Networks
• Air-Gapped Systems
• Secure Laboratories
• Enterprise Data Centers
• Controlled ITAD Facilities
• High-Security Environments

The sanitization operation can be executed locally while device and verification information is recorded for reporting.

Enterprise and ITAD environments may process multiple retired storage devices.

DSP can provide operational visibility across supported devices, including:

• Device Identification
• Selected Method
• Active Pass
• Progress
• Write Rate
• Elapsed Time
• ETA
• Verification Status
• Errors
• Completion Status

This helps operators manage multiple sanitization jobs without losing device-level audit information.

After execution and verification, DSP can generate an audit-ready sanitization certificate.

The key principle is:

Select the method according to the storage technology, security requirement, device condition and applicable policy.

NAVSO P-5239-26 is one of the supported sanitization methodologies available through DSP.

The DSP Sanitization Engine can provide separate profiles for modern and historical methodologies such as:

Each method remains a separate selectable DSP sanitization profile, with its applicable execution, verification and reporting workflow.

• 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