Skip to content
Best SASE Solutions

Guide, 12 Nov 2026, read 12/13 Nov 2026

SASE can reach OT and IoT sites, but segmentation and discovery depend on what each vendor ships at the edge

See the rankingAll guides

Why OT sites are not just branches

An OT site has devices that cannot run an agent: PLCs, building controllers, cameras, scanners. Many of them speak protocols that tolerate delay poorly and patch rarely. The site often has one modest link, sometimes cellular or satellite, and change windows measured in months. A SASE design built for laptops does not carry over.

The question is not whether the vendor says IoT and OT somewhere on a page. It is what sits at the site, what it can see, and who can reach what once it is installed.

Regulation adds a layer. Plants in energy, water and manufacturing often have rules on remote access and data location, so ask each vendor where session logs are stored and for how long.

What vendors publish

Each row is the vendor's statement from the pages read on 12 Nov 2026. I did not test any of these.

VendorOT and IoT as publishedWhat sits at the site
Cato NetworksIoT/OT Security is a native feature of the Cato Management Application: device discovery, classification and segmentation (Cato states)Socket or vSocket; Cato states no additional sensors or appliances are required; separate license terms none found on 12 Nov 2026
NetskopeUniversal ZTNA for remote, campus, IoT and OT; Device Intelligence gives visibility and risk scoringLocal Broker extends ZTNA to on-premises and OT environments; Converged Gateway for SD-WAN with built-in 4G/5G
ZscalerZero Trust Exchange described as an integrated platform for users, workloads, IoT/OT and B2B partnersDevice Segmentation sized 200 to 5,000 endpoints; Zero Trust Branch ZT 400, 600, 800, 8010 or VM, 200 Mbps to 10 Gbps
Palo Alto NetworksPrisma SD-WAN with integrated IoT security (vendor claim)Prisma SD-WAN device at the branch; an Enterprise IoT Security item is listed on the page
Open SystemsOT, IoT and CPS security via Nozomi Networks as preferred provider, announced 30 Apr 2026Partner product, not the SASE platform
Check PointAgentless access for unmanaged devices in Private AccessApplies to users on unmanaged devices; OT-specific features none found on 12 Nov 2026

Discovery comes before policy

You cannot write a segment for devices you have not found. Cato states that it discovers and classifies every device with purpose-built AI/ML that maps type, manufacturer and version. Netskope describes Device Intelligence with visibility and risk scoring for IoT and OT. These are all vendor statements. In practice I treat discovery output as a first draft, since inventory from a flat OT network usually surprises its owners.

The useful test is whether discovery runs passively from traffic the edge device already sees, or whether it needs a separate sensor. Cato states no additional sensors are required. Open Systems points to a partner for that function.

Segmentation is the control that works

For OT, the most reliable control is limiting which devices talk to which. Zscaler's Device Segmentation is built for this and is sized by endpoints, which means your quote scales with how many devices you segment, not how many users you have. Cato says it segments devices through the same cloud platform. Palo Alto Networks pairs it with Prisma SD-WAN.

Plan the segments with the plant engineers, not around them. Production teams know which controller must talk to which historian, and security teams do not.

Remote access for engineers and vendors

Maintenance contractors need access into the plant, often from unmanaged laptops. Netskope's Local Broker is described as extending ZTNA to on-premises and OT environments and avoiding cloud hairpinning. Check Point describes agentless access for unmanaged devices with device posture checks. This is where ZTNA earns its place at an OT site: time-limited, per-application access for named people replaces a standing VPN account.

Record every session. If the SASE vendor cannot give you session logs for contractor access, you will need another tool for it.

Plants in remote areas often depend on cellular or satellite. Netskope states its SD-WAN includes built-in 4G/5G with a Zero Trust SIM and 400+ cellular networks. Arista lists satellite among VeloCloud WAN choices. A PoP-based inspection service adds latency to every flow, so check whether the control loop traffic needs to leave the site at all. Keep local control traffic local and send only the management and reporting flows to the cloud.

Questions for the vendor

Ask: which OT protocols are identified, what happens to unknown ones, whether the edge device supports a hardware bypass if it fails, what the device supports for operating temperature and power, and who patches it. If the answer to the last question is you, in an environment with change windows twice a year, that is a design constraint.

Who owns the edge device at a plant

At a branch the network team owns the edge device. At a plant it is often unclear. Operations may refuse any change that touches the production network, and security may refuse to leave a device unmanaged. Settle ownership before the pilot: who can reboot the device, who approves a firmware update, and who gets the alert at night.

Write a bypass rule too. If the edge device or the cloud service fails, what happens to production traffic? Some plants need fail-open for safety reasons and others need fail-closed. That is a plant decision, not a vendor default, and the vendor pages I read do not state which behavior applies. Ask for it in writing.

Sources

  1. Cato Networks, IoT/OT security, read 12 Nov 2026
  2. Netskope, Private Access, read 12 Nov 2026
  3. Netskope, Converged Gateway, read 12 Nov 2026
  4. Zscaler, Zero Trust Exchange, read 12 Nov 2026
  5. Zscaler, pricing page, read 12 Nov 2026
  6. Palo Alto Networks, Prisma SD-WAN, read 12 Nov 2026
  7. Open Systems, press releases, read 12 Nov 2026
  8. Check Point, Private Access, read 12 Nov 2026
  9. Arista, VeloCloud SD-WAN Edge 7x0 datasheet, read 12 Nov 2026

Last reviewed 12 Nov 2026.