Understanding Annex A in the Context of AI Agents
ISO/IEC 42001:2023 is the first international management system standard focused specifically on artificial intelligence, published in December 2023. It defines requirements for establishing, implementing, maintaining, and continually improving an AI management system, and it follows the same Plan-Do-Check-Act structure used in other ISO management system standards such as ISO/IEC 27001, including a normative Annex A that lists control objectives and controls. Certification to ISO/IEC 42001 assesses conformance to the overall management system, not to Annex A controls examined in isolation. The exact clause numbering, control titles, and grouping in Annex A are part of a commercially licensed ISO publication, so organizations and auditors should verify precise wording against a licensed copy of the standard or through an accredited certification body rather than relying on secondary summaries. For governance leaders, the practical challenge is that the standard was written to cover AI systems broadly, before autonomous, tool-using agents became common. Publicly available descriptions of the standard do not confirm agent-specific provisions, which means applying Annex A to agent behavior requires deliberate interpretation rather than a direct one-to-one mapping.
The Gap Between Documented Policy and Observed Agent Behavior
Management system audits generally expect two things to be present and consistent: documented policy and evidence that the policy was actually applied over time. This distinction matters more for AI agents than for static AI systems, because agents take autonomous, multi-step actions, invoke tools, and operate under permissions that can change dynamically. A governance policy stating that agents operate under least privilege is not, by itself, audit evidence. What an auditor needs is a demonstrable trail showing which permissions were active at the time of each agent action, which tools were invoked, and whether those actions stayed within approved boundaries. Without runtime instrumentation, an organization typically has only design-time documentation, which is insufficient to demonstrate that controls operated as intended. This is the core gap that governance teams preparing for ISO 42001 audits tend to encounter: policies are mature, but the technical evidence linking those policies to actual agent behavior is incomplete or scattered across systems that were not built to produce audit-ready records.
Mapping Control Themes to Runtime Evidence
- Governance and accountability: agent identity registries and approval records showing who is accountable for each agent's configuration and actions.
- Risk management: incident and escalation logs tied to specific agent actions, not general risk narratives.
- Operational controls and least privilege: permission grant and revocation history, plus tool approval workflow records.
- Monitoring and continual improvement: runtime monitoring output and periodic review records showing controls were checked over time, not only at design.