An SSD may still contain its data after a degaussing cycle, whether the device continues to operate or suffers unrelated electronic damage. NIST Special Publication 800-88 Revision 2 explicitly says degaussing should not be used for nonmagnetic information storage media such as flash storage and SSDs.
Enterprise teams should route SSDs to a suitable logical technique or SSD destruction service based on the required Clear, Purge, or Destroy outcome. They should not send mixed HDD and SSD inventories through one degaussing process.
What Does a Degausser Actually Do?
A degausser generates a magnetic field intended to change magnetic domains in compatible storage media. Magnetic HDDs encode information through magnetization on coated platter surfaces.
When correctly matched to suitable magnetic media, degaussing can alter:
- User data
- File-system structures
- Firmware-related magnetic information
- Servo patterns used for head positioning
The field must be sufficient for the medium’s coercivity, which describes resistance to changes in magnetization. A weak or unsuitable field can damage operation while failing to sanitize target data.
Degaussing is therefore a media-specific physical Purge technique. It is not a general electronic eraser.
How Does an SSD Store Data?
An SSD stores persistent data in NAND flash memory cells by controlling and measuring electrical charge states. It has no spinning magnetic platter.
Key SSD components include:
- NAND flash packages
- One or more memory dies inside a package
- Controller
- Firmware
- Volatile or nonvolatile cache
- Power-management components
- Printed circuit board
- Connectors and enclosure
The controller maps logical block addresses presented to the host to physical NAND locations. It also manages wear, bad blocks, error correction, garbage collection, and spare capacity.
NAND cells are semiconductor structures
NAND flash cells retain information by maintaining electrical states in transistor structures. A magnetic degaussing field does not reset those states in the way it changes magnetic grains on an HDD platter.
SSD operation can be damaged without sanitizing NAND
A strong external field or degausser environment could affect electronic components in an unpredictable way. If the controller or circuit fails, the SSD may stop appearing to a computer while the NAND packages retain data.
Device failure must not be treated as proof of sanitization.
What Does NIST SP 800-88 Rev. 2 Say?
NIST SP 800-88 Rev. 2 states that degaussing should not be used for nonmagnetic information storage media, including flash storage such as SSDs. This is a direct media-method mismatch.
The current NIST publication, issued in September 2025, supersedes Revision 1. It defines:
- Clear: Logical techniques that address data in user-addressable storage locations.
- Purge: Logical or physical techniques that make target-data recovery infeasible against advanced laboratory capabilities.
- Destroy: Techniques that make target-data recovery infeasible against advanced laboratory capabilities and leave the media unable to store data.
Degaussing can potentially support Purge for suitable magnetic media when field strength is carefully matched to coercivity. It does not support Clear, Purge, or Destroy for an SSD because it does not alter NAND data.
The NIST SP 800-88 Rev. 2 PDF gives a direct validation example: a degausser can complete a cycle against an SSD while no sensitive data is sanitized.
Why Can the Degausser Report Success?
A degausser’s cycle status normally reports machine operation, not whether the inserted device used magnetic storage. The equipment may confirm that a field was generated for the intended time without identifying NAND flash.
A successful machine cycle can therefore coexist with a failed sanitization outcome.
This illustrates the difference between:
- Process completion: The equipment completed its cycle.
- Media eligibility: The inserted device was suitable for the technique.
- Verification: The organization inspected the technique result.
- Validation: The organization decided whether target data was effectively sanitized.
A cycle light or printed receipt cannot replace media identification.
Will a Stronger Degausser Work on an SSD?
No. Increasing magnetic field strength does not create a valid NAND sanitization process. The problem is not insufficient gauss; it is the absence of magnetic data storage.
A stronger field may:
- Have no relevant effect on NAND data
- Damage supporting electronics
- Make normal access harder
- Create safety or equipment risks
- Produce an inoperable device with unsanitized memory
An organization should not attempt to solve a technology mismatch by repeating cycles or using stronger equipment.
Does Degaussing Work on NVMe, USB, or Memory Cards?
No. NVMe SSDs, SATA SSDs, USB flash drives, SD cards, microSD cards, embedded flash, eMMC, and UFS storage use semiconductor memory rather than magnetic recording. Degaussing is not an approved sanitization technique for their stored data.
The external shape can mislead operators:
- A 2.5-inch SATA SSD resembles a 2.5-inch HDD.
- An enterprise SSD can use a metal carrier similar to an HDD caddy.
- A hybrid drive can contain both magnetic and flash storage.
- Servers and appliances can contain small boot modules or embedded flash.
Inventory should identify storage technology, not only form factor.
Why Are Hybrid Drives a Special Risk?
A hybrid drive contains magnetic storage and solid-state memory, so degaussing can affect the platters while leaving flash components unsanitized. A process that records the device only as an HDD can miss this second storage technology.
Hybrid media can contain:
- Magnetic platters
- NAND cache
- Controller metadata
- Nonvolatile configuration information
- Circuit-board memory
Current NSA/CSS Policy Manual 9-12 provides separate procedures for hybrid drives within its scope. The policy recognizes that degaussing is not effective for the solid-state component.
The project should identify model and storage architecture before assigning a sanitization technique.
Can Magnets Erase an SSD?
Ordinary magnets do not sanitize an SSD, and placing an SSD near a magnet is not a controlled data-destruction method. NAND flash is designed around electrical charge, not magnetic polarity.
This includes:
- Permanent magnets
- Speaker magnets
- Handheld magnets
- Magnetic trays
- Magnetic degaussing wands
- Bulk degaussers
Some magnetic fields can interfere with electronics or sensors, but interference is not sanitization. A device can fail for reasons unrelated to the data stored in NAND.
Which Logical Sanitization Methods Can Work on SSDs?
A suitable device-supported sanitization command or cryptographic erase can work when the SSD, implementation, tool, and policy meet the required conditions. Simple host overwriting is not always sufficient.
Why ordinary overwriting is limited
SSDs manage physical NAND internally. Host software cannot directly choose every cell that previously held data because the controller uses:
- Wear leveling
- Overprovisioning
- Spare blocks
- Bad-block replacement
- Garbage collection
- Logical-to-physical translation
Writing to every logical block may leave prior data in locations not exposed through the normal interface.
Device sanitize commands
Some SSDs support commands designed to sanitize internal storage. The organization must know:
- Exact command
- Drive and firmware support
- Areas addressed
- Estimated duration
- Completion status
- Error behavior
- Required power conditions
- Verification method
A tool label such as “secure erase” does not prove which command ran.
Cryptographic erase
Cryptographic erase makes encrypted target data inaccessible by sanitizing the relevant keys. Its assurance depends on conditions such as:
- Data was encrypted before sensitive information was stored.
- Encryption covered the target data and relevant storage areas.
- Key generation and storage were sound.
- Every required key copy is sanitized.
- The implementation and cryptographic strength meet policy.
- The result is verified and validated.
Cryptographic erase is not an automatic approval merely because the SSD advertises encryption.
The comparison Hard Drive Wiping vs. Physical Destruction explains how reuse and Destroy decisions affect method selection.
When Should an SSD Be Physically Destroyed?
Physical destruction is appropriate when policy assigns Destroy, the SSD is failed or unsupported, a logical technique cannot be validated, reuse is prohibited, or the consequence of release requires a destructive outcome.
Common triggers include:
- Drive does not enumerate
- Firmware or controller failure
- Unsupported sanitize command
- Tool reports an error
- Storage architecture is unknown
- Cryptographic-erase conditions cannot be established
- Contract requires destruction
- Classified or program-specific procedure applies
- Reuse is not authorized
- Asset cannot be tied to a valid logical-sanitization record
Physical destruction must address NAND packages and memory dies, not only the enclosure.
Why Is Crushing an SSD Not Always Enough?
Crushing can bend a board or break an enclosure while leaving one or more NAND packages intact. An inoperable SSD can still contain data-bearing semiconductor components.
A crusher designed for magnetic HDD platters may:
- Puncture one board region
- Miss memory packages
- Detach intact chips
- Damage the controller but not NAND
- Produce output unsuitable for the required Destroy outcome
The organization should inspect data-bearing remnants and validate the result. The service name “physical destruction” does not replace output requirements.
Why Is SSD Shredding Different From HDD Shredding?
HDD destruction targets magnetic platter surfaces; SSD destruction targets NAND packages and memory dies. The machines and acceptable output may differ.
An HDD shredder is built to tear metal chassis and rigid platter materials. An SSD process must reduce small semiconductor packages and prevent intact packages or dies from passing through.
The detailed guide SSD Shredding and Chip-Level Destruction covers equipment, fragments, verification, and current NSA/CSS context.
How Should SSD Sanitization Be Verified and Validated?
Verification confirms what technique completed; validation determines whether the result adequately protects the target data. A degaussing receipt fails because the technique does not apply to the media.
For logical techniques
Record:
- SSD make, model, serial number, and firmware
- Interface and capacity
- Sanitization method
- Exact command or cryptographic technique
- Tool and version
- Command scope
- Completion status
- Errors and anomalies
- Verification result
- Validation decision
For physical techniques
Record:
- Equipment make and model
- Media approval
- Output requirement
- NAND-package and fragment inspection
- Oversize or intact components
- Reprocessing
- Validation
For failed media identification
If an SSD was mistakenly degaussed:
- Isolate the device and affected batch.
- Do not release or recycle it.
- Correct the asset record.
- Select an SSD-suitable technique.
- Investigate why sorting failed.
- Review other devices from the same process.
- Document the exception and final result.
What Documentation Should an Enterprise Retain?
Retain evidence that connects the SSD to the correct method, technique, result, validation, and disposition. A generic certificate stating “magnetically erased” should be rejected for an SSD.
The record can include:
- Asset and serial number
- Manufacturer and model
- SSD, NVMe, eMMC, UFS, or other media type
- Source system
- Data classification
- Clear, Purge, or Destroy
- Technique
- Tool or equipment
- Verification
- Validation
- Date and location
- Operator and reviewer
- Exceptions
- Final disposition
A chain-of-custody record should account for the asset before validation. A Certificate of Destruction should name the actual SSD technique.
How Should Procurement Prevent SSD Degaussing Errors?
Procurement should require media identification, separate routing, technique-level reporting, and exception handling. A contract that says “degauss all drives” creates a foreseeable control gap.
Ask providers:
- How are HDDs, SSDs, hybrid drives, and HAMR drives identified?
- Are 2.5-inch HDDs and SSDs sorted by model rather than shape?
- Which SSD logical commands are supported?
- How are command scope and errors recorded?
- Which equipment physically destroys SSDs?
- How are NAND packages and dies addressed?
- What happens when media type is uncertain?
- How are mistaken-method events reported?
- Can every certificate state the exact technique?
- How are assets reconciled across sorting and processing?
The provider should demonstrate the workflow before production processing.
Why Degaussing Does Not Work on SSDs: Decision Summary
Degaussing cannot sanitize NAND flash because it targets magnetic domains that SSDs do not use. Neither a stronger field, repeated cycle, damaged controller, nor failed power-on test changes that fact.
Use this process:
- Identify the media technology.
- Separate SSDs, HDDs, hybrids, and other media.
- Assign Clear, Purge, or Destroy.
- For reuse, select a supported SSD logical technique.
- Confirm command scope, encryption conditions, and tool support.
- For Destroy, use equipment suited to solid-state storage.
- Verify the logical result or physical remnants.
- Validate against target-data sensitivity.
- Isolate errors and reprocess with a suitable technique.
- Record the asset, method, evidence, and disposition.
Data Destruction Inc. provides SSD destruction, SSD shredding, and data wiping for approved enterprise projects. The project scope defines media identification, command or equipment suitability, custody, verification, and evidence before processing.
Frequently Asked Questions
Can a powerful magnet wipe an SSD?
No. SSDs store data in semiconductor memory as electrical states. Magnetic fields do not provide a valid NAND sanitization technique.
Can degaussing damage an SSD?
It may cause unrelated electronic problems, but damage does not prove that NAND data was sanitized.
What happens if an SSD is put through a degausser?
The equipment may complete its cycle while the SSD data remains. Isolate the device and process it with an SSD-suitable technique.
Does degaussing work on an NVMe drive?
No. NVMe describes an interface and command protocol used by solid-state storage. The data remains in nonmagnetic NAND flash.
Does degaussing work on a hybrid drive?
It can affect the magnetic portion if properly matched, but it does not sanitize the flash component. Hybrid drives require a process for both technologies.
Can an SSD be wiped and reused?
Yes, when the drive is operational, the selected logical technique is supported, the required storage scope is addressed, and the result is validated.
Is overwriting enough for an SSD?
Simple host overwriting may not reach prior data in spare, overprovisioned, remapped, or other controller-managed areas. Use current media-specific guidance.
Is cryptographic erase always enough?
No. It depends on encryption coverage, key management, implementation, cryptographic strength, and successful sanitization of every relevant key copy.
Does NIST SP 800-88 Rev. 2 prohibit SSD degaussing?
NIST states that degaussing should not be used for nonmagnetic media such as flash storage and SSDs.
What physical method should be used?
Use a technique and equipment approved by the organization’s current standard, policy, contract, and data-risk decision for solid-state media.
Request an SSD Sanitization Assessment
Provide SSD models, quantities, condition, interfaces, data classification, reuse goals, service location, governing requirements, and evidence needs. Data Destruction Inc. will review the scope and identify suitable logical or physical options.
Request an SSD Destruction Quote
Call: (866) 850-7977
Sources
- National Institute of Standards and Technology, NIST Special Publication 800-88 Revision 2, Guidelines for Media Sanitization, September 2025.
- National Institute of Standards and Technology, NIST SP 800-88 Rev. 2 PDF, Sections 3.1.2, 3.2, 4.5, and Appendix B.
- National Security Agency and Central Security Service, NSA/CSS Policy Manual 9-12, Storage Device Sanitization Manual, February 19, 2026.
- National Security Agency, Media Destruction Guidance and Evaluated Products Lists.