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.3: E26 4.4.3 Network isolation

It must be possible to stop all network traffic into and out of a security zone, where the response plan calls for it, by the stated procedure (for example a physical switch or unplugging a cable to the router or firewall) with instructions and clear marking so staff can do it efficiently; data dependencies that affect function and safety must be identified, showing where a system needs compensating inputs when isolated.

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.

  • 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 1 it maps to, and the evidence behind each claim, over MCP and REST.