NIST SP 800-218A PS.2.1: Provide hashes or signatures for models, components and changes (Medium)

What does PS.2.1 require?

The integrity verification information made available to acquirers includes cryptographic hashes or digital signatures for a model and its components, artefacts and documentation, and digital signatures for changes to the model.

Maintained by Gerard Blokdyk

Other controls in Protect Software (PS) – NIST SP 800-218A

PS.1.1 Store all code and model elements on least-privilege terms, with reward models and weights kept apart (High)
PS.1.2 Protect training, test, fine-tuning and alignment data from unauthorised access and change (High, new task)
PS.1.3 Protect model weights and configuration parameters (High, new task)
PS.3.1 Archive release files with versioned infrastructure tools, model selection rationale and training process records (Low)
PS.3.2 Provenance data for models, components, derivatives and the data behind them (Medium, modified task)

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpoint All NIST SP 800-218A controls