OT / ICS / SCADA Security

How Do I Prevent My OT Systems from Being Publicly Accessible?

The answer isn't a better firewall. It's making your industrial systems invisible. Network Cloaking removes OT assets from the internet's attack surface entirely — so attackers can't target what they can't find.
Stop OT Attacks Before They Can Start

100K+

ICS devices exposed on Shodan

91%

of OT breaches start with internet-facing assets

0

BlastShield-protected assets visible to attackers

What is BlastShield?

BlastShield is a zero-trust network access solution that helps organizations implement a zero-trust architecture.

Instead of relying on enhanced identity governance (EIG), complex layers of micro-segmentation, or cloud-based gateways, BlastShield utilizes a software-defined perimeter (SDP) approach for more granular access controls and reduced risk from stolen credentials and complex management.

Start a free trial
The Problem

Your OT Systems Are Visible to Every Attacker on the Internet

Search Shodan.io for "Modbus" or "Siemens S7" and you'll find thousands of live PLCs, HMIs, and RTUs openly accessible on the public internet — including, potentially, yours. This isn't a theoretical risk. CISA has issued repeated advisories about internet-connected PLCs being actively attacked, with attackers disrupting water treatment facilities, energy infrastructure, and manufacturing operations.

Critical exposure fact: Industrial protocols — Modbus, DNP3, BACnet, EtherNet/IP — were designed in the 1970s–1990s for closed networks. They have no built-in authentication, encryption, or access control. Any internet-facing exposure is an open door.

The root cause is architectural: most OT networks were built assuming physical isolation (air-gapping) would provide security. Remote access needs, IT/OT convergence, and cloud connectivity have eroded that isolation — but the security architecture never caught up. The result is industrial devices on routable IP addresses, waiting to be discovered.
What Attackers Do When They Find Your OT Systems
Internet-exposed OT assets don't stay unnoticed. Automated scanners continuously sweep the entire IPv4 address space — roughly every 40 minutes for common industrial ports. Once discovered, attackers:
  • Fingerprint the device type, firmware version, and vendor to identify known CVEs
  • Attempt default credential login (most OT devices ship with documented default passwords)
  • Map the broader network topology through protocol enumeration
  • Sell access to ransomware groups or nation-state operators on dark web markets
  • Stage attacks for later activation — often sitting undetected for months

Most Commonly Exposed OT Protocols and Their Risk

Protocol

Default Port

Used In

Risk if Internet-Exposed

Modbus TCP

502

PLCs, RTUs, meters

Critical — no authentication

DNP3

20000

Utilities, water, grid

Critical — unauthenticated by default

BACnet

47808

Building automation

Critical — no encryption

EtherNet/IP

102

Siemens PLCs

Critical — S7comm has no auth

OPC-DA/UA

135, 4840

SCADA historians

High — often misconfigured

VNC / RDP to HMI

5900, 3389

Human-machine interfaces

Critical — frequent brute-force target

The Operational Payback

How to Prevent OT Systems from Being Publicly Accessible: A Five-Layer Approach

Protecting OT systems from internet exposure requires more than a firewall rule. True protection eliminates discoverability at the architecture level.
1

Implement Network Cloaking (Software Defined Perimeter)

The most effective approach is to make OT assets invisible — not just blocked. A Software Defined Perimeter (SDP) creates a "dark" network where devices do not respond to any unauthenticated traffic. Attackers cannot discover what they cannot probe. This eliminates reconnaissance entirely, not just exploitation. BlastShield implements this via cryptographic single-packet authorization (SPA): an OT asset only "wakes up" to a connection after cryptographic identity is verified.

2

Eliminate All Direct Internet-Facing OT Connectivity

Audit every OT device with a routable IP address. Industrial protocols (Modbus, DNP3, BACnet) must never be directly internet-routable. All remote access must route through an authenticated, encrypted gateway — and that gateway itself should be cloaked, not just hardened. Remove any direct inbound rules from your firewall that expose OT ports to the internet.

3

Replace VPN Gateways with Zero-Trust Remote Access

VPN concentrators are internet-facing by design — they must be reachable to receive connections. This makes them discoverable and a consistent exploit target. Zero Trust Network Access (ZTNA) for OT flips this model: the access gateway is invisible until the user proves identity. No open ports, no discoverable endpoints, no VPN exploits.

4

Continuously Monitor for Unauthorized Exposure

Search your own assets on Shodan, Censys, and FOFA regularly. Any OT device appearing in these searches represents an uncontrolled exposure. Set up automated alerts for your IP ranges and CIDR blocks so new exposures are detected within hours, not months.

