A.7 Physical controls

A.7.14 Secure disposal or re-use of equipment

Not mandatory by default – decided in your SoA

What it means in plain language

Before disposing of or reusing equipment, make sure sensitive data and licensed software are securely removed.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Secure disposal or reuse often fails when organizations focus on physical handoff and ignore hidden storage, firmware settings, or licensed software left behind. The Secure Disposal & Reuse Procedure should decision points for wiping, destruction, redeployment, and resale, with accountable ownership across IT, asset management, and approved vendors. It should also align disposal actions with inventory, legal retention, and privacy obligations so every device leaves controlled custody with traceable evidence.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Equipment is reassigned to another user without verified sanitization, so prior data, credentials, browser profiles, or cached tokens may remain accessible to the next owner.
  • Retired laptops or drives are handed to a recycler without chain-of-custody records, making it unclear who removed, transported, stored, or destroyed the media.
  • Asset records show disposal status but not the method used, leaving no link between the item, the wipe certificate, and the authorized release decision.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Create a disposal decision tree for each equipment class: reuse in place, redeploy internally, return to less sensitive use, send for wipe, or destroy. The asset owner should confirm data classification, software licensing, and any legal hold before release, while IT or a trusted specialist performs the sanitization step.
  • Use concrete tools such as wipe logs, destruction certificates, transfer forms, and asset register status codes. For reusable devices, record the wipe standard or equivalent method, verification result, operator identity, and date; for destroyed items, note serial numbers, component type, and approved disposal route.
  • Control handover to external vendors through documented chain of custody and receiving signatures. Where a device contains removable media, keep media control separate from chassis disposal so a failed drive or memory module is not overlooked. Any exception, such as emergency disposal, should be approved and later reviewed.
  • After reuse, confirm licensed software removal or reallocation, user account deletion, and any required configuration reset. Review periodic samples from the asset register to detect gaps between retirement, wipe completion, and status change, then address missing records through corrective action rather than informal reminders.

What an auditor will ask to see

  • Asset register entry showing retirement date, sanitization outcome, disposal route, and final status.
  • Wipe report or destruction certificate listing serial number, method, operator, and verification result.
  • Chain-of-custody form with release, transport, receiver, and disposal timestamps or signatures.
  • Reuse checklist confirming software removal, account reset, and authorization for redeployment.

Baseline documents in the kit

These free kit documents help you document or evidence A.7.14. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.7.10 — Storage media and A.5.33 — Protection of records. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.