If a hard-coded identity that differs for each device is relied on for security, it is built to withstand tampering by physical, electrical or software means, for example a network access key stored in a UICC. Status in Table B.1: M F (l) (mandatory, a shall provision; applies only where each device carries its own hard-coded identity used for security).
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.