IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems
UR E26 section 4: requirements (identify, protect, detect, respond, recover) – 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-4.4.1: E26 4.4.1 Incident response plan

The owner develops a response plan covering relevant contingencies with predetermined instructions to detect, respond to and limit incidents against CBSs in scope, built from information stakeholders supply during design and construction, aboard by the first annual survey and kept current. It must set out notification of the proper authority, evidence reporting and timely corrective action to confine an incident to its segment, and at least include isolation breakpoints, alarms and indicators of ongoing events, expected major consequences, response options preferring those that avoid shutdown or transfer to local control, and information for independent or local control; it is kept in hard copy.

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

What else in your programme already covers this

This control maps to 3 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.

  • C11 Control 11: Responsible person(s) ashore (UR E26 4.5.1.3)
  • C12 Control 12: Reporting (UR E26 4.4.1.3)
  • C14 Control 14: Incident detection, response and recovery (UR E26 4.4.1 and 4.5.1)

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 section 4: requirements (identify, protect, detect, respond, recover) – IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems

Query this from an agent

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