Agencies should base the decision to allow an executable to run on the following, in this order of preference: (1) validation of its cryptographic hash; (2) the executable's absolute path; (3) its digital signature; and (4) its parent folder.
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.