Fleet-wide OT cybersecurity is a different problem at sea than on land. Vessels run overlapping IP ranges by vendor design, connectivity drops in and out with the satellite link, and crews aren’t cybersecurity experts. This case study shows how a leading European dredging operator secured its entire fleet against IACS UR E26/E27 requirements — without reconfiguring a single network.
The operator needed to meet IACS maritime cybersecurity requirements and secure onboard OT systems against rising threats, but four realities stood in the way. Vendor restrictions meant multiple vessel systems shared identical subnet ranges, ruling out standardized IP addressing. Vessels operated with intermittent, low-bandwidth satellite connections, so any solution had to work offline. Onboard crews needed simple, clear alerts — not a SOC analyst’s dashboard. And with vessels scattered across the globe, the operator had no centralized way to see fleet-wide risk.
Radiflow deployed its full OT security portfolio, purpose-built for maritime constraints:
Onboard, traffic flows from the vessel OT layer through the vSAP smart collector to iSID for threat detection, then syncs over an encrypted satellite link to iCEN and CIARA on shore — autonomous when offline, synchronized when connected.
The result: full fleet OT visibility and compliance, continuous protection whether vessels are docked or in remote waters, and faster, simpler crew response when it matters.
Why the Same Vulnerability Creates Different Risk in Different Plants
Belden and Radiflow Partner to Close the Gap Between OT Threat Detection and Network Response
BaseRock partners with Radiflow to add OT risk assessment and continuous monitoring to its IEC 62443 advisory services