IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems
UR E26 sections 5 and 6: demonstration of compliance and exclusions – IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems

IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems E26-5.3: E26 5.3 During the operational life of the ship

After delivery the owner runs the technical and organisational countermeasures: modifies CBSs under E22 management of change with documentation kept current; keeps the test procedure aligned with CBSs, networks, emerging risks, threats and vulnerabilities; provides procedures, periodic training and drills; maintains hardware and software; and keeps test results and the current procedure aboard for the Society. Before the first annual survey it submits a ship cyber security and resilience programme (policies, procedures and plans for the processes in section 4) for approval and then shows records of implementation; later annual surveys check implementation on request; a change of management company needs re-verification; and special survey includes witnessed testing to the test procedure.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in UR E26 sections 5 and 6: demonstration of compliance and exclusions – IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems

Query this from an agent

The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.