WHITE PAPER

Building a Hidden Network

Why Network Cloaking is the Future of OT Network Protection
Download PDF

The Evolving Threat Landscape in Operational Technology (OT)

Operational Technology (OT) networks, which control and monitor physical processes, face a unique and rapidly escalating array of cyber threats. Understanding the distinct characteristics of these environments and the growing sophistication of adversarial tactics is crucial for developing effective defense strategies.

Unique Characteristics and Vulnerabilities of OT Networks

OT networks are fundamentally distinct from traditional Information Technology (IT) networks, as they manage and control physical processes through specialized protocols and devices. These include Programmable Logic Controllers (PLCs), Human-Machine Interfaces (HMIs), and Supervisory Control and Data Acquisition (SCADA) systems, all engineered for real-time operations and high availability. Even slight delays or disruptions in these systems can have catastrophic consequences.

A paramount difference lies in the core priorities: OT environments prioritize safety and continuous availability above all else, often superseding data confidentiality and security. Operational downtime in these critical infrastructures can result in substantial financial losses, widespread service disruptions, physical injuries, or even loss of life.

This fundamental divergence in priorities creates a significant challenge when attempting to apply IT-centric security solutions to OT. Traditional IT security practices, such as frequent patching and vulnerability scanning, are designed for IT’s priority stack. When directly applied to OT, they often cause unacceptable disruption or fail to integrate with the unique constraints of industrial control systems. This inherent conflict leads to a reluctance to implement security measures that might jeopardize uptime, resulting in delayed updates and a stagnant security posture. Any effective OT security solution must therefore be purpose-built to align with OT’s unique operational constraints and priorities, as retrofitting IT solutions without this fundamental understanding is often destined for failure. A solution that inherently minimizes disruption and simplifies management will achieve far greater adoption and success in OT environments.

A significant challenge stems from the widespread prevalence of legacy OT systems. Many of these assets are decades old, running on outdated operating systems like Windows 7 or XP, and relying on vendor-locked hardware. These systems frequently lack modern security features, are prohibitively difficult or expensive to upgrade, and often no longer receive vendor support. Crucially, these older systems often cannot be patched or updated without incurring significant operational downtime, rendering them perpetually vulnerable to known and unknown exploits.

This pervasive presence of decades-old, unpatchable, and unsupported legacy systems means these systems are not just temporarily unpatched; they often cannot be patched at all due to their age, proprietary nature, or lack of vendor support. This directly gives rise to “forever-day” vulnerabilities, meaning these security flaws will persist indefinitely. The long operational lifecycle of OT equipment ensures that these vulnerabilities remain a permanent, unmitigated attack surface. Consequently, traditional security models that rely heavily on regular patching are inherently insufficient for a significant portion of the OT landscape

A truly robust OT security solution must provide a compensatory control, effectively acting as a “virtual patch,” to shield these vulnerable systems without requiring direct modification or operational downtime

The Growing Sophistication of Cyber Threats

The increasing convergence of IT and OT networks, driven by advancements in AI and the Internet of Things (IoT), has blurred boundaries between these two domains. While offering efficiency benefits, this convergence simultaneously eliminates the historical “air gap” that once protected OT, exposing industrial systems to IT vulnerabilities and direct internet connectivity, significantly expanding the overall attack surface. This integration, while beneficial for efficiency and enhanced analytics, simultaneously dismantles the traditional “air gap” that historically safeguarded OT systems, exposing them to IT vulnerabilities and the internet, creating a significantly expanded and inherently more complex attack surface.

The benefits of convergence come with a steep increase in risk if not managed with a fundamentally different security approach. Security solutions for converged IT/OT environments cannot simply be IT solutions extended to OT; they must be purpose-built to handle the unique sensitivities of OT while securing the new IT/OT interfaces, specifically addressing lateral movement and initial access vectors that exploit this convergence.

A staggering statistic reveals that over 70% of successful breaches now leverage lateral movement techniques, including ransomware, malware propagation, credential harvesting, remote services exploitation, and “living off the land” tactics. Attackers, once inside the perimeter, move laterally to escalate privileges, access sensitive data, and deploy payloads, often remaining undetected for extended periods, averaging 95 days. This high percentage of breaches involving lateral movement indicates that traditional perimeter defenses are insufficient. The “inside is trusted” model is broken, necessitating a shift to internal segmentation and continuous verification.

Artificial Intelligence (AI) is rapidly transforming the threat landscape. Attackers are increasingly employing AI for automated reconnaissance, enabling them to swiftly scan networks, identify open ports and services, collect open-source intelligence (OSINT), analyze misconfigurations, and meticulously map out infrastructure. This reconnaissance dramatically accelerates what was previously a time-consuming manual process, making critical infrastructure vulnerable to AI algorithms that can quickly identify and exploit weaknesses. This evolution of attack capabilities renders traditional perimeter defenses, which often rely on detecting known threats or acting after reconnaissance has occurred, increasingly insufficient. A proactive defense that prevents reconnaissance altogether, effectively “blinding” the attacker, becomes paramount, shifting the strategy from a reactive detection-and-response model to a proactive prevention model at the earliest possible stage of the cyber kill chain.

