Develop a response plan covering relevant contingencies, kept in hard copy, prioritising actions by safety significance together with shore management. IT-only incidents (load planning apart) are usually security issues: notify designated company contacts, available to the Master, and start investigation and recovery. OT loss can immediately affect safety, so SMS operational and emergency procedures should cover cyber incidents, loss of critical systems and alternative modes, including multiple simultaneous failures; plans should address at least loss of electronic navigation or its data integrity, loss of external data such as GNSS, loss of essential shore connectivity including GMDSS, loss of industrial control systems or their data integrity, and ransomware or denial of service, under ISM chapter 8. Plans should keep existing emergency procedures workable, include communication and escalation to shore support, be simple, and be given to the Master and officers for training. Plans should also state when OT should be disconnected from shore links, with networks designed and documented so the link can be cut quickly (a marked cable or firewall power-off), procedures provided to the Master and crew trained to operate the ship disconnected.
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.