🚨 CMMC Phase One started November 10! Here's everything you need to know →

How to Choose and Use Media Destruction Tools (Physical & Logical) to Comply with FAR 52.204-21 / CMMC 2.0 Level 1 - Control - MP.L1-B.1.VII

Practical guidance for selecting and operating physical and logical media destruction tools to meet FAR 52.204-21 and CMMC 2.0 Level 1 media protection requirements.

April 07, 2026
5 min read

Share:

Schedule Your Free Compliance Consultation

Feeling overwhelmed by compliance requirements? Not sure where to start? Get expert guidance tailored to your specific needs in just 15 minutes.

Personalized Compliance Roadmap
Expert Answers to Your Questions
No Obligation, 100% Free

Limited spots available!

Meeting FAR 52.204-21 and CMMC 2.0 Level 1 MP.L1-B.1.VII requires clear, repeatable processes for rendering media that stored Covered Contractor Information (including CUI) unreadable before reuse or disposal — and that means choosing the right physical and logical destruction tools, using them correctly, and documenting the outcome.

What the requirement means in practice

At small-business scale, the requirement boils down to three objectives: 1) identify media that has been used to store controlled data, 2) apply an approved sanitization or destruction method appropriate to the media type and reuse decision, and 3) record and verify the action for audit (CMMC)/contract compliance (FAR). NIST SP 800-88 Rev. 1 provides accepted technical guidance for sanitization decisions (clear, purge, destroy) and should be your technical baseline when developing SOPs under the Compliance Framework.

Types of media and the appropriate destruction methods

Different media need different tools and validation: magnetic hard drives (HDDs) can often be securely overwritten (logical erase) or physically shredded; SSDs, USB flash, and eMMC require different approaches — overwriting is unreliable on many flash devices, so crypto-erase or physical destruction/disintegration is preferred. Tape backup media usually require degaussing followed by shredding or physical destruction. Key technical options to consider: ATA Secure Erase (hdparm) for many HDDs/SSDs, NVMe secure format (nvme format --ses or vendor-specific secure erase), blkdiscard or "nvme format" for flash where supported, and cryptographic key destruction for devices protected with full disk encryption (e.g., LUKS cryptsetup luksKillSlot or destruction of encryption keys). Note: legacy tools like DBAN only target spinning media and are not safe for SSDs; use vendor-certified or NIST-aligned tools for evidence and verification.

Practical commands and tool examples (use with caution)

Examples small organizations might use for logical sanitization: on Linux, to issue an ATA secure erase (HDD/SSD): set a temporary password with hdparm and run hdparm --security-erase NULL /dev/sdX (follow vendor guidance and confirm device not frozen). For NVMe drives use the vendor NVMe CLI: nvme format /dev/nvme0n1 -s 1 (secure erase). For encrypted devices, cryptographic erase (destroying keys) is fast and effective: cryptsetup luksKillSlot /dev/sdaX . For verification and enterprise reporting, use certified erasure software (e.g., Blancco) that produces a signed certificate-of-erasure; these are important for FAR-style audits.</p>

How to choose vendors and physical destruction tools

When evaluating shredder/crusher/degausser vendors or on-site destruction services, look for NAID AAA certification (for data destruction vendors), NIST SP 800-88 alignment, insured chain-of-custody, and the ability to provide a Certificate of Destruction (CoD) with serial numbers or photographed evidence. For physical devices: choose an SSD-capable disintegrator or an industrial shredder rated for media level P-4/P-5 depending on the sensitivity and whether drives will be reused. Degaussers are effective for many magnetic tapes and HDD platters but are ineffective on most SSDs; confirm the media type before buying. Small businesses often balance cost and risk: for <20 drives/year, vendor destruction with NAID proof is usually more cost-effective and defensible than buying industrial equipment.

Small-business scenarios and recommended approaches

