Key Takeaways
- Government IT asset disposal requires separate checks for data security, property authorization, and environmental compliance.
- NIST SP 800-88 Rev. 2 provides guidance for selecting and documenting appropriate media sanitization methods.
- Federal agencies must follow applicable property-disposition procedures before transferring, selling, donating, or recycling government-owned equipment.
- State and local agencies must verify the surplus-property rules and electronics-recycling laws that apply in their jurisdictions.
- Government contractors should review relevant contract requirements, including DFARS, NIST SP 800-171, and CMMC obligations where applicable.
- R2v3 certification can help agencies evaluate a recycler’s environmental, data-security, and downstream-management practices, but it does not replace other compliance checks.
- Asset-level records should connect each device to its sanitization outcome, transfer approval, receiving party, and final disposition.
Retiring government IT equipment such as laptops, servers, and other IT assets takes more than wiping the hard drives and calling an electronics recycling pickup. Government agencies such as the U.S. Department of Defense (DoD), the Department of Veterans Affairs (VA), the Texas Department of Information Resources (DIR), and local governments such as the City of Philadelphia must secure confidential data and follow the property-disposal and electronics-recycling requirements that apply to their assets.
These responsibilities overlap, but they serve different purposes. Sanitizing a device does not on its own make it ready for disposal, and using a recycler is not adequate proof that data was handled securely.
The rules that apply also differ from organization to organization. Federal agencies follow federal property and security policies, state and local governments follow state and local rules, and government contractors may have specific contractual requirements. Agencies need to understand all of these when designing a disposal process that combines security, property control, and environmental compliance.
Two Compliance Obligations, One Disposal Event
Government IT asset recycling and disposal involves separate compliance tracks. Agencies should coordinate them before retired equipment is transferred, sold, donated, recycled, or destroyed.
| Compliance area | Main purpose | Key references |
|---|---|---|
| Data sanitization | Protect information stored on devices and media | NIST SP 800-88, FISMA, applicable agency security policies |
| Property disposition | Ensure government-owned equipment is disposed of through an authorized process | Applicable Federal Management Regulation provisions and agency procedures |
| Electronics recycling | Ensure equipment is handled through a permitted and appropriate recycling route | Applicable federal guidance, state laws, and agency requirements |
These requirements should be considered together, but each one must be met separately.
The Data-Security Obligation: NIST SP 800-88 and FISMA
Before data-bearing equipment leaves agency control, the agency must establish how the data on it will be protected. Media sanitization is the process of making access to data on storage media infeasible for a given level of effort, in line with the sensitivity of the information and applicable security requirements.
The Federal Information Security Modernization Act (FISMA) provides a structure for information-security risk management at federal agencies. Agency security programs and policies determine how its requirements apply to specific information systems, data, and equipment.
NIST Special Publication 800-88, Guidelines for Media Sanitization, provides technical guidance for selecting and managing sanitization methods. Revision 2, published in September 2025, is the current revision. Agencies should use the current publication together with their security policies and any other requirements that apply.
The suitable approach depends on:
- Media type: Hard disk drives, solid-state drives, and other storage media may need different methods.
- Information sensitivity: Government information requires different levels of protection depending on how sensitive it is.
- Intended disposition: Equipment staying in internal use may be handled differently from media being released to an outside organization.
- Verification: Agencies must be able to show that sanitization was performed to the correct standard.
For example, a retired laptop containing routine administrative files and a server holding sensitive program information should not automatically receive the same sanitization treatment. The agency must determine the appropriate method based on the media, the data, and the applicable policy.
The Property-Disposal Obligation: Federal Property Rules and General Services Administration (GSA) FMR Bulletin B-34
Properly sanitizing equipment does not by itself entitle an agency to dispose of it. Federal agencies are also subject to the property-management and disposition regulations that apply to government-owned property.
Relevant Federal Management Regulation provisions include parts of 41 CFR Parts 102-35, 102-36, and 102-40, depending on the property and the situation. Agencies may have to show that equipment is excess, complete screening or reporting, and obtain authorization before a disposition or transfer.
GSA FMR Bulletin B-34, Disposal of Federal Electronic Assets, is also relevant to federal electronics disposition. Agencies should consult the official bulletin and current guidance to determine the requirements that apply to their assets and planned disposal route.
A recycler’s certification should not be treated as a universal legal requirement without verifying the exact scope and current applicability of the relevant rule.
Before releasing equipment, agencies should confirm:
- Security: Has the proper sanitization or data destruction been completed?
- Property authorization: Did the agency follow the appropriate screening, approval, and disposition processes?
- Recycling route: Do the receiving organization and its proposed process meet the requirements that apply to this equipment?
These checks are related but not interchangeable. Data sanitization is concerned with the data on the device, property rules govern how the property can be disposed of, and recycling requirements cover the device’s end-of-life handling.

