One secure update mechanism can be configured to run automatically: it learns of available updates without user action when connected and either installs them without interaction or processes them after consent with minimal interaction. Status in Table B.1: R F (g) (recommendation, a should provision; applies only where the device's software can be updated).
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.