Does the Cyber Resilience Act Apply to Maritime Software?
Learn if the EU CRA applies to Maritime Software, what the core compliance requirements are, and how to start preparing your engineering teams automatically.
Core Definition
It Depends. Exempt if covered by specific marine equipment directives. Vessel navigation software governed by IMO/marine equipment directives may be exempt, but shore-side fleet management software usually isn't. If you do not fall into an explicit exemption, your Maritime Software will be subjected to the CRA's strict requirements.
Key Compliance Steps for Maritime Software
- Determine Classification: Check if your Maritime Software falls under the default category or Class I/Class II, which dictate stricter conformity assessment paths.
- Perform Risk Assessment: Map out the attack surface for your software and document the mitigations for the "secure by design" requirement.
- Implement Vulnerability Reporting: Provide a 24-hour reporting mechanism to ENISA for actively exploited vulnerabilities.
- Generate an SBOM: Ensure all dependencies used in your Maritime Software are documented in a machine-readable Software Bill of Materials.
- Avoid the Common Pitfall: Assuming the maritime exemption covers the entire company's software stack instead of just the specific regulated equipment.
How This Plays Out in Practice
Vessel navigation software governed by IMO/marine equipment directives may be exempt, but shore-side fleet management software usually isn't.
What to Watch For
Assuming the maritime exemption covers the entire company's software stack instead of just the specific regulated equipment.
Assess Your CRA Readiness
Evaluate your product's Cyber Resilience Act readiness using our interactive tool. Find exactly which of the 22 security requirements apply directly to Maritime Software.