Quality management centres on customers: their requirements are established and built into quality management practices. Requirements of internal and external customers are determined and I&T standards and practices are brought into line with them, and roles and responsibilities for settling conflicts between users and the IT organisation are defined and communicated. For every business process, operational service and new solution, the business's needs and expectations are managed and the quality acceptance criteria kept up to date. Customer requirements are communicated throughout business and IT. The views of customers on how processes, services and solutions are delivered are gathered periodically, and their effect on standards is assessed so that expectations are met. Quality acceptance criteria are recorded so they can be written into service level agreements.
This control maps to 2 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 2 it maps to, and the evidence behind each claim, over MCP and REST.