ASD ISM 1781 Encrypt network data with ASD-approved cryptography
What it says
All data communicated over network infrastructure is encrypted using ASD-approved cryptography.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Encrypt all data that travels over any network, including internal traffic inside secure areas, using ASD-approved cryptography.
All data communicated over network infrastructure must be encrypted using ASD-approved cryptography. Network infrastructure is whatever carries data between workstations, servers and network devices, so traffic that never leaves the organisation's own wired or wireless networks counts too, even inside secure areas. ASD-approved cryptography means ASD-Approved Cryptographic Algorithms and Protocols, or high assurance ones, properly implemented. The statement makes no exception for protocols that cannot encrypt. ISM-0469 also requires an ASD-Approved Cryptographic Protocol, or a high assurance one, for data in transit.
Free. Save your status, tasks and notes.
Why it matters
Physical security cannot stop a compromised switch, router or wireless access point copying clear-text passwords and data passing through it. Encrypting all data in transit with ASD-approved cryptography means copied traffic cannot be read without the keys.
How to implement
Map every data flow, including internal ones.
List each protocol used between workstations, servers, storage, backup and management systems and network devices, from flow records or packet captures as well as design documents, so undocumented clear-text traffic shows up. Note how each flow is encrypted today, if at all.
Move each flow to an ASD-approved protocol.
Use TLS, SSH or IPsec set up as the ISM requires, such as the latest TLS version (ISM-1139) with AES-GCM (ISM-1369). Replace clear-text protocols, for example HTTP with HTTPS and Telnet with SSH, and include directory, file sharing and database traffic, and event logs sent to the centralised event logging facility (ISM-1984).
Encrypt links for traffic with no encrypted form.
Use MACsec in confidentiality mode on wired links (ISM-2163) and WPA3-Enterprise 192-bit mode on wireless networks (ISM-1332), so frames such as address assignment and device discovery are encrypted too. Link encryption is undone inside each network device, so it does not replace end-to-end encryption for protocols that support it.
Replace systems that cannot encrypt.
Where a legacy system or appliance cannot use any approved protocol, replace it. Carrying its traffic in IPsec from a device directly beside it reduces the exposure but leaves that short link in clear text, so track it as a shortfall until replaced, because the statement allows no exception.
Get evidence for links and services you do not run.
For carrier links and cloud or managed services, confirm from the provider's settings or IRAP assessment report that traffic uses ASD-approved cryptography. If not, add your own encryption, using evaluated products or High Assurance Cryptographic Equipment where ISM-0465 or ISM-0467 applies, or raise a shortfall with the provider.
Keep it running
Make encryption a condition of connecting any new system, device, link or protocol, and alert on clear-text protocols seen in flow records. Recheck protocol settings when ASD updates its approved algorithms and protocols.
Evidence and audit
- Check 1 of 4What an auditor asks for
Ask for
Flow records or traffic analysis from a sample of user, server, management and wireless segments, with the list of data flows and how each is encrypted.
Look at
Whether every protocol seen is on the list, and whether any of its data travels in clear text.
Good evidence
Every protocol seen is on the list with its data encrypted by ASD-approved cryptography, including inside secure areas, and no clear-text flow is excused by an exception or accepted risk.
- Check 2 of 4What an auditor asks for
Ask for
A packet capture from a sample of internal links, such as between workstations and file servers or between application and database servers.
Look at
Whether any credentials, file contents, queries or management commands can be read.
Good evidence
None of them can be read, including in traffic that never leaves the building.
- Check 3 of 4What an auditor asks for
Ask for
The settings a sample of encrypted services accept, tested with a scanner or a client that also offers older versions and clear text.
Look at
Which protocol versions and algorithms each service accepts, and whether it falls back to clear text.
- Check 4 of 4What an auditor asks for
Ask for
Encryption evidence for carrier links and cloud or managed services, such as provider settings or an IRAP assessment report.
Look at
Whether traffic over each link or service the organisation does not run is encrypted, and how.
Good evidence
Every such link and service carries traffic encrypted with ASD-approved cryptography, by the provider or by the organisation's own encryption layer.
Mappings
Closest match in ISO/IEC 27001: A.8.20, Networks security, which this control partially meets.
ISO/IEC 27001: 1 mapping
This control partially meets A.8.20.
ISM-1781 requires all data communicated over network infrastructure to be encrypted to protect confidentiality and reduce interception risk. ISO/IEC 27001:2022 Annex A 8.20 requires networks and network devices to be secured, managed and controlled, which typically includes implementing encrypted protocols (e.g. TLS, IPsec, SSH) and secure network configurations. Annex A 8.20 is broader because it covers many network security measures beyond encryption, while ISM-1781 is specifically about encrypting network data in transit.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




