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

How to Sanitize or Destroy Information System Media to Meet FAR 52.204-21 / CMMC 2.0 Level 1 - Control - MP.L1-B.1.VII (Checklist & Tools)

Practical, step-by-step guidance and a checklist for sanitizing or destroying information system media to satisfy FAR 52.204-21 and CMMC 2.0 Level 1 (MP.L1-B.1.VII).

•
April 22, 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!

If your small business handles Federal Contract Information (FCI) or needs to demonstrate alignment with FAR 52.204-21 and CMMC 2.0 Level 1 MP.L1-B.1.VII, you must implement repeatable, documented processes to sanitize or destroy information system media before disposal or reuse — this post gives clear, practical steps, tools, and a checklist you can use right away.

Understanding the requirement in the Compliance Framework context

At Level 1 the objective is to prevent inadvertent disclosure of contractor-held FCI by ensuring that media containing that information cannot be read after transfer, reuse, or disposal. For Compliance Framework implementation this maps to having policies, defined procedures, technical controls, and evidence of performed sanitization or destruction for all media types — hard drives, SSDs, removable USBs, SD cards, mobile devices, optical media, backup tapes, and printed materials.

Practical implementation steps (policy → process → proof)

Start by formalizing a Media Sanitization and Disposal Policy that states when media must be sanitized/destroyed, roles and responsibilities, approved methods (per NIST SP 800‑88 Rev. 1 principles: Clear, Purge, Destroy), retention of evidence, and rules for using third-party vendors. Then operationalize with a media inventory, a documented procedure for each media type, and a consistent evidence capture process (sanitization logs, photos, certificates of destruction).

Inventory and classification

Inventory every asset that can store information: asset tag/serial, owner, last content classification (FCI/CUI/public), storage location, and disposition status. For small businesses, a shared spreadsheet or a lightweight asset tracking tool (e.g., GLPI, Snipe-IT) is sufficient. Ensure each inventory row includes a sanitization decision: reuse internally, transfer to another party, recycle, or destroy.

Sanitization methods with technical details

Use the NIST SP 800‑88 categories: Clear (logical overwrite), Purge (cryptographic erase or block erase), and Destroy (physical destruction). Examples and technical commands: - For HDDs (magnetic): use full overwrite. Linux example: shred -v -n 3 /dev/sdX or dd if=/dev/zero of=/dev/sdX bs=1M status=progress. Windows: diskpart → select disk N → clean all (this writes zeros). - For SSDs/NVMe: do NOT rely on multiple overwrites because of wear-leveling; use vendor ATA Secure Erase or NVMe format. Examples: hdparm --user-master u --security-set-pass P /dev/sdX && hdparm --security-erase P /dev/sdX; for NVMe: nvme format /dev/nvme0n1 --ses=1 (or use vendor utilities). Alternatively use crypto-erase by destroying keys if full-disk encryption was used. - For mobile devices: perform factory reset + crypto erase, then physically destroy if device will be disposed. For iOS/Android, remove user accounts, encrypt, then factory reset and verify no accounts remain. - For removable flash (USB/SD): if reuse, overwrite with a full-block write; otherwise physically destroy (shred or incinerate) because flash can retain data after logical erase. - For backup tapes: degauss and then shred/physically destroy. Verify whether the degausser is appropriate for the tape model. - For paper: cross-cut shredding (P-4/P-5 for higher risk) or pulping; for CUI treat as high-sensitivity and shred onsite or use bonded shredding services. Always test your process on sample devices to verify data cannot be recovered (use a forensic recovery tool to confirm) and document the test results.

Tools, vendors, and small-business considerations

Open-source and built-in tools can work for small shops: Linux shred, dd, hdparm, nvme-cli, Windows diskpart/cipher, and vendor utilities from Samsung, Intel, etc. For guaranteed audit-proof destruction, commercial tools and services are recommended: Blancco (certified sanitization software), DriveSavers/Ontrack for verified erasure and recovery proofs, and NAID AAA certified destruction vendors for physical destruction and certificates. Small businesses often find hybrid approaches most cost-effective: do low-risk media sanitization in-house and use certified vendors for high-risk media or bulk disposals. Retain vendor certificates of destruction (CoD) and a signed chain-of-custody for each batch.

Real-world small-business scenarios

Scenario A — Laptop decommission: A 12-person engineering firm decommissions a laptop with design documents (FCI). Process: inventory update → full-disk encryption applied while in service → perform ATA Secure Erase via vendor tool; if ATA is unsupported, send to NAID vendor for physical destruction. Evidence: erasure log, screenshot of tool success, and vendor CoD if destroyed. Scenario B — USB drives returned by contractors: the firm collects drives, runs a two-pass overwrite with shred, and then tests a sample using a forensic tool (Autopsy or FTK Imager) to confirm data is unrecoverable; logs are kept for audit.

Compliance tips, best practices, and evidence for auditors

Best practices: maintain a template sanitization checklist (asset ID, method used, operator, date/time, verification steps, proof artifacts), keep policy mapped to FAR 52.204-21 and your CMMC practice MP.L1-B.1.VII, train staff annually, and use role-based access to disposal procedures. Evidence to collect: sanitized media inventory entries, operator logs (who performed which action), verification screenshots or hash comparisons before/after, CoDs from vendors, and periodic internal audits showing random verification attempts. Retain records for the contract lifecycle plus a reasonable retention period (commonly contract end + 3 years) so you can demonstrate compliance on demand.

Risks of not implementing proper sanitization and destruction

Failing to sanitize or destroy media places FCI at risk of unauthorized disclosure, which can lead to contract penalties, removal from future bidding, reputational damage, and potential legal liability depending on the data exposed. Technically, leftover data on retired drives or flash can be trivially recovered by adversaries or resellers — a ransomware actor can find credentials or sensitive project data on decommissioned devices. From an audit perspective, lack of documented procedures and evidence is as damaging as a technical failure.

Summary: Implement a simple policy-driven media sanitization lifecycle — inventory, choose method (Clear/Purge/Destroy) based on media type and risk, use appropriate technical tools (secure-erase, vendor utilities, or certified destruction), capture evidence (logs, CoDs, verification) and train personnel. For small businesses this approach balances cost and compliance: use in-house tools where safe and certified vendors for high-risk disposals, and keep clear, auditable records to demonstrate fulfillment of FAR 52.204-21 and CMMC 2.0 Level 1 MP.L1-B.1.VII requirements.

 

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