Join our Newsletter — 33% off our NHI Course
Home› Guides› IT Asset Disposition (ITAD) Security Guide: Chain of…
Guide Data Security

IT Asset Disposition (ITAD) Security Guide: Chain of Custody, Vendor Assurance and Proof of Sanitisation

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 14 min read
On this page

Retired laptops, servers, phones and storage arrays leave the organisation still holding customer data, credentials and keys, and the weakest point is usually not the wiping tool but the handover to whoever collects, moves and processes the equipment. IT asset disposition (ITAD) covers everything from the decision to retire an asset to the final certificate that its data is gone and the hardware has been reused, recycled or destroyed. This guide focuses on the security controls around that process: chain of custody, choosing and assuring ITAD vendors, what a certificate of sanitisation must contain, how to reconcile assets, and how to measure the programme. It is written for security, IT operations, procurement and privacy teams. Sanitisation techniques themselves are covered in the Media Sanitisation Guide, and retention decisions in the Data Retention and Secure Deletion Guide.

Key takeaways

  • Custody fails before technology does. The SEC's 2022 Morgan Stanley Smith Barney action concerned a moving company with no data destruction experience that sold decommissioned drives, which were then resold online with customer data on them.
  • Track by serial number end to end. NIST SP 800-88 Rev. 2 asks for records when media enters the environment, when it leaves its last location and when it reaches its post-sanitisation destination; reconcile all three.
  • Certificates must be per device. SP 800-88 Rev. 2 says a certificate of sanitisation should be completed for each item of storage media, with make, model, serial, method, tool and version, and who verified it.
  • Certification is due diligence, not a guarantee. R2v3, e-Stewards and NAID AAA show that a vendor has been audited, but you still need contract terms, your own audits and sample verification.
  • Retire the identity as well as the hardware. Remove devices from MDM and directory services, revoke device certificates and rotate any secrets stored on network and server equipment before it leaves.

What ITAD covers and where the risk sits

NIST SP 800-88 Rev. 2, Guidelines for Media Sanitization (Final, September 2025, superseding Rev. 1 of December 2014), frames sanitisation as making access to target data infeasible for a given level of effort, inside an organisational sanitisation programme. ITAD wraps that programme in logistics and supplier management. Each stage has its own failure mode.

StageTypical activityMain security riskControl
Retirement decisionRefresh, failure, lease return, office closureAsset never flagged for sanitisationDisposal workflow triggered from the asset register
Identity and data retirementBackup, MDM removal, account and certificate revocationDevice still trusted by the directory; secrets left in configsDeregistration and rotation checklist before collection
Storage on siteCages, cupboards, loading baysTheft, loss, unrecorded removalLocked, access-controlled store; counts against register
Collection and transportVendor pickup, courier, own staffUnvetted carriers, items going missing in transitSigned manifest by serial number; sealed containers; vetted drivers
ProcessingWiping, shredding, refurbishing, recyclingWrong method for the media; skipped devices; downstream resaleContracted methods; per-device certificates; downstream controls
Final dispositionResale, donation, recycling, destructionData-bearing parts leaving with no recordReconciliation and certificate archive

Choosing the sanitisation outcome per asset

SP 800-88 Rev. 2 defines three outcomes. Clear applies logical techniques to all user-addressable locations and protects against simple, non-invasive recovery. Purge makes recovery infeasible using state-of-the-art laboratory techniques while the media may remain reusable; logical purge includes overwrite, block erase and cryptographic erase. Destroy makes recovery infeasible and leaves the media unusable, using techniques such as disintegrating, incinerating, melting, pulverising and shredding.

