ASD ISM 0459 Use full disk encryption, or partial if only encrypted volumes are writable
What it says
Full disk encryption, or partial encryption where access controls only allow writing to encrypted partitions or volumes, is implemented when encrypting media.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishWhen encrypting media, use full disk encryption, or partial encryption only if access controls stop writing anywhere except encrypted partitions or volumes.
When media is encrypted, one of two approaches must be implemented, and encrypting individual files alone meets neither:
- Full disk encryption: the whole drive is encrypted, apart from any small start-up area the encryption product needs.
- Partial encryption: only some partitions or volumes (separately managed sections of a drive) are encrypted, and access controls only allow writing to the encrypted ones. Data already on an unencrypted partition still falls short of ISM-1059, which requires all data on media to be encrypted.
Free. Save your status, tasks and notes.
Why it matters
Encrypting only files can leave readable temporary copies elsewhere on a drive, open to anyone holding lost or stolen media. Encrypting the whole drive, or blocking writes outside encrypted partitions or volumes, removes those places for unencrypted copies to land.
How to implement
Use full disk encryption by default.
Choose the option that encrypts the whole drive, not only used space, because free space can still hold deleted data. Roll it out from your endpoint management tool so new devices get the setting.
Clear data from unencrypted partitions before using partial encryption.
A write block does not encrypt what is already there, and ISM-1059 requires all data on media to be encrypted. Copy everything on the drive to encrypted storage, sanitise the whole drive (ISM-0354 and ISM-0359 require overwriting media in its entirety), then restore the data to encrypted partitions or volumes.
Block writes to unencrypted partitions and volumes when using partial encryption.
Use the access controls in the operating system or encryption product that deny write access to anything unencrypted, for every account, including administrators and applications. Apply the same setting to removable media.
Add full disk or partial encryption where only files are encrypted.
File or folder tools alone do not meet this, though they can stay on top. Where a bought device or service offers only file-level encryption, use another product or keep the data off it. A recorded risk leaves a known shortfall until closed.
Keep it running
Check settings after operating system upgrades, re-imaging and drive replacements, because these can change encryption or write rules. A new encryption product or a newly partitioned drive should trigger another look.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
The encryption report from the management console, compared with an asset list and an independent discovery scan.
Look at
The encryption type on each device, and any device in the scan missing from the report.
Good evidence
Every device uses full disk encryption or partial encryption with write controls, none relies on file-level encryption alone, and none in the scan is missing from the report.
- Check 2 of 3What an auditor asks for
Ask for
A demonstration on sampled partially encrypted media, including removable media, of saving a test file to each unencrypted partition or volume.
Look at
Whether the write is refused for an ordinary user, an administrator and an application.
Good evidence
Every attempt by the user, the administrator and the application to write outside an encrypted partition or volume is refused, so the only writable locations are encrypted.
- Check 3 of 3What an auditor asks for
Ask for
An offline read of the raw contents of a sampled drive, on a system authorised for its level.
Look at
Whether any partition or free space holds readable data, such as temporary files or data from before encryption.
Good evidence
Every area holding data is unreadable without the key, and any unencrypted partition holds only the start-up files the encryption product needs.
Mappings
Closest match in ISO/IEC 27001: A.8.24, Use of cryptography, which this control partially meets.
ISO/IEC 27001: 1 mapping
This control partially meets A.8.24.
ISM-0459 requires implementing full disk encryption, or partial disk encryption where controls ensure data can only be written to the encrypted partition, to protect data at rest on storage media. This is a direct instance of cryptography use: disk/volume encryption is a concrete application of cryptographic controls and depends on appropriate key handling to prevent offline access to data if a device or drive is lost, stolen, or removed. Annex A 8.24 is broader because it requires the organisation to define and implement rules for cryptography and cryptographic key management across all relevant use cases (not only disks), whereas ISM-0459 focuses specifically on encryption-at-rest for disks/partitions and the write-to-encrypted-partition condition.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




