<node id="693264">
  <nid>693264</nid>
  <type>news</type>
  <uid>
    <user id="36253"><![CDATA[36253]]></user>
  </uid>
  <created>1792157346</created>
  <changed>1792415094</changed>
  <title><![CDATA[When a Ship’s Systems Lie, Cybersecurity Gets Complicated]]></title>
  <body><![CDATA[<p>Sailors at sea rely on electronic equipment to keep ships on course and out of danger, but what happens when hackers get involved? Are the mariners equipped to handle modern cybersecurity threats like GPS spoofing?</p><p>In a <a href="https://arxiv.org/pdf/2609.12810">study</a> accepted for the 2026 <a href="https://www.sigsac.org/ccs/CCS2026/index.html">ACM Conference on Computer and Communications Security</a>, Georgia Tech researchers interviewed 20 military sailors about their cybersecurity experiences, training, and responses to hypothetical scenarios. Their findings point to a gap between how mariners are trained to handle emergencies and how cyberattacks can compromise the systems they depend on.&nbsp;</p><p>The study found several gaps in how crews prepare for cyber threats:</p><ul><li data-list-item-id="edf63c815360cecb04c01d6561be9a7b1">Training often misses the mark. Thirteen participants said that standard cybersecurity training was largely irrelevant to their shipboard duties, and 14 reported receiving no mission-specific cybersecurity training.</li><li data-list-item-id="e619f896d048b6bcd034a76176e6067bb">Operational technology is often overlooked. Eighteen participants said their training did not distinguish between traditional information technology and operational technology, such as navigation and propulsion systems.</li><li data-list-item-id="e928f3fef211e61dcd97e963697bd9389">Obvious failures are easier to recognize. Eighteen participants said they would primarily look for visible signs of operational problems when identifying a potential cyberattack.</li><li data-list-item-id="e1499170bf08bd8a760ed09fee3a091d7">Cybersecurity is often a low priority. Seventeen participants described their cybersecurity training as absent, low quality, or a low priority.</li></ul><p>These gaps matter because cyberattacks can compromise a system without causing it to stop working. For example, an attacker could manipulate navigation data, leaving a crew to make decisions based on false information.</p><p>“I’d assume it was anything but cyber at first. It would probably take me quite some time to get to that conclusion,” one participant told the researchers.</p><p>The team examined three hypothetical scenarios: GPS spoofing, loss of propulsion control in a high-traffic area, and failure of electronic navigation systems in a congested channel at night.</p><p>In each scenario, mariners would first focus on keeping the vessel safe, using established procedures to stabilize the ship and troubleshoot its systems. While this response is essential during an emergency, it could delay recognition of an attack if crews do not consider that the system or its data may have been compromised.</p><p>For example, a ship navigating a narrow channel depends on accurate location information, but what happens when its navigation systems appear to work normally while a hacker manipulates that data?</p><p>An attacker could use GPS spoofing to falsify a vessel’s reported position. If the false position is close enough to the ship’s actual location, a mariner might not notice anything wrong. The vessel could gradually head toward shallow water or another obstacle without triggering an obvious error or alarm.</p><p>“By the time the mariner realizes something is wrong, the ship’s size and limited maneuverability could make it too late to avoid a grounding or collision,” said <strong>Anna Raymaker</strong>, a Georgia Tech Ph.D. student who studies maritime security.</p><p>The scenario illustrates a central challenge in maritime cybersecurity: An equipment failure may be easy to recognize, but a cyberattack that provides false information can be much harder to detect.</p><p><a href="https://arxiv.org/pdf/2609.12810"><em>Batten the Hatches: Cybersecurity with Military Mariners</em></a><em>&nbsp;</em>was written by master’s student <strong>Ryan Von Brock</strong>, Raymaker, Research Scientist <strong>Animesh Chhotaray</strong>, Associate Professors <strong>Frank Li</strong> and <strong>Saman Zonouz</strong>, and Provost &amp; Executive Vice President for Academic Affairs <strong>Raheem Beyah</strong>.</p><p>The research was conducted in Georgia Tech’s <a href="https://sites.gatech.edu/capcpsec/">Cyber-Physical Security Lab</a>, a collaboration between the <a href="https://scp.cc.gatech.edu/">School of Cybersecurity and Privacy</a> and the <a href="https://ece.gatech.edu/">School of Electrical and Computer Engineering</a>.&nbsp;</p><p><em>Photos by Terence Rushin/College of Computing</em></p>]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2026-10-16T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[Maritime cybersecurity training leaves sailors vulnerable to attacks that manipulate ship systems without obvious failures. The Georgia Tech study identifies weaknesses in preparation and threat recognition among military mariners.]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[<p>Maritime cybersecurity training leaves sailors vulnerable to attacks that manipulate ship systems without obvious failures. The Georgia Tech study identifies weaknesses in preparation and threat recognition among military mariners. Interviews with 20 military sailors found that 13 considered standard training irrelevant, while 14 lacked mission-specific cybersecurity training. Operational technology gaps affected 18 participants, and 18 said they would mainly seek visible operational problems when detecting attacks. In scenarios involving GPS spoofing and navigation or propulsion failures, crews prioritized vessel safety, but false data could delay detection and cause grounding or collision.</p>]]></value>
    </item>
  </field_summary>
  <field_media>
          <item>
        <nid>
          <node id="681456">
            <nid>681456</nid>
            <type>image</type>
            <title><![CDATA[Saman-Zonouz-Lab_banner.jpg]]></title>
            <body><![CDATA[]]></body>
                          <field_image>
                <item>
                  <fid>265864</fid>
                  <filename><![CDATA[Saman-Zonouz-Lab_banner.jpg]]></filename>
                  <filepath><![CDATA[/sites/default/files/2026/10/19/Saman-Zonouz-Lab_banner.jpg]]></filepath>
                  <file_full_path><![CDATA[http://hg.gatech.edu//sites/default/files/2026/10/19/Saman-Zonouz-Lab_banner.jpg]]></file_full_path>
                  <filemime>image/jpeg</filemime>
                  <image_740><![CDATA[]]></image_740>
                  <image_alt><![CDATA[A group photo of students and faculty standing around lab equipment found on a ship. ]]></image_alt>
                </item>
              </field_image>
            
                      </node>
        </nid>
      </item>
          <item>
        <nid>
          <node id="681458">
            <nid>681458</nid>
            <type>image</type>
            <title><![CDATA[Saman-Zonouz-Lab_side-view.jpg]]></title>
            <body><![CDATA[]]></body>
                          <field_image>
                <item>
                  <fid>265866</fid>
                  <filename><![CDATA[Saman-Zonouz-Lab_side-view.jpg]]></filename>
                  <filepath><![CDATA[/sites/default/files/2026/10/19/Saman-Zonouz-Lab_side-view.jpg]]></filepath>
                  <file_full_path><![CDATA[http://hg.gatech.edu//sites/default/files/2026/10/19/Saman-Zonouz-Lab_side-view.jpg]]></file_full_path>
                  <filemime>image/jpeg</filemime>
                  <image_740><![CDATA[]]></image_740>
                  <image_alt><![CDATA[A group of students working on lab equipment. The equipment replicates a ship's helm. ]]></image_alt>
                </item>
              </field_image>
            
                      </node>
        </nid>
      </item>
          <item>
        <nid>
          <node id="681457">
            <nid>681457</nid>
            <type>image</type>
            <title><![CDATA[Saman-Zonouz-Lab_ship-equipment.jpg]]></title>
            <body><![CDATA[]]></body>
                          <field_image>
                <item>
                  <fid>265865</fid>
                  <filename><![CDATA[Saman-Zonouz-Lab_ship-equipment.jpg]]></filename>
                  <filepath><![CDATA[/sites/default/files/2026/10/19/Saman-Zonouz-Lab_ship-equipment.jpg]]></filepath>
                  <file_full_path><![CDATA[http://hg.gatech.edu//sites/default/files/2026/10/19/Saman-Zonouz-Lab_ship-equipment.jpg]]></file_full_path>
                  <filemime>image/jpeg</filemime>
                  <image_740><![CDATA[]]></image_740>
                  <image_alt><![CDATA[Lab equipment of a ship steering wheel and other electronic  measuring devices. ]]></image_alt>
                </item>
              </field_image>
            
                      </node>
        </nid>
      </item>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[jpopham3@gatech.edu]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[<p>John Popham</p><p>Communications Officer for the School of Cybersecurity and Privacy</p>]]></value>
    </item>
  </field_contact>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <!--  TO DO: correct to not conflate categories and news room topics  -->
  <!--  Disquisition: it's funny how I write these TODOs and then never
         revisit them. It's as though the act of writing the thing down frees me
         from the responsibility to actually solve the problem. But what can I
         say? There are more problems than there's time to solve.  -->
  <links_related> </links_related>
  <files> </files>
  <og_groups>
          <item>47223</item>
          <item>1188</item>
          <item>660406</item>
          <item>660367</item>
      </og_groups>
  <og_groups_both>
          <item>
        <![CDATA[Computer Science/Information Technology and Security]]>
      </item>
          <item>
        <![CDATA[Engineering]]>
      </item>
          <item>
        <![CDATA[Military Technology]]>
      </item>
          <item>
        <![CDATA[Research]]>
      </item>
          <item>
        <![CDATA[Student and Faculty]]>
      </item>
          <item>
        <![CDATA[Student Research]]>
      </item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>153</tid>
        <value><![CDATA[Computer Science/Information Technology and Security]]></value>
      </item>
          <item>
        <tid>145</tid>
        <value><![CDATA[Engineering]]></value>
      </item>
          <item>
        <tid>147</tid>
        <value><![CDATA[Military Technology]]></value>
      </item>
          <item>
        <tid>135</tid>
        <value><![CDATA[Research]]></value>
      </item>
          <item>
        <tid>134</tid>
        <value><![CDATA[Student and Faculty]]></value>
      </item>
          <item>
        <tid>8862</tid>
        <value><![CDATA[Student Research]]></value>
      </item>
      </field_categories>
  <core_research_areas>
          <term tid="145171"><![CDATA[Cybersecurity]]></term>
          <term tid="39501"><![CDATA[People and Technology]]></term>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>47223</item>
          <item>1188</item>
          <item>660406</item>
          <item>660367</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[College of Computing]]></item>
          <item><![CDATA[Research Horizons]]></item>
          <item><![CDATA[School of Cybersecurity &amp; Privacy]]></item>
          <item><![CDATA[School of Cybersecurity and Privacy]]></item>
      </og_groups_both>
  <field_keywords>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
