Each module is verified against the module test specification written during software system design, showing whether it does what it is meant to do and nothing it is not meant to do. Results are documented and corrective action procedures for failed tests are specified. Together with code review, module testing gives the assurance that a module satisfies its specification.
This control maps to 2 controls across 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.