What does a supplier holding it actually tell us?

That somebody there owns how AI gets managed, that decisions follow a describable process, and that the process is maintained rather than written once. It tells you nothing about whether a specific product suits your work, which remains a separate question you have to answer yourself.

How does it relate to the security certification we already hold?

It follows the same management system shape, so the structure will be familiar and much of the surrounding discipline carries over from one to the other. It remains a separate certification covering a different subject, so holding the security one does not mean holding this one.

Glossary

ISO 42001

An international standard for how an organisation manages its use of AI, certifying the way the organisation runs rather than any particular system.

In plain terms

A standard about how a company manages AI, not about whether any particular AI is good. A certified organisation has shown it has a way of deciding, checking and improving. It has not shown that any given tool works.

Why it matters

Because supplier questionnaires have started asking for it, and because what it means is routinely overstated in both directions. It is neither proof that a product is safe nor an empty badge: it is evidence that somebody inside the organisation owns the question and has a process behind the answer.

How it works

It is a management system standard, and the title says so. What gets established, implemented, maintained and continually improved is the organisation's system for managing AI, which is a different object from any model or product the organisation ships.

It reaches organisations that only use AI. The stated applicability covers any organisation, of any size, type and nature, that provides or uses products or services utilising these systems, so buying rather than building does not put you outside its scope.

Continual improvement is part of the requirement rather than an aspiration. That is what makes it a live commitment: the certified thing is a working process, so it has to keep working, and an organisation that stopped doing the thing has a problem the certificate will eventually reflect.

It shares its shape with the security standard many buyers already know. Anybody who has been through that will recognise the structure, which is deliberate and makes it cheaper to adopt alongside one already in place than to start from nothing.

What it evidences is ownership and process. Somebody is accountable, decisions get made in a describable way, and there is a record. That is a genuine and bounded claim, and it is worth more in a supplier conversation than most of what is offered alongside it.

Scope is the part a buyer should read rather than assume. A certificate describes the system it was granted against, so what matters is whether the deployment you care about sits inside the scope described, and a deployment that grew after the assessment may not.

What it does not evidence is that any particular system behaves well. A certified organisation can ship something unsuitable for your use, and the certificate is untouched by that, because the standard was never making a claim about outputs.

What a certificate covers

It is worth being precise about why the left-hand column is still worth paying for, because the correction can read as dismissal. An organisation with a working management system is one where somebody can tell you who decided to deploy a tool, what was considered, what happens when it misbehaves and who would notice. Ask those four questions of an organisation without one and you get shrugs and a redirect to the vendor's marketing page. That difference is real and it predicts how a supplier will behave when something goes wrong, which is the moment you actually care about. What it will never do is substitute for testing the thing on your own work. The two are complementary and the certificate is the cheaper of them, which is exactly why it gets asked for first and why it quietly ends up standing in for the more expensive check that nobody scheduled.

Seen in the wild

A supplier questionnaire asking for it alongside the security certification.
Vanta
An assistant deployment that the management system has to account for.
ChatGPT
A search deployment reaching further than the certified scope described.
Glean

Common misconceptions

People assume

It certifies that an AI system is safe.

In fact

It certifies the management system: how an organisation establishes, maintains and improves the way it handles AI. A certified organisation can still ship something that does not suit your use, and the certificate says nothing about that.

People assume

It is for companies that build AI.

In fact

The stated applicability covers organisations that provide or use products or services utilising these systems, of any size or type. Using AI without building any is squarely inside the scope rather than outside it.

Questions

What does a supplier holding it actually tell us?: That somebody there owns how AI gets managed, that decisions follow a describable process, and that the process is maintained rather than written once. It tells you nothing about whether a specific product suits your work, which remains a separate question you have to answer yourself.
Does it apply to us if we only use AI tools?: Yes. The stated applicability covers any organisation, regardless of size, type and nature, that provides or uses products or services utilising these systems. Whether pursuing certification is worth it is a commercial judgement, but scope is not the reason to decline.
How does it relate to the security certification we already hold?: It follows the same management system shape, so the structure will be familiar and much of the surrounding discipline carries over from one to the other. It remains a separate certification covering a different subject, so holding the security one does not mean holding this one.