Validation assures that the derived requirements are complete and correct relative to the system requirements the item was allocated, through objective and subjective means, typically throughout the life cycle. Allocated system requirements are assumed validated by the system process, and not every derived requirement needs validation: design decisions that affect safety or functional requirements allocated elsewhere, and decisions or assumptions that constrain later design, are treated as derived requirements and validated, against the allocated system requirements or, if not traceable to a higher requirement, against the design decision they come from. The objectives: derived requirements against which the item is verified are correct and complete; derived requirements are evaluated for safety impact; omissions and errors are fed back for resolution.
This control maps to 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.