AI Security

AI governance guides

Owners, purposes, provider decisions, reviews, and the evidence NIST AI RMF, ISO/IEC 42001, and the EU AI Act ask for.

What these guides cover

AI governance is the set of decisions an organization makes about the AI systems it builds and uses: which systems exist, who owns each one, what each is for, which providers are allowed, and how often those decisions are reviewed, together with evidence that the decisions are followed. NIST AI RMF, ISO/IEC 42001, and the EU AI Act ask for the same core records in different words: an inventory, named owners, documented purposes, third-party decisions, monitoring, and logs. An inventory built by survey goes stale within weeks. Built from what devices connect to and what agents report, it stays current and states its own coverage. Runtime enforcement then carries the decisions out, and its decision records become the evidence.

Risks

  • An AI inventory that misses the tools people actually use
  • AI systems with no owner, or an owner who has left
  • Provider policies written down but never enforced
  • Evidence assembled by hand the week before an audit

Control priorities

  • An inventory built from observation, with stated coverage
  • One owner and a documented purpose per AI system
  • Provider decisions enforced on devices, with violations counted
  • Framework evidence exported from the records themselves

Recommended reading order

Start with what AI governance is, then use the framework-neutral checklist to see the shared controls. Read the crosswalk to choose a framework, then its guide and checklist: NIST AI RMF, ISO/IEC 42001, or the EU AI Act. The how-tos cover the inventory, owners, provider decisions, reviews, and evidence export in the order you would do them.

Guides in this collection

AI governance

What is AI governance? Owners, decisions, and evidence for AI systems

The four things AI governance frameworks deal with, and how to keep the record current instead of rewriting a spreadsheet.

Read guide
AI governance

AI governance checklist: 20 controls for teams shipping AI

Inventory, owners, provider decisions, reviews, runtime controls, and logs, each mapped to NIST AI RMF and EU AI Act references.

Read guide
AI governance

NIST AI RMF vs ISO 42001 vs EU AI Act: how they compare and overlap

A crosswalk of the shared AI governance controls, the EU AI Act dates as amended, and which framework to start with.

Read guide
AI governance

NIST AI RMF for engineering teams: what each function asks for

A plain guide to the NIST AI RMF 1.0 functions and where engineering evidence comes from, including the Generative AI Profile.

Read guide
AI governance

NIST AI RMF checklist: GOVERN, MAP, MEASURE and MANAGE

Every NIST AI RMF subcategory in four tables, with the owner of the evidence and the Arcjet record where one exists.

Read guide
AI governance

ISO/IEC 42001 explained: the AI management system standard for software teams

Clauses 4 to 10, control topics in our own grouping, and the line between management-system work and evidence a running system can record.

Read guide
AI governance

ISO 42001 Annex A checklist: evidence for each control topic

Clauses 4 to 10 and the control topics as checklist rows, in our own words, with the evidence owner for each.

Read guide
AI governance

EU AI Act for deployers: what companies that use AI must do

Most software companies are deployers of third-party AI and providers of the agents they ship. Here is what each role owes.

Read guide
AI governance

EU AI Act checklist for providers and deployers

Every EU AI Act obligation by article, split by role, with who usually produces the evidence and which rows Arcjet records.

Read guide
AI governance

How to build an AI inventory that stays current

A survey can't tell you what it missed. An observed AI inventory states its own coverage.

Read guide
AI governance

How to approve or prohibit AI providers, and enforce the decision

Prohibiting the ChatGPT app while approving the OpenAI API is one decision, not two policies.

Read guide
AI governance

How to assign owners to AI systems, and what an owner is accountable for

An owner who has left the company is no owner. Ownership has to lapse on its own.

Read guide
AI governance

How to export AI governance evidence to Vanta, Drata, or your GRC tool

Back each AI governance control in your GRC tool with the record from the control itself.

Read guide
AI governance

How long to keep AI system logs: EU AI Act, NIST and HIPAA

Six months is the EU AI Act's floor for high-risk systems. What sets your real period, and what each record should hold.

Read guide
AI governance

AI governance for coding agents: Claude Code, Copilot, Cursor and Codex

Coding agents run shell commands with your engineers' credentials. Put them in the AI inventory, with an owner and decisions their hooks enforce.

Read guide
AI governance

How to classify AI systems by risk, including EU AI Act categories

You tier AI systems, not models: the same model can power a minimal-risk coding assistant and a high-risk hiring tool.

Read guide
AI governance

How to detect when an AI system drifts from its documented purpose

An AI system's record says what it's for. Its runtime records say what it does. Purpose drift is the gap, and the owner should hear about it.

Read guide