Requirements for the allocated COTS IP functions are captured to the extent the verification strategy needs (complete DO-254 capture where the strategy is purely requirements-based testing), and derived requirements cover the used functions (parameters, configuration, selectable aspects), deactivation or disabling of unused functions, and correct control and use of the IP per the provider's data. COTS IP requirements are validated within the custom device validation process, and requirements-based verification of them follows DO-254 6.2.
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.