HQ NORCROSS, GA · 470-284-5400
Critical Technology Services
A secure financial-services data center with high-density server racks glowing under deep navy and royal-blue light.
FIELD NOTES

GLBA Data Destruction Requirements

GLBA data destruction: what the Safeguards Rule and FTC disposal expectations mean for retiring drives, and the audit trail examiners expect.

July 6, 2026 4 MIN READ CRITICAL TECHNOLOGY SERVICES ComplianceFinancial ServicesData Destruction

GLBA requires financial institutions to securely dispose of customer information so it cannot be read or reconstructed — which means data destruction to a recognized standard, documented with a certificate of destruction and an unbroken chain of custody. The law sets the obligation to protect customer data through the end of its lifecycle; the method and the proof are what turn that obligation into something you can defend in an examination.

For financial services, a retired drive isn’t just old hardware — it’s a container of regulated customer information, and its disposal is squarely inside your compliance program. Here is what GLBA actually expects and how to meet it cleanly.

What GLBA says about disposal

The Gramm-Leach-Bliley Act’s Safeguards Rule, enforced by the FTC, requires financial institutions to develop and maintain safeguards that protect customer information. Those safeguards aren’t limited to systems in active use — they extend to how you retire and dispose of the media that held the data.

The disposal expectation is straightforward in principle: properly dispose of customer information so it can’t be accessed after the equipment leaves your control. Deleting files or reformatting a drive doesn’t clear that bar — the underlying data is recoverable with off-the-shelf tools. Proper disposal means rendering the data unreadable and unrecoverable, and being able to prove it.

GLBA doesn’t hand you a technical recipe. It sets the duty of care and leaves the method to established practice — which is where sanitization standards come in.

NIST 800-88 as the method

The widely accepted way to meet GLBA’s “properly dispose” expectation is NIST SP 800-88 Rev. 1, the U.S. reference for media sanitization. It defines three levels matched to media type and data sensitivity:

  • Clear — overwrite user-addressable space to defeat simple recovery.
  • Purge — firmware-level sanitize or cryptographic erase that defeats laboratory recovery.
  • Destroy — physical destruction (shredding, disintegration) so media can never be read.

For customer financial data leaving your custody, that typically means Purge or Destroy. Where physical destruction is required, media is shredded to under 2mm. The standard’s discipline — method matched to media — is exactly the kind of defensible, documented decision an examiner wants to see. For the deeper dive, see how we handle data destruction.

The audit trail examiners expect

In financial services, doing the destruction is only half the job. The other half is proving it — and the proof is what an FTC inquiry, an SEC or FINRA examination, or an internal auditor will actually ask for.

Two documents carry that weight:

  • A certificate of destruction issued per device, tied to the serial number, so each specific asset is accounted for.
  • An unbroken chain of custody showing who handled each device from pickup through final disposition.
RequirementWhat it looks likeWhy examiners want it
Secure disposalNIST 800-88 wipe or physical destructionMeets “properly dispose” duty
Per-serial proofCertificate of destruction per deviceTies destruction to specific media
Chain of custodyDocumented custody, pickup to dispositionShows no gap where data could leak
ReportingAudit-ready records on demandAnswers exams without follow-up

If a provider can destroy data but can’t produce serial-level evidence, you don’t have a compliant program — you have a liability with a receipt missing.

Chain of custody: closing the gap

The most exploitable weakness in disposal isn’t the destruction itself — it’s the handoffs around it. Every point where a drive changes hands without a record is a gap an examiner will flag and an incident could exploit.

A defensible chain of custody logs each asset by serial number at pickup, tracks it through transport and processing, and closes the loop with the certificate of destruction. Whether the work happens onsite at your facility or offsite at a secure processing site, the custody record has to be continuous. That continuity is what lets you stand in front of a regulator and show, device by device, that customer data was destroyed — not just that a truck came and took some equipment away.

Your vendor is part of your compliance

GLBA’s expectations follow the data, which means the third party you hand retired equipment to is inside your compliance perimeter. Choosing a provider with recognized certifications — R2v3, ISO 14001, ISO 9001, ISO 45001 — and a documented, serial-level process isn’t a nice-to-have; it’s how you demonstrate due diligence in vendor selection.

CTS works with financial services organizations on exactly this: NIST 800-88-aligned data destruction, media shredded to under 2mm where physical destruction is required, a certificate of destruction per serial, and continuous chain of custody — onsite or offsite, with national coverage from our Norcross, GA headquarters.

Getting examiner-ready

GLBA data destruction comes down to three things: destroy customer information to a recognized standard, prove it at the serial level, and keep an unbroken chain of custody from pickup to certificate. Get those right and disposal stops being an audit risk and becomes evidence of a well-run program.

If you’re a financial institution planning a hardware refresh, a branch consolidation, or a datacenter decommission, talk to our team about building a defensible, examiner-ready disposal process — or start with our financial services overview to see how the pieces fit your regulatory picture.

FAQ

Questions we get a lot.

01

What does GLBA require for data destruction?

The Gramm-Leach-Bliley Act's Safeguards Rule requires financial institutions to protect customer information throughout its lifecycle, including secure disposal. In practice that means you must properly dispose of customer information so it cannot be read or reconstructed — through data destruction to a recognized standard — and be able to show it was done. GLBA sets the obligation; standards like NIST 800-88 provide the method.
02

What does 'properly dispose of customer information' mean under GLBA?

It means rendering customer information unreadable and unrecoverable before media leaves your control — not just deleting files or reformatting drives. Acceptable approaches include wiping to NIST 800-88 or physically destroying the media (shredding). The key is that the data cannot be reconstructed and that you have documentation proving disposal.
03

Is NIST 800-88 the standard for GLBA data destruction?

GLBA doesn't name a specific technical standard, but NIST SP 800-88 Rev. 1 is the widely accepted method for meeting the 'properly dispose' expectation. It defines Clear, Purge, and Destroy levels matched to media type, which maps cleanly to what examiners expect to see documented.
04

What audit trail do financial examiners expect for destroyed data?

Examiners and assessors expect an unbroken chain of custody from pickup to final disposition, plus a certificate of destruction tied to each device serial number. That serial-level evidence is what lets you demonstrate — to an FTC inquiry, an SEC or FINRA examination, or an internal audit — that specific media holding customer data was actually destroyed.
05

Who is covered by GLBA data disposal requirements?

GLBA applies to financial institutions broadly defined — banks, credit unions, lenders, investment advisers, insurers, and many fintech and service providers that handle consumer financial information. The FTC's Safeguards Rule and disposal expectations reach a wide set of businesses, and vendors handling that data on your behalf are part of your compliance obligation.
READY TO START?

Talk to the operator.