Critical security parameters used for update integrity and authenticity checks, or for protecting communication with associated services, are unique to each device and generated by a mechanism that lowers the risk of automated attacks against device classes. A manufacturer public key used to verify updates is not critical and need not be unique. Status in Table B.1: M F (m) (mandatory, a shall provision; applies only where critical security parameters protect update checks or associated-service communication).
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.