Guide 7 of 7The metal
What happens to the drives when the server is handed back?
The floor of the stack is metal you never touch while the rental runs, and its drives outlive your tenancy in them. What happens to the media underneath is set out by ASD's media guidelines, one kind of media at a time.
General information, not legal or security advice.
By media type
The question starts with policy, not with a shredder: since media can store sensitive or classified data, ASD's guidelines ask that a media management policy is developed, implemented and maintained, so that all types of media, and the data they store, are protected appropriately. On a rented machine that policy has an end date, and the guidelines answer the end date by media type.
- Magnetic drives. Non-volatile magnetic media is sanitised by overwriting it at least once, or three times if it was made before 2001 or holds under 15 GB, in its entirety with a random pattern, followed by a read back for verification. For hard drives, the host-protected area and device configuration overlay table are reset before sanitisation, and the ATA secure erase command is used as well as block overwriting software, so that the drive’s growth defects table is overwritten too.
- Flash, meaning the solid-state drives in most rented machines. Wear levelling spreads writes evenly across the memory blocks, which is why flash media is overwritten with a random pattern at least twice, followed by a read back for verification, as this helps to ensure every block is overwritten. Even so, the guidelines warn that wear levelling and bad memory blocks mean some blocks may not be overwritten.
- Volatile memory, the working memory that loses its contents the moment power goes. Volatile media is sanitised by removing its power for at least 10 minutes.
- When overwriting will not do. Media that cannot be successfully sanitised is destroyed prior to its disposal, and the destruction methods ASD identifies are designed to ensure that recovery of data is impossible or impractical.
The nearest official rule is written for media released into the public domain, not for a server handed back to its provider, and it sets the bar this guide measures against: before media can be released into the public domain, it needs to be sanitised, destroyed or declassified, and because such media still presents a security risk, even a minor one, an appropriate authority needs to formally authorise its release.
Before the first use
The guidelines ask for the same kind of care at the other end of a machine's life, and it matters more on a rented one. Sanitising media before its first use can assist in reducing cyber supply chain risks, such as new media containing malicious code, and sanitising it before first use in a different security domain can prevent potential data spills from occurring. On a dedicated server whose drives arrive already installed, the first-use step is one question in the provider conversation: what was on these disks before they were shipped, and who can say so.
The companion habit from ASD's guidance for business data is encryption: apply full disk encryption to devices such as laptops, servers and mobile phones that store or access personal data, and consider file level encryption for added protection, checking that data is encrypted when it is transmitted as well, such as when information is sent over the internet. ASD's media guidelines explain the value of both: suitably encrypting media helps prevent malicious actors from gaining easy access to sensitive or classified data stored on it if it is lost or stolen, and it is critical that ASD-approved cryptography is used to do it.
Full disk encryption
Encryption and wiping are different instruments, and the guidelines treat them that way. When encryption is applied to media, it is important that full disk encryption is used, because it provides a greater level of protection than file-based encryption: file-based encryption may encrypt individual files, but unencrypted copies of files may be left behind in temporary locations that the operating system uses. The business-data guidance adds the practical extras: file level encryption for added protection, and encryption in transit for information sent over the internet.
What encryption does not do is end the story. It protects the data while the machine is yours and while the disk is intact; it is not a substitute for the end-of-life step: the nearest official rule, written for media released into the public domain rather than a server handed back, still asks that media be sanitised, destroyed or declassified, with the release formally authorised. Both belts, in other words, and the second one still gets fastened on the day the machine goes back.
Where this page stops
Two boundaries worth stating plainly. The first is this page's own: it answers how media is wiped, by type, under ASD's guidelines, and it stops there. What a hosting contract says about handing data back, deleting it, or the format and notice periods around the end of a tenancy is a contract question, and this page does not answer it. The second is the page's length: the sanitisation methods are a short list, and the guidelines answer the question media by media rather than method by method, so the page stays close to what ASD actually states.
What the page can leave you with is the short version, in the form of the two questions to put in writing before the machine is delivered and before it goes back. Before the first use: what was on these disks before they reached me? Before the handback: how are these drives sanitised, who does it, and who authorises the release?
The whole stack, bottom to top (dedicated-servers.com.au home)