Cyber Regulatory Landscape and Industry Responses in the Shipbuilding and Maritime Sector – Part 8: R E26 is ship-level, while SCARP is fleet-level.
Why SCARP Is an Owner’s Responsibility, Not a Newbuilding Document Whenever UR E26 comes up on site, there’s a reaction I hear all the time: “Isn’t that just something the yard prepares during newbuilding to satisfy Class?” That’s not entirely wrong. But it’s only half the story . If you look at International Association of Classification Societies (IACS) UR E26 purely as a documentation requirement , you miss the most important question for owners: “Who is responsible for this ship — and this fleet — for the next 20 years, and how?” This post reframes UR E26 from a shipowner responsibility perspective . 1️⃣ What question does UR E26 really ask? UR E26 is actually very straightforward. It asks only one thing: “Does this ship have cyber resilience?” That’s why UR E26 requires the following six Deliverables : No UR E26 Deliverable Nature 01 Ship Asset Inventory Technical document 02 Zones & Conduit Diagram Network architecture 03 CSDD Design description 04 Ris...