ShipPaulJobs Weekly Regulatory Brief No. 1, November 2026: The MASS Code, the CRA Reporting Clock and New Class Cyber Guidance
New and revised rules on ship cyber security, autonomous ships and smart ships from IMO, IACS and class societies, the EU, NIST, IEC and BIMCO. Launch issue, covering April to November 2026.
Ask a superintendent what changed in the rules this year and you usually get one answer: UR E26 and E27. That answer is now out of date. Since April, IMO has adopted its first code for autonomous ships, the EU has started a 24-hour clock on product vulnerabilities, NIST has written ships into its OT security guide, and two class societies have changed how they check cyber security in practice. None of these replaces E26/E27. Each one adds a new desk that your evidence must now satisfy. This launch issue gathers them in one place; from here on, the Regulatory Brief arrives every week.

At a Glance
| Date | Who | What | Status |
|---|---|---|---|
| 17 Nov 2026 | EU · ENISA | EU CRA Single Reporting Platform upgraded to version 1.4 | Guidance |
| 30 Oct 2026 | ClassNK | ClassNK publishes 2nd edition of its Guidelines for Cyber Security Management System for Ships | Guidance |
| 13 Oct 2026 | Korean Register (KR) | KR launches pilot of its Cyber Resilience Platform (KR-CRP) for UR E26 documentation | News |
| 21 Sep 2026 | NIST | NIST releases draft SP 800-82 Rev. 4, Guide to OT Security, now covering maritime vessels | Draft |
| 11 Sep 2026 | EU · Cyber Resilience Act | EU Cyber Resilience Act reporting obligations apply from 11 September 2026 | In force |
| 1 Jul 2026 | IMO | IMO MASS Code takes effect as a non-mandatory instrument | In force |
| 22 May 2026 | IMO · MSC 111 | MSC 111 approves a roadmap for a non-mandatory Maritime Cyber Code and revises MSC-FAL.1/Circ.3 | Adopted |
| 21 May 2026 | IMO · MSC 111 | IMO adopts the MASS Code, Resolution MSC.595(111) | Adopted |
| 5 Apr 2026 | ClassNK | ClassNK grants AUTO-Nav2(All) autonomous navigation notation to container ship Genbu | Notation |
Ⅰ. Autonomous Ships: The MASS Code Leaves the Drawing Board
For ten years, autonomous ships lived in trials and approvals in principle. In May 2026 IMO gave them a rulebook. It is voluntary for now, but it is the first time a flag state, a yard and a class society can point to the same international text when they argue about who is in control of a ship that nobody is steering by hand.
The Code is goal-based: it does not prescribe a sensor or a software design, it asks the owner to show that an autonomous or remotely operated function is at least as safe as the conventional one it replaces. It covers cargo ships of 500 GT and above and sits beside SOLAS rather than inside it.
Because it is non-mandatory, no ship has to follow it yet. What it starts is an Experience-Building Phase: IMO wants operational data from real MASS projects before writing a mandatory code, planned for 1 January 2032 at the earliest. DNV notes that MSC 112 in December 2026 is expected to set out how that phase will run.
Ⅱ. Cyber Rules at IMO: From Guidelines Toward a Code
Today IMO's cyber rule for ships is essentially one circular, MSC-FAL.1/Circ.3, enforced through the ISM Code. MSC 111 did two things. It made a small revision to that circular, and it approved a roadmap for a Maritime Cyber Code, still non-mandatory, with a working group meeting in 2027. It also approved IMO's Strategy on Maritime Digitalization.
Ⅲ. The EU Cyber Resilience Act: The Reporting Clock Has Started
The CRA applies to products with digital elements sold in the EU, which includes a great deal of marine equipment, from navigation software to engine-room controllers. Its first live obligation is reporting: an early warning within 24 hours and a notification within 72 hours once a manufacturer knows that a vulnerability in its product is being actively exploited, or that a severe incident has occurred. The rest of the Act, including the security requirements themselves, applies from 11 December 2027.
Reports go through one ENISA platform, which forwards them to the national CSIRTs. Two months after launch it is already on its fourth version, so suppliers should check the current user manual rather than a copy saved in September.
Ⅳ. NIST Writes Ships Into Its OT Security Guide
SP 800-82 is the reference many OT security teams already use for plants and utilities. The fourth revision, now a public draft, lists maritime vessels among the OT environments it covers and aligns its advice with NIST CSF 2.0, the same five functions UR E26 is built on. Comments are open until 30 November 2026.
Ⅴ. Class Societies: How Cyber Is Checked Is Changing
Operators have been answering the same cyber questions several times: once for class, once for RightShip, once for SIRE 2.0, once for TMSA. ClassNK's second edition lines its management-system audit up against all of those schemes, so one body of evidence can serve several inspections.
KR is attacking the same problem from the newbuilding side. UR E26 produces a stack of design documents, and KR-CRP moves their preparation and review onto one platform linked to drawing approval and survey.
Ⅵ. What to Watch Next
- 30 November 2026: comment deadline for NIST SP 800-82 Rev. 4.
- December 2026, MSC 112: expected to frame the MASS Code Experience-Building Phase.
- 2027: IMO working group on the non-mandatory Maritime Cyber Code.
- 11 December 2027: the remaining EU CRA obligations apply.
Every item in this brief also appears, by year, month and week, on the Maritime Regulatory Watch page, together with the reference documents most often downloaded.
⚓ Join the ShipPaulJobs Community
Join →
Comments
Post a Comment