Compliance

IT asset disposition for universities: a NIST SP 800-88 Rev. 2 playbook

Retiring a laptop is a data-security event, a property-records event and sometimes a federal-grant event. Here's how to run university ITAD so all three hold up.

Published · Nov 20, 2026
HECVAT — 2024 REVISION
GASBCompliance
6 min read
Published
Read
6 min
Topic
Compliance

IT asset disposition (ITAD) is everything that happens to a device after the institution decides it's done with it: data sanitization, redeployment or resale, recycling, and the records that prove each step. On a campus it's also where three groups' obligations collide. Information security needs proof the data is gone. The controller needs the asset off the books with the right disposal date and proceeds. And if the device was bought on a federal award, sponsored programs needs the disposition to follow the award's rules.

Most audit findings in this area aren't about a drive that leaked. They're about a drive nobody can prove didn't.

What is IT asset disposition?

IT asset disposition is the governed process for retiring IT equipment: removing it from service, sanitizing any storage media to a defined standard, choosing a route (internal reuse, resale, donation, or certified recycling), and recording the outcome so the asset's history is complete. ITAD differs from "e-waste pickup" in that the record matters as much as the logistics.

What changed in NIST SP 800-88 Rev. 2?

NIST SP 800-88 is the federal guideline for media sanitization that most universities adopt by reference in their data-security policy. Revision 2 was finalized in September 2025, replacing Revision 1 from 2014. The changes that matter for a campus program:

  • It's now about the program, not just the technique. Rev. 2 is organized around establishing an enterprise media-sanitization program — roles, decisions, and records — rather than leaning on the long media-by-media tables of Rev. 1.
  • Verification and validation are separate. Verification confirms a sanitization technique ran without errors on a given device. Validation asks whether the overall program produces the intended outcome. Expect auditors to ask about both.
  • Clear carries more caveats. Rev. 2 is explicit that a Clear (overwrite) on modern flash and high-density magnetic media can leave data recoverable in ways it didn't on older drives.
  • Degaussing moved. It's treated as a physical purge technique rather than a destruction method.
  • Cryptographic erase is better specified, including when keys are managed outside the device.

If your policy still cites "NIST 800-88 Rev. 1" by name, plan a revision. The three outcome categories below didn't go away.

What's the difference between Clear, Purge and Destroy?

  • Clear uses standard read/write commands to overwrite user-addressable storage. It protects against simple, non-invasive recovery. Suitable for low-sensitivity media staying inside the institution.
  • Purge makes recovery infeasible even with laboratory techniques. On modern drives this usually means the device's own sanitize command or cryptographic erase on a self-encrypting drive. The default for anything holding regulated or sensitive data, especially if it leaves campus.
  • Destroy physically renders the media unusable: shredding, disintegration, pulverizing, incineration. Use it when the data is highly sensitive, when the media is broken and a Purge can't be verified, or when policy simply requires it.

The right category follows the data classification, not the device type. A faculty laptop that only ever held public course material and one that held IRB-protected interview recordings may be the same model; they shouldn't be sanitized the same way.

How should a university map data classes to sanitization?

Write the mapping down once, in policy, and make the disposition workflow enforce it. A typical starting point:

Data classification on the device Minimum sanitization Typical route
Public / low risk, staying on campus Clear Internal redeployment, loaner pool
Internal or confidential, leaving campus Purge Resale, donation
Regulated (HIPAA PHI, CUI, export-controlled, PCI) Purge, or Destroy per the data's own rules Resale only after verified purge; otherwise destroy
Failed or unreadable media Destroy Certified destruction vendor

Two details trip up campuses. First, research data carries its own terms. A data use agreement, a DoD contract with CUI requirements, or an export-control plan can impose stricter handling than your general policy; the sponsored programs office should be able to flag those devices. Second, "we always shred" isn't a policy shortcut. Destruction is fine, but you still need the per-device record that says it happened.

What should a certificate of sanitization include?

A certificate is only as useful as its link back to specific assets. At minimum:

  • Asset tag and serial number for each device (not just a count or a weight).
  • Media type and the sanitization category and method used.
  • Whether verification was performed, how, and its result.
  • Date, location, and the person or vendor who performed it.
  • The receiving vendor and, for recycling, their certification (R2 or e-Stewards).
  • Signature of the responsible official.

Store it against the asset records, not as a PDF in someone's inbox. When an auditor samples five retired assets from last fiscal year, you want five certificates in five clicks.

What does chain of custody look like?

Every hand-off between retirement and final disposition should be recorded: pulled from service by whom, stored where, picked up when and by which vendor, received and processed when. Gaps in custody are where devices go missing. A locked surplus cage with a sign-in sheet is a control; a pallet by the loading dock is not.

How do grant-funded devices change disposition?

Equipment bought on a federal award is subject to Uniform Guidance at 2 CFR 200.313. When it's no longer needed for the award, items with a current per-unit fair market value of $10,000 or less (the threshold for awards made on or after October 1, 2024; $5,000 before that) can be retained, sold or otherwise disposed of with no further obligation to the awarding agency. Above that, the agency is generally entitled to its share, and you request disposition instructions. Either way, the property record needs the disposal date and sale price.

Most retired laptops fall well under the threshold, but research instruments and high-end workstations often don't, and an institution's own capitalization threshold may be lower than the federal one. The disposition workflow should know which devices are federal equipment before they leave the building. See 2 CFR 200.313 equipment management for the full set of property-record requirements.

A university ITAD workflow that survives audit

  1. Retire in the system of record first. Mark the asset retired, with a reason, before it moves. MDM unenrollment and account removal happen here.
  2. Group retirements into lots by route and sanitization standard. A lot is the unit vendors pick up and certify.
  3. Check every asset's data class against the lot's standard. A PHI-bearing device shouldn't be able to join a Clear-only lot.
  4. Check federal and capital status. Flag grant-funded equipment and anything above your capitalization threshold for sponsored programs and the controller.
  5. Sanitize, verify, record. Per device, with method and result.
  6. Hand off with custody records. Pickup time, vendor, receiving signature.
  7. Close the lot with certificates and proceeds. Attach the certificate of sanitization or destruction, the weight ticket for recycling, and any resale proceeds, then post the disposal to the asset register.

Where Habeo fits

Habeo's surplus and disposition workflow runs that process inside the asset register. Retired assets join a named surplus lot with a route and a sanitization standard; assets carrying PHI or CUI can't be added to a lot whose standard is Clear or none, and the lot can't be finalized until every regulated asset on it has an adequate standard. Closing a lot produces a NIST 800-88-style disposal certificate listing each asset's tag, serial, book value, data class and grant, with the chain-of-custody log. Closing it also freezes each asset's book value at disposal and ends its grant allocations.

What Habeo can't do is watch the drive being wiped. It records the standard you required, the method the technician or vendor reports, and who handled the device; the physical sanitization still depends on your technicians and vendors doing what they certify.

Related reading: the glossary entry on NIST SP 800-88 and IT asset disposition.

For asset directors

Could we save your team a week of reconciliation?

We will pull a sample of your inventory live, walk you through the migration plan, and stay through your fiscal close. No statement of work. No agents on endpoints.

No card required · up to 2,000 endpoints · 14 days on your own data. Or see pricing.

“The institutional record, finally in one place. We’re using Habeo every day — and the controller’s office is, too.”

§
From the Journal
Field notes · Vol. II
Liked the read? Try Habeo on your own devices — 14 days free, no card.
Start free trial