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.

Official Page · Maritime Cyber & AI Briefing

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.

Rule books, a ship and a shield: maritime regulatory watch

At a Glance

DateWhoWhatStatus
17 Nov 2026EU · ENISAEU CRA Single Reporting Platform upgraded to version 1.4Guidance
30 Oct 2026ClassNKClassNK publishes 2nd edition of its Guidelines for Cyber Security Management System for ShipsGuidance
13 Oct 2026Korean Register (KR)KR launches pilot of its Cyber Resilience Platform (KR-CRP) for UR E26 documentationNews
21 Sep 2026NISTNIST releases draft SP 800-82 Rev. 4, Guide to OT Security, now covering maritime vesselsDraft
11 Sep 2026EU · Cyber Resilience ActEU Cyber Resilience Act reporting obligations apply from 11 September 2026In force
1 Jul 2026IMOIMO MASS Code takes effect as a non-mandatory instrumentIn force
22 May 2026IMO · MSC 111MSC 111 approves a roadmap for a non-mandatory Maritime Cyber Code and revises MSC-FAL.1/Circ.3Adopted
21 May 2026IMO · MSC 111IMO adopts the MASS Code, Resolution MSC.595(111)Adopted
5 Apr 2026ClassNKClassNK grants AUTO-Nav2(All) autonomous navigation notation to container ship GenbuNotation

Ⅰ. 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.

21 May 2026 · IMO · MSC 111 · Adopted · Autonomous (MASS)
IMO adopts the MASS Code, Resolution MSC.595(111)

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.

1 Jul 2026 · IMO · In force · Autonomous (MASS)
IMO MASS Code takes effect as a non-mandatory instrument

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.

5 Apr 2026 · ClassNK · Notation · Autonomous (MASS) · Smart ship
ClassNK grants AUTO-Nav2(All) autonomous navigation notation to container ship Genbu

Class did not wait for IMO. ClassNK put an autonomous navigation notation on a working coastal container ship, built on its own guidelines from the MEGURI2040 trials. This is the pattern to expect: class notations move first, and the international code catches up.

What it means on board and in the yard
An autonomous or remotely operated function is, in the end, a computer-based system with a radio link. Every MASS project therefore lands on the same desk as UR E26: asset inventory, network zones, remote access, and what happens when the link is lost. If you are designing one, treat the MASS Code and E26 as one conversation, not two.

Ⅱ. Cyber Rules at IMO: From Guidelines Toward a Code

22 May 2026 · IMO · MSC 111 · Adopted · Cyber security · Smart ship
MSC 111 approves a roadmap for a non-mandatory Maritime Cyber Code and revises MSC-FAL.1/Circ.3

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.

What it means on board and in the yard
Nothing changes on board this year. But a code, even a voluntary one, tends to become the checklist that flag states, vetting inspectors and insurers use. Owners who already run E26-style asset registers and incident plans will find the code describes what they do; owners who rely on a one-page ISM cyber annex will have work to do.

Ⅲ. The EU Cyber Resilience Act: The Reporting Clock Has Started

11 Sep 2026 · EU · Cyber Resilience Act · In force · Cyber security
EU Cyber Resilience Act reporting obligations apply from 11 September 2026

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.

17 Nov 2026 · EU · ENISA · Guidance · Cyber security
EU CRA Single Reporting Platform upgraded to version 1.4

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.

What it means on board and in the yard
For a marine equipment maker, the hard part is not the form, it is knowing within 24 hours. That requires a product security contact, a way to hear from customers and researchers, and a list of which software runs on which ships. For an owner, it is a reason to ask suppliers: who do we call, and how fast will you tell us?

Ⅳ. NIST Writes Ships Into Its OT Security Guide

21 Sep 2026 · NIST · Draft · Cyber security
NIST releases draft SP 800-82 Rev. 4, Guide to OT Security, now covering maritime vessels

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.

What it means on board and in the yard
This matters less for what it requires (NIST guidance is voluntary) than for what it signals: ship systems are now treated as mainstream OT. Shore-side OT security teams, consultants and tool vendors will start to apply plant-world practices to ships. If you have comments from the ship side, this month is the time to send them.

Ⅴ. Class Societies: How Cyber Is Checked Is Changing

30 Oct 2026 · ClassNK · Guidance · Cyber security
ClassNK publishes 2nd edition of its Guidelines for Cyber Security Management System for Ships

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.

13 Oct 2026 · Korean Register (KR) · News · Cyber security
KR launches pilot of its Cyber Resilience Platform (KR-CRP) for UR E26 documentation

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 it means on board and in the yard
Both moves point the same way: class societies are turning cyber from a pile of PDFs into structured evidence that can be reused. For yards and owners, the practical step is the same: keep one asset inventory and one set of zone and conduit drawings as the master, and generate each submission from it.

Ⅵ. 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.

ShipPaulJobs | Brief
Official Page · Maritime Cyber & AI Briefing

The official briefing page of ShipPaulJobs, published on LinkedIn as ShipPaulJobs | Brief. Each week the Regulatory Brief explains new and revised rules on ship cyber security, autonomous ships and smart ships, and links to the official documents.

⚓ Join the ShipPaulJobs Community

Join →
Share

Comments

Top Ranked · Last 30 Days

Popular Posts