Degaussing HDDs: Media Compatibility and Evidence

Short answer

Use degaussing only when the magnetic recording medium, the particular degausser and the approved operating procedure are demonstrably compatible. A drive becoming unreadable after exposure is not enough evidence that its data was sanitized. Do not use a magnetic treatment as an SSD erasure method, and do not assume that every device sold as a hard drive has the same storage components.

Before committing an asset, answer three questions: what exactly contains the target data, which documented treatment covers that material, and what evidence will let the responsible reviewer accept the result? If any answer is missing, keep the drive under controlled custody and choose another authorized route. A generic field-strength advertisement cannot answer those questions.

Who this is for

This guide is for ITAD operators, disposal managers and information owners deciding whether a degaussing service is suitable for a specific HDD lot. It concerns authorized end-of-life sanitization, not restoring drives to service or recovering files. It does not give a universal exposure setting, pass count or machine operating procedure.

The technical references checked for this guide are NIST SP 800-88 Revision 2, published September 2025, and the NSA/CSS October 2026 equipment lists. The latter concern their stated NSA/CSS equipment and media scope; they are not a blanket commercial certification. The currently linked full Manual 9-12 was inaccessible during this review. No additional requirements from that manual are reconstructed here.

When to use this

Evaluate this route when a magnetic HDD is destined for an approved disposal process and a qualified treatment facility can establish compatibility before accepting the job. A failed interface does not necessarily prevent an external physical treatment, but it makes the pre-treatment identity record more important.

Create a separate exception lane for unknown recording technology, missing labels, hybrid devices and mixed boxes of drives. An intake queue that groups devices by enclosure size alone can silently put different media into one process. Resolve identity while it is still possible to associate the device with its original system and owner.

When not to use this

Do not select degaussing to preserve resale functionality. Do not use it for flash-only storage, or treat it as a way to erase other retained copies such as backups. Do not proceed while a legal hold, unresolved ownership question or required recovery decision remains open.

Stop if the facility cannot identify its exact machine, provide applicable media support, explain an adapter requirement, or supply the prescribed completion evidence. An offer to repeat an unsupported treatment several times does not resolve the missing support.

Workflow

1. Freeze the asset and data scope

Record the asset identifier, manufacturer, exact model and serial number before treatment. If the drive cannot report its identity electronically, preserve a legible label photograph and the intake association. Mark which fields were observed and which remain uncertain.

Define the decision as treatment of a particular physical asset. A statement about one drive does not cover a removed controller board, an image made during diagnosis, or another drive previously swapped into the same server bay. Keep those objects as separate entries when they belong to the deletion scope.

For a mixed shipment, create distinct work orders for identified conventional magnetic drives and unresolved devices. This makes it possible to reject one exception without falsely closing the entire shipment.

2. Establish the storage technology

Collect the model-specific description of recording technology and persistent components. Resolve whether the device is a regular magnetic HDD, a hybrid with non-magnetic storage, or a different technology. Do not infer that a magnetic platter treatment also treats flash attached to the assembly.

NIST SP 800-88 Rev. 2 warns that modern magnetic media and hybrid constructions complicate degaussing; unsuitable treatment can disable a device without sanitizing its target data. It does not classify degaussing itself as a destroy technique. These are reasons to require a compatibility decision before running the machine, rather than to substitute a stronger-sounding marketing phrase.

If support evidence is unavailable, record “compatibility unresolved,” not “probably standard HDD.” A conservative unresolved state is more useful than a successful-looking record whose central assumption cannot be checked.

3. Match the machine and procedure

The October 2026 NSA/CSS Magnetic Degaussers list covers specified magnetic media and excludes HAMR HDDs from its acceptable HDD entries. It directs hybrid and HAMR questions to the separate HDD list. It also notes model-specific passes, adapters or disassembly requirements. Its 30,000-gauss threshold for accepting new degaussers for evaluation is not a universal drive-level operating prescription.

For a job using that framework, match the exact equipment model and permitted material. Do not transfer approval between similarly named models. For a job governed by another organizational standard, retain the actual authority and compatibility evidence rather than borrowing the NSA label.

Ask the facility to identify the applicable loading arrangement and operating instructions for the selected machine. Record the document revision used. This guide deliberately supplies no exposure time, orientation or opening instructions for unidentified equipment.

4. Check the evidence collection route before processing

Agree how the operator will bind each asset to its treatment event: scan, job identifier, timestamp and operator record are possible elements. Decide how an interrupted cycle, failed check or missing item will be flagged. A facility-wide daily total cannot on its own establish which serial numbers were processed.