A proactive defense that prevents reconnaissance altogether,effectively “blinding” the attacker, becomes paramount.

Reconnaissance is the crucial preliminary phase of any cyberattack, where attackers gather vital information about a target system’s vulnerabilities. Therefore, breaking the MITRE ATT&CK chain at its earliest stages, specifically the Discovery phase (Tactic TA0102), is paramount for effective OT defense. The strategic importance of this early disruption cannot be overstated. In OT, where downtime and physical impact are critical, preventing an attack from even starting (by denying reconnaissance) is far more valuable than detecting it during the mid-attack phase. This shift in the defense paradigm from containment to preemption provides a significant strategic advantage.

A New Paradigm: Network Cloaking for OT Security

Network Cloaking delivers the first security architecture that can provide AI-resistant solutions for OT.

In Plain Terms

Cloaking software creates a “secure virtual network overlay” that runs on top of your existing OT network. It makes devices completely invisible unless the user is pre-approved. Here’s how it functions:

1. Secure Overlay Network

2. No Device Exposure by Default

3. Access Requires Mutual Authentication

4. Built-in Microsegmentation

5. Encrypted Point-to-Point Communication

Where It Is Installed?

Cloaking software is not installed on OT devices. Instead, it runs on trusted systems such as:

No Network Rebuild Needed

Cloaking is a software overlay — not a replacement for your existing network.

What Happens to Unauthorized Traffic?

If a user or device isn’t authenticated:

Scalability and Simplicity

Cloaking is designed for large, distributed OT environments:

Zero Trust (ZT) is a set of cybersecurity concepts and approaches that move defenses from network-centric, perimeter-based security (e.g. “castle and moat”) to a model where the trust of users, assets, and resources is not implied.

In today’s ubiquitous enterprise perimeter-based security models, users are provided access to assets and resources based on their location and network connectivity. For example, employees connecting to a corporate network at their physical office may have broad access to devices such as servers, printers, and workstations across the network. In this perimeter-centric model, access to applications and data is controlled by managing a complex system of configurations and policies that include network subnetting, firewall access control lists (ACLs), authentication, virtual private networks (VPNs), digital certificates, identity management, and privileged access management (PAM). User permissions differ based on whether they are inside or outside the perimeter.

While the concepts of Zero Trust have been around for a long time, John Kindervag of Forrester is credited with coining the term. (ZT) was born out of necessity with the movement of resources and users outside of the traditional enterprise perimeter. Assets and data have moved from private data centers to cloud applications, such as Amazon Web Services, Microsoft Azure, Google Cloud Platform, Salesforce.com, ServiceNow, Hubspot, Workday, Monday, Asana, SAP Cloud, Oracle Cloud, and thousands of other SaaS applications. Users, including employees and contractors, are now spending more time working remotely than from the office. Finally, the explosion of the Internet of things (IoT) has added billions of new devices connected to the network that may connect to industrial operational technology (OT) systems and private and public cloud applications.

In 2020, the United States National Institute of Standards and Technology (NIST) published “NIST SP 800-207: Zero Trust Architecture.” A ZT approach focuses on protecting all enterprise assets (devices, infrastructure components, applications, virtual, and cloud components) and subjects (end users, applications, and other non-human entities that request information from resources).

A Definition of Zero Trust and Zero Trust Architecture:

Zero trust (ZT) provides a collection of concepts and ideas designed to minimize uncertainty in enforcing accurate, least privilege per-request access decisions in information systems and services in the face of a network viewed as compromised.

Zero trust architecture (ZTA) is an enterprise’s cybersecurity plan that utilizes zero trust concepts and encompasses component relationships, workflow planning, and access policies. Therefore, a zero trust enterprise is the network infrastructure (physical and virtual) and operational policies that are in place for an enterprise as a product of a zero trust architecture plan.

Zero Trust Architecture Deployment Models

To understand zero trust, it is helpful to understand the components of zero trust architecture according to NIST SP 800-207.

While IT focuses on information security, OT prioritizes operational continuity and safety. Because when OT networks stop, the world stops.

Technical Specifications

The BlastShield ZTNA solution is an advanced implementation of a software-defined perimeter (SDP). Here is a summary of the technical specifications of the solution.

Table 1: BlastShield Technical Specifications

Technical Specification

Description

BlastShield Supported Operating Systems (as of November 3, 2022)

Client:

MacOS 10.13 or later; Windows 10 or later; most modern Linux distributions running on either a 64- bit Intel CPU or 32-bit or 64-bit ARM CPU; iOS version 13 or later; Android version 7 or later

Authenticator:

iOS 13 or later; Android 7 or later

Host Agent:

Ubuntu

18.04.6 LTS, 20.04.4 LTS, 20.04.5 LTS, 22.04 LTS, and 22.04.1 LTS; Debian 10 (Buster) and 11 (Bullseye); CentOS 7 and 8; Amazon Linux 2; Raspbian GNU/Linux 10 (Buster); Fedora 35 and 36; Windows Server 2012, 2016, 2019, 10; MacOS 10.13 or later; 64-bit

Gateway Agent:

x86 and 32/64-bit Arm CPUs are supported

