Does ISO/IEC 42001 Certification Mean Compliance with the EU AI Act?

Why a management-system certificate is not an AI Act conformity result

ISO describes ISO/IEC 42001:2023 as the international standard for AI management systems. Certification is voluntary, is performed by independent certification bodies, and confirms that the organisation's AI management system meets the standard's own requirements. ISO says the standard supports AI compliance by giving organisations a framework to meet their obligations more effectively. It does not say that certification equals legal compliance.

The EU AI Act works differently. It is a regulation with a risk-based approach, and its requirements for high-risk systems attach to the system, to the role of the organisation (provider or deployer) and to how the system is used. A certificate shows that governance processes exist and operate across the scope of the management system. It is not an assessment of whether a given high-risk system meets the Act's requirements.

This distinction matters most when a certificate is presented internally or to customers as the answer to an AI Act question. The accurate statement is narrower: the organisation operates a certified management system, and that system should make AI Act work more structured and repeatable.

Harmonised standards and the presumption of conformity

Recital 121 of the AI Act says that compliance with harmonised standards, as defined in Regulation (EU) No 1025/2012, should be a means for providers to demonstrate conformity with the Regulation's requirements. The Commission's standardisation guidance says harmonised standards will offer legal certainty, and that providers can choose any other framework to demonstrate compliance.

Two points follow. First, the route to a presumption of conformity runs through harmonised standards, not through voluntary certification in general. Compliance teams should not assume that ISO/IEC 42001 confers a presumption of conformity. Second, using another framework is permitted, but it places the burden on the provider to show how that framework's outputs satisfy each requirement. A certificate alone does not carry that argument.

Timing should be tracked as of November 2026. The Digital Omnibus on AI entered into force on 27 July 2026 and changed the application dates for high-risk rules. The current dates are 2 December 2027 for stand-alone high-risk AI systems and 2 August 2028 for high-risk AI systems embedded in products. Earlier timing that depended on the Commission confirming that standards were available no longer applies. The fixed dates mean planning can proceed without waiting on standards, though the status of harmonised standards should still be monitored.

Where a management system helps and where gaps remain

The table maps requirement areas for high-risk systems to what an AI management system can contribute at the organisational level. It is a conceptual gap analysis. A formal mapping of specific ISO/IEC 42001 clauses and Annex A controls to the Act's provisions should be built from the primary texts and reviewed by legal counsel.

• Risk management: An AIMS defines risk assessment and treatment processes across the organisation. Still needed: a documented, system-specific risk management process for each high-risk system, kept up to date across its lifecycle.
• Data governance: An AIMS can set data management policies and responsibilities. Still needed: evidence that the data used by a given system meets the Act's data requirements.
• Technical documentation: An AIMS requires documented information. Still needed: system-level technical documentation in the form the Act requires, per system.
• Record-keeping: An AIMS can require monitoring and retention practices. Still needed: automatic, event-level records generated by the system in operation.
• Human oversight: An AIMS can assign roles and accountability. Still needed: oversight mechanisms built into the system, and records showing that oversight occurred.
• Accuracy and robustness: An AIMS can require performance evaluation processes. Still needed: system-level test results and declared performance for each high-risk system.

Obligations that sit outside a management-system audit

Conformity assessment has no counterpart in a management-system certification. It is a determination about a specific high-risk system, made by the provider under the Act's procedures. An ISO/IEC 42001 audit samples evidence that processes are defined and followed. It does not reach a conclusion about whether an individual system meets the Act.

Risk classification and role determination are also outside the certificate. Whether a system is high-risk, whether it is stand-alone or embedded in a product, and whether the organisation acts as provider or deployer are legal determinations. They drive which obligations apply and which date applies. Each system needs these determinations recorded before a gap analysis is meaningful.

Finally, scope matters. A certificate covers the AI management system as scoped. AI systems, business units or third-party components outside that scope are not covered by it, yet the Act's obligations follow the system and the role regardless of how the certificate is scoped.

Where runtime policy enforcement fits alongside a certified management system

A certified management system sets the rules, roles and review cycles. Runtime controls determine whether those rules hold when a system is operating. The two are complementary: the management system says what should happen, and system-level evidence shows what did.

Trussed enforces policy in the execution path, across models, agents, tools, MCP servers, AI sites and coding assistants. Policy is enforced at runtime, not reviewed after the fact, with outcomes such as allow, redact, block, rate limit or escalate for human approval. Enforcement applies to individual interactions and tool calls. Each enforcement decision produces audit-ready evidence, which is continuous and mapped to the EU AI Act among other frameworks. That evidence is relevant to the record-keeping and human oversight obligations, because escalations for human approval and the decisions around them are captured as they happen.

This does not make Trussed a source of certification, and it does not by itself deliver EU AI Act compliance. Risk classification, technical documentation, conformity assessment and the management system remain the organisation's responsibility. Runtime enforcement and its evidence address one part of the gap: demonstrating what an AI system was allowed to do and what it did.