Include equipment condition and required verification checks in the work order. The NSA customer FAQ describes a calibrated field-verification device as supplemental to routine manufacturer maintenance, not a replacement. Preserve the actual relevant result and its date instead of merely checking a box that says “machine checked.”

Separate evidence needed to accept the machine's condition from evidence that this asset actually went through the prescribed process. Both questions matter, and neither record substitutes for the other.

5. Control exceptions and onward disposition

A completed treatment event should move to review; a failure should move to an exception state with the asset still accounted for. Do not relabel a failed cycle as complete because a drive no longer enumerates. Repeated failure needs an authorized alternative treatment decision.

Where the October 2026 NSA degausser framework applies, HDD treatment also calls for deformation of all platters. That is an additional stage, not proof that an otherwise unsupported magnetic treatment worked. Track the stages separately so a missing second event cannot disappear inside a single “destroyed” status.

Before the lot leaves custody, reconcile submitted assets, completed records, unresolved exceptions and the authorized destination. Keep identifiers available long enough to finish that reconciliation; remove sensitive ownership markings at the appropriate release stage under the applicable procedure.

Verification checklist

• Does the record identify the actual physical asset and its storage technology?
• Is the selected machine supported for this medium under the recorded authority and revision?
• Were required equipment checks and the prescribed procedure documented?
• Can the individual asset be linked to a completed treatment event?
• Were interruptions, unsupported components and failed checks kept visible?
• Were any required additional stages completed and reviewed?
• Did an authorized reviewer accept the evidence before release?

These are acceptance questions, not a claim that a workstation read test can inspect the post-treatment magnetic state. A failed read proves only the observed access failure. It cannot distinguish all possible reasons why access failed.

Verification note: evidence to collect

No degausser, field instrument or physical drive was tested for this article. For an actual job, collect the model-specific compatibility decision, machine identity, operating-procedure revision, equipment-check evidence, individual treatment record and exception disposition. The reviewer should be able to reproduce the administrative reasoning without relying on a sales brochure or an operator's memory.

A simple rehearsal can check the record workflow without processing media: submit a fictional identifier, mark a simulated interruption and confirm that the release report leaves it unresolved. Such a rehearsal tests record handling only. It must never be presented as a sanitization trial.

Resale and evidence checklist

Separate storage intended for reuse from assets assigned to physical disposal before authorizing treatment. Preserve the owner's selected destination, any contractual handling conditions and the final custody transfer. Do not advertise a degaussed asset as a verified reusable drive merely because its outer case is intact.

The downstream report should name the actual method and scope. “Processed at a destruction facility” is too broad when it hides whether a hybrid component was omitted or an additional required step remains outstanding.

What not to publish

Keep customer serial numbers, shipment identifiers, access-control details and internal security classifications out of public case studies. Publish no blanket claim that any magnet, any field rating or any non-working drive establishes irreversible data removal. Do not attach an equipment-list label to a service provider without checking what that label actually describes.

Common mistakes

The most consequential mistake is treating a physical symptom as a sanitization result: the device stopped working, therefore the information must be gone. Another is treating procurement evidence as job evidence: the facility bought a suitable machine, therefore every item in the shipment was correctly processed.

Also avoid flattening mixed storage into “HDD,” using an old acceptable-material list without checking its edition, or closing an entire batch while an unidentified item remains. Each shortcut removes a question that the final reviewer still needs answered.

CliDeck workflow fit

Use an asset-linked checklist to preserve scope, process evidence and unresolved questions through handoffs. Where console records exist, keep their purpose narrow: they may support intake identification or prior state, not demonstrate the effectiveness of an external magnetic process. This workflow advice makes no claim about unannounced wiping-software capabilities or certification.

FAQ

Is there one field-strength number that proves every HDD is sanitized?

No universal number is established here. The media, equipment support and complete procedure must match. A procurement threshold and a specific asset's accepted treatment are different claims.

Does an unreadable drive count as successfully degaussed?

No. Unreadability alone does not establish what happened to the target data. Preserve the treatment and compatibility evidence.

Can the same process cover an SSD in the same drive caddy?

Do not infer that. Identify the storage technology and assign a suitable authorized method for that device.

Related guides

For unresolved devices, use the failed-drive exception workflow. Review the evidence coverage model when one assembly contains multiple retained-data locations, and the NIST program guide for acceptance roles.