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.5.2: E26 4.5.2 Backup and restore capability

CBSs and networks in scope must support timely, complete and safe backup and restore, with backups regularly maintained and tested, so the ship can regain navigation and operation from a secure copy or image, with sufficient information and facilities, backup of data (offline backups considered against ransomware and worms) and backup plans setting scope, mode, frequency, medium and retention.

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.

  • C13 Control 13: Backup and systems restore (UR E26 4.5.2)

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.