Access to development, test and production environments is controlled on need and interaction between them monitored to prevent unauthorised activity, data contamination or malware; production data used in non-production environments requires approval, personal data protection measures and strict transfer controls. A change management process prevents unoverseen or disruptive alteration of IT assets, assessing business need, urgency, risks mitigated or created, performance impact and effects on connected systems; third-party firmware and software releases come only from verified sources with checksum validation; all changes are approved by the appropriate management level, with a delegated procedure for time-critical changes. Patch management keeps firmware and software current, assessing patch criticality and the criticality of what it patches and setting timeframes commensurate with risk; patches come from verified sources with integrity validated; virtual patches are temporary and reviewed with a view to applying the real update. Changes and patches are tested in a separate environment with stakeholders, defined scenarios and documented results and acceptance, allowing for low-risk patch categories identified by a process. Only authorised, competent staff with strictly controlled rights deploy to production, with the author of any source or binary movement identifiable and code integrity checked between environments; backups are taken before deployment; systems are monitored during deployment with logs captured; rollback procedures with system-specific steps exist; blue-green strategies are used only where appropriate with dependencies and data schemas mapped; and where third parties update production systems the institution is informed of their activities and, for critical systems, obtains independent review.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.