How the Federal Electronics Disposition Process Works
Federal agencies should coordinate property procedures with information-security controls rather than treating disposal as a single handoff to a vendor. The specific process varies by asset, condition, and federal and agency requirements.
1. Screen, Report, and Determine the Appropriate Disposition
The agency first identifies equipment it no longer needs and determines whether it qualifies as excess property. Staff should follow internal screening and reporting procedures, including reporting to GSA when required. The equipment may then be considered for transfer, donation, sale, recycling, or another disposition permitted by the circumstances and governing rules.
Abandonment or destruction should not be treated as an easy way around the normal process. The agency must confirm that the relevant rules allow it and that the necessary conditions and approvals are in place.
2. Sanitize Data Before Transfer or Release
Once the agency has decided on the intended disposition, it must determine and complete the required sanitization or destruction process before the equipment is released.
The agency should verify:
- Which devices contain storage media or other information-bearing components.
- Which sanitization method the applicable security policy requires.
- Whether the process was completed and documented.
- Whether any media cannot be sanitized and needs approved physical destruction instead.
Property-disposal approval and data sanitization are separate controls. Coordinating their timing helps prevent equipment from being transferred before the proper security measures are complete.
Learn more: Data Destruction and Device Disposal: The Ultimate Security Guide
3. Link Disposition Records With Sanitization Evidence
A well-managed disposal record connects each asset to its security outcome and final destination. Depending on the process, records may include:
| Record | What it helps demonstrate |
|---|---|
| Asset inventory | Identifies the equipment being retired |
| Sanitization or destruction record | Documents the data-handling method and result |
| Property-disposition approval | Supports the authority for the transfer or disposal |
| Transfer or recycling record | Identifies the receiving party and final disposition |
| Certificate of Destruction, where applicable | Provides evidence of the data destruction service performed |
A Certificate of Destruction can support an audit trail, but it is not proof of compliance on its own. Agencies need to make sure the documentation identifies the assets or services and matches the property and disposition records. They should also review the ITAD provider’s certifications and compliance standards to assess whether its practices meet applicable requirements.
The goal is a traceable record showing which asset was handled, what happened to its data, who received the equipment, and how the disposition was completed.
State and Local Government: A Different Compliance Framework
State and local governments face the same data-security and environmental issues, but they shouldn’t assume the federal property-disposal process automatically applies to their equipment. Requirements vary with state law, local policy, funding sources, and any rules that apply to the information itself.
Check State Surplus-Property and Disposal Laws
Agencies should identify who is responsible for disposing of public property before equipment is retired. These rules may cover declaring assets as surplus, offering assets to other public entities first, and when an asset may be sold, donated, transferred, or destroyed. Other policies, such as local procurement or records-management rules, can also affect the process.
For example, a city IT department replacing office computers may need approval under its local surplus-property procedure before arranging their removal. Sanitizing the computers does not replace that approval.
Check State Electronics-Recycling Requirements Separately
Agencies also need to determine whether state electronics-recycling laws restrict how the equipment can be handled. Requirements vary by jurisdiction and asset type, and may involve:
- Limits on sending covered electronics to landfill.
- State-sanctioned collection or recycling programs.
- Extended Producer Responsibility (EPR) measures that set recycling targets for some products.
- Exemptions or special rules for particular equipment or organizations.
For example, Texas e-waste recycling laws establish manufacturer take-back programs for covered computers and televisions, while New Jersey E-Cycle requirements and Pennsylvania IT asset disposal regulations set different rules for covered electronics, collection programs, and recycling stakeholders.
Understanding applicable e-waste compliance requirements can help agencies identify their recycling obligations and confirm that their chosen disposal route meets them.
For state and local IT teams, the practical approach is to complete two distinct checks before release:
- 1. Property authorization: Is the agency permitted to transfer, sell, donate, recycle, or destroy the asset under the rules that apply?
- 2. Recycling compliance: Does the selected route meet the applicable state and local electronics-handling requirements?
Handling both checks alongside data sanitization helps agencies avoid securing the data while overlooking the legal requirements that still apply to the equipment itself.
Government Contractors: CMMC, DFARS, and NIST SP 800-171
Government contractors have different responsibilities from federal agencies that dispose of government property. Contractors that handle Federal Contract Information (FCI) or Controlled Unclassified Information (CUI) may have specific security obligations when retiring devices that store or process this data. Which obligations apply depends on the contract, the information involved, and the security requirements that apply to the contractor.
Apply the Requirements Relevant to the Contract
For covered defense contractors, DFARS 252.204-7012 establishes safeguarding and incident-reporting requirements for covered defense information. Where applicable, it also references the security controls in NIST SP 800-171 for covered contractor information systems.
Media protection is an important part of this framework. NIST SP 800-171 control 3.8.3 addresses sanitizing or destroying hard drives and similar media containing CUI before disposal or release for reuse. Contractors should not assume every contract has the same implementation or assessment requirements; they must follow the contract clauses, implementation, and assessment criteria that apply to them.
CMMC requirements also depend on the program level and the contract. Contractors should confirm what is required before choosing a disposal process.
Retain Evidence of Media Sanitization
Contractors need to keep documentation that links each retired asset to the outcome of its sanitization or data destruction. Depending on the applicable requirements, useful evidence may include:
- Asset identifiers and inventory records.
- The sanitization or destruction method used.
- Verification results and service records.
- Transfer documentation and chain of custody.
A qualified IT asset disposition (ITAD) provider can support this process by documenting asset handling and providing relevant service records. However, a Certificate of Destruction alone does not establish CMMC compliance; contractors remain responsible for meeting the security and contractual requirements that apply to their systems and information.