5

Enforce Strict Egress Filtering from OT Networks

Attackers who compromise an OT asset will attempt to communicate outbound — for command and control, data exfiltration, and ransomware beacon activity. Default-deny egress policies on OT network segments limit attacker dwell time and prevent OT assets from becoming outbound attack launchers.

The key distinction: A firewall blocks accessafter discovery. Network Cloaking prevents discovery entirely. In a world where attackers scan the entire internet in under an hour, the difference between "blocked" and "invisible" determines whether you're targeted at all.

How to Prevent OT Systems from Being Publicly Accessible: A Five-Layer Approach

BlastShield by BlastWave implements Network Cloaking through a Software Defined Perimeter architecture that has been purpose-built for OT environments. Unlike generic ZTNA solutions designed for IT, BlastShield requires no agents on OT devices, no changes to PLC firmware, and no operational downtime.
How It Works
BlastShield wraps your existing OT network infrastructure with a dark perimeter. OT devices — PLCs, HMIs, RTUs, historians — remain on your network exactly as they are. BlastShield adds a cloaking layer that makes them invisible to all traffic except from authenticated BlastShield users. From the internet, your OT network simply doesn't exist.Authentication uses phishing-resistant MFA with cryptographic device identity — not passwords, not SMS codes that can be intercepted. Even if an attacker has a valid username and password, they cannot initiate a connection to a BlastShield-protected asset without the registered cryptographic identity of an enrolled device.
Zero Changes to OT Device Configuration
OT devices don't run agents. BlastShield is deployed at the network layer, not the endpoint layer. This means legacy PLCs from the 1990s, HMIs running Windows XP, and RTUs with no update capability all receive the same level of protection as modern devices — without any changes to their configuration or firmware.

Frequently Asked Questions

How do I protect my OT systems from being publicly accessible on the internet?

The most effective approach is Network Cloaking — deploying a Software Defined Perimeter that makes your OT assets invisible to unauthorized parties. Unlike firewalls, which block traffic after a system is discovered, cloaking prevents discovery entirely. BlastShield by BlastWave implements this without requiring any agents or configuration changes on OT devices.

Is my OT network really visible on the internet? How do I check?

Search Shodan.io or Censys.io for your organization's IP ranges or known device types. If any industrial devices appear, they are publicly accessible. CISA's "Known Exploited Vulnerabilities" catalog also lists active exploitation of internet-exposed OT protocols. You can also request a BlastWave reconnaissance assessment to see exactly what attackers can find.

What is the difference between a firewall, a VPN, and Network Cloaking for OT?

A firewall is reactive: it receives traffic and decides whether to block it — but the device is already visible. A VPN encrypts traffic but the VPN gateway itself is internet-facing and discoverable (and frequently exploited). Network Cloaking makes the OT asset and its access gateway invisible to unauthenticated traffic — no response, no discoverable endpoint, no attack surface.

How quickly can an attacker find my internet-exposed OT system?

Automated internet scanners (Shodan, Censys, Masscan) sweep the entire IPv4 address space roughly every 40–60 minutes for common OT ports. A new internet-facing OT device can appear in attacker reconnaissance databases within hours of deployment. Time to first unauthorized connection attempt is typically under 24 hours for common OT ports.

Does removing OT internet exposure affect operational continuity?

No. BlastShield's Network Cloaking maintains full connectivity for authorized users while being invisible to unauthorized parties. Engineers, operators, and vendors retain the same remote access they depend on — the difference is that only authenticated users can see or reach the OT asset. Operational continuity is preserved; the attack surface is eliminated.

Related OT Security Problems

Preventing internet exposure is the first line of defense. These related pages address the additional layers of OT security BlastWave protects against:
Legacy Systems

How to Protect Legacy OT Without Downtime

Shield vulnerable systems without requiring patches, firmware updates, or operational downtime.

Ransomware & Lateral Movement

How to Prevent Lateral Movement from IT to OT

Stop attackers and ransomware from moving between corporate and industrial networks.

Credential Security

How to Protect OT Devices from Weak Passwords

Shield vulnerable systems without requiring patches, firmware updates, or operational downtime.

Unknown Devices

How to Protect All OT Devices — Known and Unknown

Extend protection to every device on your network, even those you haven't inventoried.

See How BlastShield Cloaks Your OT Network

Get a live demonstration of Network Cloaking and see exactly what attackers currently find when they scan for your OT systems — and how BlastShield eliminates that exposure.
Learn About Network Cloaking