Reused systems, equipment and items bring maturity but are not assumed to meet the new installation's requirements: even with no design change, the requirements they were certificated against are validated for the new application and changed as needed, assumptions from the earlier aircraft are managed for the new one, derived requirements, interface compatibility and the operating environment are validated, and broad interface definitions are checked for details such as the load on cables or how data buses are terminated that an earlier use met but the new one may not. Verification against these requirements follows, including integration with the aircraft as needed (see Section 6).
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.