SituationUsual choiceWhy
Asset will be resold or redeployed, data of moderate sensitivityPurge (logical), with verificationKeeps resale value; SP 800-88 notes purge or clear may be preferred where reuse, contracts, environment or cost matter
Encrypted laptop or phone going to refurbishmentCryptographic erase or factory reset that destroys keys, then verificationFast and reliable where encryption was on from first use
Data was ever stored in plaintext on the deviceDo not rely on cryptographic eraseSP 800-88 Rev. 2 says cryptographic erase cannot be used if sensitive data was previously stored unencrypted
Failed drive, unknown history, or highly sensitive dataDestroyMedia that cannot be logically sanitised or verified; SP 800-88 notes destruction can be the simplest option when there is no reuse
Magnetic-only media (tapes, older hard drives)Degauss or destroyThe UK NCSC notes degaussing suits only exclusively magnetic media and the degausser must match the drive technology

For destruction, the NCSC's secure sanitisation guidance recommends particles of 6 mm or less for OFFICIAL data, with particle size verified afterwards, and erasing the data first where possible. SP 800-88 Rev. 2 points to IEEE 2883 for current media-specific techniques and to ISO/IEC 27040 for programme elements.

Chain of custody

SP 800-88 Rev. 2 does not use the phrase "chain of custody", but its record-keeping expectations amount to one: track media from the moment it enters the environment, through the point it leaves its last location, to its post-sanitisation destination, with the property management function tracking sanitised media. A workable chain of custody has these parts.

  1. Asset register entry: every data-bearing asset has an asset tag and manufacturer serial number recorded, including removable drives inside servers and arrays. Reconcile against the Asset Inventory and CMDB Security Guide approach.
  2. Pre-collection count: before collection, list items by serial number on a manifest, place them in sealed, numbered containers and record the seal numbers.
  3. Handover signatures: your representative and the driver both sign the manifest, with date, time and vehicle. Use only carriers named in the contract.
  4. Receipt at the facility: the vendor confirms receipt with seal numbers intact and a count by serial, and reports discrepancies within an agreed time, for example one working day.
  5. Processing record: each device is linked to its sanitisation or destruction record.
  6. Final reconciliation: your team matches register, manifest, receipt and certificates. Any item without a certificate is treated as a potential data loss until found.

On-site versus off-site: SP 800-88 Rev. 2 lists who performs sanitisation and whether it is on or off site as factors to weigh. On-site shredding or wiping removes the transport risk and suits high-sensitivity media; off-site processing is cheaper at volume but needs stronger transport controls. Many organisations wipe or destroy drives on site and send only the sanitised chassis away.

Vendor assurance

Certifications and what they tell you

SchemeRun byWhat the official pages say it coversWhat to check
R2v3SERI; certification bodies audit facilitiesFull reverse supply chain; environmental, health and safety, quality and data security; Appendix B adds enhanced data destruction with serial-level tracking; Appendix C (test and repair) requires logical sanitisation; certification covers downstream vendorsThat the facility you use holds Appendix B if data destruction is in scope
e-StewardsBasel Action NetworkRecycling and refurbishment by certified processors, who must destroy all residual data; also addresses hazardous e-waste exportCertificate scope and site address
NAID AAA Certificationi-SIGMAVoluntary certification for member companies providing secure information destructionThe service types certified (for example on-site or plant-based) in the directory listing
CAS-S and ADISA (UK)NCSC (CAS-S); ADISANamed by the NCSC as recognised certifications to look for when assessing a sanitisation provider; CAS-S is for providers serving HMG customersCurrent listing and scope of certification

In the United States, the FTC Disposal Rule at 16 CFR 682.3 gives examples of reasonable due diligence on a disposal company: reviewing an independent audit, checking references, requiring trade association certification and reviewing its security policies, then monitoring its compliance. That list is a sound baseline anywhere.

