Standards, if the applicant invokes them, join the project's certification basis and plans and may be enforced by tools. Requirements standards (10.2.1) may set methods and criteria for writing and validating requirements, notations, tool use and how derived requirements reach the system process; design standards (10.2.2) may cover representation methods and notations, naming, design methods, tool use, component selection, assessing alternatives and fail-safe and fault-tolerant constructs, and feedback to requirements; V&V standards (10.2.3) set rules and criteria for those processes; and archive standards (10.2.4) govern product data retention, content, format and media.
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.