EU Cyber Resilience Act Guide for Maritime Navigation & Vessel Systems Vendors
Outside the CRA when the equipment falls within the scope of Directive 2014/90/EU. Other products are default class unless their core functionality matches an Annex III category, such as a satellite or cellular modem for connection to the internet (Annex III, point 12)
Vendors of electronic chart display systems (ECDIS), AIS transponders, vessel management systems and integrated bridge systems must first check whether each product falls within the scope of Directive 2014/90/EU on marine equipment. Equipment within that scope is outside the CRA (Article 2(4)). Other products with digital elements, such as installed port management software, are in CRA scope. They are default class unless their core functionality matches an Annex III category. Maritime systems face dual regulatory pressure from both the CRA and IMO MSC-FAL.1/Circ.3 cyber risk management guidelines, and vendors must reconcile these frameworks. The integration of navigation systems with satellite communications and shore-side networks significantly expands the attack surface that must be addressed under Annex I.
Last updated 26 October 2026
CRA Scope and Classification for Maritime Systems
Maritime navigation and vessel management products sold to EU operators - including ECDIS systems, AIS Class A and B transponders, integrated bridge systems (IBS), voyage data recorders (VDR), engine management and monitoring systems, and port management information systems - are products with digital elements under Article 3(1) of the CRA. The CRA does not apply to equipment that falls within the scope of Directive 2014/90/EU on marine equipment (Article 2(4)). That Directive covers equipment placed on board EU ships for which the international conventions require the approval of the flag State administration. Check each product against it first. Navigation equipment for SOLAS ships, such as ECDIS, AIS Class A transponders and VDRs, is the main case to check. Products outside that scope are classified by core functionality (Article 7(1)). Annex III lists no navigation, bridge or vessel category, so these products are default class. A role in collision avoidance, safe navigation or a SOLAS safety management system raises the risk that the Article 13(2) cybersecurity risk assessment has to address. It does not change the class. A satellite or cellular modem for connection to the internet, or a router or switch for the vessel network, is Important Class I (Annex III, point 12). A shipboard firewall is Important Class II (Annex III, Class II, point 2). Vendors must document the scope and classification rationale for each product.
Technical Security Obligations for Vessel-Deployed Systems
Maritime systems present unique security engineering challenges: they must operate reliably in isolated environments with limited connectivity, while increasingly being accessed remotely by shore-side technical teams. Annex I obligations for maritime vendors include: ensuring that remote access functionality - whether via satellite, cellular, or VSAT - is authenticated and encrypted with no unauthenticated bypass; eliminating default credentials on all management interfaces; providing firmware update mechanisms that function in both connected and air-gapped vessel environments; implementing tamper-evident audit logging that survives power interruptions; and documenting all external interfaces including NMEA 0183/2000 ports, USB interfaces, and network connections to other vessel systems. The SBOM requirement must cover navigation chart software components, database engines, and any real-time operating system components embedded in navigation hardware.
CVD Policy Under Article 13 for Maritime Vendors
Article 13 requires a published coordinated vulnerability disclosure policy. Maritime system vendors have historically operated in a sector with limited security researcher engagement, but this is changing rapidly as the sector's digital connectivity increases. Vendors should establish CVD policies that accommodate: reports from maritime security researchers and classification society cyber teams; interaction with the European Maritime Safety Agency (EMSA) and national maritime CSIRTs; and the operational reality that vessel operators may not be able to apply patches immediately due to voyage schedules and flag-state approval requirements. The CVD policy must specify how vendors communicate vulnerability information and available mitigations to vessel operators when immediate patching is not feasible. A machine-readable security.txt file at the vendor domain is the standard discovery mechanism for researchers.
Article 14 Incident Reporting in Maritime Context
Article 14 requires maritime system vendors to notify the relevant national CSIRT within 24 hours of becoming aware of active exploitation of a vulnerability in a deployed product. For navigation systems, active exploitation could compromise vessel positioning data, enable unauthorised route modifications, or disrupt communications - scenarios with direct safety implications. Vendors must maintain incident response procedures capable of meeting the 24-hour notification window, including out-of-hours escalation paths. When a vulnerability affects vessels at sea, vendors should also establish direct communication channels with vessel operators and ship managers, separate from the regulatory notification process. EMSA and relevant maritime CSIRTs should be included in the vendor's notification contact registry. Incidents involving actual maritime safety consequences must also be reported through existing flag-state and port-state control channels, creating parallel reporting obligations.
Conformity Assessment and Interaction with Maritime Type Approval
Maritime navigation systems often require type approval from flag-state authorities or classification societies under SOLAS and IMO performance standards. Equipment within the scope of Directive 2014/90/EU follows the conformity assessment of that Directive, and the CRA does not apply to it (Article 2(4)). For a maritime product in CRA scope, the CRA conformity assessment is a separate requirement. CE marking under the CRA does not replace maritime type approval, and type approval does not replace CRA conformity. A default-class product can use Module A internal control (Article 32(1)). An Important Class I product, such as a satellite modem for connection to the internet, can use Module A only when the manufacturer fully applies a harmonised standard, a common specification or a European cybersecurity certification scheme at assurance level at least substantial (Article 32(2)). No CRA harmonised standard is cited in the Official Journal yet, so today a Class I product needs a notified body (Module B plus Module C, or Module H). Classification society cyber requirements, such as IACS UR E26 and E27, can feed the Article 13(2) risk assessment and the technical documentation. Every in-scope product needs full technical documentation, including the maritime-specific threat model, SBOM, and security testing evidence. The declaration of conformity must be maintained throughout the product support period.
Work through the CRA for each product in one workspace.
Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.
Frequently asked
Our ECDIS systems are type-approved under IEC 61174. Does this satisfy CRA conformity requirements?+
First check whether the CRA applies. When the ECDIS falls within the scope of Directive 2014/90/EU, the CRA does not apply to it (Article 2(4)). When the ECDIS is outside that scope, the CRA applies, and IEC 61174 type approval does not satisfy it. IEC 61174 addresses navigation performance standards. The CRA requires a separate conformity assessment focused on security-by-design, vulnerability management, CVD policy, and SBOM obligations under Annex I. No CRA harmonised standard is cited in the Official Journal yet. IEC 62443 can support the assessment, but it is not a harmonised standard under the CRA and gives no presumption of conformity. For an in-scope product, both type approval and CRA CE marking are needed for EU market access.
Vessels can be at sea for months without connectivity. How do we meet the firmware update obligations of Annex I?+
Annex I requires that security updates be made available without undue delay - it does not require immediate installation by the operator. Your obligation as a manufacturer is to issue and publish security updates promptly when vulnerabilities are identified. For vessel operators who cannot apply updates immediately, you must provide documented interim mitigations and configuration guidance. Your CVD policy and security advisory processes should clearly communicate update availability, severity, and interim workarounds. Delivery mechanisms for offline update packages - USB media, port-of-call update procedures - should be documented and tested.
Do AIS transponders fall under the CRA, and which class applies?+
First check Directive 2014/90/EU. An AIS transponder that falls within the scope of that Directive is outside the CRA (Article 2(4)). Class A transponders are carried under SOLAS, so check them first. An AIS transponder outside that scope is a product with digital elements in CRA scope. Annex III lists no AIS or navigation category, so it is default class and can use Module A internal control (Article 32(1)). Its role in vessel tracking and collision avoidance raises the risk that the Article 13(2) cybersecurity risk assessment must address. It does not change the class. Vendors should document their scope and classification analysis for each model.
Key CRA articles for Maritime Navigation & Vessel Systems Vendors
Free CRA tools
This industry guide is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.
Need a CVD policy template for Maritime Navigation & Vessel Systems Vendors?
Download a free CRA-compliant vulnerability disclosure policy and deploy it in minutes.