Each modification is documented with the detailed change specification; an impact analysis covering hardware, software, human interaction, the environment and possible interactions; all approvals; progress; test cases for affected subsystems and elements including revalidation data; configuration management history; deviations from normal operation and conditions; and needed changes to procedures and documentation. Manufacturers and suppliers claiming compliance run a system that starts changes when hardware or software defects are found and tells users when a defect affects safety. Modifications use at least the expertise, automated tools, planning and management of the original development, and the modified system is reverified and revalidated.
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.