AI Risk Wire

Practices

What do standards and provider frameworks expect of a frontier model, and who documents it?

24practices tracked
15of the 24 practices are named by at least one standard
0emerging: documented by providers, named by no stored standard
20providers whose documents we read

Each practice opens to show what names it, which providers document it and whether an outside party does. A provider count is out of the providers we read. "Emerging" marks a practice that providers document and no standard we store names; "not yet matched" marks one we have not matched against the standards' items, so we cannot say whether a standard names it.

Governance

Testing

Safeguards

No standard we store and no provider document we read names: Domain safeguards.

Standards we store

We do not store the text of: MITRE ATLAS, NIST AI RMF, EU GPAI Code of Practice, OWASP Top 10 for LLM.

Not shown for now: Input and output classifiers, Prompt-injection defence, Weight and model security. A second, blind reading of which sentences belong to these practices disagreed with the first too often, so their counts are held back until the matching is reviewed.

Compiled from MITRE ATLAS, NIST AI RMF, EU GPAI Code of Practice, OWASP Top 10 for LLM and the safety frameworks providers publish. A practice is attached to a standard where the standard's own stored text names it; for safeguards, the sentence is shown on the control's page. The match was made by a model reading those sentences and is shown as made, not reviewed by a person. "Documented by" counts providers whose model documents state the practice; a practice a provider's documents do not state is not shown as absent.

Every item of each stored standard is listed here or matched above. An unmatched item may be outside the scope of model documentation (for example an organisation's own governance), or a practice we do not yet track.