ASD ISM 0347 Use write-once media for secure data transfers
What it says
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.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishWhen moving data between different security levels, make sure to use media that can't be changed, unless the destination can ensure it's read-only.
When transferring data between systems with different security levels, it's crucial to use media that can't be altered, like write-once CDs. This is important because changing data mid-transfer could lead to leaks or misuse of sensitive information, so using write-once media prevents tampering.
Free. Save your status, tasks and notes.
Why it matters
Using write-once media for cross-domain manual transfers prevents post-write modification and reduces leakage and integrity risks between security domains.
How to implement
IT staff should organise a review of existing media usage processes: Ensure staff members are aware of which types of physical media (like CDs or DVDs) can only be written to once.
This can involve updating procedures and providing training to relevant staff on the secure handling of such media.
System owners should coordinate with the IT team to source appropriate write-once media: Identify and purchase media that can be used to securely transfer data.
This includes liaising with suppliers to confirm that the media meets security requirements and is compatible with existing systems.
The IT team should implement a verification process to ensure the media is write-once: Conduct tests to confirm that the media can be written to only once and mark it as secured.
This might involve attempting to overwrite the media after data is transferred to verify that it's not possible.
Managers should establish a policy for data transfer approval: Create a clear procedure for approving transfers, including a checklist that ensures write-once media is being used for high-security data movements.
This could involve setting up a quick form that requires sign-off from a data protection officer.
The IT team should install software to ensure read-only access on receiving systems: Where exceptions are necessary, configure the systems that will receive data to allow only read access, preventing any changes.
This may involve using operating system settings or third-party software to enforce read-only restrictions.
Keep it running
For each manual cross-domain transfer, use write-once media unless the destination can enforce read-only mounting; periodically test and document that control.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
Documentation of the media usage policy: Request written policies that specify the use of write-once media for data transfers between different security levels.
Look at
Specific types of media mentioned and procedures for approval.
Good evidence
Is a detailed policy clearly outlining these requirements.
- Check 2 of 5What an auditor asks for
Ask for
Them how they select appropriate media for transfers. Ensure they describe the process for confirming the media is write-once.
Good evidence
Is they can articulate the sourcing and testing protocols to ensure media is not reusable.
- Check 3 of 5What an auditor asks for
Look at
Logs that document data transfers, noting the type of media used. Verify that the logs state write-once media was utilised.
Good evidence
Is detailed, regularly updated logs showing compliance with the media use policy.
- Check 4 of 5What an auditor asks for
Good evidence
Observation is staff consistently following procedures and conducting verification checks.
- Check 5 of 5What an auditor asks for
Ask for
To see any systems configured for read-only access: Request a demonstration of the configured read-only setting on systems receiving data.
Look at
Logical settings that prevent data modification.
Good evidence
Would be consistent configuration and a strong knowledge of the protocols to maintain read-only settings.
Mappings
Closest match in ISO/IEC 27001: A.5.14, Information transfer policies and procedures, which this control partially meets.
ISO/IEC 27001: 1 mapping
This control partially meets A.5.14.
Annex A 5.14 requires controlled information transfer rules and procedures for all transfer facilities, including manual transfers. ISM-0347 supports this by prescribing a specific secure method for manual cross-domain transfer (write-once media unless read-only can be ensured), which operationalises part of a transfer procedure. ISM-0347 is a technical constraint for a particular high-risk transfer scenario, whereas Annex A 5.14 is broader and requires governance across all transfer types.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




