NIST AI RMF documents: the policies and records to keep
The AI RMF is voluntary, but these records show you use it: AI policy, roles, system inventory, risk file, test plans, vendor rules and incident logs.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
The AI RMF is voluntary, but these records show you use it: AI policy, roles, system inventory, risk file, test plans, vendor rules and incident logs.
Avoid common NIST AI RMF errors: treating it as a checklist, skipping the AI inventory, ignoring vendor models, no monitoring plan and one-off effort.
The NIST AI RMF has no pass or fail. Run it as a living program with an AI inventory, drift checks, incident review and a monthly cadence you can sustain.
A week by week plan to put the NIST AI RMF into practice yourself, from an AI inventory in week one to monitoring and a target profile by week twelve.
NIS2 Article 21 lists ten measure areas but no control catalogue. This checklist turns them into engineering tasks, owners and the evidence to keep.
A spreadsheet can run a small NIS2 program if it tracks the ten Article 21 areas, the 24 hour clock and suppliers. Know the signs it has stopped working.
NIS2 scoping starts with whether you are in a listed sector and over the size threshold, then which systems and suppliers carry the Article 21 measures.
NIS2 names policy areas, not a template pack. Map each Article 21(2) measure to a document, then add board approvals and an incident reporting playbook.
New to NIS2? Teams misjudge scope, skip board duties, leave the incident clocks untested and ignore suppliers. See what the text says and how to fix each.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.