<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Future - Tag - Maritimeinfosec.org</title><link>https://maritimeinfosec.org/tags/future/</link><description>Future - Tag - Maritimeinfosec.org</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>Copyright Maritimeinfosec.org 2018-2026</copyright><lastBuildDate>Fri, 12 Jun 2020 12:13:12 +0000</lastBuildDate><atom:link href="https://maritimeinfosec.org/tags/future/" rel="self" type="application/rss+xml"/><item><title>The future of maritime information systems</title><link>https://maritimeinfosec.org/future-of-maritime-information-systems/</link><pubDate>Fri, 12 Jun 2020 12:13:12 +0000</pubDate><author>Olivier JACQ</author><guid>https://maritimeinfosec.org/future-of-maritime-information-systems/</guid><description>&lt;p>By now, after reading the various articles on this site, you have probably understood that maritime information systems contain vulnerabilities. The real challenge is that the future of maritime information systems is being built while many of these vulnerabilities remain unresolved. It is a bit like adding extra floors to a house while the concrete of the ground floor has not yet fully set. In short, it is risky. Ships being built today are still insufficiently secured, yet they are designed to remain in service until around 2060.&lt;/p></description></item></channel></rss>