ASD ISM 2068 Restrict internet access for networked devices
What it says
Internet connectivity for networked devices is strictly limited to those that require access.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Only networked devices that require internet access may have internet connectivity; every other device on your networks must have none, directly or through a proxy.
Internet connectivity for networked devices must be strictly limited to the devices that require it. Networked devices means anything connected to the organisation's networks, including servers, workstations, network devices, printers, cameras and building or industrial control systems. Strictly means no device has internet connectivity by default: a device, or group of identical devices, gets it only where its function depends on it. Every other device has none, whether directly or through a proxy, in either direction.
Free. Save your status, tasks and notes.
Why it matters
Each device with internet connectivity can be attacked from outside, fetch malicious code or send data out. Printers, cameras and building controllers often need no access and are hard to patch, so removing their connectivity removes that exposure.
How to implement
List every networked device and whether it requires internet access.
Start from the asset inventory and compare it with a network discovery scan, so unlisted devices show up. For each device or group of identical devices, record the function that needs the internet, such as receiving vendor updates or reaching a cloud service it depends on.
Challenge each claimed need.
Ask which function stops working without the internet, and whether an internal source, such as an internal update server, could serve it instead. Where a vendor says its device needs access, get the vendor's answer to both questions in writing. Grant access only where no internal source can do the job.
Deny internet traffic by default at the gateway.
Set inbound and outbound rules to deny, then allow only listed devices, or segments holding only listed devices. Apply the same limit at web proxies and in cloud network rules. Putting devices with no need on segments with no internet route makes this easier to hold.
Close connections that bypass the gateway.
Look for devices with their own mobile data modem, wireless links to outside networks or vendor remote access units, which are common on building, security and industrial systems. Remove each, or route its traffic through the gateway under the same rules.
Keep it running
Update the list of devices that require access when devices are added, replaced or retired, or a vendor changes how a device connects. Set an alert on firewall and proxy logs for any unlisted device reaching the internet.
Evidence and audit
- Check 1 of 4What an auditor asks for
Ask for
The list of devices that require internet access, compared with firewall and proxy logs of devices that reached the internet over a sample period.
Look at
Whether the logs cover all gateway and proxy traffic for the period, and whether any device reached the internet, directly or through a proxy, without being on the list.
Good evidence
The logs cover all gateway and proxy traffic for the period, every device seen reaching the internet is on the list, and no unlisted device appears, directly or through a proxy.
- Check 2 of 4What an auditor asks for
Ask for
Inbound and outbound internet rules on the gateway, web proxies and cloud networks.
Look at
The default action in each direction and the scope of each allow rule.
Good evidence
Internet traffic is denied by default in both directions, and every allow rule names listed devices, or segments holding only listed devices, rather than whole internal address ranges.
- Check 3 of 4What an auditor asks for
Ask for
A connection test from devices not on the list, chosen from a discovery scan and including a printer, a camera or building controller, and a server, each trying to reach an internet address directly, through the proxy and by domain name.
Look at
Whether any attempt succeeds.
Good evidence
Every attempt from an unlisted device fails, by every route tried.
- Check 4 of 4What an auditor asks for
Ask for
The recorded reasons for a sample of listed devices, with each device's logged internet traffic.
Look at
Whether each reason shows the device requires internet access, and whether its traffic matches that reason.
Good evidence
Each sampled device has a reason naming a function that no internal source could serve, and its logged internet traffic fits that function.
Mappings
Closest match in ISO/IEC 27001: A.8.23, Web filtering, which partially overlaps with this control.
ISO/IEC 27001: 3 mappings
This control partially overlaps A.8.23.
ISM-2068 requires organisations to strictly limit internet connectivity to only those networked devices that require access. Annex A 8.23 relates by managing access to external websites through web filtering to reduce exposure to malicious content, controlling internet use once connectivity exists.
This control depends on A.8.21.
ISM-2068 requires organisations to strictly limit internet connectivity to only those networked devices that require access. Annex A 8.21 supports this by requiring security mechanisms and service requirements for network services to be identified, implemented and monitored, which can include enforcing and monitoring internet egress controls.
This control depends on A.8.22.
ISM-2068 requires organisations to strictly limit internet connectivity to only those networked devices that require access. Annex A 8.22 supports this by requiring segregation of groups of information services, users and systems, which enables isolating non-internet-requiring devices onto networks without outbound internet paths. The ISO control provides broader network architecture guidance, while ISM-2068 is focused on restricting internet access.
ASD Essential Eight: 1 mapping
This control partially overlaps E8-RA-ML1.4.
E8-RA-ML1.4 requires that privileged accounts authorised to use online services are limited to only the access required for their duties. ISM-2068 overlaps by limiting which networked devices are allowed internet connectivity, which can indirectly constrain where privileged accounts can access online services from and reduce unnecessary pathways. The primary is identity/authorisation focused for privileged accounts, while ISM-2068 is device/network connectivity scoping irrespective of account privilege.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




