Insight

The sanitisation standards changed. Most disposal policies didn't.

Current sanitisation standards ask you to specify a required outcome and prove it per device, not to prescribe a method. What Clear, Purge and Destroy mean, and what adequate per-device evidence looks like.

The outcome matters more than the method

Most disposal policies still specify how storage must be erased. Current data sanitisation standards instead require organisations to identify the sanitisation outcome appropriate to the risk and establish evidence that the outcome was achieved for each device.

A policy that specifies a number of overwrite passes rather than a required sanitisation outcome is specifying the wrong thing.

The question worth asking is: What sanitisation outcome do we need for each type of media, and what evidence will prove it?

This article explains the current sanitisation outcome definitions, how they apply to different storage technologies, and what adequate evidence should look like when equipment has been processed.

What the current standards actually say

For teams reviewing data sanitisation standards in Australia, the practical starting point is NIST SP 800-88 Revision 2, supported by IEEE 2883-2022.

NIST SP 800-88 Rev 2 was published in September 2025. It supersedes Revision 1, published in December 2014, which NIST has withdrawn. This matters because the guidance against which many disposal policies were written has now been retired.

Revision 2 also changes the document’s focus. It removes Revision 1’s device-by-device appendices and concentrates on establishing and running a media sanitisation programme: selecting appropriate outcomes, overseeing processing, verifying and validating results, and retaining evidence. It is not simply a list of approved overwrite patterns.

IEEE 2883-2022 provides media-specific requirements and sanitisation techniques alongside NIST’s programme guidance. NIST points readers towards IEEE 2883 for relevant technical methods rather than attempting to prescribe every method for every device.

Neither NIST SP 800-88 nor IEEE 2883 is a certification that an ITAD supplier can hold. A supplier should be able to explain how its methods follow the guidance and substantiate its processing results.

Clear, Purge and Destroy: three different outcomes

These are not three competing product names or three settings in erasure software. They describe what the sanitisation must achieve against different levels of possible data recovery (IEEE 2883 calls the third category “Destruct”, where NIST calls it “Destroy”).

Clear — protection against straightforward recovery.

Clear applies logical techniques to user-addressable storage so that information cannot be recovered through ordinary, non-invasive access using the device’s normal interface. An appropriate overwrite of a supported magnetic hard drive can be a Clear technique. A Clear result does not, by itself, establish resistance to advanced laboratory recovery from areas outside that interface.

Clear can be sufficient where the information classification, destination of the asset and organisation’s risk assessment allow it. It should be an explicit decision, not the default because the equipment happens to support an overwrite command.

Purge — protection against advanced recovery.

Purge aims to make recovery of the target data infeasible even using state-of-the-art laboratory techniques, while potentially allowing the storage device to be reused. Depending on the media and its capabilities, suitable techniques can include dedicated device sanitise commands, block erase or cryptographic erase.

Cryptographic erase works by making the relevant encryption keys unavailable, not by writing across every storage cell. It depends on sound encryption implementation and key management; merely selecting an option labelled “crypto erase” is not enough. NIST generally favours Purge over Clear where a suitable method is available.

Destroy — render the media unusable and its data unrecoverable.

Destruction is the appropriate outcome where reuse is prohibited, the storage has failed, no reliable sanitisation technique is supported or the assessed risk demands it. The physical technique must suit the media and achieve the required security result. Drilling one hole through a drive, for example, should not automatically be treated as adequate destruction.

The distinction is a risk decision, not a technician’s personal preference. Classification, contractual obligations, future custody, device condition and intended disposition all matter. A functioning drive may be securely purged and reused; an inaccessible drive containing equally sensitive information may have to be destroyed.

Verification determines the outcome of the sanitisation technique that was applied. Validation confirms that the target data was in fact effectively sanitised.

Both sit downstream of the outcome decision. The organisation establishes what has to be achieved; verification and validation then establish whether it was.

For the practical distinction between software sanitisation and physical processing, see Secure Data Destruction & Brand Protection.

What adequate sanitisation evidence looks like

Because neither standard certifies an ITAD supplier, an organisation needs evidence of what actually happened to its equipment.

That evidence must be specific to each device.

A verifiable sanitisation record should identify four things:

  1. The standard applied. The record must identify the sanitisation standard followed for that device, rather than relying on a general statement about the supplier’s procedures.
  2. The outcome achieved. The result must identify whether the device achieved Clear, Purge or Destroy, as applicable. It should establish the outcome, not simply state that an erasure process was attempted.
  3. The device serial number. The individual device serial number must appear on the record itself, linking the result to an identifiable physical asset or storage device.
  4. The processing date and time. A time and date stamp must establish when sanitisation was performed.

All four elements matter. Together, they allow an organisation to return to a record months later, identify the exact device, establish which standard was applied, determine the sanitisation outcome and confirm when the work was completed.

Per-device erasure record showing the IEEE 2883-2022 standard applied, a Pass Purge result, the drive serial number and the date and time of erasure
A per-device sanitisation record: the standard applied, the outcome achieved, the device serial number and the time the work was done. Verified sector counts confirm the result rather than assuming the command succeeded.

