ASD ISM 1287 Ensure gateway and CDS file content sanitisation
What it says
Files imported or exported via gateways or CDSs undergo content sanitisation.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishFiles passing through gateways or CDSs are cleaned to remove harmful content.
This control is about making sure any file passing through your computer systems' entry and exit points is cleaned. This matters because harmful content like viruses or sensitive information leaks could get through if files aren't properly checked, potentially causing financial loss or damaging your business's reputation.
Free. Save your status, tasks and notes.
Why it matters
Failure to sanitise files at gateways or CDS may allow malware infiltration, exposing the organisation to potential data breaches and reputational damage.
How to implement
System owners should work with IT staff to identify all gateways and Cross Domain Solutions (CDSs) where files enter or exit the organisation.
This can be done by reviewing network diagrams and data flow maps to ensure all potential entry and exit points are covered.
IT teams need to choose appropriate content sanitisation tools to clean files.
They can look up recommendations from the Australian Cyber Security Centre (ACSC) or consult with experts to select tools that specifically remove viruses and strip harmful elements from files.
Managers should set policies specifying that all files go through these selected tools before being used or sent out.
This means establishing clear guidelines that staff must follow to submit files for sanitisation during regular workplace activities.
IT staff are tasked with configuring the tools to automatically process files as they pass through gateways.
This involves setting up the tools to work continuously in the background without needing constant supervision, ensuring no file goes unchecked.
Office managers should conduct regular training sessions to remind all employees about the importance of this process.
Using real-world examples of what could happen if harmful files get through can reinforce why they need to follow the process.
Keep it running
Regularly update sanitisation tools and monitor logs for anomalies. Validate gateway/CDS file-type rules, and quarantine suspect files for analysis before allowing import or export.
Evidence and audit
- Check 1 of 5What an auditor asks for
Ask for
The list of gateways and CDSs identified by the organisation: Check that each entry and exit point for files is covered and noted.
Good evidence
Includes a comprehensive list that matches your network setup and data flow maps.
- Check 2 of 5What an auditor asks for
Look at
The criteria used for selecting these tools.
Good evidence
Provides documentation showing the tools chosen based on ACSC guidelines or expert consultation.
- Check 3 of 5What an auditor asks for
Ask for
The policy documents regarding file sanitisation: Review them to ensure there's a clear process for file checking before any use or distribution.
Good evidence
Includes a policy that all staff understand and follow.
- Check 4 of 5What an auditor asks for
Good evidence
Shows logs proving the tools are set up and operational around the clock.
- Check 5 of 5What an auditor asks for
Ask for
Training records for staff awareness sessions.
Look at
Attendance and content details to verify that training is thorough and frequent.
Good evidence
Includes regular sessions and materials that cover risks and processes.
Mappings
Closest match in ISO/IEC 27001: A.8.7, Protection against malware, which this control partially meets.
ISO/IEC 27001: 1 mapping
This control partially meets A.8.7.
ISM-1287 requires that files imported or exported via gateways or cross domain solutions (CDSs) undergo content sanitisation to remove harmful or unsafe content. This supports Annex A 8.7 by providing a concrete preventative mechanism to reduce malware introduction via file transfer paths, particularly for externally sourced or cross-boundary files. Annex A 8.7 is broader and includes endpoint/network malware protections and awareness, while ISM-1287 is specific to sanitising files at transfer enforcement points.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




