Data in transit is encrypted with an approved cryptographic standard, at minimum TLS 1.3, and an approved algorithm, per the ACSC guidelines for using cryptography and Annex A of ACSC Implementing Certificates, TLS and HTTPS. The ATO stopped accepting TLS 1.2 on inbound channels (SBR and the ATO API Portal) from 31 January 2026, because ASD no longer treats TLS 1.2 as an approved protocol (ISM-0481). Cloud products give their domain name and either the back-end TLS configuration (for example a load balancer) or an SSL Labs report; indirectly connecting products give an SSP licensing agreement, SSP portal screenshots or an API call screenshot showing the protocol; desktop products connecting directly to the ATO need not provide evidence. v6.0 and v6.05 accepted TLS 1.2.
This control maps to 3 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 3 it maps to, and the evidence behind each claim, over MCP and REST.