SOC 2 CC6.5: Secure Disposal of Devices and Data, Explained by an Auditor
SOC 2 CC6.5 explained by an auditor: what it covers, how cloud-native teams meet it, NIST 800-88 Rev. 2 sanitization, and the disposal evidence auditors want.
On this page · 12 sections
- SOC 2 CC6.5 requires that protections over physical assets stay in place until the data and software on those assets can no longer be read or recovered and are no longer needed.
- The criterion is about physical assets: laptops, drives, servers, phones, and backup media. Deleting confidential customer data from cloud systems is addressed mainly by C1.2 when Confidentiality is in scope.
- Cloud-native companies still have CC6.5 obligations. The cloud provider handles its own drives, but you handle every laptop and device your people use.
- If no assets were disposed of during the review period, the auditor may report that the control did not operate and could not be tested. That is not an exception, but it should be expected and described accurately.
What is SOC 2 CC6.5?
SOC 2 CC6.5 is the Trust Services Criterion that governs the end of an asset's life. It requires a service organization to keep its logical and physical protections over physical assets in place until the ability to read or recover data and software from those assets "has been diminished" and the data is no longer required to meet the organization's objectives. In short, you do not stop protecting a device until the data on it is gone.
CC6.5 is a common criterion, so it applies to every SOC 2 examination. It sits in the CC6 Logical and Physical Access Controls series between CC6.4, which restricts physical access, and CC6.6, which addresses threats from outside the system boundary.
The criterion protects against a specific risk: data walking out of the organization on hardware that was retired, returned, resold, recycled, or lost in transit. A decommissioned laptop sold without a proper wipe can expose customer data just as surely as a breached database.
What are the CC6.5 points of focus?
The CC6.5 points of focus describe two activities. The first is identifying the data and software stored on equipment that is to be disposed of. The second is removing that data and software, using procedures that make it unreadable, before the equipment leaves the entity's physical control. Like all points of focus, these illustrate how the criterion can be met rather than adding requirements.
In practice, those two activities translate into four questions an auditor will ask:
| Question | What a good answer looks like |
|---|---|
| Do you know which physical assets hold in-scope data? | An asset inventory covering laptops, servers, removable media, and mobile devices, with owners and status |
| Is there a defined procedure for sanitizing or destroying each media type? | A disposal or media sanitization procedure that names methods by media type and sensitivity |
| Is sanitization completed before the asset leaves your control? | Wipe or destruction records dated before the asset was handed to a recycler, reseller, or courier |
| Can you prove it happened? | Certificates of destruction, MDM wipe logs, or sanitization tool reports, linked to asset identifiers |
Does CC6.5 cover deleting data in the cloud?
CC6.5 is written about physical assets, so its primary focus is hardware. Logical deletion of data from cloud databases, storage buckets, and SaaS tools is addressed most directly elsewhere in the Trust Services Criteria.
| Disposal scenario | Primary criterion | Notes |
|---|---|---|
| Wiping or destroying a retired laptop, drive, or server | CC6.5 | The core of the criterion |
| Physical media in your cloud provider's data centers | CC6.5, at the subservice organization | Usually carved out; you monitor through the provider's SOC 2 report |
| Deleting confidential customer data at contract end | C1.2 | Applies when the Confidentiality category is in scope |
| Disposing of personal information at the end of its retention period | P4.3 | Applies when the Privacy category is in scope |
| Removing access for a departing employee | CC6.2 | Access removal is not data disposal |
In practice, many control sets map a single "data retention and disposal" policy to CC6.5, C1.2, and P4.3 together. That is fine, as long as the controls actually address each criterion. If your report covers Security only, the auditor will focus CC6.5 testing on physical assets. If you also include Confidentiality, expect separate testing of how confidential data is identified and deleted when retention ends or a customer leaves.
How does CC6.5 apply to a cloud-native company?
CC6.5 applies to a cloud-native company in two places: the cloud provider's physical infrastructure and the company's own devices.
The cloud provider's hardware
Your cloud provider decommissions its own drives and servers. In your SOC 2 report, the provider is typically a subservice organization presented under the carve-out method, so its media sanitization controls are excluded from your report. The auditor expects you to monitor them, usually by obtaining the provider's SOC 2 report each year and reviewing it, including the section on how the provider sanitizes and destroys media. Our guide on how to verify a SOC 2 report covers what to check during that review.
Your own devices
Every employee laptop, phone, and any removable drive that touches customer data or production credentials is a physical asset in scope. For a fully remote company, this is where CC6.5 actually lives. The common scenarios are:
- An employee leaves and returns the laptop. The device is wiped or reimaged before it is reissued, or sanitized before it is sold or recycled.
- An employee leaves and does not return the laptop. The device is remotely wiped through MDM, the attempt is logged, and recovery is pursued. An unreturned, un-wiped device holding customer data is a meaningful gap.
- A device fails and is sent for warranty repair. The drive is removed or sanitized first, or the repair vendor's handling is covered by contract.
- A device is lost or stolen. Full-disk encryption plus a remote wipe command limits exposure, and the incident is logged.
Full-disk encryption on every endpoint matters here. When the drive is encrypted and the key is destroyed, the data is effectively unrecoverable. That is the principle behind cryptographic erase.
What does NIST SP 800-88 Revision 2 mean for SOC 2 disposal?
NIST SP 800-88, Guidelines for Media Sanitization, is the reference most SOC 2 disposal procedures cite. NIST published Revision 2 on September 26, 2025, superseding Revision 1 from 2014. SOC 2 does not require you to follow NIST, but citing a recognized standard in your procedure gives the auditor a clear benchmark.
Three points matter for SOC 2 procedures written or updated in 2026:
- The focus is now a sanitization program. Revision 2 is oriented toward establishing an enterprise media sanitization program rather than looking up a technique for each device. That aligns well with how auditors evaluate CC6.5: as a repeatable, documented process.
- Clear, purge, and destroy remain the three methods. Clear uses standard read and write commands to overwrite data. Purge uses techniques intended to make recovery infeasible even with laboratory methods. Destroy physically renders the media unusable. Revision 2 favors purge over clear where possible.
- Device-specific techniques moved out. Apart from cryptographic erase, Revision 2 leaves technology-specific techniques to other standards, such as IEEE 2883 for storage sanitization.
If your disposal procedure still cites "NIST SP 800-88 Rev. 1" or prescribes multi-pass overwrites for modern SSDs, update it. Multi-pass overwriting was designed for older magnetic media and is not a reliable method for flash storage.
What evidence do auditors request for CC6.5?
| Evidence | What it demonstrates |
|---|---|
| Media sanitization or asset disposal procedure, with methods by media type | A defined process exists and references a recognized standard |
| Asset inventory showing status changes (active, retired, disposed) | Identification of assets due for disposal |
| List of assets disposed of during the period | The population for testing |
| Certificates of destruction or sanitization from the disposal vendor | Third-party proof, tied to serial numbers or asset tags |
| MDM wipe logs for returned or unreturned devices | Remote sanitization occurred and was confirmed |
| Endpoint encryption compliance report | Full-disk encryption makes cryptographic erase effective |
| Disposal vendor contract or due diligence | The vendor's handling of your media is controlled |
| Cloud provider SOC 2 report and your review notes | Monitoring of the subservice organization's media controls |
A useful certificate of destruction identifies the vendor, the date, the method used, and each asset by serial number or asset tag. A certificate that says "15 laptops destroyed" without identifiers cannot be traced to your inventory, so it proves less than you might think.
How do auditors test CC6.5?
In a SOC 2 Type 2 examination, auditors typically obtain the population of assets disposed of or sanitized during the period, select a sample, and trace each one to evidence that sanitization or destruction occurred before the asset left the organization's control. They also inspect the procedure and, for a Type 1, confirm that the process is designed and in place as of the report date.
What happens if nothing was disposed of during the period?
If no assets were disposed of during the review period, the auditor cannot test operating effectiveness, because the control never operated. SOC 2 reports commonly describe this situation in the test results, stating that the circumstances that would trigger the control did not occur during the period, so no testing of operating effectiveness was performed. This is not an exception and does not affect the opinion, but readers of the report will see it.
Two practical points follow. First, this outcome is common in young companies with small device fleets, so do not invent disposals to have something to test. Second, if devices were reissued after a wipe, that wipe is often a testable occurrence. Talk to your auditor about whether reimaging before reissue is part of the control description.
What are the most common CC6.5 exceptions?
1. Certificates without identifiers
The disposal vendor provides a batch certificate with a count but no serial numbers, so the auditor cannot match it to the assets in your inventory.
2. Devices handed over before sanitization
Laptops were given to a reseller with a promise to wipe them later, and the wipe record is dated after the handover. The criterion requires protections to remain until the data is unrecoverable.
3. Unreturned devices with no remote wipe
A departing employee kept their laptop, and no MDM wipe was issued or confirmed. This can surface during CC6.2 testing of terminations as well.
4. Inventory gaps
The inventory shows a device as "active" long after the employee left, or never recorded the device at all. Disposal cannot be tested for assets the organization does not know it has.
5. An outdated procedure
The procedure prescribes methods that do not match the devices in use, such as degaussing for SSD-based laptops. Degaussing does not sanitize flash storage, so the procedure itself is unsuitable for the assets it covers.
How does CC6.5 map to ISO 27001:2022?
The table shows close ISO/IEC 27001:2022 Annex A equivalents. It is a practitioner mapping, not an official crosswalk.
| CC6.5 theme | Closest ISO 27001:2022 Annex A controls |
|---|---|
| Media handling and disposal | A.7.10 Storage media |
| Secure disposal or reuse of equipment | A.7.14 Secure disposal or re-use of equipment |
| Deleting information no longer required | A.8.10 Information deletion |
| Knowing which assets exist | A.5.9 Inventory of information and other associated assets |
How should you prepare for CC6.5?
- Inventory every device that holds in-scope data. Include laptops, phones, removable media, and any on-premises hardware, with status and owner.
- Write a short sanitization procedure. Name the method for each media type, reference NIST SP 800-88 Revision 2, and require sanitization before an asset leaves your control.
- Enforce full-disk encryption on endpoints. It makes cryptographic erase available and protects lost devices.
- Use MDM for remote wipe. Issue and log wipes for unreturned, lost, or stolen devices, and link the wipe to the offboarding ticket.
- Require itemized certificates. Make serial-level certificates of destruction a contract term with your disposal vendor.
- Review your cloud provider's SOC 2 report. Record your review, including the media sanitization controls, each year.
A SOC 2 readiness assessment from Ledger Audits reviews your disposal procedure, inventory, and evidence trail together, so gaps between them surface before your auditor finds them.
Related reading
- SOC 2 CC6.4: Physical Access Controls
- SOC 2 CC6.2: User Provisioning and Offboarding
- SOC 2 CC6.1: Logical Access, MFA, and Encryption
- How to Verify a SOC 2 Report
- External: NIST SP 800-88 Rev. 2, Guidelines for Media Sanitization
- External: AICPA 2017 Trust Services Criteria (With Revised Points of Focus, 2022)
Frequently asked questions
What does SOC 2 CC6.5 require?
SOC 2 CC6.5 requires a service organization to keep logical and physical protections over physical assets in place until the data and software on those assets can no longer be read or recovered and are no longer needed. In practice, devices and media must be sanitized or destroyed before they leave the organization's control.
Does SOC 2 require NIST 800-88?
SOC 2 does not require NIST SP 800-88. It requires that data on physical assets be made unrecoverable before protections are removed. Many organizations reference NIST SP 800-88, now in Revision 2 published in September 2025, because it gives the auditor a recognized benchmark for the methods used.
Is a certificate of destruction required for SOC 2?
A certificate of destruction is not explicitly required, but it is the most common evidence that a third-party vendor sanitized or destroyed your media. To be useful, the certificate should list each asset by serial number or asset tag, the method used, and the date, so the auditor can trace it to your asset inventory.
How does CC6.5 apply if we have no servers?
If you run entirely in the cloud, your cloud provider handles disposal of its own hardware, and you monitor that by reviewing its SOC 2 report. CC6.5 still applies to your own devices, such as employee laptops and phones, which must be wiped or destroyed before they are resold, recycled, or reissued.
What is the difference between CC6.5 and C1.2?
CC6.5 is a common criterion about physical assets: protections stay in place until data on the hardware is unrecoverable. C1.2 is a Confidentiality criterion about disposing of confidential information, including logical deletion from systems and databases, to meet the entity's objectives. C1.2 applies only when Confidentiality is in scope.
What if we did not dispose of any devices during the audit period?
If no disposals occurred, the auditor cannot test operating effectiveness of the control. The SOC 2 report will usually state that the circumstances triggering the control did not occur during the period. This is not an exception, and it is common for smaller companies.
Get independent eyes on it before your auditor or buyer does.
Ledger Audits provides readiness and internal audit work only. We never issue SOC 2 reports or ISO certificates, which keeps our review independent of your examination.
Book a discovery call