Capability

OT Security testing

OT (operational technology) attacks don’t start on the plant floor. They walk in through IT. Our OT security testing follows that exact path, from IT perimeter breach to OT pivot, so you find the gap before a real attacker does.

THE IT/OT boundary is where most attacks succeed.

OT security testing is an authorised engagement in which the Swarm maps the attack paths between your IT environment and operational systems, testing whether SCADA, DCS, PLC, and Industrial Control System (ICS) environments can be reached and compromised from a realistic attacker position. 

Most attacks on operational technology don’t start in your facility. They start in your IT environment and walk straight through.

Built without attackers in mind.

SCADA systems, PLCs, and distributed control systems were never designed for a connected world. Many run on legacy software, unsupported operating systems, and protocols that assumed isolation, until they’re not. 

telecomms antenna near a fence

Gaps compound quietly.

Annual compliance audits don’t catch a misconfiguration from last week’s maintenance window, a new vendor remote access connection, or an engineer’s workstation that hasn’t been patched in three years.

unsupervised operations box in open technical area

The air gap myth.

The air gap is rarely real. Engineers and vendors use USB drives, laptops, and remote connections to maintain systems. Each one introduces a pathway. The assumed boundary is often a paper wall. 

WE ATTACK THE SYSTEMS YOU TRUST.

Real attackers don’t pick one technique and stop. They find a foothold and pull on everything connected to it. The Swarm works the same way.

Passive network reconnaissance

We map your OT environment before touching anything. Exposed interfaces, architecture, protocol usage, and device behaviour – all visible by observation alone before a single packet is sent. 

IT/OT boundary and segmentation testing

We test whether your OT network is truly isolated or whether the assumed boundary is a paper wall. Firewall configurations, VLAN segmentation, and remote access pathways are all in scope.

IT-to-OT pivot simulation

Starting from assumed compromise within your IT environment, we simulate the full lateral movement journey toward your operational systems.

PLC and engineering workstation access

Device access, logic integrity, and the workstations used to program them. A compromised workstation with vendor software isn’t just a security incident, it’s potential control over your operation.

Default and hardcoded credential exploitation

The credentials shipped with your PLCs and controllers are often never changed. Default and hardcoded credentials in industrial devices are among the most consistently exploitable weaknesses the Swarm encounters.

Protocol and configuration review

We assess the industrial protocol configurations across your environment including Modbus, DNP3, and EtherNet/IP, for authentication controls, encryption gaps, and default credentials.

We know that real attack surfaces don’t come in neat categories. If yours doesn’t fit above, tell us what you’re working with.

What aN OPERATIONAL TECHNOLOGY Finding Looks Like

Finding

Starting from an assumed IT network compromise, CovertSwarm identified crossover points into a fully segregated OT environment. Segmentation was present but inconsistently enforced. The majority of OT management interfaces discovered were unauthenticated.

Impact

We gained full control of both IT and OT networks. Legacy engineer workstations contained stored credentials, operational process notes, and infrastructure references that accelerated movement deeper into the environment.

Remediation

Enforce segmentation between IT and OT networks. Remove unnecessary crossover points between environments. Address legacy endpoints storing sensitive operational context. Tighten credential storage and management. Improve visibility over internal movement and access.

Want the full picture?

The full range of offensive security the Swarm runs: every discipline, how they connect, and what each one tests.

Stories from the Swarm

These stories are real, but the names are deeply redacted. We’ll tell you how we uncovered the threats no one else could see, and why constant cyber attack is the best way to outpace cyber threats.

Frequently asked questions

Is OT Security testing safe for live systems?

Yes, when scoped and executed correctly. Our default posture is passive: we map, observe, and analyse your environment before any active testing begins. Where active testing is agreed, we plan around your operational windows, use test environments where available, and document hard stop conditions before any activity starts.

How is an OT security test scoped?

Scoping begins with a technical conversation to understand your environment: what systems are in scope, what the operational constraints are, what the realistic attacker starting position is, and what techniques are permitted. A formal Rules of Engagement document is agreed and signed before any activity begins. We also identify what is explicitly out of scope. Safety instrumented systems, for example, typically require separate written agreement before active testing. For organisations under IEC 62443, NCSC CAF, or NIS2 obligations, the scoping process also documents how the engagement produces audit-ready evidence for each relevant framework.

How is this different from an annual compliance audit?

An annual compliance audit gives you a snapshot of your security posture on the day the auditor arrived. It does not find the vendor remote access connection that was added last month, the misconfiguration introduced during the last maintenance window, or the flat network segment that has existed quietly for three years. We test the way a real threat actor operates: continuously, persistently, and without waiting for your compliance calendar. 

Will testing affect our operational systems or production?

Not when the engagement is properly scoped. We begin every OT engagement with passive observation – no packets are sent to live systems during the reconnaissance phase. Where active testing is required, it is planned for maintenance windows or non-production environments. The scope of what is and is not in scope for active testing is agreed and documented before we begin. 

How does OT security testing fit into Constant Cyber Attack?

In a point-in-time engagement, OT is tested once within a defined window. Inside Constant Cyber Attack, OT becomes a continuous vector: new vendor connections, configuration changes, and network modifications are tested as they happen, not once a year after they’ve been in place for months. 

What do we receive at the end?

You receive findings in real time via the CovertSwarm Portal as they are discovered, not in a PDF three weeks after the engagement closes. The final deliverable includes an executive summary, technical detail per finding, board-level and technical outcome lines, specific remediation guidance for the teams responsible for implementing it, and access to the Swarm team for validation and retesting. 

Which sectors does CovertSwarm test OT environments in?

We test OT environments across energy and utilities, manufacturing, transport, and industrial facilities. For organisations under IEC 62443, NCSC CAF, or NIS2 obligations, engagement scope and deliverables are aligned to the relevant framework requirements.