The plan must require a configuration change control process that manages the baseline, with consistent criteria for the change types in scope; documented change decisions and temporary changes with their expected duration; testing before production unless a risk assessment supports otherwise; review of changes with their test and risk results before implementation; a fresh API 1164 impact assessment whenever a zone or conduit change might alter the baseline impact assessment; configuration management of cryptographic mechanisms, above all those with expiry or renewal dates; approval before implementation, with key stakeholders and the managers answerable for the controlled process's safety, integrity and reliability in the review and approval; controls to roll back temporary changes; updates to the baseline inventory for permanent changes; current as-built connection and configuration documents, architecture diagrams and zone membership lists; integration with the risk management process; and an emergency change procedure for urgent changes that protect essential functions.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.