The regulated company need not review the code of software products that are standard or configurable. Bespoke applications, and bespoke software added to configured products such as interfaces, macros and report generation, are built to defined standards, and whether new software is reviewed during development, and how deeply, is decided by risk, complexity and novelty. A suitable subject matter expert, usually from the organisation doing the development, carries out the reviews, and the regulated company makes sure the resulting corrective actions are followed through to a satisfactory close, as Appendix D4 explains.
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.