As suits the software, the requirements cover: function and capability (performance, physical characteristics, computing environment, compatibility with upgrades and with SOUP versions); inputs and outputs of the software system (characteristics of data, ranges, limits and defaults); interfaces to other systems; alarms, warnings and messages to the operator generated by software; security (protection of sensitive information against compromise, authentication, authorization, audit trails, integrity of communication, protection against malware); usability engineering requirements where human error could matter; data definitions and database requirements; installation and acceptance at the site of operation; how the software is operated and maintained; IT-network aspects (alarms over networks, protocols, loss of network services); maintenance done by users; and regulatory requirements. They may overlap and need not all be known at the outset. Applies to classes A, B and C.
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.