Why R2v3 Matters in Government IT Asset Disposal
Data sanitization protects information, but it does not cover every risk from retired electronics. Agencies and contractors also need to pay attention to how equipment is processed, how materials are handled, and what happens downstream.
Understand the Role of R2 Certification
R2v3 is an electronics recycling and reuse standard that addresses environmental, worker-safety, data-security, and downstream-management practices. It can help procurement teams assess how a recycling provider manages electronic equipment beyond the initial collection.
Whether R2v3 is required for a federal disposal depends on the specific asset and transaction. If federal guidance or an applicable contract calls for a specific certification, the agency or contractor should confirm that the provider holds it and that it covers the activities involved. Certification should not be presented as a universal requirement for every government electronics disposal without confirming the governing rule.
Evaluate Downstream Processing and Accountability
Recycling providers’ practices matter because equipment can pass between several organizations before it is recycled or its materials are recovered. Procurement teams should understand how a provider selects and manages downstream vendors and documents equipment and recovered materials.
When evaluating an R2v3-certified provider, teams should verify:
- That the certification is current and covers the relevant facility and activities.
- How downstream vendors are selected and monitored.
- How data-bearing equipment and materials are handled.
- What records are available to demonstrate final disposition.
R2v3 certification can strengthen a vendor’s suitability, but it does not replace checks for data sanitization, property-disposal authorization, state law, or contract-specific obligations.
Learn more: Hummingbird International, LLC Is Now R2v3 Certified
Checklist for Compliant Government IT Asset Disposal
Before Disposal
☐ Inventory all retired IT assets
☐ Identify devices containing sensitive data
☐ Confirm applicable disposal requirements
☐ Obtain required property-disposal approvals
☐ Select a qualified ITAD provider
Data Sanitization
☐ Select the appropriate sanitization method
☐ Verify sanitization or physical destruction
☐ Collect asset-level sanitization records
Collection & Transportation
☐ Secure and label retired assets
☐ Document pickup and transportation
☐ Maintain chain of custody
☐ Confirm delivery to the authorized provider
Vendor Verification
☐ Verify required certifications and their scope
☐ Review data-security and recycling procedures
☐ Check downstream processing practices
☐ Confirm asset-level reporting
Final Disposition
☐ Verify authorized transfer, reuse, recycling, or destruction
☐ Match assets to final disposition records
☐ Obtain applicable certificates and reports
☐ Archive records for audits
Final Check
☐ All assets accounted for
☐ Sanitization and disposition documented
☐ Applicable compliance requirements verified
Conclusion
Government IT asset disposal involves more than removing outdated equipment from service. Agencies must protect the information stored on retired devices, follow the property-disposition procedures that apply to government-owned equipment, and ensure electronics are handled through appropriate recycling channels. Meeting one obligation does not automatically satisfy the others.
A coordinated process helps agencies avoid premature equipment transfers, undocumented data sanitization, and improper disposal. This means identifying applicable requirements early, obtaining the necessary approvals, verifying sanitization results, maintaining chain-of-custody records, and confirming each device’s final destination.
Working with an experienced IT asset disposition provider can help agencies manage collection, data destruction, asset tracking, and responsible recycling. Hummingbird International supports government organizations with secure IT asset disposal and electronics recycling services, helping them maintain documentation and manage retired equipment responsibly.
Frequently Asked Questions
1. What regulations apply to government IT asset disposal?
Requirements depend on the organization and the type of equipment being disposed of. Federal agencies may need to consider applicable Federal Management Regulation provisions, GSA guidance, FISMA, and NIST SP 800-88. State and local agencies must also review their surplus-property procedures and state electronics-recycling laws. Government contractors should check relevant contract clauses and security requirements.
2. Is data wiping enough to make government IT equipment ready for disposal?
Not necessarily. The agency must select a sanitization method appropriate for the storage media, information sensitivity, and applicable security requirements. It must also verify and document the outcome. Media that cannot be effectively sanitized may require approved physical destruction.
3. Does NIST SP 800-88 apply to all government IT equipment?
NIST SP 800-88 provides guidance for sanitizing information stored on media. Its application depends on the agency’s security policies and the requirements governing the information and equipment. It is particularly relevant to devices containing storage media, such as laptops, servers, and external drives.
4. Is R2v3 certification mandatory for government electronics recycling?
R2v3 should not be treated as a universal legal requirement for every government agency or disposal transaction. However, it can help agencies evaluate a recycling provider’s data-security, environmental, worker-safety, and downstream-management practices. Agencies should verify whether a specific certification is required by applicable regulations, procurement rules, or contracts.
5. What IT asset disposal services does Hummingbird International provide for government agencies?
Hummingbird International provides IT asset disposition (ITAD), secure data destruction, and electronics recycling services to help organizations manage retired IT equipment. Services support secure asset handling, data sanitization or destruction, responsible material recovery, and documentation of the disposal process. Government agencies should confirm that the services, certifications, and documentation offered meet their specific regulatory, procurement, and security requirements.