
On 10 November 2026 the Santos Port Authority (APS), which runs Latin America's busiest port, confirmed that it had suffered a cyberattack on its online systems. The incident was identified after a power cut hit the company's servers on the morning of Friday 6 November; internet and telephony were restored on Monday 9 November after three days of unavailability, while the official website and other internal systems were still being brought back gradually. The authority said that logistics operations, vessel movements and land access were never interrupted, that no service stopped being delivered, and that the cause and the scope were still under investigation.
We are not going to comment on the choices made in Santos. A port authority that keeps ships moving while its office systems are down, says so publicly within days, and restores from backups is doing the hard part right. What is worth a few minutes of your time is the shape of the incident, because it is one we see again and again in ports of every size: the quay keeps working, the administration goes dark, and the first question nobody can answer is « when did it start? ».
What is actually known
Sources: SBT News (10 November 2026), Rádio Itatiaia (10 November 2026). The picture may change as the investigation continues.
Where
When
Impact
Response
Attacker claims
Why « the quay works, the office is dark » is the pattern that matters
In a port authority, the systems that move ships and trucks are usually the best protected: segmented, monitored, operated by the terminals themselves. Next to them live the systems the public and the staff actually use every day: the website, the e-mail, the telephony, the permit and invoicing tools, the support databases. They are reachable from the internet, they are shared by everyone, and they are the ones that go dark first.
That is why the public line of almost every port authority incident is the same, from San Diego in 2018 to Lisbon in 2022 and now Santos: operations are not affected. It is true, and it is not the whole story. Three days without e-mail and telephony at the authority of a port that handles a continent's trade is an incident, even when no container stops. The detail that matters most in Santos is the timeline: the incident was noticed after a power cut, and the investigation is still working out whether the two are related. A system that does not keep its logs somewhere central cannot answer that question, and the answer decides everything that follows: what to restore, from which backup, and what to tell the customers.
What a port team can do this week
None of this requires a budget line. It requires an afternoon, a spreadsheet and the honesty to write « unknown » where it applies.
Draw the line between the quay and the office, on paper
Rehearse the alternative channels
Time the restore
Send the logs somewhere that survives the outage
If you have the same cases
Most port authorities do, and that is fine: you are grown-ups, you can handle it. If you want a quick, private way to see where you stand, we built two self-assessments that take about two minutes and stay in your browser until you decide otherwise: one for engineers, one for the people who lead the team. If something in your result worries you, talk to us in confidence. And when one port sees a threat, every member of the Alliance is told: that is the whole point.
Keep reading
Every public port cyber incident, on one
Port engineer cyber self-assessment: 2-minute test
Team cyber assessment for port and terminal
The launch offer for member organizations
DMS Group: the logistics chain, from the
Want a second pair of eyes on your site?
Every member gets cyber advice and two site visits a year. Start with a two-minute self-assessment.



