What is the recommended network design to minimize risk from IoT devices with internet access?

What is the recommended network design to minimize risk from IoT devices with internet access?

• A. Connect IoT devices directly to the corporate network
• B. Disable Internet access for all IoT devices
• C. Place IoT devices on the main DMZ
• D. Place all IoT devices that have access to the Internet on an isolated network

Answer: (D)

Isolating IoT devices that have internet access on a separate network is the best way to reduce risk. IoT devices are often under-secured, hard to patch, and can be targeted to gain a foothold in your environment. When they’re placed on their own network, even if one device is compromised, the attacker’s ability to move laterally into sensitive corporate resources is greatly limited. This setup acts as a barrier, containing potential breaches within that isolated segment. Even with internet access enabled, you can enforce strict controls at the network edge—firewalls, network ACLs, and gateway protections—to govern what traffic can enter or leave the IoT network. You might allow necessary outbound connections for updates or cloud services, but block unnecessary inbound connections and prevent direct paths to internal systems. This way, you preserve essential functionality while reducing exposure. The other options pose more risk or are less practical. Connecting IoT devices directly to the corporate network creates a direct route into critical assets. Trying to disable internet access entirely for all IoT devices can break functionality and updates some devices require. Placing IoT devices in the main DMZ can expose them to external threats and still leaves a potential bridge to internal networks if misconfigured. Isolating them on a dedicated, restricted network achieves containment and controlled access, which is the safer design choice.

Isolating IoT devices that have internet access on a separate network is the best way to reduce risk. IoT devices are often under-secured, hard to patch, and can be targeted to gain a foothold in your environment. When they’re placed on their own network, even if one device is compromised, the attacker’s ability to move laterally into sensitive corporate resources is greatly limited. This setup acts as a barrier, containing potential breaches within that isolated segment.

Even with internet access enabled, you can enforce strict controls at the network edge—firewalls, network ACLs, and gateway protections—to govern what traffic can enter or leave the IoT network. You might allow necessary outbound connections for updates or cloud services, but block unnecessary inbound connections and prevent direct paths to internal systems. This way, you preserve essential functionality while reducing exposure.

The other options pose more risk or are less practical. Connecting IoT devices directly to the corporate network creates a direct route into critical assets. Trying to disable internet access entirely for all IoT devices can break functionality and updates some devices require. Placing IoT devices in the main DMZ can expose them to external threats and still leaves a potential bridge to internal networks if misconfigured. Isolating them on a dedicated, restricted network achieves containment and controlled access, which is the safer design choice.