<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Visualisation - Tag - Maritimeinfosec.org</title><link>https://maritimeinfosec.org/tags/visualisation/</link><description>Visualisation - Tag - Maritimeinfosec.org</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>Copyright Maritimeinfosec.org 2018-2026</copyright><lastBuildDate>Fri, 16 Oct 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://maritimeinfosec.org/tags/visualisation/" rel="self" type="application/rss+xml"/><item><title>Fifteen years of maritime cyber incidents, animated</title><link>https://maritimeinfosec.org/fifteen-years-of-maritime-cyber-incidents-animated/</link><pubDate>Fri, 16 Oct 2026 10:00:00 +0200</pubDate><author>Olivier JACQ</author><guid>https://maritimeinfosec.org/fifteen-years-of-maritime-cyber-incidents-animated/</guid><description><![CDATA[<p>As of 15 October 2026, my maritime cyber incident dataset, which I have compiled for more than six years, holds 4,622 incidents dated from 2012 to today. To see how it came together, I ran <a href="https://gource.io/" target="_blank" rel="noopener noreferrer "><em>Gource</em></a>, a free tool built to animate the history of a code repository, on the records themselves.</p>
<p>Each dot is one incident, placed at the date it happened and coloured by type, including denial of service (DoS) and ransomware. The legend at the bottom right gives the colours. The silhouettes moving around stand for the origin category, such as hacktivism or cybercrime. No group or victim name appears.</p>]]></description></item></channel></rss>