Scenario A — Laptop retirement (10 laptops with SSDs): Step 1 — Ensure full-disk encryption (BitLocker/FileVault) was enabled during operational life; Step 2 — perform cryptographic erasure by destroying disk keys (manage-bde -protectors -disable on Windows then remove keys, or cryptsetup luksKillSlot on Linux) and/or run vendor secure-erase if SSD supports it; Step 3 — if drives will leave custody without reuse, hand to NAID-certified vendor for physical destruction and obtain CoD and photos. Scenario B — Backup tapes from an offsite rotation: degauss all tapes and then shred or incinerate; vendor receipts and serial-numbered CoDs must be retained for contract compliance.

Cloud and virtual media considerations

Cloud VMs, snapshots, and backups are logical media and require different controls: use strong encryption for data-at-rest and treat key destruction as media destruction (destroy encryption keys and verify snapshot deletion). When terminating a cloud service, obtain written confirmation from the CSP that snapshots and backups were securely deleted and that underlying media adheres to the CSP's data sanitization policy; keep these confirmations in your compliance evidence pack.

Implementation steps, documentation, and verification

Build a short SOP under your Compliance Framework: 1) Inventory and classify media (asset tag, serial number, last user). 2) Select sanitization method per NIST 800-88 (clear/purge/destroy). 3) Execute using certified tools or vendor services (log commands, tool version, operator). 4) Verify outcome (read-back checks, vendor CoD, photos, serial numbers). 5) Record chain-of-custody and retain destruction evidence per contract (recommend keeping records at least for the life of the contract + 3 years, or per your organization’s record retention policy). Use simple templates: Media Destruction Log, Chain-of-Custody form, Certificate of Destruction upload into your contract evidence repository for auditors and CMMC assessors.

Risks of not implementing and compliance tips/best practices

Failing to properly sanitize or destroy media risks CUI exposure, contract termination, monetary penalties, loss of future contracting opportunities, and reputational damage. Practical best practices: 1) enable full-disk encryption by default so cryptographic erase is an option, 2) avoid relying on factory resets for mobile devices unless combined with encryption and verification, 3) use vendor-certified erasure tools and NAID-certified destruction services where possible, 4) maintain a simple asset-tagging and disposal workflow so no media is “forgotten”, 5) train staff on the SOP and require two-person witness for high-risk disposals, and 6) keep destruction evidence centralized for FAR and CMMC assessment.

In summary, compliance with FAR 52.204-21 and CMMC 2.0 Level 1 MP.L1-B.1.VII is achievable for small businesses by applying NIST 800-88 guidance: classify media, choose methods appropriate to media types (use crypto-erase and vendor-certified tools for flash/SSD, degauss and shred tapes/HDDs when required), document and verify every destruction event, and prefer NAID-certified vendors when you outsource. Implement these steps in a short SOP, keep destruction evidence, and you’ll significantly reduce the risk of data exposure while meeting auditor expectations.

 

Quick & Simple

Discover Our Cybersecurity Compliance Solutions:

Whether you need to meet and maintain your compliance requirements, help your clients meet them, or verify supplier compliance we have the expertise and solution for you

 CMMC Level 1 Compliance App

CMMC Level 1 Compliance

Become compliant, provide compliance services, or verify partner compliance with CMMC Level 1 Basic Safeguarding of Covered Contractor Information Systems requirements.
 NIST SP 800-171 & CMMC Level 2 Compliance App

NIST SP 800-171 & CMMC Level 2 Compliance

Become compliant, provide compliance services, or verify partner compliance with NIST SP 800-171 and CMMC Level 2 requirements.
 HIPAA Compliance App

HIPAA Compliance

Become compliant, provide compliance services, or verify partner compliance with HIPAA security rule requirements.
 ISO 27001 Compliance App

ISO 27001 Compliance

Become compliant, provide compliance services, or verify partner compliance with ISO 27001 requirements.
 FAR 52.204-21 Compliance App

FAR 52.204-21 Compliance

Become compliant, provide compliance services, or verify partner compliance with FAR 52.204-21 Basic Safeguarding of Covered Contractor Information Systems requirements.
 
Hello! How can we help today? 😃

Chat with Lakeridge

We typically reply within minutes