The owner prepares a recovery plan to restore CBSs in scope to operation after an incident, including where help is available and from whom, based on stakeholder information, aboard by the first annual survey and kept current, understandable to crew and outside staff, with recovery media or tools aboard. It names the systems involved, sets a recovery time objective for communication and processing and a recovery point objective for data needed to restore safe OT and ship operation, lists potential incidents with procedures, and covers restoring without disrupting redundant or local operation, backup and secure storage, a current logical network diagram, responsible staff, external support contacts and current configurations, prioritising navigation and operation; hard copies are held aboard and ashore.
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.