Regulations · ISO/IEC 42001, AI management systems
ISO/IEC 42001, on every AI call.
Roles, AI systems and their owners, suppliers, model access and every change, recorded in one place and mapped to the standard's controls.
What Vidai enforces or records
Following ISO/IEC 42001.
- Roles, and who holds them
- AI systems and their owners
- Suppliers: the providers and models in use
- Model access, and every change to it, recorded
- An evidence pack mapped to the standard's controls (Enterprise)
Retention it sets
Call records and tamper-evident records kept for at least a year.
Coverage
Each control, shown as it really is.
| Enforced | Every key in scope has it in force. |
|---|---|
| Observed only | It's watched and logged, but some keys only observe. |
| Partly | Some keys have it and some don't, with how many. |
| Nothing in place | Nothing in scope provides it yet. |
| Your organisation's process | Vidai doesn't cover it. Listed so you see what isn't covered: always last, never hidden. |
Which controls a setting covers is our reading, not legal advice; the official text decides, and your auditor makes the call on compliance. Coverage counts AI calls sent through Vidai, not your other systems.
How we start together
Start with one team, on your own AI traffic.
- 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.