The validation approach matches the rigor and independence of requirements validation to the function's assurance level: process independence between requirement definition and validation is defined per level (validation not left solely to the requirement author at the higher levels), and the approach determined in 5.4.2.2 sets which combinations of methods and coverage are applied to each function's requirements, with Revision B allowing a less prescriptive choice of methods than the prior edition.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.