The organization determines and records the design and development inputs that relate to product requirements. These include the functional, performance, usability and safety needs arising from the intended use; applicable regulatory requirements and standards; relevant risk management outputs; information from earlier similar designs where appropriate; and any further requirements essential to designing the product and its processes. The inputs are reviewed for adequacy and approved. Requirements must be complete and unambiguous, must be capable of verification or validation, and must not contradict each other.
This control maps to 8 controls across 6 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 8 it maps to, and the evidence behind each claim, over MCP and REST.