Does the CRA apply to maritime manufacturers?

With IACS UR E26 and E27, many maritime manufacturers have spent the past few years building cyber resilience into their systems and equipment – and for many, that work is still ongoing. Now, the EU Cyber Resilience Act (CRA) may add another layer of obligations: cybersecurity requirements under EU product harmonisation legislation for placing products with digital elements on the EU/EEA market.

For maritime manufacturers, this raises some immediate questions: Does the CRA apply to my products? Do I need to comply? And what does this mean for my ability to sell products in the EU? 

 

Does the CRA apply to maritime products? 

The CRA applies broadly to products with digital elements made available on the EU market. This can include connected hardware and software products used in the maritime sector.

However, being a maritime manufacturer does not automatically determine whether a product falls inside or outside the scope of the CRA. Applicability needs to be considered at the level of the individual product, including how it is placed on the EU market.

In other words, maritime products are not automatically exempt from the CRA simply because they are intended for use on board a vessel.

 

An important maritime consideration: the Marine Equipment Directive 

There is, however, an important maritime-specific consideration. The CRA excludes equipment falling within the scope of the Marine Equipment Directive (MED - Directive 2014/90/EU).

This does not amount to a general exemption for the maritime industry. A product being installed onboard a vessel, class-approved or subject to IACS requirements does not by itself mean that it falls outside the CRA.

For example, an Electronic Chart Display and Information System (ECDIS) that falls within the scope of the MED is excluded from the CRA under Article 2(4). By contrast, an Electronic Record Book (ERB) is listed in Chapter 9 of the current MED implementing regulation as equipment not subject to MED certification. If supplied as a connected product with digital elements on the EU market, an ERB may therefore fall within the CRA, subject to the CRA’s other applicability conditions and exclusions.

Manufacturers therefore need to establish whether their particular product falls within the MED exclusion or another applicable exclusion.
 

What does it mean if a product is in scope? 

If a product falls within the scope of the CRA, manufacturers will need to assess cybersecurity risks throughout the product lifecycle and determine which of the CRA’s essential cybersecurity requirements apply. These span both product-level technical measures and the processes used to develop, maintain and support the product.

Relevant areas include cybersecurity risk assessment, security by design and by default, vulnerability handling, security updates and support periods, technical documentation, reporting of certain vulnerabilities and incidents, and conformity assessment.

The important distinction is that the CRA is not simply another set of technical cybersecurity controls. It introduces legal responsibilities associated with developing, placing and maintaining products on the EU market.

 

Haven't manufacturers already addressed some of this through IACS? 

For maritime manufacturers already working with the IACS cyber requirements, some of that work may also be relevant when preparing for the CRA.

In particular, IACS UR E27 addresses cyber resilience of onboard systems and equipment, including areas such as access control and authentication, system integrity and confidentiality, secure development, security updates, hardening, logging and monitoring, testing and documentation. Some of these areas are also addressed by the CRA.

IACS UR E26 provides additional context around how systems and equipment are securely integrated and operated at ship level.

There could therefore be areas of overlap between IACS work and what manufacturers need to address under the CRA. This is relevant both to manufacturers with IACS work already underway and to those planning IACS and CRA activities in parallel. Depending on the individual product and the work already undertaken or planned, some cybersecurity controls, processes, documentation or evidence may be relevant to both.

However, they differ in areas such as product scope, purpose and legal implications. Manufacturers should therefore not assume that meeting IACS UR E26 or E27 requirements means that they have already addressed the CRA.

Any potential reuse or coordination should be assessed against the CRA requirements to determine which elements may be relevant and, importantly, what additional work is required. The CRA introduces requirements and legal obligations that are not addressed, or are addressed differently, by IACS E26/E27, including areas such as CRA-specific risk assessment, technical product requirements, integrated component vulnerability reporting, support periods, technical documentation and conformity assessment.

 

What should maritime manufacturers do now? 

For manufacturers trying to understand what the CRA means for them, the first step is to establish where they stand. The following steps offer a practical starting point:

  1. Analyse how the CRA applies to your products. Product scope and applicability criteria under the CRA differ from those under IACS UR E27. Important applicability criteria are direct or indirect data connections to devices or networks, and placing on the EU/EEA market. Also include your lifecycle services in the assessment as they may substantially modify products already placed on the market.
  2. Check for exclusions. For each product, determine whether an exclusion applies, in particular whether the product falls within the scope of the EU Marine Equipment Directive according to the current implementing regulation.
  3. Assess against CRA requirements. For products in scope, identify the CRA requirements that apply and what must be in place to meet them. These include cybersecurity risk assessment, support period, a secure development lifecycle, vulnerability handling, technical documentation and conformity assessment. Achieving conformity under the CRA conformity may also require changes to the product’s intended purpose or even a technical redesign.
  4. Build on what you already have. Where you have worked with IACS UR E27, review which existing controls, processes and technical documentation may support CRA compliance. Treat your achievements with IACS UR E27 as a head start rather than a finish line. Where CRA and IACS UR E27 work are starting at the same time, consider the requirements together to identify potential overlaps and avoid duplicating effort.  

With the CRA's manufacturer reporting obligations applying since 11 September 2026 and its full requirements applying from 11 December 2027, now is the time to start.

 

Conclusion 

For manufacturers at the beginning of their CRA journey, DNV Cyber's whitepaper What the Cyber Resilience Act means for manufacturers provides a broader introduction to the regulation, its key requirements and practical steps for starting the compliance journey. 

Related content