Skip to content

The system releases the container, not a person

Security of intermodal terminal and logistics facility systems

What physically leaves the terminal is decided by a record in the system. Who can change that record, and whether it will be noticed, is a question about cargo security, not about office convenience. We provide independent supervision of the facility's logical layer, during construction, expansion and live operation.

Who this is for

For operators of intermodal and handling terminals and of large logistics facilities: when building a new terminal, when expanding or modernising an existing one, and for a facility already in operation whose logical layer has never been examined as a whole. Poland has more than forty intermodal terminals in operation, with a further eleven under construction or modernisation within EU-funded projects. This is a generation of facilities whose control and integration layer is being created right now.

A terminal is a storage yard run by a database

At a terminal, everything of value happens twice: once physically and once in the system. The container sits in the yard, but it is released by a record in the terminal operating system. The crane lifts the steel, but the system tells the operator which container it is and where it goes.

Terminal or warehouse management system

TOS or WMS: pre-advice, statuses, release codes, settlements, storage.

Entry gate

Automatic vehicle and container identification (OCR, ANPR), barriers, road and rail weighbridges, driver kiosks.

Handling equipment

Cranes, reachstackers and carriers, together with on-board terminals and the radio network serving the yard.

Facility security systems

CCTV, access control, perimeter protection, fire systems.

External integrations

EDI and API links with customers, forwarders, rail carriers, shipping lines, customs agencies and customs systems.

Remote access channels

The operator's VPN gateway, the TOS integrator's service channel, the handling equipment and gate automation vendors' channels, the maintenance provider's access.

Office environment

Mail, file storage, HR, accounting, settlement and invoicing systems.

Every contractor is responsible for their own system, but nobody is responsible for how those systems look together — or for what can be done by reaching them from outside.

Six cases worth knowing

Logistics adds a motive absent elsewhere: terminal systems are sometimes targeted by organised crime that does not want to destroy them, but to quietly change a single record inside them.

Antwerp, 2011 to 2013

When the goal is not destruction but one record

A smuggling network gained access to the systems of terminal companies in the port of Antwerp in order to intercept container release codes and collect, with their own transport, containers belonging to unsuspecting customers before the rightful consignee arrived. Entry came in two stages: it began with malware sent to employees, and when the intrusion was detected and the network protected with a firewall, the perpetrators switched to physical means — installing keyloggers on keyboards and their own devices hidden in disk enclosures and power strips. In June 2013 police searched more than twenty locations and detained fifteen people, including two IT specialists. Here nobody halts the terminal or demands a ransom. The facility operates normally, and the only trace is a container released on a valid code to the wrong person.

DP World Australia, November 2023

Three days and thirty thousand containers

On 10 November 2023 the operator disconnected four container terminals — in Melbourne, Sydney, Brisbane and Fremantle — from the internet to halt an ongoing attack. The terminals stopped releasing and receiving cargo, and around thirty thousand containers were stranded in the yards. The operator handles close to 40 percent of Australia's freight movements. On resuming work on 13 November, the expectation was to move around five thousand containers, less than a quarter of normal daily volume. This is the right measure of risk for a terminal: not the cost of restoring the system, but the cost of the queue forming at the gate and spreading through the whole chain.

Maersk and NotPetya, June 2017

And the question of whether manual working is possible

On 27 June 2017 malware spread through an infected update to accounting software and paralysed a global carrier along with its terminal company. Disruption affected terminals on several continents, including Rotterdam, Los Angeles, New York, Barcelona, Algeciras and Mumbai. The company valued the impact at 200 to 300 million dollars. Recovery involved reinstalling around 45 thousand computers, 4 thousand servers and 2.5 thousand applications, completed in ten days rather than the estimated six months. Through that period the company handled around 80 percent of normal volume, working manually.

Nagoya and Expeditors

Two invoices for the same kind of downtime

On 4 July 2023 a ransomware attack halted Japan's largest container terminal in the port of Nagoya. Loading and unloading stopped, and the terminal resumed work on the afternoon of 6 July, after roughly two days. The effect passed immediately to an automotive manufacturer, which suspended its export component packing line. In February 2022 the global forwarder Expeditors International shut down most systems after an attack and operated in reduced mode for close to three weeks. The company valued the event at around 60 million dollars, of which 40 million was lost freight capacity and cargo detention charges, and 20 million the cost of investigation and environment recovery. Restoring the IT is the smaller part of the loss. The larger part is what did not move in the meantime.

Blue Yonder and Kojima

You are a link in someone else's chain

On 21 November 2024 an attack struck a supply chain management software vendor. The vendor itself runs no warehouse, but its customers do: retail chains lost the management system for fresh food warehousing, and a restaurant chain lost its staff scheduling system. In February 2022 an attack on a single parts supplier, Kojima Industries, halted fourteen Toyota plants and twenty-eight production lines for a day — Toyota itself was not attacked. The lesson runs both ways: an incident at your system vendor, service company or connectivity provider reaches your facility, and you stand in exactly the same relation to your own customers.