Contract terms

  • Methods: the sanitisation outcome (clear, purge or destroy) per asset class, the tools allowed and the verification required.
  • Certificates: per-device certificates in a machine-readable format within a fixed time after collection.
  • Subcontractors and downstream: no subcontracting of data-bearing processing without approval, and no resale of data-bearing components that have not been sanitised and certified.
  • Personnel and facility: background screening of staff handling assets, access-controlled processing areas and CCTV retention long enough to support investigations.
  • Audit rights: announced and unannounced audits, and the right to send sample devices for independent forensic verification.
  • Incident terms: notification of lost or unaccounted items within a fixed time, and cooperation with your breach process. Under GDPR, an ITAD vendor handling devices that hold personal data is a processor, so the Article 28 contract terms and Article 32 security measures apply.

Treat ITAD vendors as third parties with access to your most sensitive data at its least protected moment. See the Vendor Security Assessment Template.

Certificates, verification and evidence

SP 800-88 Rev. 2 separates verification (inspecting results to confirm the technique completed successfully) from validation (a decision to approve the sanitisation as effective or reject it, with rejected media sanitised again by a different or stronger method). Its certificate of sanitisation should be completed for each item and include the following fields.

FieldWhy it matters
Manufacturer, model and serial numberMatches the certificate to the asset register; batch certificates ("200 drives destroyed") cannot be reconciled
Organisational media or property numberLinks to your asset tag
Media type and sourceShows the method suited the media (for example SSD versus magnetic)
Sanitisation method and techniqueClear, purge or destroy, and how
Tool used, including versionAllows recall if a tool version is found defective
Verification methodEvidence the result was checked
Name, title, date, location, contact details and signature of those who verified and validatedAccountability
  • Sample testing: send a small random sample of "sanitised" drives each year to an independent laboratory to attempt recovery. This is the only direct test that the vendor's process works.
  • Cryptographic erase evidence: SP 800-88 Rev. 2 lists documentation items for cryptographic erase and warns not to trust it where backups or escrowed keys exist without high confidence in key handling. Record that keys were destroyed, not only that the device was reset.
  • Retention: keep certificates and manifests for at least as long as the data on the device would have been retained, so you can answer a regulator or a data subject later.

Where identity fits

A retired device is often still an identity. Laptops remain registered in the directory and MDM, servers and network appliances hold service account passwords, API keys, SNMP communities, VPN pre-shared keys and private keys in configuration files, and hardware security tokens may still be enrolled.

  • Devices: retire the device object in your directory and MDM, revoke device certificates, and remove enrolment and activation locks (for example Apple Activation Lock or Android factory reset protection) so the vendor does not need your credentials and the next owner is not locked out.
  • Servers and network gear: rotate every secret stored on the device before it leaves, not after a certificate arrives. See the NHI Offboarding and Decommissioning Guide.
  • Keys in hardware: clear TPMs and zeroise HSMs and smart cards; SP 800-88 Rev. 2 recommends zeroisation of target keys as part of cryptographic erase. See the HSM Deployment and Operations Guide.

Implementation roadmap

  1. Inventory and policy (month 1): list data-bearing asset classes, assign a default outcome per class and write it into the disposal policy. The Data Retention and Disposal Policy Template is a starting point.
  2. Retirement checklist (month 1 to 2): build the identity and data retirement steps into the IT asset workflow so nothing is collected before they are done.
  3. Vendor selection (month 2 to 3): run due diligence, confirm certification scope for the actual facility and agree the contract terms above.
  4. Pilot (month 3): run one site or one asset class through the full chain, reconcile every serial and sample-test drives.
  5. Scale and audit (month 4 onwards): extend to all sites, schedule vendor audits and annual sample testing.
  6. Fallback: if a vendor fails an audit or loses items, suspend collections, switch to on-site destruction for high-sensitivity media and keep assets in the secure store until a replacement is contracted.

Small organisations can often destroy or wipe drives themselves with a documented tool and keep certificates, sending only sanitised hardware to a certified recycler. Large organisations usually need a contracted ITAD vendor with on-site services for data centres, serial-level reporting through an API or portal, and a dedicated reconciliation owner.

