The assets to protect are the final keys and the key agreement function itself, together with the security-relevant material around them: raw, sifted and error-corrected data produced during a session, the authentication key for classical-channel messages, the keys protecting the link between the key manager and the module when final keys are uploaded, and the module's functions, which must not be misused by illegitimate users.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.