Why the choice matters
An ISO/IEC 27001 certificate is only as useful as the body that issued it. Your customers, partners, and their vendor risk teams will look at the certificate, check who issued it, and decide whether it means anything. A certificate they can verify in a few minutes answers their questions. One they can’t verify creates new ones.
The certification body you choose also shapes the experience: how the audit is planned, how your team’s time is used, and how the three-year cycle of surveillance audits and recertification runs after the first certificate is issued.
This guide covers what to check, what to ask, and what to be cautious about. It applies to any certification body you are considering.
Accreditation and certification are different things
The two words are easy to mix up, and the difference matters.
- Certification is what your organization receives. An independent certification body audits your information security management system (ISMS) and, if it meets the requirements of ISO/IEC 27001, issues a certificate.
- Accreditation is what the certification body holds. An accreditation body, such as ANAB in the United States, formally recognizes that the certification body operates according to international standards, chiefly ISO/IEC 17021-1 and, for information security, ISO/IEC 27006-1, and audits it on an ongoing basis.
Your organization does not become “ISO accredited,” and it does not become “ISO certified” either. It becomes certified to ISO/IEC 27001, by a certification body that should itself be accredited.
Accreditation is not legally required, and some certification bodies operate without it. But a certificate from an accredited certification body is tied to an accreditation body that is a signatory to the international multilateral recognition arrangement, and it can be checked in public registries. That arrangement was run by the International Accreditation Forum (IAF) until January 1, 2026, when IAF and ILAC combined into the Global Accreditation Cooperation Incorporated (Global ACI). IAF marks remain valid during the transition. That independent confirmation of the certification body’s competence is what gives the certificate its weight with customers. Ask your customers whether they require a certificate from an accredited certification body.
Verify the certification body before you sign
This takes a few minutes and is worth doing for every certification body on your list.
- Look it up in IAF CertSearch, the global database of accredited certifications, or with the national accreditation body in its country. An accredited certification body appears there, along with the standards it is accredited for.
- Check the standard, not just the name. Accreditation is granted standard by standard. A body accredited for one ISO standard is not automatically accredited for ISO/IEC 27001, or for other standards such as ISO/IEC 27701.
- Check the version. Certifications are now issued against ISO/IEC 27001:2022. The transition from the 2013 version ended in October 2025.
Know what a valid certificate shows
You will hand this certificate to your customers, so it helps to know what a reviewer looks for. A certificate from an accredited certification body should show:
- Certificate number, a unique reference that can be used to look up the certificate
- The standard, for example ISO/IEC 27001:2022
- The scope, the locations and business operations the certification covers
- The Statement of Applicability version, which ISO/IEC 27006-1 requires on the certificate
- The effective date, when the current certificate took effect
- The expiration date, since a certificate is valid for up to three years, subject to annual surveillance audits
- The accreditation body’s name or mark, identifying who accredited the certification body
- The certification body’s name, identifying who performed the audit
The scope statement deserves extra attention. The certificate shows the location of the certified organization, and the scope must be clear about what happens at each site. Under ISO/IEC 27006-1, when all in-scope activities are performed remotely, the certificate states that. Ask each certification body how it will word your scope, and whether that wording will answer your customers’ questions.
Guidance standards such as ISO/IEC 27017, 27018, and 27019 have no standalone certificate, and ANAB does not accredit certification to them. An ISO/IEC 27001 certificate can reference their controls as a control set in the Statement of Applicability, and it must state that those controls were not used for conformity assessment. Be cautious of anyone offering a separate certificate for them.
Impartiality: the body that certifies you can’t build your ISMS
An accredited certification body must stay impartial. It audits the management system you built. It cannot design that system, write your policies, or run your program. Under ISO/IEC 17021-1, an accredited certification body cannot offer management system consulting to any organization, and it cannot perform internal audits for the clients it certifies. Before accepting a client, an accredited certification body performs client acceptance and impartiality checks to confirm it can audit you objectively.
This is one of the clearest ways to tell certification bodies apart. If a firm offers to build your ISMS and then certify it, or offers a bundle in which the same firm does both, ask how it meets the impartiality requirements of ISO/IEC 17021-1. Implementation help, if you need it, should come from someone other than the body that certifies you.
A related question comes up with compliance software. Many organizations run their ISMS evidence through a GRC platform. A certification body can audit using your platform or its own tools, but it should audit the ISMS you actually operate, and its decision should not depend on which software you use.
Understand how the audit works
ISO/IEC 27001 certification follows a defined cycle. Ask each certification body to walk you through how it handles each step:
- Application and scoping. You describe your organization so the certification body can confirm the ISMS scope, size the audit, and check its impartiality.
- Stage 1 audit. A review of the design of your ISMS and its documentation, including the scope, risk assessment, risk treatment, internal audit, and management review.
- Stage 2 audit. Testing of how your ISMS is implemented and whether it operates effectively, on site or through virtual sessions that show your environments.
- Certification decision. An independent review of the audit results and a decision to grant, or refuse, certification.
- Surveillance audits. In the first and second years after the certification decision.
- Recertification. A recertification audit in the third year, completed before the certificate expires, to begin a new cycle.
Ask who will be on the audit team and how the certification body qualifies its auditors. ISO/IEC 27006-1 requires recognized qualifications, training, and monitored audit experience; an ISO/IEC 27001 Lead Auditor credential is one example. The team should also understand the technology your ISMS covers. Ask, too, whether the same people are likely to return for surveillance audits. A team that already knows your ISMS uses your people’s time better.
Look at how the certification body scopes and quotes
The main things that drive an ISO/IEC 27001 audit are fairly consistent: the number of people working within the ISMS, the number of physical and virtual locations it covers, the complexity of your technology, and any outsourced processes. ISO/IEC 27006-1 sets a starting audit time based on the number of people working within the ISMS scope, including contractors, adjusted for complexity, and limits how far that time can be reduced. An unusually small quote is worth a question.
Before you sign, a certification body should be able to tell you in writing:
- The scope it will certify and how the certificate will word it
- The fee for the initial audit and for the surveillance and recertification audits that follow
- What could change the fee during the three-year cycle
- What it will need from your team, and when
Red flags
None of these alone settles the question, but each one deserves a direct answer:
- The certification body can’t be found in IAF CertSearch or with a national accreditation body, or isn’t accredited for ISO/IEC 27001.
- The certificate it issues carries no accreditation body name or mark.
- The same firm offers to build your ISMS or write your policies and then certify it.
- It offers a standalone certificate for a guidance standard such as ISO/IEC 27018.
- The quote arrives before anyone asks about your people, locations, or technology.
- There is no Stage 1 and Stage 2 audit, or no plan for annual surveillance audits.
- No one can tell you who will be on the audit team or how they are qualified.
Questions to ask every certification body
Bring the same list to every call so the answers can be compared side by side.
- Which accreditation body accredits you, and for which standards? Where can we verify it?
- Are you accredited for ISO/IEC 27001:2022, and for ISO/IEC 27701 if we need it?
- Will your certificate carry your accreditation body’s mark?
- How will you word our scope on the certificate?
- Have you provided, or will you provide, any consulting on our ISMS? How do you check impartiality?
- Who will lead our audits, and how are your auditors qualified?
- Will the same team return for surveillance audits?
- What drives your fee, and what could change it over the three-year cycle?
- Can you audit using our GRC platform, and does using one change anything?
- How do you handle complaints and appeals?
- Can you certify our locations outside the United States?
- How do our customers verify our certificate after it is issued?