In this lesson
After this lesson you can:
- Explain what accreditation is, and who checks the organisation that checked you.
- Tell an accredited ISO 27001 certificate from an unaccredited one in about fifteen minutes.
- Ask a certification body the two questions that settle whether its certificate will hold up.
Read first: What ISO 27001 is and how long a certificate lasts
Two documents, one difference.
Put two ISO 27001 certificates side by side and you will struggle to tell them apart. Both name an organisation. Both cite ISO/IEC 27001. Both carry a crest, a signature, an issue date and an expiry date three years later. One of them represents a surveyed management system audited by people whose competence somebody verified. The other represents a transaction.
The difference is not on the face of the document in any obvious way, which is exactly why the market for the second kind exists. A company that wants a certificate rather than an ISMS can buy one quickly and cheaply, and for a while nothing goes wrong. What goes wrong, eventually, is a procurement team at a larger customer whose vendor review includes the step most reviews skip. They look for the accreditation mark, and it is not there.
This page is about that step. It is written for two readers: the buyer holding a supplier’s certificate and wondering what it proves, and the company about to choose a certification body and hoping to pick one whose certificate still means something in three years.
The chain of trust has three links, not two.
Most people picture certification as two parties. You implement an ISMS, an auditor checks it, you get a certificate. That picture is missing the link that makes the whole arrangement worth anything, because it leaves the obvious question unanswered: who checked the auditor?
The answer is a national accreditation body. In India that is NABCB, under the Quality Council of India, whose published ISMS accreditation criteria set out what it requires of a certification body. Other countries have their own, and the arrangement is the same everywhere. The accreditation body does not audit you. It audits the organisation that audits you, against ISO/IEC 27006-1, the standard that specifies what a body must be before it is allowed to certify an information security management system, together with ISO/IEC 17021-1, the general standard for bodies that certify management systems of any kind.
There is a fourth link above that, and it is the one that lets a certificate cross a border. The International Accreditation Forum operates multilateral recognition arrangements under which signatory accreditation bodies undertake to recognise certificates issued by certification bodies accredited by the other signatories. Information security sits inside that structure as a sub-scope rather than a main scope, with ISO/IEC 27001 as the Level 5 document and ISO/IEC 27006 as the Level 4 document, beneath the management systems certification main scope. The practical consequence is the useful part. A certificate accredited in one signatory country is meant to be accepted in the others, which is the entire reason an Indian company’s certificate carries weight with a German customer.
Remove accreditation and that structure does not degrade gracefully. It vanishes. An unaccredited certificate is not weakly recognised internationally. It is recognised by nobody except the company that sold it.
| What is true | Accredited certificate | Unaccredited certificate |
|---|---|---|
| Someone independent checked the certifier | Yes. A national accreditation body assessed them. | No. Nobody audited the auditor. |
| Recognised in other countries | Yes, through the IAF multilateral arrangements. | No. Recognition stops at the issuer. |
| Auditor competence is specified and tested | Yes, under ISO/IEC 27006-1 and ISO/IEC 17021-1. | Set by the issuer, to no external standard. |
| Audit duration follows a published method | Yes. Annex C and D of ISO/IEC 27006-1 govern it. | Whatever was quoted. Often a single day. |
| Surveillance keeps it alive | Yes, on a mandated three-year cycle. | Frequently none after issue. |
| Survives an enterprise vendor review | Normally yes. | Rejected once the reviewer looks for the mark. |
Why the cheap certificate is expensive.
The commercial logic of an unaccredited certificate is seductive and wrong in a specific way worth naming. It is not that the certificate is a scam. It is that it solves the wrong problem. A certificate is not the asset. The asset is a customer’s willingness to stop asking questions, and that willingness is produced by accreditation, not by the PDF.
So the saving is temporary and the cost is deferred. A company that buys an unaccredited certificate in year one typically discovers the gap at the worst available moment, which is during a security review on a deal that is already in late stage. At that point it needs an accredited certificate quickly, and an accredited audit cannot be rushed, because audit duration is itself governed by Annexes C and D of ISO/IEC 27006-1. The money spent on the first certificate is simply gone, and the second one now has a deadline attached.
There is a subtler cost too. An unaccredited audit that finds nothing teaches the organisation that its ISMS is fine. It is the one outcome worse than finding problems, because it removes the reason to look.
Accreditation is granted scope by scope.
This is the trap that catches careful people, and it does not require anyone to lie. A certification body is accredited for named standards, one at a time. A body accredited for ISO 9001 quality management is not thereby accredited for ISO/IEC 27001. It may be accredited for both. It may be accredited for one and not the other and describe itself, perfectly truthfully, as an accredited certification body.
So the sentence to distrust is not a false claim. It is a true claim doing work it cannot do. Read “we are an accredited certification body” as the beginning of a question rather than an answer, and finish it yourself: accredited by whom, and for which standards? Both halves of the answer are published in the accreditation body’s own directory, and the search takes a minute.
What changed in 2024, and why it is newly answerable.
For nearly a decade the relevant standard was ISO/IEC 27006:2015. In March 2024 it was replaced by ISO/IEC 27006-1:2024, which revised what a certification body must demonstrate, adapted the rules to remote and hybrid auditing, and moved the audit-duration material to Annex C, with the calculation methods in Annex D. The 2024 edition also introduced an effective number of persons concept for organisations where many people perform identical activities, which changes how audit time is worked out for large, uniform workforces.
The part that matters to a buyer is the timetable rather than the content. IAF MD 29:2024 set out the transition: accreditation bodies had to be ready to assess against the new edition by the end of December 2024, new initial and extension assessments had to use it from the end of March 2025, and the transition had to be complete by 31 March 2026. Some accreditation bodies set earlier internal dates than the IAF deadline. At least one has said that accreditations not updated by then would be withdrawn.
That date has now passed. It gives you a question you could not usefully ask two years ago, and it is a good one to put to a certification body in writing: is your ISO/IEC 27001 accreditation current under ISO/IEC 27006-1:2024, and which accreditation body holds it? A body that is genuinely accredited answers in one line. A body that is not will answer a different question.
Four checks, about fifteen minutes.
This is the sequence we run on a supplier certificate, and the same sequence read from the other side is a specification for the certificate you want to end up holding. None of it needs a paid database or a relationship with an accreditation body.
Check 1
Find the accreditation mark, not the certifier logo
An accredited certificate carries two marks: the certification body’s own, and the accreditation body’s, usually with an accreditation number beside it. One logo alone tells you nothing. A certificate that says only "certified to ISO 27001" with a single crest is the shape most unaccredited documents take.
ISO/IEC 17021-1 and the accreditation body’s own mark rules
Check 2
Look the certification body up in the accreditation body’s directory
Every national accreditation body publishes a searchable list of the bodies it accredits and the standards each is accredited for. Search the certifier’s name there. If the certifier is not listed, or is listed without ISO/IEC 27001 in its scope, the certificate is not accredited for this standard whatever the mark implies.
the accreditation body’s public directory
Check 3
Verify the certificate in the issuer’s own register
Accredited certification bodies publish a register of the certificates they have issued. Search the certificate number and confirm the status reads current rather than suspended, withdrawn or expired. Trust the register over the PDF, because the PDF cannot tell you what happened after it was printed.
the certification body’s public certificate register
Check 4
Read the scope statement and the edition
Confirm the scope covers the services, sites and systems you are relying on, and that the certificate cites ISO/IEC 27001:2022. A narrow scope on a genuine certificate is the most common surprise in a vendor file, and it is not a defect in the certificate so much as a mismatch with what you assumed it covered.
IAF MD 26:2022, the ISO/IEC 27001:2022 transition requirements
Two notes on doing this in practice. First, trust registers over documents. A PDF records the moment it was generated and tells you nothing about a suspension that happened afterwards, which is why check three is the one not to skip. Second, the IAF operates a global certificate database at IAF CertSearch, which is worth a look as a second source. We lead on the certification body’s own register because coverage in any central database depends on what the issuing body has published there, and an absence can mean nothing at all.
If the checks come back clean and the scope still does not cover the service you are buying, you have not found a bad certificate. You have found a good certificate about something else. Say so plainly to the supplier and ask for one that names the right entity, sites and systems. Reading a certificate properly covers the validity window and the scope statement in more detail.
If you already hold an unaccredited certificate.
Nothing here is an accusation. A large share of unaccredited certificates were bought in good faith by people who asked for ISO 27001 certification, received a document that said ISO 27001 certification, and had no reason to know that an invisible layer was missing. The question now is only what to do about it.
The honest answer is that the existing certificate does not convert. Accreditation is not a sticker that can be added afterwards, because the accredited audit is the thing that was never performed. What you have instead is a head start: if the ISMS behind the certificate is real, much of the work an accredited audit will look for already exists, and the gap is narrower than starting from nothing.
The sequence that works is unglamorous. Establish what your ISMS actually covers today, run a readiness pass against ISO/IEC 27001:2022 to find what an accredited auditor would raise, fix those things, then appoint an accredited certification body and go through Stage 1 and Stage 2 properly. The certification process sets out what each stage involves, and the implementation roadmap covers the work before it.
One thing to avoid: do not let the old certificate keep circulating while the real one is in progress. A supplier who presents an unaccredited certificate to a customer who then checks it has created a trust problem considerably more expensive than the compliance problem underneath it.
Not sure what your certificate proves?
Send us the certificate and the scope statement. We will tell you who accredited the issuer, whether the scope covers what your customers are asking about, and what an accredited audit would raise. No obligation either way.
Key takeaways.
- Accreditation is the missing third link: a national accreditation body assesses the certification body against ISO/IEC 27006-1 and ISO/IEC 17021-1 before its certificates count as accredited.
- An unaccredited certificate is usually genuine and usually lawful. It is also recognised by nobody except its issuer, because the IAF recognition arrangements only reach accredited certificates.
- Accreditation is scope-specific. A body accredited for ISO 9001 can describe itself as accredited and still not be accredited for ISO/IEC 27001.
- ISO/IEC 27006-1:2024 replaced the 2015 edition in March 2024, and the IAF transition deadline of 31 March 2026 has passed. Ask a certification body whether its accreditation is current under it.
- Four checks settle any certificate in about fifteen minutes: the accreditation mark, the accreditation body’s directory, the issuer’s own certificate register, and the scope statement.
- Trust registers over PDFs. A document cannot tell you about a suspension that happened after it was printed.
- An unaccredited certificate cannot be upgraded. The accredited audit is the step that was never performed, so it has to be performed.
Quick check.
Which organisation assesses a certification body before its ISO 27001 certificates count as accredited?
- ISO itself
- A national accreditation body
- The International Accreditation Forum directly
- The client being certified
Check the answer
B. ISO writes standards and certifies nobody. A national accreditation body assesses the certification body against ISO/IEC 27006-1 and ISO/IEC 17021-1. The IAF sits above the accreditation bodies and operates the recognition arrangements between them rather than assessing certification bodies itself. ISO/IEC 27006-1:2024
A certification body appears in a national accreditation body’s directory, but its accredited scope lists ISO 9001 and ISO 14001 only. Is its ISO 27001 certificate accredited?
- Yes, the body is accredited
- No
- Only if the certificate carries the mark
Check the answer
B. Accreditation is granted scope by scope. A body accredited for quality and environmental management is not accredited for information security management, and it can still describe itself truthfully as an accredited certification body. The mark on the certificate does not cure the gap. NABCB BCB 125, ISMS accreditation criteria
Spot the mistake. A supplier’s certificate passes all four checks, so your reviewer records the service as covered by ISO 27001 and closes the review.
Check the answer
The reviewer never read the scope statement against the service being bought.. A valid, accredited certificate can cover a head office while the platform you are buying runs from a different subsidiary and data centre. Nothing is wrong with the certificate. It is simply about something else, and scope rather than validity is the thing that was not checked. Reading a certificate before you rely on it
Sources.
- ISO/IEC 27006-1:2024, requirements for bodies auditing and certifying an ISMSISO catalogue entry 82908, published March 2024, replacing ISO/IEC 27006:2015 and Amd 1:2020Used here: What a certification body must prove, and that the standard is an add-on to ISO/IEC 17021-1
- IAF multilateral recognition arrangement, member list and scope structureInternational Accreditation Forum, member list dated 31 December 2025Used here: ISMS as a sub-scope, with ISO/IEC 27001 at Level 5 and ISO/IEC 27006 at Level 4, and the recognition undertaking
- IAF MD 29:2024, transition to ISO/IEC 27006-1:2024International Accreditation Forum, announcement and mandatory documentUsed here: The transition milestones, and the 31 March 2026 completion date
- IAF MD 26:2022, transition requirements for ISO/IEC 27001:2022International Accreditation Forum, issued 9 August 2022Used here: That a current certificate cites the 2022 edition
- IAF MD 13, competence requirements for ISMS accreditation bodiesInternational Accreditation Forum, Issue 2 Version 2, 19 September 2022Used here: That the accreditation body itself is held to a competence standard
- NABCB BCB 125, accreditation criteria for ISMS certification bodiesNational Accreditation Board for Certification Bodies, Quality Council of India, January 2026Used here: India’s national accreditation body and its published ISMS criteria
Last checked against the ISO catalogue, the IAF’s published mandatory documents and member list, and NABCB’s accreditation criteria on 9 November 2026.