Skip to content
Media
ASD ISMISM-1067

ASD ISM 1067 Secure erase for non-volatile magnetic media

What it says

The ATA secure erase command is used, in addition to block overwriting software, to ensure the growth defects table of non-volatile magnetic hard drives is overwritten.

Quoted as published. Everything else on this page is written by Control Stack.

What it means

In plain English

Use secure erase plus software to fully overwrite data on hard drives, including hidden areas.

When you get rid of old hard drives or computers, you want to make sure no one can dig up any old files from them. This control tells us how to securely erase all the information stored on magnetic hard drives, even in the hidden parts. It's important because if data isn't erased properly, someone could access sensitive business or personal information without your knowledge.

Why it matters

Failure to use ATA Secure Erase plus block overwriting can leave data in growth defect tables, enabling data recovery.

How to implement

  1. The IT team should ensure that they have access to secure erase software that can completely wipe hard drives before disposal or reuse.

    They can download reliable software from trusted sources recommended by the Australian Cyber Security Centre (ACSC).

  2. Managers should coordinate with the IT team to set up a regular schedule for checking which drives need erasing.

    They can list all drives that are due for replacement and prioritise those containing sensitive data.

  3. Office managers should keep a record of all equipment that contains hard drives.

    They should work with IT to ensure that every drive is securely erased before disposal. Keep a simple spreadsheet to track this.

  4. Employees who use computers should inform IT staff when a machine is no longer needed or needs to be replaced.

    IT staff can then initiate the secure erase process following the guidelines from the software provider.

  5. Procurement should ensure that any new hardware purchases come with clear instructions or software for secure erase procedures.

    This ensures compliance even as new devices are introduced into the workplace.

Keep it running

For HDD disposal, run ATA Secure Erase and then block-overwrite; record logs to confirm growth defect tables are overwritten.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The secure erase policy document: Request a document that outlines the procedures and tools used for secure erasing drives.

    Look at

    References to specific software and processes for checking completeness of erasure.

    Good evidence

    Is a detailed policy that explains how all drives are managed and verified once erased.

  2. Check 2 of 5What an auditor asks for

    Ask for

    Evidence of software tools used: Request documentation showing the secure erase software in use within the organisation.

    Look at

    Purchase orders or software licences to confirm the legitimacy and validity of these tools.

    Good evidence

    Includes up-to-date licences and records of software installation.

  3. Check 3 of 5What an auditor asks for

    Ask for

    To see records of erased drives: Request logs or a list of drives that have been securely erased.

    Look at

    Whether the records include dates, responsible personnel, and methods used.

    Good evidence

    Is a comprehensive log showing systematic records of the secure erase process.

  4. Check 4 of 5What an auditor asks for

    Ask for

    Evidence of staff training: Request records or certificates showing that IT staff have been trained in secure data erasure.

    Look at

    Course outlines or training dates to confirm relevance and recent training.

    Good evidence

    Includes recent training sessions and staff acknowledgements of the procedures.

  5. Check 5 of 5What an auditor asks for

    Ask for

    The IT disposal checklist: Request the checklist used by IT staff before disposing of or repurposing drives. Look to ensure it includes a verification step for secure erasure completion.

    Good evidence

    Is a checklist that is routinely used with all necessary steps clearly marked and actioned.

Mappings

Closest match in ISO/IEC 27001: A.7.10, Secure management of storage media, which this control partially meets.

ISO 27001

ISO/IEC 27001: 2 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.