Port Terminal Operator Keeps Gate, Yard and Berth Systems Accountable With Ollandi
Summary
A container terminal operator deployed Ollandi to understand how failures across its terminal operating system, gate automation, network and vendor access affect operations. Disruptions are now traced to their cause while queues are still forming, and vendor access is reviewed against contract scope.
Before Ollandi
- Gate slowdowns could originate in the terminal operating system, the network, an expired certificate or a vendor update. Diagnosis took hours.
- Trucks queued while teams established which system was at fault.
- Several equipment vendors held remote access that had never been reviewed as a whole.
After Ollandi
- Each degraded component is reported in operational terms: affected gate lanes, berths or yard blocks.
- Cases are routed to the owning team or vendor with evidence attached.
- Every vendor remote access path is mapped, including what it can reach and when it is used.
- Access outside agreed windows or contract scope is raised for security review.
Deployment
- Product: Ollandi, modelling terminal IT and operational systems as one environment.
- Operating control: Observe & Notify. Ollandi does not issue commands to terminal or equipment systems.
- All operational decisions remain with the terminal control room and security leadership.
By the numbers
Measured across Glemad's production deployments and published in the ADT research paper:
- Threat coverage: 40 to 60% more multi-step attack chains identified than siloed detection tools.
- False positive rate: 1.2%, against an industry average of 23.5%.
These figures come from environments with mature telemetry and defined policy baselines. Results depend on the quality of the telemetry available.
