| Asset inventory | E26: inventory of computer-based systems on board, kept up to date through the ship's life. E27: system documentation from the supplier. | § 101.650(b)(3)-(4): inventory of network-connected systems, network map, OT device configuration. | One walk-down builds the inventory and network map both rules ask for. |
| Zones, conduits, and segmentation | E26: security zones and conduits, with the zone boundary devices documented. | § 101.650(h): IT/OT segmentation; every IT to OT connection logged and monitored. | IEC 62443 zone and conduit design, and the firewall work that enforces it. |
| Supplier and supply chain security | E27: security capabilities based on IEC 62443-3-3, secure development aligned with 62443-4-1, class-witnessed type approval. | § 101.650(f): cyber capability in procurement, vendor vulnerability notice, third-party remote connections monitored. | E27 gap assessments and type-approval prep for suppliers; vendor and remote access review for owners. |
| Access control and account security | E26 and E27: user identification, authentication, least privilege, and control of remote and wireless access. | § 101.650(a): lockout, default passwords, MFA, least privilege, separate credentials, removal on departure. § 101.650(i): physical access. | MFA and secure remote access for OEMs, account cleanup, hardening. |
| Detection and monitoring | E26 4.3: networks continuously monitored, with alarms on malfunction or degraded capacity; verification and diagnostic functions on systems and networks. | § 101.650(c)(1): logs secured; § 101.650(h)(2): IT to OT connections monitored; § 101.630(c)(9): monitoring in the Plan. | 24x7 MSP + Metrics and Reports on the IT to OT and vendor connections. |
| Incident response | E26 4.4: owner's incident response plan; local, independent or manual operation; network isolation; fallback to a minimal risk condition. | § 101.650(g)(2): Cyber Incident Response Plan; § 101.620(b)(6): owner ensures it is developed and executed. | CIRP drafts written for the CySO, tested in a tabletop. |
| Recovery and backups | E26 4.5: owner's recovery plan; backup and restore, maintained and tested; controlled shutdown, reset, roll-back, and restart. | § 101.650(g)(4): backups of critical IT and OT, protected and tested. | Backup and restore review, with a restore test on the systems that matter. |
| Management of change | E26 5.3: modifications under the management of change requirements of UR E22, documentation and the test procedure kept current; software updates and patches through MoC. | § 101.630(e): Plan amendments; § 101.630(f)(2)-(3): audits after modifications; § 101.650(e)(3): routine maintenance and KEV patching. | Change and patch procedures the crew and the CySO can follow. |
| Testing and verification | E26 5.2-5.3: ship cyber resilience test procedure at commissioning, kept current, checked at annual and special surveys. E27: type-approval testing. | § 101.635: drills twice a year, exercises yearly; § 101.630(f): annual audit; § 101.650(e)(1)-(2): Assessment and penetration testing. | Test procedures, independent audits, drills, and tabletop exercises. |
| Training | E26 5.3: owner provides periodic training and drills for crew and concerned personnel ashore. | § 101.650(d): all personnel by Jan. 12, 2026, then yearly; key personnel; OT-specific training. | Crew and superintendent training through CambiOS Academy. |
| Reporting | E26 4.4.1: the incident response plan covers notifying the proper authority and reporting evidence of the incident. | § 101.305 and § 101.650(g)(1): report cyber incidents to the National Response Center; § 101.630(c)(13). | Reporting procedures written into the CIRP and practiced in drills. |