Handling equipment and the vendor channel

A risk that requires no attacker

In February 2022 an attack on a European terminal group affected its facilities in Belgium, the Netherlands and Germany, among them a terminal in the Northern Port of Gdańsk. The terminal kept working, but the event shows that belonging to an international group also means a shared attack surface. A separate thread concerns the equipment itself: the United States Coast Guard issued warnings in 2023 and December 2024 regarding Chinese-built ship-to-shore cranes, and congressional committees concluded an inquiry into the matter in March 2024. Among the findings was the presence in cranes of cellular modems that port operators had not ordered and that were not needed for the equipment to work. To be fair: what was described was risk and unexplained connectivity, not a confirmed attack.

All the events cited come from publicly available sources: CERT Polska (NASK) reports, company statements and annual reports, regulatory decisions, security researchers' publications and press coverage. This material is informational and does not constitute legal advice.

How a terminal differs from other facilities

A terminal's risk profile is unlike most industries, and not because of scale, but because of what exactly a record in the system does.

A record in the system has material effect

In most industries, compromising data means an information leak. Here it means releasing goods. This is the only IT layer in which changing one field transfers ownership of a physical thing.

The criminal motive is not ransom

Smuggling networks do not want the terminal stopped; they want it running quietly and releasing one container. No backup protects against that — separation of duties and an event log somebody actually reads do.

Zero tolerance of downtime, with an external meter running

Downtime is priced by somebody else: demurrage and detention from carriers, contractual penalties from customers, rail slots that cannot be recovered.

You are the link whose absence others feel

The consequences of an incident fall on customers and carriers, not only on the operator — and they increasingly ask about your controls before signing.

Long-lived equipment, short-lived support

A crane runs for twenty-five years and more. Its controller and the computer managing it have vendor support measured in years.

Many external parties with equal standing

Drivers, forwarders, customs agencies, rail carriers, authorities and service companies all operate on site and in the system at once. Each needs access and each is a separate decision.

The formal dimension of records

Where a facility operates under customs procedures or as an approved place, the integrity and accountability of data stops being a matter of good order and becomes a matter of compliance.

What exactly we verify

For each area we agree with the investor or operator what precisely counts as "verified", so that the scope is unambiguous for all parties.

Remote access and edge devices

What we verify

What is visible from the internet and why; restriction of connection sources, a second authentication factor without exceptions, software currency of the firewall and VPN concentrator.

Risk if skipped

The shortest path into the facility — precisely the one used on 29 December 2025.

Network segmentation

What we verify

Whether the operational layer, gate automation, CCTV, yard radio network, office network and guest networks are genuinely separated rather than merely described in the design.

Risk if skipped

Access to a camera or a driver kiosk grants access to the system managing cargo.

Terminal or warehouse management system

What we verify

Separation of privileges and roles, how release codes are issued and passed on, who can change cargo status and approve their own change, named accounts, integrator access.

Risk if skipped

Release of cargo to an unauthorised party with no trace of a break-in — the Antwerp scenario.

Event logging and review

What we verify

Whether status changes, releases and corrections are recorded immutably, whether logs are collected outside the source system, and whether anyone genuinely looks at them.

Risk if skipped

Manipulation of cargo data goes undetected, and afterwards the sequence of events cannot be established.

Gate, OCR, ANPR, weighbridges and driver kiosks

What we verify

Configuration and currency of controllers and readers, integration with the terminal system, the possibility of substituting a reading or bypassing a check, supplier service access.

Risk if skipped

Substituting a vehicle, a false reading, or bypassing entry and exit control.

Handling equipment and the yard radio network

What we verify

Security of the wireless network serving the yard, configuration of on-board terminals, crane controllers and industrial computers, and their separation from the rest of the network.

Risk if skipped

Entry into the operational layer from within the site, without defeating external protections.

Vendor and integrator channels

What we verify

The scope and manner of device connections to supplier systems, presence of undocumented external connectivity (cloud, modem, dongle), the ability to change settings remotely and its limitation in the contract.

Risk if skipped

An uncontrolled channel bypassing the facility's protections, as in the ship-to-shore crane warnings.

External integrations: EDI, API, customers, rail, customs

What we verify

Who connects to whom, with which credentials, in which direction, how keys are protected, and whether those connections are separated from the facility's other systems.

Risk if skipped

Using the terminal as a way into a partner's systems, or the reverse.

Accounts, passwords and third party access

What we verify

Elimination of factory credentials, named accounts, role-appropriate privileges, credential rotation after every change of contractor or employee, no shared passwords between facilities.

Risk if skipped

The single most common cause of incidents across the industry.

CCTV, access control and perimeter protection

What we verify

Access to recordings and controllers, accounts and passwords, currency of recorders and cameras, isolation from other systems, linkage with entry records.

Risk if skipped

External viewing of the facility, interference with the event record, and loss of evidence.

Endpoint and server protection

What we verify

The presence and actual operation of modern protection that detects destructive activity, not merely classic antivirus.

