<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Fraud - Tag - Maritimeinfosec.org</title><link>https://maritimeinfosec.org/tags/fraud/</link><description>Fraud - Tag - Maritimeinfosec.org</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>Copyright Maritimeinfosec.org 2018-2026</copyright><lastBuildDate>Sun, 27 Sep 2026 14:45:00 +0200</lastBuildDate><atom:link href="https://maritimeinfosec.org/tags/fraud/" rel="self" type="application/rss+xml"/><item><title>What does a maritime cyber incident cost?</title><link>https://maritimeinfosec.org/what-does-a-maritime-cyber-incident-cost/</link><pubDate>Sun, 27 Sep 2026 14:45:00 +0200</pubDate><author>Olivier JACQ</author><guid>https://maritimeinfosec.org/what-does-a-maritime-cyber-incident-cost/</guid><description><![CDATA[<p>Recently a researcher wrote about me, behind the paywall of an academic paper, without consulting me or offering a right of reply, that when I spoke up it was to praise the resilience of the maritime sector and to argue that attacks on it are impossible. For someone who has worked on the subject for more than 25 years, who started this blog in 2017 (when maritime cyber was still of no interest to anyone), who built the first global database of maritime cybersecurity incidents more than five years ago, and who describes part of it here, you will find that as funny as I do.</p>
<p>To those researchers, if you have a minimum of ethics and consideration, allow me only the freedom not to fan the flames when an incident happens, and to avoid on those occasions, out of modesty or out of ethics, reaching every time for the &ldquo;I told you so&rdquo; or the &ldquo;if you need me, I am here&rdquo;.</p>]]></description></item></channel></rss>