Requirement 0061 (Part Three: Information, section 9.2 Classifications and Caveats; applies to All entities; dated 31 October 2024; retained from Release 2025): Security classified information is clearly marked with the applicable security classification, and when relevant, security caveat, by using text-based markings, unless impractical for operational reasons. Markings show the classification and, where relevant, the caveat in text, centre top and bottom of each page recommended; colour-based or entity schemes are alternatives only where text is impractical.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.