IACS Recommendation No. 194 - Cybersecurity Controls for Existing Ships
Cybersecurity controls (section 4.2 table) – IACS Recommendation No. 194 - Cybersecurity Controls for Existing Ships

IACS Recommendation No. 194 - Cybersecurity Controls for Existing Ships C1: Control 1: Vessel asset inventory (UR E26 4.1.1; Rec. 190)

Keep lists of the OT systems on board, compiled by hand (for example a spreadsheet), generated by an asset scanner, or both, describing each system and its key attributes such as equipment type, manufacturer, software version and patch level. Rationale by reference to UR E26 4.1.1.2 and IACS Rec. 190.

Maintained by Gerard Blokdyk

What else in your programme already covers this

This control maps to 2 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

BIMCO Cyber Security · 1 control

  • 3.2 IT and OT systems documentation

IACS Unified Requirements E26/E27 - Cyber Resilience of Ships and On-Board Systems · 1 control

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.

Other controls in Cybersecurity controls (section 4.2 table) – IACS Recommendation No. 194 - Cybersecurity Controls for Existing Ships

Query this from an agent

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

MCP endpointAll IACS Recommendation No. 194 - Cybersecurity Controls for Existing Ships controls