A batch-level statement that equipment was securely processed satisfies none of these requirements on its own. It may confirm that a job was completed, but it does not establish what happened to an individual drive.

Across a project, the same discipline should produce a record that reconciles every unit, exceptions included.

Disposal audit report extract showing erasure results per unit, including a failed erasure escalated to physical destruction
An extract from a disposal audit report. Where erasure failed, the device was escalated to physical destruction and the final state recorded against the original assignment.

The same principle applies when specifying erasure software.

Mandating a particular erasure product in a disposal policy or tender is the same category of error as prescribing a fixed number of overwrite passes. Both specify a means of performing the work when the requirement should identify the outcome and the evidence needed to prove it.

Independently certified erasure tools can support methods following the same sanitisation standards. The distinction that matters to the customer is whether the supplier can produce the required evidence for each individual device.

A product name on a tender response is not a substitute for a serialised sanitisation record.

Organisations should therefore require suppliers to demonstrate the appropriate outcome and supply per-device evidence, rather than making a particular software product a mandatory condition.

Policies that currently mandate named erasure products should be revised to specify the required sanitisation outcome, the applicable standards and the evidence that must be returned.

Why overwrite logic breaks on flash storage

A conventional overwrite command writes to locations exposed through a device’s normal interface. On a solid-state drive (SSD), those locations do not map permanently to the same physical flash cells.

Wear levelling moves writes around. Over-provisioned capacity, retired blocks and spare cells can sit beyond normal host access. An overwrite may therefore report success without reaching every location where older data has been stored. Repeating the same host-level pass does not solve that underlying limitation.

For flash media, the relevant standards direct attention to suitable device-native sanitise operations and, where their prerequisites are satisfied, cryptographic erase. The correct choice depends on the device’s actual capabilities and the required Clear or Purge outcome.

A useful supplier answer identifies the command or technique used and its limitations. A statement that a number of passes were completed is not enough.

Beyond physical drives: logical and cloud storage

NIST SP 800-88 Rev 2 explicitly extends its scope to logical and cloud storage, areas not addressed by Revision 1.

A physical device may be correctly sanitised while copies remain in virtual disks, cloud volumes, backups or other managed storage. Sanitising the physical hardware does not automatically resolve those separate data holdings.

An organisation’s sanitisation programme should identify who controls that storage, what methods are available, how completion is confirmed and what evidence the provider can supply.

A disposal conversation limited to physical drives no longer covers the full obligation.

What to put in your disposal policy

Replace instructions based on a fixed pass count with requirements for an outcome, a suitable method and evidence of completion. The four lines below are illustrative starting points to be adapted against your own contractual, regulatory and internal obligations — general information, not legal or compliance advice:

Data-bearing media must be assigned a minimum sanitisation outcome of Clear, Purge or Destroy based on information sensitivity, media type, intended disposition and applicable contractual requirements.
Sanitisation techniques must be appropriate to the media and selected with reference to current NIST SP 800-88 guidance and applicable IEEE 2883 requirements.
A certificate of sanitisation must be retained, supported by traceable per-device records identifying the asset, sanitisation method and technique, verification and validation results, processing date and final disposition.
Media that cannot be sanitised or adequately verified must remain controlled and be escalated for an approved alternative, including physical destruction where required.

Revision 2 explicitly addresses retention of sanitisation evidence, including certificates of sanitisation. A certificate should be traceable to the devices processed, rather than merely recording that a batch was completed.

These requirements should sit within a broader IT Asset Lifecycle Management procedure covering collection, custody, processing and final disposition.

Also define who can approve exceptions and whether a failed device can leave controlled custody before a final decision.

Five questions to ask a disposal supplier

  1. What method do you use for each media type? Ask about magnetic HDDs, SATA and NVMe SSDs, mobile devices and failed or locked equipment separately. A single answer for everything is a warning sign.
  2. What happens if sanitisation fails? Ask how failed devices are isolated, whether retrying is permitted, who authorises escalation and when destruction becomes necessary.
  3. How is the result verified and validated? What does the tool or operator actually check, and how do you confirm the target data was effectively sanitised?
  4. What evidence do we receive? Request the certificate of sanitisation, method, tool or equipment used, outcome, exceptions, processing date and relevant destruction certificates, not merely a statement that the job is complete.
  5. How detailed is the reporting? Can each result be reconciled to a device serial number or other unique identifier, including any units sent for destruction?

The supplier’s answers should match the policy and be documented before collection, not negotiated after an exception occurs.

Review the outcome and the evidence

Review your current disposal policy and establish whether it specifies a sanitisation method or the required outcome. Then examine the evidence returned by your disposal supplier. Does it identify individual devices, the standard applied, the result achieved and the date the work was completed?

Shield Solutions produces per-device sanitisation records identifying the standard applied, the outcome achieved, the device serial number and the processing date. These are supported by certificates tying the applicable standard, sanitisation status and completion date to each asset and storage device serial number, with client portal visibility.

Further information about our management systems and assurance approach is available under Compliance & Governance.

The practical next step is to make sure your disposal policy requires the right outcome and that your supplier can provide the individual device records needed to prove it.