BlastShield Storage and Memory Requirements

Client:

100 MB storage, 50 MB RAM 6 MB

Authenticator:

6 MB

Host Agent:

3 MB (Linux) to 100 MB (Windows), 50 MB

Gateway Agent:

2 GB storage, 1 GB RAM

Cryptographic Engine

WolfSSL WolfCrypt (FIPS 140-2 FIPS-ready)

Supported Algorithms

Symmetric (encryption): AES-256-GCM stream encryption. ECDHE and HKDF for key negotiation Asymmetric (authentication): ECDSA with the NIST-approved curve curve P-256, ECDHE, HKDF

Supported Phishing Resistant MFA Approaches

  1. Passwordless authentication using the BlastShield Authenticator Mobile App with a biometric
  2. FIDO2 security key with a passcode

NAT Traversal Scheme

UDP hole-punch

Topology Supported

Peer-to-peer full-mesh

NAT Traversal Scheme

  • User to application
  • User to machine
  • Machine to machine (site-to-site)
  • Machine to user
  • Machine to application
  • User to user
  • User to cloud application (BlastShield SaaS Proxy)

Performance (Max Throughput)

Client-to-application:

  • 1,060 Mbps (1 client)
  • 2,040 Mbps (2 clients)
  • 2,521 Mbps (3 clients)

Site-to-Site:

  • 2,670 Mbps

Device Invisibility Enablement

Delete inbound security groups on devices installed with BlastShield agents. Public IP addresses will not be visible to the public Internet and therefore not scannable.

Orchestration and Management

The BlastShield Orchestrator is used to create, modify, and remove all Users, Agents, and Policies within the BlastShield Network. Only users with authorized privileges can access and use the Orchestrator. As discussed earlier in this document, the Orchestrator acts as a ZTA policy engine (PE) and policy administrator (PA). Rather than configuring subnets, ACLs, and VPNs, BlastShield makes it easy to set up granular access by creating and managing Users, Agents, Groups, Policies, and Proxies.

Step 1: Add a New Agent in the Orchestrator

  • Click on “Agents” in the “Manage” menu in the left sidebar, then click the red “Add New Agent” button at the top right.
  • The New Agent dialogue opens. Add a name for the Agent and a DNS Hostname. The DNS Hostname is optional and can be used to identify the Agent in the BlastShield network as BlastShield runs its own DNS.
  • Then click on the red “Save and Download Invitation” button and choose the option for “Save and copy Linux/macOS installation command to the clipboard”. Click on that option to copy the command.

Step 2: Install and register the agent

  • Open a terminal session on the Linux server where you are going to install the Agent
  • Paste the command you just copied to the terminal and hit enter. This will start the software download. The software will automatically install and run.
  • The Agent will then automatically register with the Orchestrator. When the process is complete, you will see the following message in the terminal window: “Installation successful, the agent IP address is <Agent IP address>.”

Step 3: View the status of the Agent

  • Now that the installation and registration processes are complete, your Agent is up and running.
  • You can check the status of the Agent by typing the following: sudo systemctl status blastshield
  • The logs may be viewed as follows: a. sudo journalctl -u blastshield. service
  • The status of the new Agent on your server should appear as “Online” in the Orchestrator as shown in the image below

For more detailed instructions on implementation for Linux, Windows and MacOS, visit support.blastwave.com.

BlastWave also provides professional services and phone support.

BlastShield Licensing and Pricing

BlastWave licenses the use of its downloadable BlastShield software and access to its cloudbased Orchestrator on a per agent basis. Pricing is based on the number and type of devices protected by BlastShield, represented by the number of installed Active Clients, Agents, and Gateways. BlastWave charges an annual licensing fee for each device depending upon the type of agent installed.

Our licensing includes access to features such as ZTNA, phishing-resistant MFA, single sign-on (SSO) support, microsegmentation, cloud orchestration, gateways, REST API, and optional on-prem orchestration.

Conclusion and Recommendations

Industry trends and Federal Government mandates are driving adoption of zero trust architectures (ZTA). Federal agencies, enterprises, and industrial companies would be wise to learn more about zero trust concepts and develop strategies to migrate to a ZTA. Recognizing the importance of improving cybersecurity controls, the U.S. has directed many security-related agencies to facilitate sweeping changes in the way they manage cybersecurity. The U.S. Office of Management and Budget issued a memorandum that set a deadline of FY 2024 for agencies to comply with sweeping new cybersecurity guidelines based on the NIST SP 800-207: Zero Trust Architecture and CISA Zero Trust Security Model Guidance.

BlastWave’s BlastShield Zero-Trust Network Access (ZTNA) solution can help organizations accelerate the migration to ZTA. BlastShield uses a software-defined perimeter (SDP) approach to ZTA that combines phishing resistant MFA, simple orchestration, granular access controls, peer-to-peer full-mesh networking, and device invisibility to provide a level of security that goes beyond zero trust standards. BlastWave radically simplifies the security stack and enables zero trust without sacrificing performance or cost.

Download the White Paper!

Learn how to implement BlastShield to comply with Zero Trust architecture requirements.

Our Privacy Policy applies.