SHA-256 / FIPS 180-4 evidence for defense AI workflows.
For program office leads and ATO-package owners: use the self-serve API to gate the workflow and link the SHA-256 / FIPS 180-4 requirement to the evidence record for the defense AI workflow under review.
What you get.
SHA-256 / FIPS 180-4 in ATTESTATION.json
Every artifact your defense AI workflow emits is hashed and named; the SHA-256 / FIPS 180-4 control reference sits next to the hash.
Defense anchors named alongside
The evidence record names NIST AI RMF · DoW RAI · OMB M-25-21 together. Internal or external defense compliance sees the regime they care about, not a generic list.
Bit-exact on your hardware
The measurement engine runs in-enclave. Defense evidence rules can permit recompute on customer infrastructure; the record supports that review property by construction.
Related coverage.
SHA-256 / FIPS 180-4 reference · Open the SHA-256 / FIPS 180-4 reference · SHA-256 / FIPS 180-4 capability brief · Defense vertical landing
Every defense-shaped landing for the corpus lives under register 09.
See the Defense evidence workflow path in the Console.
Open the Console to see sealed records; the Docs carry the endpoints.