An independent, third-party certification body · operating to ISO/IEC 17021-1:2015
Verify a Certificate ↗·Global · Remote & on-site·EN
Certification

What ISO 9001 does not do

ISO 9001 is the most widely held management system certificate in the world, and the one most often described as something it is not. A quality guarantee. A mark of a good company. Proof that the work will be right.

It is none of those. Being clear about that is what makes the rest of it worth something.

It does not certify your product

This is the misunderstanding that causes the most trouble, usually in the middle of a dispute.

ISO 9001 certifies a management system: how you decide what the work requires, how you carry it out consistently, and how you respond when something goes wrong. It says nothing about any individual product or job.

A certified company can ship a defective unit. What the standard asks is that it notices, records it, finds the cause, and changes something so the same fault does not arrive again with a different person. A customer who reads the certificate as a warranty has misread it, and a supplier who sells it that way has misled them.

It does not make you better than an uncertified competitor

Certification demonstrates that a system exists and that an independent party examined it. Whether you use it well is up to you.

Plenty of excellent organisations are uncertified, usually because nobody has asked them for it yet. Plenty of certified ones do the minimum. The certificate tells a buyer that the discipline has been examined; it does not rank you against anyone.

A technician checking work against a tablet in a workshop
The audit asks what you did when this check failed, not whether it passed today.

It is not the cost of the audit

The quotation covers the audit days. The real cost is the work around them: writing down how things are actually done, training people on it, running the system long enough to have records worth examining, and acting on what your own internal audit finds.

Organisations that treat the certificate as a purchase discover this at Stage 2, when an auditor asks for evidence of something that has only ever been discussed. Organisations that treat it as a way of working find the audit is the smallest part of the year.

It does not survive neglect

A certificate is a state you maintain. Surveillance audits happen annually, and a certificate can be suspended or withdrawn when the system has stopped being used. A certification body that never withdrew one would not be worth having.

That is a feature. The value of your certificate to a customer depends on the fact that it could be taken away.

When to wait

There are times when our honest answer is not yet.

If the business is about to change shape, a scope written for the old shape will need changing almost immediately. If the system exists only as documents nobody follows, the audit will find exactly that, and a failed Stage 2 costs more than the delay. And if a tender closes in three weeks, certification will not arrive in time, so the useful conversation is about the next tender rather than this one.

What it does do

An accredited ISO 9001 certificate tells a customer that an independent body examined how you work against an international standard, that it will do so again every year, and that the certificate is withdrawn if you stop.

For a buyer who cannot audit you, that is the difference between a claim and evidence. For you, the useful part is rarely the certificate on the wall. It is that the same job gets done the same way when the person who set it up is on leave.

What ISO/IEC 27001 does not do

ISO/IEC 27001 is the certificate most often asked for by enterprise buyers, and the one most often misread by everybody involved. It is worth being clear about what it does not prove, because the gap between what it says and what people hear is where trust gets lost later.

It is not a penetration test

A certification audit examines whether you run an information security management system: whether risks are assessed, controls chosen deliberately, people trained, incidents handled, and the whole thing reviewed and improved.

It is not a technical assessment of your software. Nobody fuzzes your API during a Stage 2 audit. If your question is “can this application be broken into”, the answer comes from a penetration test and a remediation programme, not from us. The two are complementary, and neither substitutes for the other.

An organisation that holds ISO/IEC 27001 and has never had a technical test of its product has a gap. The standard will ask whether you have considered technical testing, which is not the same as having done it well.

It is not a guarantee against breach

No management system prevents a determined attacker, a supplier compromise, or a person doing something careless at the wrong moment.

What certification demonstrates is that the organisation decided what matters, chose controls on purpose, and has a route for noticing and handling the incident when it comes. A certified organisation can be breached on Tuesday. What the standard asks is that the breach is detected, contained, reported where the law requires, investigated, and that something changes afterwards.

Any certificate sold as a promise that nothing will happen is being sold dishonestly, and the first incident will prove it.

A desk at night with a laptop, documents and reading glasses
The scope statement is one paragraph on the certificate, and it decides what the rest of it means.

It is worth exactly what its scope says

This is the part that gets skipped, and it is the most important sentence on the certificate.

Certification covers a defined scope: which parts of the organisation, which services, which locations, which information. A certificate scoped to one product line says nothing about the rest of the business. A certificate scoped to a head office says nothing about the development team in another country.

A narrow scope, honestly stated, is worth more than a broad one that does not survive reading. The buyer you most want to impress is the one who reads the scope statement first, and they can tell the difference.

If you are evaluating a supplier’s certificate, read the scope and ask whether it covers the service you are buying. If it does not, the certificate is not wrong, it is just not about you.

It does not replace your own judgement about suppliers

A certified supplier is a supplier who has been examined by an accredited third party against an international standard. That is genuinely useful, and it is not a substitute for knowing what data you are giving them, what happens if they fail, and what your contract says.

Certification reduces how much you have to take on faith. It does not reduce it to nothing.

What it does do

With all of that said: an accredited ISO/IEC 27001 certificate tells a customer that an independent body with its own accreditation examined your security management system against a published standard, that it will do so again every year, and that the certificate can be suspended or withdrawn if the system stops being used.

For a buyer who cannot audit you, that is the difference between a claim and evidence. For a supplier, it is usually the difference between answering a security questionnaire for three weeks and answering it with one document.

Neither of those is the same as being secure. The organisations that get the most out of certification are the ones that never pretended otherwise.