Can an AI Vendor Claim ISO/IEC 42001 Compliance Without Certification?

What ISO/IEC 42001 certification actually requires

ISO/IEC 42001:2023 specifies requirements for establishing, implementing, maintaining and continually improving an Artificial Intelligence Management System (AIMS) within an organization. It is a management system standard. An AIMS is a set of interrelated elements that establish policies, objectives and processes for the responsible development, provision or use of AI systems. It is not a product feature or a prescriptive technical control set, so a model or tool is not "ISO 42001 compliant" in the way software might support a particular feature. The claim, if made, is about the organization's management system.

Certification is voluntary. Organizations choose it when they want independent confirmation that their AIMS meets the requirements of the standard. ISO defines certification as written assurance, in the form of a certificate, from an independent body. ISO itself does not carry out certification or issue certificates, and an organization cannot be certified by ISO. A certificate that names ISO as the issuer is therefore inconsistent with ISO's own position.

Certification bodies may be accredited by national accreditation bodies, but ISO's wording does not make accreditation automatic. A certificate alone does not prove the issuer was accredited. Two standards describe the expected conduct of these bodies. ISO/IEC 17021-1 sets requirements for the competence, consistency and impartiality of bodies that audit and certify management systems. ISO/IEC 42006:2025 adds AI-specific requirements for bodies that audit and certify an AIMS, building on 17021-1. Both are published as of November 2026.

ISO/IEC 42001 shares the harmonized structure of other ISO management system standards and uses a risk-based approach closely aligned with ISO/IEC 27001. That familiarity helps reviewers read it, but an ISO/IEC 27001 certificate is a different assurance and does not stand in for ISO/IEC 42001.

Classifying the claim by who gave the assurance

Vendor language often blurs four different situations. The useful question is not whether the words sound strong but who provided the assurance and against what. "Aligned with" and "compliant with" are not defined certification terms, so classify the claim before judging it.

• Self-declared alignment or compliance: Shows the vendor's own view of its position. Provides no independent assurance and is not certification. Treat it as a statement to be tested, not evidence.
• Internal gap assessment: Shows the vendor has compared its practices to the requirements. It is performed by an interested party, so it cannot confirm that requirements are met.
• Third-party attestation or review: Shows an outside party looked at something. Its weight depends on who performed it, the criteria used and the scope. It is not an ISO/IEC 42001 certificate unless a certification body issued one.
• Formal certification: Independent written assurance that the AIMS meets the standard's requirements within the certificate's scope. It adds confidence but does not by itself guarantee outcomes.

When a non-certified claim is acceptable, conditional or disqualifying

Lack of a certificate is not itself a breach of the standard, so the decision rests on your own policy and audit obligations. A practical approach is to set three outcomes before the vendor conversation begins.

Acceptable: your policy does not require certification for the use case, and the vendor describes its position precisely. A statement such as "we have completed an internal gap assessment against ISO/IEC 42001 and have not been independently certified" is accurate and can be weighed on its merits.

Conditional: the vendor holds no certificate but is transparent about it, and supplies internal audit results, management review records and operational control evidence. You may accept this with compensating steps, such as your own review of the evidence, contractual commitments about how the claim is described, and a requirement to notify you of any change in certification status.

Disqualifying: the vendor says it is certified and cannot produce a certificate, or the certificate names ISO as issuer, or the scope excludes the service you are buying, or the vendor will not share the evidence listed above. It is also disqualifying when your own audit or regulatory obligations call for independent certification and the vendor cannot meet that. If a certificate or logo appears to be misused, complaints go to the issuing certification body.

Write the outcome into the due diligence record, with the claim type and the evidence reviewed. That record is what your own auditors will ask to see.

Where runtime evidence helps, and where it does not

Because ISO/IEC 42001 is a management system standard, technical records are best treated as supporting evidence that controls operate. They do not replace an audit by an independent certification body, and they do not turn an uncertified management system into a certified one. A buyer can still ask a practical question the certificate alone does not answer: what was the AI system allowed to do in production, and what did it actually do?

This is where enforcement in the execution path matters. Trussed enforces policy inside the AI execution path, across models, agents, tools, MCP servers, AI sites and coding assistants. It can allow, redact, block, rate limit or escalate for human approval at the level of individual interactions and tool calls. That enforcement generates continuous, audit-ready evidence, mapped to frameworks including NIST and the EU AI Act. Policy is enforced at runtime, not reviewed after the fact, so the evidence reflects what happened rather than what was intended.

That evidence can help a regulated enterprise verify operational controls, whether it is assessing a vendor or answering its own auditors. It supports, and never substitutes for, a vendor's or buyer's ISO/IEC 42001 certification status. Trussed makes no claim of ISO/IEC 42001 certification.