A consumer relying on a VSA must verify the envelope signature against its preconfigured roots of trust, check that the subject matches the artifact digest, check that the predicate type is the VSA v1 type, check that the verifier matches the key used for the signature, check that resourceUri matches the expected value, check that verificationResult is PASSED, and check that verifiedLevels holds the expected value; it may check further fields. A VSA does not protect against a compromised verifier such as a malicious insider, so consumers should choose the verifiers in their roots of trust carefully.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.