--- title: "Guidelines for media" source: "https://www.cyber.gov.au/ism/oscal/v2026.09.4/artifacts/ISM_catalog.json" collection: "asd-ism" guidance_commit: "db3111cd9d11643ac08b34b4d75b0d0d983ca388" --- # Guidelines for media Source: https://www.cyber.gov.au/ism/oscal/v2026.09.4/artifacts/ISM_catalog.json OSCAL release: 2026.09.4 Catalog SHA-256: `237ea09362b8449ed5c5ee85de4725a0468ee73d13af7cf61c26d4e6ac47f12d` Rendered controls: 56 ## Media usage OSCAL sort-id: `catalog[1].group[14].group[1]` ### Overview #### Further information Further information on cyber supply chain risk management can be found in the ‘Cyber supply chain risk management’ section of the [Guidelines for procurement and outsourcing](https://www.cyber.gov.au/business-government/asds-cyber-security-frameworks/ism/cyber-security-guidelines/guidelines-for-procurement-and-outsourcing). Further information on the protection of media can be found in the Department of Home Affairs’ [Protective Security Policy Framework](https://www.protectivesecurity.gov.au/). Further information on securing media when not in use can be found in the ‘IT equipment and media’ section of the [Guidelines for physical security](https://www.cyber.gov.au/business-government/asds-cyber-security-frameworks/ism/cyber-security-guidelines/guidelines-for-physical-security). Further information on encrypting media can be found in the ‘Cryptographic fundamentals’ section of the [Guidelines for cryptography](https://www.cyber.gov.au/business-government/asds-cyber-security-frameworks/ism/cyber-security-guidelines/guidelines-for-cryptography). Further information on using media to transfer data between systems can be found in the ‘Data transfers’ section of the [Guidelines for data transfers](https://www.cyber.gov.au/business-government/asds-cyber-security-frameworks/ism/cyber-security-guidelines/guidelines-for-data-transfers). ### Media management policy OSCAL sort-id: `catalog[1].group[14].group[1].group[01]` #### Overview Since media can store sensitive or classified data, it is important that a media management policy is developed, implemented and maintained to ensure that all types of media, and the data it stores, is protected in an appropriate manner. In many cases, an organisation’s media management policy will be closely tied to their removable media usage policy. ### ISM-1549 - Revision: 1 - Updated: Dec-22 - Applicability: NC, OS, P, S, TS #### Statement A media management policy is developed, implemented and maintained. ### Removable media usage policy OSCAL sort-id: `catalog[1].group[14].group[1].group[02]` #### Overview Establishing a removable media usage policy can decrease the likelihood and consequence of data spills, data loss and data theft. In doing so, a removable media usage policy will likely cover the following: - permitted types and uses of removable media - registration and labelling of removable media - handling and protection of removable media - reporting of lost or stolen removable media - sanitisation or destruction of removable media at the end of its life. ### ISM-1359 - Revision: 4 - Updated: Dec-22 - Applicability: NC, OS, P, S, TS #### Statement A removable media usage policy is developed, implemented and maintained. ### Removable media register OSCAL sort-id: `catalog[1].group[14].group[1].group[03]` #### Overview Developing, implementing, maintaining and regularly verifying a register of removable media can assist an organisation in tracking and accounting for authorised removable media as well as identifying any unauthorised removable media in use within their organisation. ### ISM-1713 - Revision: 3 - Updated: Jun-26 - Applicability: NC, OS, P, S, TS #### Statement A removable media register is developed, implemented, maintained and regularly verified. ### Labelling media OSCAL sort-id: `catalog[1].group[14].group[1].group[04]` #### Overview Labelling media helps personnel to identify its sensitivity or classification and ensure that appropriate measures are applied to its storage, handling and use. While text-based protective markings are typically used for labelling media, there may be circumstances where colour-based protective markings or other marking schemes need to be used instead. In such cases, the marking scheme will need to be documented and personnel trained in its use. ### ISM-0332 - Revision: 6 - Updated: Jun-26 - Applicability: NC, OS, P, S, TS #### Statement Media, except for internally mounted fixed media within information technology equipment, is labelled with protective markings reflecting its sensitivity or classification. ### Classifying media OSCAL sort-id: `catalog[1].group[14].group[1].group[05]` #### Overview Media that is not correctly classified could be stored and handled inappropriately, accessed by personnel who do not have an appropriate security clearance or used with systems it is not authorised to be used with. ### ISM-0323 - Revision: 8 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement Media is classified to the highest sensitivity or classification of data it stores, unless the media has been classified to a higher sensitivity or classification. ### ISM-0337 - Revision: 6 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement Media is only used with systems that are authorised to process, store or communicate its sensitivity or classification. ### Reclassifying media OSCAL sort-id: `catalog[1].group[14].group[1].group[06]` #### Overview Some activities may necessitate or allow for a change to the sensitivity or classification of media. For example, when media is connected to a system that lacks a mechanism through which read-only access can be ensured, when media is sanitised or destroyed, or when data stored on media is subject to a sensitivity or classification change. ### ISM-0325 - Revision: 6 - Updated: Apr-21 - Applicability: NC, OS, P, S, TS #### Statement Any media connected to a system with a higher sensitivity or classification than the media is reclassified to the higher sensitivity or classification, unless the media is read-only or the system has a mechanism through which read-only access can be ensured. ### ISM-0330 - Revision: 7 - Updated: Mar-22 - Applicability: NC, OS, P, S, TS #### Statement Before reclassifying media to a lower sensitivity or classification, the media is sanitised or destroyed, and a formal administrative decision is made to reclassify it. ### Encrypting media OSCAL sort-id: `catalog[1].group[14].group[1].group[07]` #### Overview Suitably encrypting media will help prevent malicious actors from gaining easy access to any sensitive or classified data stored on it if it is lost or stolen. As such, it is critical that Australian Signals Directorate (ASD)-approved cryptography is used. Furthermore, applying encryption to media may change the way it needs to be handled. In doing so, any change in handling needs to be based on the original sensitivity or classification of the media and the level of assurance in the cryptographic equipment, applications or libraries being used to encrypt it. Finally, when encryption is applied to media, it is important that full disk encryption is used as it provides a greater level of protection than file-based encryption. This is because while file-based encryption may encrypt individual files, there is the possibility that unencrypted copies of files may be left in temporary locations used by an operating system. ### ISM-1059 - Revision: 5 - Updated: Jun-26 - Applicability: NC, OS, P, S, TS #### Statement All data stored on media is encrypted using ASD-approved cryptography. ### ISM-0459 - Revision: 5 - Updated: Jun-26 - Applicability: NC, OS, P, S, TS #### Statement Full disk encryption, or partial encryption where access controls only allow writing to encrypted partitions or volumes, is implemented when encrypting media. ### ISM-2109 - Revision: 0 - Updated: Jun-26 - Applicability: NC, OS, P, S, TS #### Statement Pre-boot authentication using passwords, or managed network-based key release, is implemented for media containing encrypted system volumes. ### Handling media OSCAL sort-id: `catalog[1].group[14].group[1].group[08]` #### Overview As media can be easily misplaced or stolen, physical handling measures should be put in place to protect the data stored on it. ### ISM-0831 - Revision: 5 - Updated: Sep-18 - Applicability: NC, OS, P, S, TS #### Statement Media is handled in a manner suitable for its sensitivity or classification. ### Sanitising media before first use OSCAL sort-id: `catalog[1].group[14].group[1].group[09]` #### Overview Sanitising media before first use can assist in reducing cyber supply chain risks, such as new media containing malicious code. In addition, sanitising media before first use in a different security domain can prevent potential data spills from occurring. ### ISM-1600 - Revision: 1 - Updated: Apr-21 - Applicability: NC, OS, P, S, TS #### Statement Media is sanitised before it is used for the first time. ### ISM-1642 - Revision: 0 - Updated: Apr-21 - Applicability: NC, OS, P, S, TS #### Statement Media is sanitised before it is reused in a different security domain. ### Using media for data transfers OSCAL sort-id: `catalog[1].group[14].group[1].group[10]` #### Overview An organisation transferring data between systems belonging to different security domains is strongly encouraged to use write-once media. When done properly, such as using non-rewritable compact discs that have been finalised, this ensures that data from the destination system cannot be accidentally transferred, or maliciously exfiltrated, onto the media and then onto another system. Alternatively, if suitable write-once media is not used, the destination system should have a mechanism through which read-only access can be ensured, such as via a read-only device or hardware write-blocker. However, the use of read-only mechanisms is not immune to failure or compromise. Therefore, rewritable media should still be sanitised following each data transfer. It is important to note that for most non-volatile flash memory media, it will be possible to sanitise and reclassify it following a data transfer to allow it to be connected to other systems again. This is not possible for SECRET and TOP SECRET non-volatile flash memory media as it cannot be reclassified following sanitisation. ### ISM-0347 - Revision: 5 - Updated: Apr-21 - Applicability: NC, OS, P, S, TS #### Statement When transferring data manually between two systems belonging to different security domains, write-once media is used unless the destination system has a mechanism through which read-only access can be ensured. ### ISM-0947 - Revision: 6 - Updated: Apr-21 - Applicability: NC, OS, P, S, TS #### Statement When transferring data manually between two systems belonging to different security domains, rewritable media is sanitised after each data transfer. ## Media sanitisation OSCAL sort-id: `catalog[1].group[14].group[2]` ### Overview #### Context When sanitising hybrid hard drives, first separate the non-volatile magnetic media from the circuit board containing non-volatile flash memory media and then sanitise each separately. When sanitising solid-state drives, the method for sanitising non-volatile flash memory media applies. #### Further information Further information on the random-access memory testing tool [MemTest86](https://www.memtest86.com/) can be obtained from PassMark Software. Further information on the graphics card random-access memory testing tools [MemtestG80](https://github.com/ihaque/memtestG80) and [MemtestCL](https://github.com/ihaque/memtestCL) can be obtained from their GitHub projects. Further information on HDDerase is available from the [Center for Memory and Recording Research](https://cmrr.ucsd.edu/resources/secure-erase.html) at the University of California San Diego. HDDerase can call the ATA secure erase command as well as reset the host-protected area and device configuration overlay table on non-volatile magnetic media. ### Media sanitisation processes and procedures OSCAL sort-id: `catalog[1].group[14].group[2].group[01]` #### Overview Using approved methods to sanitise media provides a level of assurance that, to the extent possible, no data will be left following sanitisation. The methods described in these guidelines are designed not only to prevent common data recovery practices but also to protect from those that could emerge in the future. ### ISM-0348 - Revision: 5 - Updated: Dec-22 - Applicability: NC, OS, P, S, TS #### Statement Media sanitisation processes, and supporting media sanitisation procedures, are developed, implemented and maintained. ### Volatile media sanitisation OSCAL sort-id: `catalog[1].group[14].group[2].group[02]` #### Overview When sanitising volatile media, the specified time to wait following the removal of power is based on applying a safety factor to the time recommended by research into preventing the recovery of data. In addition to the removal of power, SECRET and TOP SECRET volatile media should be overwritten at least once in its entirety with a random pattern followed by a read back for verification. ### ISM-0351 - Revision: 6 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement Volatile media is sanitised by removing its power for at least 10 minutes. ### ISM-0352 - Revision: 4 - Updated: Dec-21 - Applicability: S, TS #### Statement SECRET and TOP SECRET volatile media is sanitised by overwriting it at least once in its entirety with a random pattern followed by a read back for verification. ### Treatment of volatile media following sanitisation OSCAL sort-id: `catalog[1].group[14].group[2].group[03]` #### Overview Research suggests that short-term remanence effects are likely in volatile media. For example, up to minutes at normal room temperatures and up to hours in extremely cold temperatures. Furthermore, some volatile media can suffer from long-term remanence effects resulting from physical changes due to the continuous storage of static data for extended periods. It is for these reasons that under certain circumstances TOP SECRET volatile media retains its classification following sanitisation. Typical circumstances preventing the reclassification of TOP SECRET volatile media include a static cryptographic key being stored in the same memory location during every boot of a device, or a static image being displayed on a device and stored in volatile media for a period of months. ### ISM-0835 - Revision: 5 - Updated: Jun-26 - Applicability: TS #### Statement Following sanitisation, TOP SECRET volatile media retains its classification if it stored static data for an extended period, or had data repeatedly stored on or written to the same memory location for an extended period. ### Non-volatile magnetic media sanitisation OSCAL sort-id: `catalog[1].group[14].group[2].group[04]` #### Overview Non-volatile magnetic media encompasses non-volatile magnetic hard drives, magnetic tape and floppy disks. While non-volatile magnetic tape and floppy disks can be sanitised by overwriting them at least once (or three times if pre-2001 or under 15 GB) in their entirety with a random pattern followed by a read back for verification, additional considerations apply to non-volatile magnetic hard drives due to their use of a host-protected area, device configuration overlay table and growth defects table. The host-protected area and device configuration overlay table of non-volatile magnetic hard drives are normally not visible to a computer’s Unified Extensible Firmware Interface or operating system. Therefore, any sanitisation of the readable sectors of non-volatile magnetic hard drives will leave any data contained in sectors listed in the host-protected area and device configuration overlay table untouched. Some sanitisation applications include the ability to reset non-volatile magnetic hard drives to their default state, removing any host-protected areas or device configuration overlays. This allows the sanitisation applications to see the entire contents of non-volatile magnetic hard drives during subsequent sanitisation processes. Modern non-volatile magnetic hard drives automatically reallocate space for bad sectors at a hardware level. These bad sectors are maintained in what is known as the growth defects table or ‘g-list’. If data was stored in a sector that was subsequently added to the growth defects table, sanitising the non-volatile magnetic hard drive will not overwrite such data. While these sectors may be considered bad by non-volatile magnetic hard drives, quite often this is due to the sectors no longer meeting expected performance norms and not due to an inability to read or write to them. The Advanced Technology Attachment (ATA) secure erase command was built into the firmware of post-2001 non-volatile magnetic hard drives and can access sectors that have been added to the growth defects table. Modern non-volatile magnetic hard drives also contain a primary defects table or ‘p-list’. The primary defects table contains a list of bad sectors found during post-production processes. No data is ever stored in sectors listed in the primary defects table as they are marked as inaccessible before non-volatile magnetic hard drives are used for the first time. ### ISM-0354 - Revision: 6 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement Non-volatile magnetic media is sanitised by overwriting it at least once (or three times if pre-2001 or under 15 GB) in its entirety with a random pattern followed by a read back for verification. ### ISM-1065 - Revision: 3 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement The host-protected area and device configuration overlay table are reset prior to the sanitisation of non-volatile magnetic hard drives. ### ISM-1067 - Revision: 4 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement 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. ### Treatment of non-volatile magnetic media following sanitisation OSCAL sort-id: `catalog[1].group[14].group[2].group[05]` #### Overview Due to concerns with the sanitisation processes for non-volatile magnetic media, SECRET and TOP SECRET non-volatile magnetic media retains its classification following sanitisation. ### ISM-0356 - Revision: 6 - Updated: Dec-21 - Applicability: S, TS #### Statement Following sanitisation, SECRET and TOP SECRET non-volatile magnetic media retains its classification. ### Non-volatile erasable programmable read-only memory media sanitisation OSCAL sort-id: `catalog[1].group[14].group[2].group[06]` #### Overview When sanitising non-volatile erasable programmable read-only memory (EPROM), three times the manufacturer’s specification for ultraviolet erasure time should be applied to provide additional certainty in sanitisation processes. Subsequently, the non-volatile EPROM media should be overwritten at least once in its entirety with a random pattern followed by a read back for verification. ### ISM-0357 - Revision: 5 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement Non-volatile EPROM media is sanitised by applying three times the manufacturer’s specified ultraviolet erasure time and then overwriting it at least once in its entirety with a random pattern followed by a read back for verification. ### Non-volatile electrically erasable programmable read-only memory media sanitisation OSCAL sort-id: `catalog[1].group[14].group[2].group[07]` #### Overview A single overwrite with a random pattern, followed by a read back for verification, is considered suitable for sanitising non-volatile electrically erasable programmable read-only memory (EEPROM) media. ### ISM-0836 - Revision: 3 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement Non-volatile EEPROM media is sanitised by overwriting it at least once in its entirety with a random pattern followed by a read back for verification. ### Treatment of non-volatile erasable and electrically erasable programmable read-only memory media following sanitisation OSCAL sort-id: `catalog[1].group[14].group[2].group[08]` #### Overview As little research has been conducted into the recovery of data from non-volatile EPROM and EEPROM media, SECRET and TOP SECRET EPROM and EEPROM media retains its classification following sanitisation. ### ISM-0358 - Revision: 6 - Updated: Dec-21 - Applicability: S, TS #### Statement Following sanitisation, SECRET and TOP SECRET non-volatile EPROM and EEPROM media retains its classification. ### Non-volatile flash memory media sanitisation OSCAL sort-id: `catalog[1].group[14].group[2].group[09]` #### Overview For non-volatile flash memory media, a technique known as wear levelling ensures that writes are distributed evenly across each memory block. This feature necessitates non-volatile flash memory media being overwritten with a random pattern at least twice, and followed by a read back for verification, as this helps to ensure that all memory blocks are overwritten. ### ISM-0359 - Revision: 4 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement Non-volatile flash memory media is sanitised by overwriting it at least twice in its entirety with a random pattern followed by a read back for verification. ### Treatment of non-volatile flash memory media following sanitisation OSCAL sort-id: `catalog[1].group[14].group[2].group[10]` #### Overview Due to the use of wear levelling in non-volatile flash memory media, and the potential for bad memory blocks, it is possible that not all memory blocks will be overwritten during sanitisation processes. For this reason, SECRET and TOP SECRET non-volatile flash memory media retains its classification following sanitisation. ### ISM-0360 - Revision: 6 - Updated: Dec-21 - Applicability: S, TS #### Statement Following sanitisation, SECRET and TOP SECRET non-volatile flash memory media retains its classification. ### Media that cannot be successfully sanitised OSCAL sort-id: `catalog[1].group[14].group[2].group[11]` #### Overview In some cases, attempts to sanitise media, or verify the sanitisation of media, will be unsuccessful. For example, due to the media being faulty or damaged. In such cases, the media will need to be destroyed prior to its disposal. ### ISM-1735 - Revision: 1 - Updated: Sep-24 - Applicability: NC, OS, P, S, TS #### Statement Media that cannot be successfully sanitised is destroyed prior to its disposal. ## Media destruction OSCAL sort-id: `catalog[1].group[14].group[3]` ### Overview #### Further information Further information on cyber supply chain risk management can be found in the ‘Cyber supply chain risk management’ section of the [Guidelines for procurement and outsourcing](https://www.cyber.gov.au/business-government/asds-cyber-security-frameworks/ism/cyber-security-guidelines/guidelines-for-procurement-and-outsourcing). ### Media destruction processes and procedures OSCAL sort-id: `catalog[1].group[14].group[3].group[1]` #### Overview Developing, implementing and maintaining processes and procedures for media destruction will ensure that an organisation carries out media destruction in an appropriate and consistent manner. ### ISM-0363 - Revision: 4 - Updated: Dec-22 - Applicability: NC, OS, P, S, TS #### Statement Media destruction processes, and supporting media destruction procedures, are developed, implemented and maintained. ### Media that cannot be sanitised OSCAL sort-id: `catalog[1].group[14].group[3].group[2]` #### Overview Some media types are incapable of being sanitised. As such, they will need to be destroyed prior to their disposal. ### ISM-0350 - Revision: 5 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement The following media types are destroyed prior to their disposal: - microfiche and microfilm - optical discs - programmable read-only memory - read-only memory - other types of media that cannot be sanitised. ### Media destruction equipment OSCAL sort-id: `catalog[1].group[14].group[3].group[3]` #### Overview When physically destroying media, using approved equipment can provide a level of assurance that the data it stores is destroyed. Approved equipment includes destruction equipment listed on the Security Construction and Equipment Committee’s [Security Equipment Evaluated Products List](https://www.scec.gov.au/catalogue), and in the Australian Security Intelligence Organisation’s (ASIO) Security Equipment Guide-009, Optical Media Shredders and Security Equipment Guide-018, Destructors. ASIO’s Security Equipment Guides are available from the Protective Security Policy GovTEAMS community or ASIO by email. If using degaussers to destroy media, the United States’ National Security Agency maintains the [NSA/CSS Evaluated Products List for Magnetic Degaussers](https://www.nsa.gov/Resources/Media-Destruction-Guidance/NSA-Evaluated-Products-Lists-EPLs/) and information on common types of magnetic media and their associated magnetic field strengths and orientations. ### ISM-1361 - Revision: 3 - Updated: Jun-22 - Applicability: NC, OS, P, S, TS #### Statement Security Construction and Equipment Committee-approved equipment or ASIO-approved equipment is used when destroying media. ### ISM-1160 - Revision: 2 - Updated: Aug-20 - Applicability: NC, OS, P, S, TS #### Statement If using degaussers to destroy media, degaussers evaluated by the United States’ National Security Agency are used. ### Media destruction methods OSCAL sort-id: `catalog[1].group[14].group[3].group[4]` #### Overview The destruction methods identified below are designed to ensure that recovery of data is impossible or impractical. ### ISM-1517 - Revision: 0 - Updated: Sep-18 - Applicability: NC, OS, P, S, TS #### Statement Equipment that is capable of reducing microform to a fine powder, with resultant particles not showing more than five consecutive characters per particle upon microscopic inspection, is used to destroy microfiche and microfilm. ### ISM-1722 - Revision: 1 - Updated: Mar-22 - Applicability: NC, OS, P, S, TS #### Statement Electrostatic memory devices are destroyed using a furnace/incinerator, hammer mill, disintegrator or grinder/sander. ### ISM-1723 - Revision: 1 - Updated: Mar-22 - Applicability: NC, OS, P, S, TS #### Statement Magnetic floppy disks are destroyed using a furnace/incinerator, hammer mill, disintegrator, degausser or by cutting. ### ISM-1724 - Revision: 1 - Updated: Mar-22 - Applicability: NC, OS, P, S, TS #### Statement Magnetic hard disks are destroyed using a furnace/incinerator, hammer mill, disintegrator, grinder/sander or degausser. ### ISM-1725 - Revision: 1 - Updated: Mar-22 - Applicability: NC, OS, P, S, TS #### Statement Magnetic tapes are destroyed using a furnace/incinerator, hammer mill, disintegrator, degausser or by cutting. ### ISM-1726 - Revision: 1 - Updated: Mar-22 - Applicability: NC, OS, P, S, TS #### Statement Optical disks are destroyed using a furnace/incinerator, hammer mill, disintegrator, grinder/sander or by cutting. ### ISM-1727 - Revision: 1 - Updated: Mar-22 - Applicability: NC, OS, P, S, TS #### Statement Semiconductor memory is destroyed using a furnace/incinerator, hammer mill or disintegrator. ### ISM-0368 - Revision: 8 - Updated: Mar-22 - Applicability: NC, OS, P, S, TS #### Statement Media destroyed using a hammer mill, disintegrator, grinder/sander or by cutting results in media waste particles no larger than 9 mm. ### Treatment of media waste particles OSCAL sort-id: `catalog[1].group[14].group[3].group[5]` #### Overview Following the destruction of SECRET and TOP SECRET media, normal accounting and verification processes and procedures do not apply. However, if a destruction method is used that results in the generation of media waste particles, such as a hammer mill, disintegrator, grinder/sander or by cutting, it may still need to be stored and handled as classified waste. ### ISM-1728 - Revision: 0 - Updated: Dec-21 - Applicability: S #### Statement The resulting media waste particles from the destruction of SECRET media is stored and handled as OFFICIAL if less than or equal to 3 mm, PROTECTED if greater than 3 mm and less than or equal to 6 mm, or SECRET if greater than 6 mm and less than or equal to 9 mm. ### ISM-1729 - Revision: 0 - Updated: Dec-21 - Applicability: TS #### Statement The resulting media waste particles from the destruction of TOP SECRET media is stored and handled as OFFICIAL if less than or equal to 3 mm, or SECRET if greater than 3 mm and less than or equal to 9 mm. ### Degaussing magnetic media OSCAL sort-id: `catalog[1].group[14].group[3].group[6]` #### Overview Degaussing magnetic media changes its magnetic properties, permanently corrupting data. When degaussing magnetic media, care needs to be taken as a degausser of insufficient magnetic field strength will not be effective. In addition, since 2006 perpendicular magnetic media has progressively replaced longitudinal magnetic media. As some older degaussers are only capable of destroying longitudinal magnetic media, care needs to be taken to ensure that a degausser with a suitable magnetic orientation is also used. Furthermore, to ensure that degaussers are being used in the correct manner to effectively destroy magnetic media, product-specific directions provided by degausser manufacturers should be followed. Finally, to provide an additional level of assurance following the use of a degausser, magnetic media should be physically damaged by deforming any internal platters. ### ISM-0361 - Revision: 4 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement Magnetic media is destroyed using a degausser with a suitable magnetic field strength and magnetic orientation. ### ISM-0362 - Revision: 4 - Updated: Mar-22 - Applicability: NC, OS, P, S, TS #### Statement Product-specific directions provided by degausser manufacturers are followed. ### ISM-1641 - Revision: 2 - Updated: Mar-22 - Applicability: NC, OS, P, S, TS #### Statement Following the use of a degausser, magnetic media is physically damaged by deforming any internal platters. ### Supervision of destruction OSCAL sort-id: `catalog[1].group[14].group[3].group[7]` #### Overview To verify that media is appropriately destroyed, destruction processes need to be supervised by at least one cleared person. ### ISM-0370 - Revision: 6 - Updated: Sep-23 - Applicability: NC, OS, P, S, TS #### Statement The destruction of media is performed under the supervision of at least one cleared person. ### ISM-0371 - Revision: 4 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement Personnel supervising the destruction of media supervise its handling to the point of destruction and ensure that the destruction is completed successfully. ### Supervision of accountable material destruction OSCAL sort-id: `catalog[1].group[14].group[3].group[8]` #### Overview The successful destruction of media storing accountable material is more important than for other media. As such, its destruction should be supervised by at least two cleared personnel who sign a destruction certificate afterwards. ### ISM-0372 - Revision: 6 - Updated: Sep-23 - Applicability: NC, OS, P, S, TS #### Statement The destruction of media storing accountable material is performed under the supervision of at least two cleared personnel. ### ISM-0373 - Revision: 4 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement Personnel supervising the destruction of media storing accountable material supervise its handling to the point of destruction, ensure that the destruction is completed successfully and sign a destruction certificate afterwards. ### Outsourcing media destruction OSCAL sort-id: `catalog[1].group[14].group[3].group[9]` #### Overview While media storing accountable material cannot be outsourced, media storing non-accountable material can be outsourced when using a National Association for Information Destruction AAA certified destruction service with endorsements, as specified in ASIO’s Protective Security Circular-167, External destruction of security classified information. This publication is available from the Protective Security Policy GovTEAMS community or ASIO by email. ### ISM-0839 - Revision: 3 - Updated: Dec-21 - Applicability: OS, P, S, TS #### Statement The destruction of media storing accountable material is not outsourced. ### ISM-0840 - Revision: 4 - Updated: Jun-22 - Applicability: OS, P, S #### Statement When outsourcing the destruction of media storing non-accountable material, a National Association for Information Destruction AAA certified destruction service with endorsements, as specified in ASIO’s Protective Security Circular-167, is used. ## Media disposal OSCAL sort-id: `catalog[1].group[14].group[4]` ### Media disposal processes and procedures OSCAL sort-id: `catalog[1].group[14].group[4].group[1]` #### Overview Developing, implementing and maintaining processes and procedures for media disposal will ensure that an organisation carries out media disposal in an appropriate and consistent manner. ### ISM-0374 - Revision: 4 - Updated: Dec-22 - Applicability: NC, OS, P, S, TS #### Statement Media disposal processes, and supporting media disposal procedures, are developed, implemented and maintained. ### Disposal of media OSCAL sort-id: `catalog[1].group[14].group[4].group[2]` #### Overview Before media can be released into the public domain, it needs to be sanitised, destroyed or declassified. As sanitised, destroyed or declassified media still presents a security risk, albeit minor, an appropriate authority needs to formally authorise its release into the public domain. Furthermore, as part of disposal processes, removing labels and markings indicating the owner, sensitivity, classification or any other marking that can associate media with its prior use will ensure it does not draw undue attention following its disposal. ### ISM-0378 - Revision: 4 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement Labels and markings indicating the owner, sensitivity, classification or any other marking that can associate media with its prior use are removed prior to its disposal. ### ISM-0375 - Revision: 6 - Updated: Dec-21 - Applicability: NC, OS, P, S, TS #### Statement Following sanitisation, destruction or declassification, a formal administrative decision is made to release media, or its waste, into the public domain.