A logistics company segments its warehouse and OT network after a ransomware near-miss
A regional logistics company with 4 distribution centers and about 600 staff, a leader in its segment.
- Scale
- 4 distribution centers, ~600 staff, conveyor and sortation controllers, ~60 Windows HMIs, 5 zones per site
- Engagement
- 12 weeks from assessment to cutover, one site at a time
The challenge
Ransomware reached an office file server and was stopped by luck, hours before it could cross into a warehouse where one flat network joined office PCs, scanners, conveyor controllers and the Windows screens that operators use to run them. A shutdown there would have stopped shipping at once. Leadership asked for a design in which one infected laptop could never reach the floor.
A regional logistics company with four distribution centers had a close call. Ransomware reached an office file server and was stopped by luck, hours before it could cross into the warehouses. The client is not named on this page, and this is an illustrative engagement that describes the kind of work our team does; details are composite.
The reason it could have spread was a flat network. Office PCs, handheld scanners, conveyor and sortation controllers, and the Windows screens (human-machine interfaces, or HMIs) that operators use to run the line all shared the same address space. Our team started with a passive inventory, built from switch tables and traffic rather than active scans, because some controllers fail when they are probed. The inventory showed which devices existed, what they talked to and which of those conversations were needed.
The design borrowed the Purdue model, the layered reference that industrial standards such as ISA/IEC 62443 use. The office network sat at the top, a demilitarized zone held shared services, site operations such as the warehouse management system formed the middle, and the supervisory HMIs and controllers sat at the bottom. Each function got its own VLAN, and a firewall zone sat between each pair, set to deny everything except a short list of named flows. A conveyor controller does not need to talk to email, so it no longer can.
The Windows HMIs and servers could not be patched on the office schedule, so they got endpoint detection and response (EDR) software, tuned with the vendor's support team to avoid disrupting a running line. Vendor remote access moved to one jump host with multi-factor authentication, session recording and time-limited approval. Cutover went one site at a time in a low-volume window, with a tested rollback at each step.
The team then replayed the near-miss as a tabletop exercise against the new design: an infected office laptop could no longer reach the floor, and every flow that crossed a zone was logged and had an owner. Operators noticed no change in how the line runs. This is a technical design, not a certification, and the company decides when to extend it to its other sites.
What our team delivered
- A passive inventory of every device on the warehouse and office networks, built from switch tables and traffic, with no scanning of fragile controllers
- A zone design in Purdue-model language: enterprise network at level 4 and 5, a demilitarized zone for shared services, site operations at level 3, and supervisory HMIs and controllers at levels 2 to 0
- VLANs per function, with firewall zones between them and a default-deny policy that allows only listed flows, such as the warehouse management system reaching the sortation supervisor
- Endpoint detection and response on the Windows HMIs and servers, tuned with the vendor's support team so that it did not interrupt a running line
- Remote vendor access moved to a single jump host with multi-factor authentication, session recording and time-limited approval
- A cutover plan done one site at a time in a low-volume window, with a tested rollback, and a tabletop exercise that played the near-miss again against the new design
Result
An infected office laptop can no longer reach the controllers, and the few flows that cross zones are named, logged and owned. Operators noticed no change in how the line runs. Figures here are illustrative; the design is a technical assessment, not a certification.
Get this for your company
Related services with fixed prices and a written scope.
Emergency package: security engineer in 1 hour
Is your company in a cybersecurity crisis? Purchase this package and a security engineer will call you within 1 hour.
Callback within 1 hour, 24 hours a day, 365 days a year
$1,950 per incident
Initial assessment of public endpoints
What an attacker can see and reach from the internet: your domains, mail, websites, remote access and cloud exposure.
Report within 5 business days of kickoff
$1,000 per assessment
Managed IT and security (MSP)
One monthly price per team member: help desk, device management, patching, backup monitoring and security basics.
Onboarding starts within 10 business days
$100 per team member, per month
Show 2 more
Insurance-ready bundle
The three things cyber insurers and clients ask for most: an external assessment, a phishing simulation for 25 users and a disaster recovery plan.
Assessment report in 5 business days; plan draft in 15 business days
$5,400 per bundle, phishing simulation for 25 users
Managed security monitoring
Endpoint detection and response watched by our analysts, priced per device.
Agents deployed within 7 business days
$18 per endpoint, per month
After you purchase, we contact you within 1 hour, any time of day or night, to start onboarding.
No payment is taken online. When we call you within the hour we confirm the scope and send an invoice (ACH, card or crypto).
Purdue levels, zones and conduits
Industrial networks are split into Purdue levels, grouped into IEC 62443 zones, and joined only by controlled conduits. Plant data climbs one way through a data diode into an industrial DMZ; nothing in the enterprise zone has a direct route down to operations or the controllers.
Separate by region and by business unit
Each business unit lives in its own VRF and VLAN in every region, so a problem in retail cannot reach finance. Traffic between units has to pass a firewall that denies by default and allows only what is written down.
Incidents resolved five times faster
Mean time to resolve (MTTR) for incidents, by quarter, for a 250‑seat organisation. The first four quarters are an in-house on-call rota; the last four are under a managed service with a 24/7 operations centre, runbooks and monitoring. Illustrative figures.
Facing something similar?
Tell us about your environment. We will tell you plainly what we would do and what it would take.