Shared language for colo and enterprise media sanitization — and how Asset Decom maps each method to a serialized Certificate of Destruction.
Kansas City–based. Midwest colo + nationwide crews and freight.
CLEAR
Logical / overwrite class
PURGE
Stronger / CE class
DESTROY
Physical / unusable
CODs
Serialized per drive
Why it matters
When gear leaves a live cage, auditors do not want a vague “wiped” checkbox. They want a shared vocabulary for how thoroughly media was handled, who held it, and what paperwork closes the work order. NIST SP 800-88 Rev. 2 is that vocabulary for most U.S. enterprise and colo ITAD programs.
It does not replace your internal data-handling policy. It gives procurement, security, and vendors the same labels — Clear, Purge, Destroy — so a Certificate of Destruction (COD) and chain-of-custody log can be filed without arguing definitions after the truck rolls.
On a live data center floor that means: serials logged at extraction or intake, method chosen per asset and risk, and a COD that names what happened to each unit. For the operational media program see hard drive destruction. For full cage teardown see data center decommissioning. For residual value on chassis and components see server buyback.
CLEAR
Clear covers logical techniques that protect against simple, non-invasive recovery — for example overwrite-style approaches where the media supports them. The goal is to make user data inaccessible through ordinary means, not to defeat a well-equipped laboratory attack.
When it fits
Lower-sensitivity reuse inside a controlled environment, when your policy still treats the asset as under organizational control and allows Clear as the bar.
Limitations
Clear is typically not the right choice when media will leave organizational control, go to resale channels, or face elevated recovery risk. Many colo and enterprise policies skip Clear for drives leaving the facility and require Purge or Destroy instead.
PURGE
Purge is the stronger sanitization class — techniques intended to resist laboratory-level recovery attempts appropriate to the media type. In practice that often means cryptographic erase on self-encrypting drives, or overwrite / sanitize commands suited to HDD, SSD, and NVMe, chosen for the technology rather than a one-size script.
When it fits
The common enterprise and colo bar before reuse or resale of drives: media may still function as storage, but residual data risk is reduced to a level policy accepts for leaving controlled custody or entering secondary markets.
Reuse / resale note
When finance wants residual value on flash or disks that remain sellable devices, Purge (where media and policy allow) keeps buyback in play. Destroyed drives are debris, not inventory. Coordinate media policy with server buyback so the residual model does not assume every bay is zeroed.
DESTROY
Destroy means physical destruction so the media cannot be reused as storage: shred, disintegrate, incinerate, or another applicable process for the form factor. The outcome is unusable debris, not a wiped drive waiting for a second life.
When it fits
Highest assurance requirements; failed or unsupported media that cannot be reliably Purged; policy that requires drives leave the program as scrap; highly sensitive lots where security wants Destroy under escort before gear rolls.
Practical note
Degaussing and shredding are tools that can support a Destroy path where they fit the media. Flash and spinning disk do not always share the same physical process — name the media type so the method plan is honest on the COD.
How we apply it
We do not claim one method for every drive. Method is chosen per asset, media type, and your risk / policy posture — then recorded on a serialized COD.
Align Clear / Purge / Destroy to your written bar and the media mix on the BOM.
Log at extraction or intake so chain of custody starts in the cage, not at the dock.
Clear, Purge, or Destroy in NIST SP 800-88 Rev. 2 language — not a generic recycle note.
Certificate of Destruction audit can attach to the work order or vendor risk file.
Asset Decom’s public materials state NIST-oriented sanitization, serialized CODs, and $1M E&O / cyber liability. We do not claim certifications we do not hold. If an RFP requires a named certification, ask us directly and we will answer with current credentials only.
Operational delivery lives on the hard drive destruction page (on-site or off-site). Full cage programs run through data center decommissioning. Residual value on non-destroyed assets sits under server buyback.
FAQ
It is the U.S. framework most enterprise and colo buyers use for media sanitization vocabulary. It defines Clear, Purge, and Destroy so auditors and vendors share the same language about how thoroughly media was handled.
Clear fits lower-sensitivity reuse inside a controlled environment when policy allows. Purge is the common enterprise bar before reuse or resale. Destroy is for when policy requires media to leave as unusable debris, not a reusable storage device.
Yes. We issue a serialized COD that records the method applied to each drive or media unit under NIST SP 800-88 Rev. 2 language — not a blanket “all media wiped” statement.
Yes, when policy requires media never leave the facility uncleared, or when colo security wants wipe or destroy under escort. Off-site processing is available when sealed, logged transport is allowed. See hard drive destruction for delivery options.
Destroyed drives are not buyback candidates as storage devices. Chassis, CPUs, enterprise RAM, networking, and sometimes reusable flash when policy allows Purge and resale may still carry residual value under the same program.
Get a quote
Send the drive or media inventory — or a full rack list — and receive a range and method plan aligned to NIST SP 800-88 Rev. 2 within 24 hours. White-glove ITAD for live data centers and colo floors.
Or call 913-303-2166 · quotes@assetdecom.com
Quote desk
Send drive inventory or rack list. Method plan within 24 hours.
