Industries / Technology / IT hardware recycling
Data wiping
Data wiping is the work of removing everything a previous owner stored on a used computer, phone or server, so that the device can be sold again instead of shredded, and of proving that it was done.
6
Milestones achieved, from 2001 to 2025.
1
To watch for: announced, not yet confirmed outside.
2
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
2001
Drives erase themselves
The Secure Erase command was added to the ATA standard for PC hard drives at the request of the Center for Magnetic Recording Research (CMRR) at the University of California, San Diego. It tells the drive to overwrite every area that could hold user data, including spare sectors the computer cannot reach. By CMRR's testing it is built into all ATA drives made after 2001 with more than 15 GB, and CMRR's free HDDerase program runs it from a boot disk. A normal secure erase takes 30 to 60 minutes, the CMRR tutorial says, while drives that encrypt their data can erase by changing the key in milliseconds.
Credit
Gordon Hughes, CMRR; the T13 committee, which keeps the ATA standard
2009
Drives that encrypt everything
On 27 January 2009 the Trusted Computing Group published Opal, a specification for self-encrypting drives in PCs. Such a drive encrypts all it stores with a key held inside the drive, and a range of the disk is erased by generating a new key for it.
LessonIn November 2018 Carlo Meijer and Bernard van Gastel of Radboud University reported that the hardware encryption of many SSDs from Crucial and Samsung could be bypassed without the password, and wrote that compliance tests "do not reveal design and implementation weaknesses"; an erase that changes a key relies on firmware that outsiders rarely check.
Credit
Trusted Computing Group, Storage Work Group
2015
Factory resets leave data
Laurent Simon and Ross Anderson of the University of Cambridge bought second-hand Android phones from eBay and UK phone recyclers in 2014 and tested the factory reset on 21 smartphones from five makers, running Android 2.3 to 4.3. They estimated that up to 500 million devices might not properly erase the partition that holds account credentials, and up to 630 million might not erase the internal SD card, where photos and other media are kept. On every phone with a flawed reset they recovered the owner's Google credentials.
LessonA reset is only as good as the storage drivers beneath it; Android now requires every device launching with Android 10 or later to use file-based encryption.
Credit
Laurent Simon and Ross Anderson, University of Cambridge
2017
A sanitize command for SSDs
NVM Express revision 1.3, ratified on 26 April 2017, added an optional Sanitize command for NVMe solid-state drives (SSDs), drives that connect through PCI Express, a computer's fast internal link. It alters all user data in the drive, including caches and areas the computer cannot address, by block erase, by crypto erase (changing the media encryption keys) or by overwriting, and once started it keeps running through power cycles. Revision 1.2.1 of 2016 has no such command.
Credit
NVM Express, Inc
2019
Leased drives sold at auction
In spring 2019 Fujitsu Leasing removed hard drives from servers it had leased to Kanagawa Prefecture, Japan, and gave them to Broadlink, a Tokyo data-erasure firm, for disposal. A Broadlink employee took 18 drives of 3 TB each and sold them on Yahoo Auctions without erasing them. A man who runs an IT company bought nine, found what appeared to be prefectural documents, among them tax notices naming people and firms, and told a newspaper; the prefecture announced the leak on 6 December 2019 and later recovered all 18 drives.
LessonThe lease required a certificate that the data had been erased, but Fujitsu Leasing did not ask the recycler for one and the prefecture did not ask for it, by Monolith Law Office's account.
Credit
the buyer who reported the drives; Kanagawa Prefectural Government
2025
Erase by key, by law
Since 20 June 2025, smartphones and tablets sold in the EU must encrypt the user data in their internal storage by default with a random key, and must include a factory reset that securely erases that key and generates a new one. The regulation lists these among its "requirements for preparation for reuse".
Credit
European Commission, Regulation (EU) 2023/1670
Watch for
Microsoft reuses its own SSDs
Microsoft says its Boydton Circular Center completed a pilot in 2024 for reusing solid-state drives inside the company, "paving the way for broader reuse of high-impact components". It gives no count of drives and no method of erasure. Large cloud operators have usually destroyed drives at retirement: the Circular Drive Initiative, a group of technology companies, estimates that nine in ten drives are destroyed when taken out of service, TechSpot reported in June 2023.
Achieved whenMicrosoft or an outside auditor publishes how many drives were erased and reused and how each erasure was checked.
Claimed by
Microsoft, in its 2025 Environmental Sustainability Report, June 2025
Open
01
Check the EU reset rule
A public test of whether the factory reset on phones sold in the EU since 20 June 2025 leaves anything behind. Load each new phone with made-up data the team writes itself, including 1,000 unique marker strings spread across contacts, messages, photos and files. Reset it with the default settings, then search for the markers: in a raw copy of the user partition, on models whose bootloader (the program that starts the phone) can be set to accept outside software, which is done before any data is loaded; on any removable memory card; and in eSIM profiles and account locks.
The briefCredit · unclaimed02
Test one-button server erase
A public table of what each server maker's built-in erase leaves behind. Set up servers from Dell, HPE and Lenovo with made-up users, passwords, network settings, logs, disk arrays, TPM keys (the keys held in the server's security chip) and drive contents. Run the maker's erase, then read back every place a setting or record can stay: the management controller (BMC, the small computer that runs the server's remote console), BIOS, disk controller, security chip, boot media and drives.
The briefCredit · unclaimed
Open 01 · the brief
Check the EU reset rule
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A public test of whether the factory reset on phones sold in the EU since 20 June 2025 leaves anything behind. Load each new phone with made-up data the team writes itself, including 1,000 unique marker strings spread across contacts, messages, photos and files. Reset it with the default settings, then search for the markers: in a raw copy of the user partition, on models whose bootloader (the program that starts the phone) can be set to accept outside software, which is done before any data is loaded; on any removable memory card; and in eSIM profiles and account locks.
Why it is still open
The last broad test of phone resets, by Cambridge, covered Android 2.3 to 4.3. The EU rule now requires encryption by default and a reset that erases the key. Searches found no published test of current phones against it.
Built with what exists
New phones bought at retail, never given anyone's real data; Android SDK Platform-Tools (adb to load data, fastboot to start a recovery image without installing it and copy the user partition); grep or bulk_extractor to search the copy for markers; PhotoRec to recover files from memory cards; Python with the Faker library to write made-up contacts and messages.
First step
Buy two new phones of one model with memory card slots, plant 1,000 markers on each, reset one with the default settings, and search its card with PhotoRec.
Done looks like
At least 30 models from at least eight makers, each with a published result: encryption on or off by default, how many of the 1,000 markers were found in the user partition, and whether memory card files and eSIM profiles survive a default reset, with every log.
Open 02 · the brief
Test one-button server erase
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A public table of what each server maker's built-in erase leaves behind. Set up servers from Dell, HPE and Lenovo with made-up users, passwords, network settings, logs, disk arrays, TPM keys (the keys held in the server's security chip) and drive contents. Run the maker's erase, then read back every place a setting or record can stay: the management controller (BMC, the small computer that runs the server's remote console), BIOS, disk controller, security chip, boot media and drives.
Why it is still open
A reseller's 2026 summary of the makers' manuals lists what each erase skips. Dell's System Erase keeps the flash memory holding the service tag, asset tag and licence data; HPE's one-button secure erase needs an iLO Advanced licence and skips USB drives and SD cards. Searches found no published test that reads back what remains after each erase.
Built with what exists
New servers, or lab servers whose whole history the team controls, set up from factory defaults; the DMTF Redfish interface and ipmitool to read the management controller; Dell RACADM, HPE's iLO RESTful interface and Lenovo XClarity Essentials OneCLI; tpm2-tools; nvme-cli and sg3_utils to check drives; an AI agent that runs the checklist and cites the log line behind each finding, built with a kit such as Cursor's Agent SDK (see the Note "Findings that cite notes").
First step
Write the checklist of places from the makers' manuals and run it on one server before and after its built-in erase.
Done looks like
At least eight server models from at least three makers, each with a published checklist of at least 30 places, each marked cleared or left, with the log behind every mark.