The verification plan, PHAC or related plan describes a strategy covering verification of the IP itself (addressing the provider verification risk), verification after the applicant's own design steps such as synthesis and place-and-route, and verification of the integrated IP functions within the device; trustworthy provider test data and standard compliance test vectors may contribute, and at minimum the used functions are covered and unused functions shown correctly disabled and non-interfering.
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.