Detection and measurement

  • Reconciliation gap: assets marked retired with no matching certificate after the contracted period (target zero).
  • Certificate quality: percentage of certificates with serial number, method, tool version and verifier present (target 100 per cent).
  • Dwell time: days between retirement and certificate, and days in the on-site store; long dwell is where devices go missing.
  • Identity retirement: percentage of collected devices whose directory, MDM and certificate records were retired before collection.
  • Sample test results: recoverable data found in independent testing (target zero) and audit findings closed on time.
  • Signals to watch: retired devices that check in to MDM or authenticate to the directory after collection, and your organisation's asset tags or hostnames appearing in resale listings.

Framework mapping

FrameworkReferenceRelevance
NIST SP 800-53 Rev 5MP-6 Media Sanitization; MP-6(1) Review, Approve, Track, Document, and Verify; MP-6(2) Equipment Testing; MP-6(3) Nondestructive TechniquesSanitisation, records and verification
NIST SP 800-53 Rev 5SR-12 Component Disposal; PE-16 Delivery and Removal; CM-8 System Component InventoryDisposal, movement out of facilities, inventory
NIST SP 800-53 Rev 5SA-9 External System Services; SR-6 Supplier Assessments and ReviewsITAD vendor oversight
NIST CSF 2.0ID.AM-08, PR.DS-01, GV.SC-07Asset life cycle, data at rest, supplier risk across the relationship
ISO/IEC 27001:2022 Annex AA.7.14 Secure disposal or re-use of equipment; A.8.10 Information deletionDisposal and deletion controls
US law16 CFR 682.3 FTC Disposal Rule; SEC Regulation S-P Disposal RuleReasonable disposal measures and vendor due diligence
EU and UK GDPRArticle 28 processors; Article 32 security of processingContract and security obligations for ITAD vendors

Common failure patterns

  • Using a mover instead of a data destruction vendor: in the SEC's 2022 order, Morgan Stanley Smith Barney paid a $35 million penalty after a moving and storage company it hired sold thousands of devices, some resold on an internet auction site with unencrypted customer data still on them.
  • Encryption assumed but never turned on: the same SEC action found encryption capability on decommissioned local devices had not been activated for years, so "it was encrypted" was not true.
  • Missing items found only at reconciliation: in that case a records reconciliation found 42 servers missing. Reconcile promptly after every collection, not once a year.
  • Batch certificates: a single certificate for a pallet cannot prove any specific drive was processed.
  • Forgotten storage: drives in printers, copiers, network appliances, lab equipment and spare parts stock are left out of the register.
  • Secrets left on retired infrastructure: firewall, switch and server configurations leave with working credentials that were never rotated.

Lessons from incidents

The Morgan Stanley Smith Barney case is the clearest public example of an ITAD failure. The sanitisation tools were not the issue; the vendor was not qualified, the work was not monitored, encryption was not active and the asset count did not reconcile. The SEC found violations of the Safeguards Rule and the Disposal Rule under Regulation S-P, affecting about 15 million customers over roughly five years. Every one of the controls in this guide, from vendor due diligence to serial-level reconciliation, addresses a step in that chain.

Practitioner checklist

  • Record serial numbers and asset tags for every data-bearing asset, including drives in servers, arrays, printers and appliances.
  • Set a default sanitisation outcome (clear, purge or destroy) for each asset class in policy.
  • Complete identity and secret retirement (directory, MDM, certificates, stored credentials) before collection.
  • Use sealed containers and signed, serial-level manifests for every collection.
  • Select vendors after documented due diligence and confirm certification scope for the actual facility.
  • Require per-device certificates with the SP 800-88 Rev. 2 fields.
  • Reconcile register, manifest, receipt and certificates after every collection.
  • Sample-test sanitised drives with an independent laboratory at least yearly.
  • Audit the vendor, including unannounced visits, and review downstream processors.

Standards and references

Related NHI Mgmt Group resources: Media Sanitisation Guide · Data Retention and Secure Deletion Guide · Data Retention and Disposal Policy Template · NHI Offboarding and Decommissioning Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.