A requirement is correct to the extent that it has one meaning, can be verified, is not duplicated, agrees with the others and is needed in the set; a set of correct requirements is complete to the extent that it meets the interests of customers, users, maintainers, Certification Authorities and the aircraft, system and item developers across every operating mode and life cycle stage in the defined environment (the checks are expanded in the correctness and completeness clauses that follow).
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.