Each AI system is kept secure and well governed, with technology and cyber controls sized to the materiality of the use cases it serves and the MAS technology risk requirements applied. Three areas: the deployment environment is secured, with hardened builds, network segmentation and technical measures such as input validation, API authentication, encryption and data loss prevention; access to AI components and infrastructure during deployment is tightly held, with role-based permissions, multi-factor authentication and strong management of privileged accounts, and duties are separated where possible, for example by having different teams train and test; and third-party components such as plugins and APIs are governed, their exposure of data limited, and their security, compliance and operational risks (cyber problems or outages at the provider) watched.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.