The device includes a hardware-level mechanism for controlling access to memory, such as an MMU or MPU, execute-never protection, memory tagging or a trusted execution environment, to hinder exploits that execute injected code. Status in Table B.1: R (recommendation, a should provision).
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.