Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Written by Bill Moore, CEO & Founder TL;DR In Part 1 of this series, I looked at how computing and telecommunications gradually became what we now call Enterprise IT. That change did not happen because someone decided to merge two departments. It happened because the technologies, the systems, and the work they supported became too interconnected to describe separately.

There was a time when “Information Technology” wasn’t a department, an industry, or even a common business term. In the 1970s and 1980s, computing and telecommunications were largely separate disciplines. Computers processed information. Telecommunications moved information. Most systems operated independently, often serving specific departments or business functions. Then those worlds began to converge. Organizations started connecting computers through networks.

Every defense contractor preparing for CMMC has the same expensive surprise: the third-party engineering firm with VPN access into one file server just doubled the size of their assessment. CMMC, the Cybersecurity Maturity Model Certification that DoD will require on covered solicitations starting November 10, 2026, is scored against the systems that touch Controlled Unclassified Information, or CUI.

COMMENTARY: When the United States and Israel launched coordinated strikes against Iran on February 28, the security community mobilized around the visible response. I’ve watched that response for two weeks: teams tracking hacktivist DDoS campaigns, incident counts climbing, news coverage following close behind.

Remote access into OT and ICS environments has always carried risk. But the nature of that risk has changed. Threat detections now happen in seconds. Sensors identify anomalous behavior in real time. Identity platforms continuously evaluate trust. SIEM and OT security tools generate rich, contextual alerts instantly. Yet in most environments, access enforcement is still manual. A detection triggers a ticket. A human reviews. A decision is made. Minutes—or hours—pass before action is taken.

TL;DR Xona Platform v5.5 strengthens remote access across distributed OT environments. It introduces session resilience to maintain continuity during network interruptions, expands centralized governance for more consistent access control, and enhances support for constrained or disconnected deployments. In critical infrastructure environments, remote access is not abstract. It supports maintenance windows, emergency response, vendor coordination, and day-to-day operations across distributed sites.

Secure remote access (SRA) is no longer a stopgap or an IT workaround; it’s become foundational to industrial cybersecurity. According to KuppingerCole, demand for SRA in OT and ICS environments is accelerating due to the convergence of IT and OT networks, rising cyber threats, and mounting regulatory pressure. Traditionally, remote access in industrial environments was limited, heavily manual, and often avoided due to risk.

Security incidents and service disruptions are never simple. They are rarely the result of a single mistake, and they don’t only happen to organizations that “did something wrong.” In reality, many of the most capable, well-resourced companies experience them precisely because they operate at scale, under constant pressure, and within complex, interconnected environments.

Remote access has become essential. However, for most industrial organizations, it’s also become the most dangerous blind spot in their cybersecurity posture. The tools many teams still rely on VPNs, jump servers, and shared logins that were never built for today’s OT and IT environments. These legacy systems were designed decades ago, when connectivity was simpler and threats were fewer.

Remote access isn’t optional in critical infrastructure anymore; it’s operationally essential. Whether for maintenance, OEM support, remote field work, or incident response, industrial organizations must enable access to critical systems. But, legacy access methods like VPNs, jump servers, and even agent-based Zero Trust or IT-based remote privileged access management (RPAM) tools all share one dangerous flaw: they implicitly trust the endpoint.