Badly seated containers can lead to serious injury
Freight insurance specialist TT Club warns of slipshod work practices at container terminals that may ...
Last month a much-reported blog – included in The Loadstar – claimed “sinking ships [via hacking], really wouldn’t take much”.
Not only was that overly dramatic and not helpful for safety of life at sea, but it was irresponsible as well as being fundamentally flawed: the input assumptions were totally incorrect.
The blog jumped around without a logical flow and appeared to conclude that if you corrupted the stowage or Bayplan, via the BAPLIE message – which is given by the ...
TPM: Forwarders need 'clout' to survive as the ocean carriers move in
Gemini schedule reliability falls below 90% target for the first time
Red Sea crisis forces Maersk to increase capacity over strategy limit
Resumption of Suez transits in doubt after return of Red Sea hostilities
Maersk in firing line over 'abandoned container' in Africa
Forever 21 blames bankruptcy on de minimis exemption
Gemini carriers cut back loading allocations on challenging southern India trade
Maersk assures shareholders arms shipments 'comply with regulations'
Comment on this article
Miles Varghese
December 06, 2017 at 3:17 pmGreat post, Andy. Huge respect to CTI, but I feel as though this piece in itself may let down the guard of an industry that is severely exposed.
The technicalities and strategies will vary, but legacy systems are easy to hack. Bay plans included. We’ve seen and worked with the EDI systems in place with many liners and were appalled by the lack of security and actually trying to change that by explaining what the cloud and SaaS really means.
The risk is huge especially when so much is done by email. The industry is easily 10-20 years behind and if a hacker were to set his sights, it would be far easier to breach than what exists today.
Liners are liners, not technology companies despite their best efforts. They know only what they know, and we’re doing what we can at Octopi to educate and explain how modern software (i.e. the terminal operating system) should be handled.