The candidate is identified with its version, configuration, the operational profile and conditions of its previous use, and the safety requirements of the target application it is claimed against. This sits in clause 14, whose stated aim, per the SGS quotation, is to guide the argument that an existing item or element has proved itself in use, an alternative route to compliance when field data exist. Requirement text not held.
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.