ASD ISM 0874 Ensure internet access via organisation's gateway
What it says
Mobile devices and desktop computers access the internet via an organisation's internet gateway rather than via a direct connection to the internet.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Mobile devices and desktop computers must reach the internet through an organisation's internet gateway, not a direct connection, wherever they are.
Mobile devices and desktop computers must access the internet via an organisation's internet gateway rather than a direct connection. An internet gateway is the controlled point between the organisation's network and the internet, where security such as web content filtering is applied. This applies wherever the device is, including home and public networks. An organisation can accept the risk of direct connections to named online services, such as web conferencing, for performance reasons, but that remains a gap against this control.
Free. Save your status, tasks and notes.
Why it matters
A device connecting directly misses the security applied at the gateway, such as web content filtering (ISM-0963) and blocking of known malicious domains (ISM-1782), and its web traffic can go unfiltered and unlogged by the organisation. Routing through the gateway brings it under those protections.
How to implement
List how each device type reaches the internet today.
Cover office networks, guest Wi-Fi, home and public Wi-Fi, mobile data and phone hotspots. Include privately owned devices allowed to connect: the statement excludes none, so where you cannot route their traffic, record a gap.
Force office traffic through the gateway.
Block direct outbound traffic at the network edge, so only the gateway and web proxies (ISM-0260) can reach the internet. Use the workstation's software firewall (ISM-1416) and turn off spare network adapters, to close side routes such as a phone hotspot or mobile modem.
Send off-site traffic back through the gateway.
Use an always on VPN, set to block traffic when the tunnel is down, with split tunnelling disabled (ISM-0705). The gateway can be a bought cloud service if its agent carries all internet traffic and applies the organisation's filtering. Devices with a mobile operating system still need the VPN (ISM-2097).
Settle any direct connection service by service.
Where a named service, such as web conferencing, performs poorly through the gateway, try more capacity or a better route first. If direct access stays, record the service, the reason and the risk for the authorising officer as an open gap. Over a VPN, that direct route is split tunnelling (ISM-0705).
Keep it running
Recheck when a new connection type, device type or online service arrives, and after VPN or gateway changes. Watch gateway logs for devices that stop appearing, because silence can mean a device is going direct.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
The device management list of mobile devices and desktop computers, compared with gateway logs for the same period.
Look at
Whether every device shown as online also has traffic in the gateway logs, by device or user.
Good evidence
Every device shown as online during the period has traffic in the gateway logs, with none unaccounted for.
- Check 2 of 3What an auditor asks for
Ask for
A live test on a mobile device and a desktop computer picked from those in use, not prepared beforehand, with mobile devices also tried on home Wi-Fi and a phone hotspot.
Look at
The public IPv4 and IPv6 addresses an external site sees, whether a site the filter blocks stays blocked, and what happens when the VPN or agent is stopped.
Good evidence
The external site sees only the gateway's addresses, the blocked site stays blocked, the attempt appears in the gateway logs, and stopping the tunnel leaves no direct path to the internet.
- Check 3 of 3What an auditor asks for
Ask for
The record of any direct connections to named online services, with the VPN and routing configuration to compare it with.
Look at
Whether the configuration holds any direct route not on the record, and how each recorded one is reported.
Good evidence
The configuration holds no direct route beyond the record, and each recorded one is reported as an open gap with its risk decision, not counted as meeting this control.
Mappings
Closest match in ISO/IEC 27001: A.8.1, User end point devices, which this control partially meets.
ISO/IEC 27001: 4 mappings
This control partially meets A.8.1.
Annex A 8.1 requires organisations to protect information accessible via endpoint devices such as laptops and mobiles. ISM-0874 mandates routing internet access for mobile devices and desktop computers through a VPN to the organisation's internet gateway, which helps protect endpoint traffic and reduces exposure when endpoints are off-network. ISM-0874 is narrower because it focuses on network path/remote access controls rather than the full set of endpoint device protections in Annex A 8.1.
This control partially meets A.8.20.
ISM-0874 requires endpoints to use an organisation-controlled internet gateway for outbound internet access, preventing unmanaged direct internet connections. ISO/IEC 27001:2022 Annex A 8.20 broadly requires networks and network devices to be secured, managed and controlled, which includes controlling egress paths and gateway devices. ISM-0874 is a specific network security design rule that would typically be implemented as part of the broader Annex A 8.20 requirement.
This control partially meets A.8.22.
ISM-0874 requires endpoints to access the internet through a VPN to the organisation's internet gateway, centralising egress and inspection points. Annex A 8.22 focuses on segregating users and services within networks to reduce risk and limit lateral movement. Routing endpoint internet traffic back through the organisation can support implementing and enforcing segregation policies (e.g. separating user subnets from internet egress zones), but segregation can be implemented without mandating VPN-for-internet for all endpoints.
This control supports A.8.23.
ISM-0874 requires all user devices to route internet access through the organisation's gateway instead of direct connections. ISO/IEC 27001:2022 Annex A 8.23 requires managing access to external websites (e.g., web filtering) to reduce exposure to malicious content, which is typically enforced at a central gateway/proxy. ISM-0874 enables consistent application of web filtering and URL controls, but it does not itself require filtering decisions or policy enforcement that Annex A 8.23 focuses on.
ASD Essential Eight: 1 mapping
- E8-RA-ML1.3Prevent privileged user accounts from accessing internet, email and web servicesPartially overlaps
This control partially overlaps E8-RA-ML1.3.
ISM-0874 requires mobile devices and desktop computers to access the internet via a VPN connection to the organisation's internet gateway rather than directly. E8-RA-ML1.3 relates by restricting which accounts (privileged accounts) may access internet/email/web services, reducing exposure from high-risk identities that could otherwise traverse that VPN path. ISM-0874 is about the network path and egress enforcement, while E8-RA-ML1.3 is about account-based access restrictions irrespective of how traffic is routed.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




