Mechanisms for authenticating users to the device, or for authentication between machines, use best practice cryptography that suits the technology, the environment it operates in, the risk and how it is used: cryptography for which no feasible attack exists using readily available techniques, covering not just the primitives but also how they are implemented and how keys are generated and handled. Status in Table B.1: M F (c) (mandatory, a shall provision; applies only where cryptographic (including password-based) authentication mechanisms are used).
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.
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.