IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems
IACS UR E27 Updates + Patch

IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems IACS-UR-E27-Updates-Patch-Mechanisms-Maintenance: IACS UR E27 - Equipment Update + Patch Mechanisms + Maintenance + Lifecycle Support

UR E27 requires equipment manufacturers to provide secure update + patch mechanisms supporting ship lifecycle (typically 20-25 years). Update mechanisms: secure update procedure (signed packages + verification + rollback protection + atomic apply + emergency reverse); update verification + integrity check + rollback on failure; update delivery methods (USB + network + over-the-air OTA via satellite for shore-managed CBS + crew-installed) per CBS criticality; vendor lifecycle support commitment in contract (minimum years + security patches + critical patches + EOL planning); coordination with class society survey timing + dry-dock maintenance windows; patch testing on shadow / staging where feasible; emergency patch procedure for actively exploited vulnerabilities. Maintenance: vendor support contract + remote support agreement per UR E26 + on-site maintenance procedures + spare parts + cybersecurity-relevant configuration on replacement parts; replacement equipment same SL + capability as original; end-of-life (EOL) management + retirement decision + migration path before unsupported equipment continues in service. IACS UR E27 + update + patch + lifecycle + EOL + maintenance applies.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.