Debug interfaces are disabled, or protected by best practice authentication or access control, so attackers cannot place the device in debug mode and modify its code. Interfaces not needed after market placement are disabled in software by default and cannot be re-enabled by the user; ones needed intermittently may be enabled only through protected means. Status in Table B.1: M F (q) (mandatory, a shall provision; applies only where debug interfaces exist).
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.