If each device ships with its own pre-installed password, those passwords are generated in a way that reduces the chance of automated attacks succeeding across an entire class or type of device, for example through adequate randomness. Counters that increment, or passwords derived from public values such as the MAC address or the Wi-Fi SSID, do not satisfy this. Status in Table B.1: M F (b) (mandatory, a shall provision; applies only where each device ships with its own pre-installed password used for authentication).
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.