Guides · ISO/IEC 42001
ISO/IEC 42001 is the AI bar you can't backfill.
The AI management system standard is already in enterprise RFPs and vendor security reviews. The operational evidence it asks for has to exist already. Vidai records it from the first call, and is precise about exactly which controls it covers.
What it is
ISO 27001, but for running AI responsibly.
01
It's a procurement reality
It already appears in enterprise RFPs and vendor security reviews. "How do you govern your AI?" is now a question with a standard behind it.
02
Evidence is operational
A large share of the controls are about what your AI systems actually did: logged, monitored, accountable. That evidence is a record, not a policy document.
03
You can't backfill it
You cannot manufacture a year of operational evidence the week before the audit. The record has to have been kept all along.
Where Vidai fits
Vidai gives you the evidence. Your auditor makes the call.
Evidence for 4 controls
For these, the assessor's evidence is Vidai's own data, live and queryable.
Part of 5 more
Vidai supplies the runtime record; you run the surrounding process. Each control says which is which.
29 are your process, and we say so
No inflated coverage score. Controls Vidai doesn't cover are listed, last, never hidden, because precision is what an assessor trusts.
Checked against the standard
The ISO/IEC 42001 mapping has been checked against the official text. The evidence is whatever actually happened.
The mapping, exactly
Four controls where Vidai is the record.
| A.6.2.8AI system recording of event logs | Request logs and the tamper-evident audit log. |
|---|---|
| A.6.2.6AI system operation and monitoring | Every call is recorded: who, when, which model, what was refused and why. |
| A.9.4Intended use of the AI system | Model access limits each key to the models it's meant to use. |
| A.8.4Communication of incidents | Request logs and the audit log are the record of what happened. |
Five where Vidai gives part of the evidence
| A.4.3Data resources | Region rules and compliance routes show where data in calls may be processed. |
|---|---|
| A.4.5System and computing resources | Approved destinations list the models any call may reach. |
| A.6.2.5AI system deployment | Region rules and compliance routes record where calls are deployed. |
| A.7.5Data provenance | Region rules and compliance routes show where data went. |
| A.10.3Suppliers | Approved destinations name the models, and so the suppliers, you've approved. |
The remaining 29 Annex A controls, from the AI policy (A.2.2) to impact assessments (A.5) and data quality (A.7.4), are your AI management system's own processes. The Control room lists them as your organisation's process rather than claiming coverage. Mapping checked against ISO/IEC 42001:2023; the official text decides.
Proof · Evidence pack
Real evidence, and honest about what it is
Request logs, the audit log and reports give you the evidence for each control as records you can query and export, in every edition.
On Enterprise, an evidence pack for ISO/IEC 42001 maps Vidai's records to each of the standard's controls, with the controls that stay your organisation's own. It's evidence for your audit, never a statement that a control is met.
How we start together
Speed up your ISO/IEC 42001 readiness.
- 01
Pick one app or team
Point it at the Control room. One configuration change; nothing else changes.
- 02
Watch for two weeks
Every call priced, checked and recorded. Rules start in observe mode.
- 03
See the evidence
What it cost, what it caught and what it would have stopped, from your own traffic.