ASD ISM 1628 Prevent anonymity network traffic in outbound connections
What it says
Outbound network connections to anonymity networks are blocked.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishEnsure outbound connections to anonymous networks are blocked for security.
This control means you need to stop computers in your organisation from connecting to networks that hide where internet traffic is coming from, like Tor. It's important because if someone in your organisation can browse anonymously, they might do something harmful or illegal without being traced, causing security risks or legal issues for your business.
Free. Save your status, tasks and notes.
Why it matters
If anonymity networks are reachable outbound, staff or malware can exfiltrate data and evade monitoring, increasing insider-threat and legal/compliance risk.
How to implement
The IT team should set up your internet firewall to block access to known anonymity networks like Tor.
This can be done by updating the firewall settings with a list of these networks' server addresses, which are often provided by cyber security agencies like the Australian Cyber Security Centre.
System administrators should ensure that access to anonymity networks is routinely monitored.
Use existing network monitoring tools to flag unusual traffic that might indicate attempted connections and set up alerts to notify the team if such activity is detected.
Managers should educate staff on the potential legal and security risks of using anonymous browsing.
Hold regular information sessions or training workshops to explain why connecting to these networks is harmful and how it can affect the entire organisation.
System owners should periodically review and update the network's filtering rules.
Work with IT specialists to check that the list of blocked anonymity networks is current and includes any new ones that have been identified.
Contract with a cyber security provider to conduct regular audits of your network's security settings.
They should verify that connections to anonymity networks are blocked and help identify any configuration weaknesses that could be exploited.
Keep it running
Block outbound Tor/I2P and known anonymity VPN endpoints at the firewall/proxy, and review logs and threat intel regularly to catch new exit nodes.
Evidence and audit
- Check 1 of 4What an auditor asks for
Ask for
The latest firewall configuration report from the IT team.
Look at
The list of blocked server addresses or networks to ensure anonymity networks like Tor are included.
Good evidence
Result is a detailed list showing all identified anonymity networks are blocked.
- Check 2 of 4What an auditor asks for
Good evidence
Is no logged traffic moving to or from those networks.
- Check 3 of 4What an auditor asks for
Ask for
Evidence of user education materials or attendance records from recent awareness sessions. Review agendas or training content to confirm that digital security and risks of anonymity networks were covered.
Good evidence
Result shows regular training sessions with relevant content covered.
- Check 4 of 4What an auditor asks for
Good evidence
Shows regular updates and documented procedures.
Mappings
Closest match in ISO/IEC 27001: A.8.20, Network and network devices security, which this control partially meets.
ISO/IEC 27001: 2 mappings
This control partially meets A.8.20.
ISM-1628 requires organisations to block outbound network connections to anonymity networks (e.g. Tor or similar) to prevent covert or untraceable egress. ISO/IEC 27001:2022 Annex A 8.20 requires networks and network devices to be secured, managed and controlled, which commonly includes egress filtering and proxy/firewall policy enforcement that can implement such blocking. ISM-1628 is a specific, prescriptive instance of the broader network security management expectations in Annex A 8.20.
This control partially meets A.8.21.
ISM-1628 requires organisations to block outbound connections to anonymity networks to reduce exfiltration and command-and-control concealment. ISO/IEC 27001:2022 Annex A 8.21 focuses on identifying, implementing and monitoring security mechanisms and requirements for network services, which can include controlling which external services/protocols are permitted and monitoring for prohibited services such as anonymisers. ISM-1628 is a specific egress-control requirement, whereas Annex A 8.21 is broader and covers service-level security and monitoring beyond anonymity networks.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




