Build application architectures on secure design principles: least privilege, mediation that validates every user operation, and treating all user input as untrusted, for example by checking every input explicitly for size, type and acceptable range or format. Secure design also shrinks the attack surface: close unprotected ports and services, strip out programs and files that are not needed, and rename or delete accounts shipped by default. Implementation Groups: IG2 and IG3 (not in the IG1 baseline; applies from IG2 upward). Asset type: Software. Security function: Protect.
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.