While the system is in use it is reviewed periodically to confirm that it is still validated, meets today's regulatory requirements, is still fit for the use intended and meets company policies and procedures, and that the operational controls exist and work. The frequency is based on a documented risk assessment considering impact, complexity and stability and is adjusted on the basis of incidents and maturity; the review is sample-based and metric-driven, covers actions, procedures, inventory, changes, incidents, user access, security, backup, archiving, continuity, support, audit trails and training, and produces a documented outcome with prioritized actions and a statement on whether the system may stay in use, as detailed in Appendix O8.
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.