Specifications describe what the system will do and how it will do it at the level of detail the system needs: a requirements specification is always required, and functional, configuration and design specifications are added for configured products and custom applications according to risk, complexity and novelty. Configuration is performed and recorded against the configuration specification, custom code is developed to defined standards with design, development and review activities under a defined method, and the regulated company reviews and approves the specifications appropriate to its role, leveraging supplier specifications where the supplier has been assessed; specification records may be held in tools rather than documents.
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.