How does Zero Trust Architecture handle unmanaged IoT devices in a corporate office environment?

All answers to this question.

For IoT, Zero Trust relies heavily on "Device Profiling" and "Behavioral Analytics." Since you can't put an agent on a printer, you use your network access control (NAC) system to identify the device fingerprint. Once identified, you place that device in a restricted "IoT VLAN" with an explicit micro-perimeter. The "continuous verification" part comes from monitoring its traffic patterns. If your smart thermostat suddenly starts trying to SSH into your SQL server, the AI-driven security engine should automatically quarantine that port. You aren't trusting the device; you are trusting the behavioral profile you've established for that specific device type.

   Answered 2024-08-25 by Susan Walker

Does your current network infrastructure support MUD (Manufacturer Usage Description) files to automatically define what these devices should be allowed to do?

   Answered 2024-08-27 by Robert Wilson

• Our newer switches do support MUD, but we haven't implemented it yet. It seems like a lot of manual configuration for each vendor. Is there a centralized database for these profiles, or do we have to write a custom policy for every single smart device we bring into the building? We're looking for as much automation as possible here.

     Commented 2024-08-29 by James Taylor

The best Zero Trust move for IoT is "Dark Cloud" isolation. If the devices can't see the rest of the network, they can't be used as a pivot point for an attack.

   Answered 2024-08-31 by Barbara Martinez

• Exactly, Barbara. Total isolation via a "Deny-All" internal gateway is the only real way to sleep at night when you have 500 unpatchable sensors on the floor.

     Commented 2024-09-01 by Christopher Moore