Risk if skipped

Nothing to stop an attack while it is running.

Backups and recoverability

What we verify

Not only whether backups of the terminal system, databases and device configurations are taken, but whether they can be restored and whether they survive a ransomware attack.

Risk if skipped

No way back; rebuilding from zero with the integrator involved and waiting for parts.

Manual operation without systems

What we verify

Whether a documented and rehearsed procedure exists for handling traffic when the system is unavailable: yard printouts, fallback records, a release mode, and how data is reconciled afterwards.

Risk if skipped

The shift stands idle instead of working — and this item determines the real cost of downtime.

Software currency and equipment life cycle

What we verify

The state of software at acceptance, the update plan for coming years, and the vendor support horizon against the long life of handling equipment.

Risk if skipped

A facility commissioned with vulnerabilities publicly known for years and no plan for the years ahead.

Documentation and procedures

What we verify

Whether a current description of what is connected and how exists, along with an incident response procedure including mandatory notification and informing customers.

Risk if skipped

Reacting by trial and error at the worst possible moment.

How we structure the engagement

We agree the commercial terms up front — a fixed fee per stage or per facility, or a monthly engagement for the duration of delivery. In every variant, support with implementing our recommendations is included in the agreed fee.

Full supervision, from design to commissioning

When it makes sense

A new terminal or major expansion at design stage or in early delivery

What it covers

All five stages of Track A, support with implementing recommendations, retest and handover of documentation

Supervision from systems commissioning

When it makes sense

Construction well advanced, the terminal system and automation only now arriving on site

What it covers

Stages 3 to 5: ongoing configuration control, pre-commissioning testing, report and retest

Review of an operating facility

When it makes sense

The terminal is handling traffic and the state of the logical layer, and of who holds access, is not fully known

What it covers

Inventory, condition assessment, remediation plan matched to outage windows, and verification of completion

Network variant

When it makes sense

Several facilities run by one operator to a similar template

What it covers

Detailed examination of the first facility, a checklist for the remainder, a common standard across the network

Frequently asked questions

Intermodal terminals — the questions operators ask.

At a terminal everything of value happens twice: once physically and once in the system. The container sits in the yard, but it is released by the pre-advice, the release code, the customs status and the gate exit approval — records in the terminal operating system. Whoever can change that record effectively controls the cargo, without ever entering the yard. That is why we verify not only network access but the privilege model inside the system itself: whether one person can both issue and approve a release.

Mostly not. At an operating facility we begin with an inventory and condition assessment, neither of which requires stopping traffic. The remediation plan is split into three groups: changes that can be made remotely, those requiring a site visit, and those requiring an outage window. Outages are planned where traffic is limited anyway and agreed against your schedule. Separately we flag what can be fixed immediately with no effect on operations at all.

Because the question is not about competence but about roles in the project. The integrator delivers their own scope under schedule and budget pressure. The maintenance provider is accountable for availability and continuity, and remote access is their working tool — it is hard to expect them to propose narrowing their own privileges. The operator's IT department usually handles the office environment and takes over the facility at commissioning. Owner's supervision neither builds nor operates; it verifies, solely in the operator's interest.

We treat it as part of the design, to be deliberately specified, restricted and written into the contract, rather than as a given we learn about from an installation manual. We verify the scope and manner of device connections to supplier systems, the presence of undocumented external connectivity (cloud, modem, dongle) and the ability to change settings remotely. The United States Coast Guard warnings of 2023 and 2024 concerning ship-to-shore cranes described exactly that: cellular modems that port operators had not ordered.

Yes, and it is one of its measurable effects. Large customers, shipping lines and logistics operators increasingly include security questions in qualification questionnaires, and insurers and financing institutions ask the same. If the facility is built with public or EU funding, the due diligence question arrives even earlier. Documentation prepared once — the inventory, the register of non-conformities with the history of their resolution, the test reports — answers all of those questions and turns a problem into an argument.

No. Where facilities are built to a similar template, we examine the first in detail and carry the findings across to the rest as a checklist. This shortens the work considerably and is the cheapest way to bring a whole network of facilities into order. It also addresses a problem that recurs in portfolios: shared credentials between sites, through which compromising one terminal hands over the keys to the next.

The full study

The full study for intermodal terminals

Fifteen pages: six documented cases with their sources, the complete table of fifteen areas under control, both working tracks, NIS2 requirements for the transport sector, and the engagement variants including the network option.

Kontener wydaje system, nie człowiek

PDF document. The study is available in Polish. We use your details solely to respond to this enquiry.

Before you accept the terminal's systems

We propose a working meeting with the people responsible for the project or for operations. We will go through the list of systems planned for the facility, or already working in it, and agree the scope and a schedule matched to your delivery calendar or to the facility's outage windows.

INFO-KAN Assistant
Online

Leave your details — we'll get back to you

INFO-KAN Assistant Online

Instead of searching on your own — tell me what you need and I'll point you to the best IT solution for your business.

Start chatting