Provide, and keep current for the ship's whole life, an inventory of the hardware and software (applications, operating systems, firmware and other components) of every CBS in scope and of the networks joining them to each other and to other systems aboard or ashore, covering at least the systems listed in 1.3.2 and the hardware and software details of UR E27 3.1.1 (optionally system category and zone). Record changes that could add vulnerabilities or alter dependencies or connections, restrict access to confidential entries such as addresses, protocols and ports, and maintain software under the owner's software maintenance and update policy. The integrator submits it at design, keeps it current in construction and proves it complete and accurate at commissioning (including that software is current); in service the owner's programme covers management of change and software updates, evidenced at the first and later annual surveys and demonstrated again at special survey.
This control maps to 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.