Keep hard-copy recovery plans aboard and ashore for those handling cyber incidents, as part of the business continuity plan, prioritising the ship's operation and navigation, scaled to ship type and systems. Weigh recovery steps such as wiping drives against loss of evidence and use professional help to preserve it. Software backups aboard or ashore support IT recovery, with offline backups considered because ransomware and worms reach backup devices; OT recovery may need shore help, so the plan should say where and from whom (for example a service engineer at the next port). Response, contingency and continuity plans should complement each other, and ship-to-shore recovery should be tested often.
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.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.