The supplier sets up and keeps a formal regime for controlling how software is produced, with defined methods and tools and with rules and conventions covering, for example, permitted languages, standards for coding, naming and version control, and it considers the use of code reviews. Existing software is built by documented build processes that allow for changes to hardware, interfaces and peripherals. Where the supplier configures a product, it works to the governing configuration specification and to the applicable guidance and recommendations, 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.