<?xml version="1.0" encoding="utf-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2d1 20170631//EN" "JATS-journalpublishing1.dtd">
<ArticleSet>
  <Article>
    <Journal>
      <PublisherName>Innovative Research Publication</PublisherName>
      <JournalTitle>International Journal of Innovative Research in Computer Science and Technology</JournalTitle>
      <EISSN>2347-5552</EISSN>
     
      <Volume-Issue>Volume 14 Issue 6</Volume-Issue>
      <PartNumber/>
      <IssueLanguage>English</IssueLanguage>
      <Season>Nov-Dec - February 2026</Season>
      <SpecialIssue>N</SpecialIssue>
      <SupplementaryIssue>N</SupplementaryIssue>
      <IssueOA>Y</IssueOA>
      <PubDate>
        <Year>2026</Year>
        <Month>11</Month>
        <Day>13</Day>
      </PubDate>
      <ArticleType>Information Management</ArticleType>
      <ArticleTitle>A Cybersecurity Integration and Supply-Chain Verification Model for Shipboard Safety-Critical Systems Complying with IACS UR E26/E27</ArticleTitle>
      <SubTitle/>
      <ArticleLanguage>English</ArticleLanguage>
      <ArticleOA>Y</ArticleOA>
      <FirstPage>20</FirstPage>
      <LastPage>29</LastPage>
      <AuthorList>
        <Author>
          <FirstName>Chen-Yu Li</FirstName>          
          <AuthorLanguage>English</AuthorLanguage>
          <Affiliation/>
          <CorrespondingAuthor>Y</CorrespondingAuthor>
          <ORCID/>
                      <FirstName>Chia-Ling Chen</FirstName>          
          <AuthorLanguage>English</AuthorLanguage>
          <Affiliation/>
          <CorrespondingAuthor>N</CorrespondingAuthor>
          <ORCID/>
           
        </Author>
      </AuthorList>
      <DOI>https://doi.org/10.55524/ijircst.2026.14.6.3</DOI>
      <Abstract>Application of IACS Unified Requirements E26 and E27 in the existing vessels creates a nightmare in terms of working. It is possible that the supplier is rated highly in documentations but the ship may end up having mechanical breakdown, having been associated with a bug that is hidden within OT software. We built the Supply-chain Verified Cyber Resilience (SCV-CR) framework to deal with this gap. Ranging the perimeter of otherwise-isolated networks into view instead of physical dependencies, SCV-CR imposes separation of communication paths and physical machinery dependencies on two explicit graph structures (G N and G S ) and imposes hard Boolean admission gates on signed SBOM and VEX artifacts. Our set-up of the deterministic Monte Carlo experiment took over 20,000 iterations and six representative Maritime subsystems (PMS, AMS, IAS, ECDIS, GMDSS and cargo automation). The disruption failure rates were reduced by 16.22 percent and conditional downtime reduced by 24.28 percent and the 95th-percentile recovery time reduced to 15.31 h over the simulated rollout. Because inherent physical hazard invariants are never eliminated by the framework, it appears to offer a verifiable, mathematically-underpinned, way of audit of cyber safety by shipboard engineers and classification surveyors when carrying out physical surveys of classes.</Abstract>
      <AbstractLanguage>English</AbstractLanguage>
      <Keywords>Cyber-physical systems, IACS UR E26/E27, Maritime cybersecurity, Software bill of materials, Supply-chain verification.</Keywords>
      <URLs>
        <Abstract>https://ijircst.org/view_abstract.php?title=A Cybersecurity Integration and Supply-Chain Verification Model for Shipboard Safety-Critical Systems Complying with IACS UR E26/E27&amp;year=2026&amp;vol=14&amp;primary=QVJULTE0ODk=</Abstract>
      </URLs>      
    </Journal>
  </Article>
</ArticleSet>