Conforming implementations signal which TLS versions they support so that a TLSv1.2 or TLSv1.3 session can be negotiated according to the security policy, the first message exchange being backward compatible so a server can switch version; the profile requires TLSv1.2 or TLSv1.3 and prohibits SSL and earlier TLS versions (RFC 6176, RFC 8996).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.