Skip to main content
COOKIE NOTICECOOKIE CHOICE

We use cookies for analytics (Google Analytics) and ad measurement (Google Ads, including remarketing, and ChatGPT Ads by OpenAI). Strictly necessary cookies keep the site working. See our Cookie Policy for what each one does and how to opt out.

We’d like to use cookies for analytics (Google Analytics) and ad measurement (Google Ads, including remarketing, and ChatGPT Ads by OpenAI), and none of them is set unless you accept. Cookie Policy

ISO 27001 · Appointing an auditor

How to choose an ISO 27001 certification body

Saundhi ChauhanLead AuditorISO 27001 Lead Auditor · ISO 27701 Lead Auditor · ISO 42001 Lead Auditor

12 min readLast reviewed

The short answer

Choose on four things, in this order: the body holds a current ISO/IEC 27001 accreditation you can find in an accreditation body’s directory, it can show you how it calculated your audit days, the named lead auditor has audited systems like yours, and all four engagements across the three-year cycle are priced up front. Price differences between accredited bodies mostly reflect audit days, and audit days follow a published method rather than a negotiation. A quote at a third of the others usually means fewer days, no accreditation for this standard, or cost deferred into surveillance.

A certification body cannot certify a management system it helped build. TCSA prepares the ISMS and coordinates the audit, and the certificate comes from the body you appoint.

In this lesson

After this lesson you can:

  • Separate what a certification body does from what a consultancy does, and why the two cannot be the same organisation.
  • Put five questions to any certification body and read the answers.
  • Compare two quotes on audit days and cycle cost rather than on headline price.

Read first: What accreditation is and the certification process

What a certification body actually does.

A certification body audits your information security management system against ISO/IEC 27001 and, if it holds up, issues a certificate. That is the whole job, and the narrowness is the point. The body does not help you build the system, does not tell you how to fix what it finds, and does not have an interest in your passing. Its product is an opinion, and the value of the opinion depends entirely on its independence from you.

Which is why there is a second organisation above it. A national accreditation body assesses the certification body against ISO/IEC 27006-1 and ISO/IEC 17021-1, and that assessment is what makes the certificate recognisable to anyone who was not in the room. Accredited and unaccredited certification covers that layer in full. This page assumes you have decided you want an accredited certificate and are choosing among bodies that can issue one.

It cannot be whoever built your ISMS.

Before anything else, the rule that removes a whole category of options. ISO/IEC 17021-1 requires the certification body to be impartial, and a body may not certify a management system it designed or implemented. So the convenient single-vendor arrangement, where one firm writes your policies, runs your risk assessment and then signs your certificate, is not available from an accredited body.

If someone is offering it, one of two things is true. Either they are not accredited, in which case the certificate has the problems described on the accreditation page. Or they are describing two separate legal entities under one brand without making the separation clear, in which case ask which entity signs, who accredits it, and how the independence is maintained. Both answers are short when the arrangement is legitimate.

This is a good constraint rather than an inconvenience. A certificate issued by the people who did the work evidences nothing about the work, and your buyers know that even if they never say it.

Five questions that settle it.

Send these in an email. The quality of a certification body shows up less in the answers than in how long they take and how much hedging they contain.

  1. Question 1

    Which accreditation body holds your ISO/IEC 27001 accreditation, and what is the number?

    You want a name and a number you can search in that body’s public directory, with ISO/IEC 27001 explicitly in the accredited scope. Accreditation is granted standard by standard, so a body accredited for quality management is not accredited for information security management, however accurately it calls itself accredited.

    ISO/IEC 17021-1 and the accreditation body’s directory

  2. Question 2

    Is that accreditation current under ISO/IEC 27006-1:2024?

    The 2024 edition replaced ISO/IEC 27006:2015 in March 2024 and the IAF transition deadline was 31 March 2026, which has passed. An accredited body answers this in a sentence. It is the single most efficient question for separating a body that maintains its accreditation from one that mentions it.

    IAF MD 29:2024 and ISO/IEC 27006-1:2024

  3. Question 3

    How many audit days, and how did you calculate them?

    Duration follows a published method rather than a negotiation. Ask for the calculation: the headcount it starts from, how your scope and complexity adjusted it, and the split across Stage 1, Stage 2 and each surveillance visit. A body that cannot show the working is quoting a price rather than planning an audit.

    ISO/IEC 27006-1:2024, Annexes C and D

  4. Question 4

    Who will lead the audit, and what have they audited in our sector?

    Competence attaches to people, not to letterhead. An accredited body can still send an auditor who has never seen your kind of system, and you will spend Stage 2 explaining your architecture instead of evidencing your controls. Ask for the lead auditor and their relevant experience before you sign.

    ISO/IEC 27006-1:2024 competence requirements

  5. Question 5

    What does the three-year cycle cost, in total?

    The initial certification is one of four engagements. Two surveillance audits and a recertification follow, and a cheap Stage 2 followed by expensive surveillance is a known shape. Ask for all four priced together, and for the conditions under which audit days would be revised upward later.

    ISO/IEC 17021-1 certification cycle requirements

Figure 1 What to ask every certification body, before you compare pricesSource: ISO/IEC 27006-1:2024, ISO/IEC 17021-1, and IAF MD 29:2024

Why two quotes differ by half.

Among accredited bodies, most of the difference between quotes is audit days. This surprises people who expect certification pricing to work like consulting pricing, where a brand premium explains a gap. It largely does not, because duration is not a commercial decision.

The method lives in Annex C of ISO/IEC 27006-1:2024, with the calculation approaches in Annex D. It starts from the number of people doing work under your organisation’s control, wherever they are located, and adjusts for the complexity of your scope. The 2024 edition added an effective number of persons concept for organisations where many people perform identical activities, which matters to large and uniform workforces more than to small technical teams. How audit days are worked out walks through the mechanism and what moves it in each direction.

The consequence for you is simple. Two accredited bodies looking at the same organisation should arrive at broadly similar durations, because they are applying the same annex. A quote materially below the others is therefore interesting rather than attractive, and the question that resolves it is not about price at all. Ask both bodies for the calculation and compare the inputs.

Three legitimate reasons a quote can be genuinely lower: the body has an auditor based near you and is not charging travel, it has audited your sector enough that it needs less time to understand your architecture, or it is pricing a cycle rather than a first audit. All three are things a body will happily tell you.

What a real proposal contains.

Hold each proposal against this list. The items missing are usually the items that cost you later.

  1. The accreditation body, the accreditation number, and ISO/IEC 27001 named in the accredited scope.
  2. The scope statement that will appear on the certificate, in the words it will appear in.
  3. Audit days for Stage 1 and Stage 2 separately, with the calculation basis.
  4. Audit days and fees for both surveillance audits and for recertification.
  5. The named lead auditor, or the competence profile of whoever will lead.
  6. What happens if a nonconformity is raised, including the timescale to close it and whether a revisit is chargeable.
  7. Travel and expenses treated explicitly, not as a line to be discussed later.
  8. How a scope change mid-cycle would be handled and priced.

Item six is the one people skip and later regret. A major nonconformity at Stage 2 is a normal event rather than a disaster, but whether closing it needs a chargeable return visit is a commercial term, and it is much easier to agree before the audit than after a finding.

Red flags.

None of these is proof of anything by itself. Each is a reason to ask one more question, and the response to that question is usually decisive.

What you observedAcceptable?What to ask next
Quotes a flat price without asking your headcount or scopeNo. Duration is calculated from both.Ask which annex they calculated from.
Offers certification in days, or "in one visit"No. Stage 1 and Stage 2 are separate.Ask what happens at each stage.
Offers to write your policies and then certify youNo. Impartiality forbids it.Ask them to point to the clause that allows it.
Cannot name the accreditation body or its numberNo. This is a one-line answer.Search the directory yourself.
Will not confirm who the lead auditor isCaution. Competence is person-level.Ask for the lead auditor’s sector experience.
Guarantees you will passNo. A guaranteed outcome is not an audit.Walk away.
Figure 2 Behaviour that should prompt another questionSource: ISO/IEC 17021-1 and ISO/IEC 27006-1:2024

The last row deserves emphasis. A body that guarantees the outcome of its own audit has told you that the audit is a formality, which means the certificate is the unaccredited kind in substance whatever its paperwork says. There is no follow-up question worth asking.

Sector competence, and when it actually matters.

Accreditation makes a body competent to audit an ISMS. It does not make a particular auditor fluent in your architecture, and ISO/IEC 27006-1 treats competence as something held by people rather than by organisations. The practical question is how much of your audit will be spent on explanation.

It matters most where the technology shapes the controls. A payments platform, a multi-tenant SaaS product, a company whose production environment is entirely ephemeral infrastructure, a regulated entity carrying sector obligations on top of the standard: in each case an auditor without that background will ask for evidence in shapes you do not produce, and Stage 2 becomes a translation exercise. It matters least for a conventional office-based operation with ordinary IT.

If your obligations extend beyond the standard, say so during selection rather than during the audit. Our map of which Indian regulators expect ISO 27001 sets out where a sector overlay changes what the auditor should already understand.

You are not married to them.

People over-weight this decision because they believe it is irreversible. It is not. IAF MD 2 sets the minimum criteria for transferring an accredited certificate from one accredited certification body to another, and the receiving body must be accredited for the standard and must satisfy itself that the issuing body was accredited as well. Companies move for ordinary reasons, including auditor continuity, scheduling and price.

What this means for the decision in front of you is that you should optimise for the first cycle rather than for a lifetime. Get the accreditation right, get the audit days explained, get a lead auditor who understands your system, and accept that the rest can be revisited. Transferring a certificate covers how, and the traps around timing it badly.

Want the shortlist run for you?

Tell us your scope, headcount and which markets your buyers are in. We will tell you what audit duration to expect, which questions your situation makes load-bearing, and where sector competence will matter in your Stage 2.

Key takeaways.

  • A certification body cannot certify a management system it designed or implemented. Any single-vendor build-and-certify offer is either unaccredited or two organisations being described as one.
  • Verify the accreditation yourself in the accreditation body’s directory, with ISO/IEC 27001 named in the accredited scope. Accreditation is granted standard by standard.
  • Ask whether the accreditation is current under ISO/IEC 27006-1:2024. The IAF transition deadline of 31 March 2026 has passed, so this is now a one-line question with a revealing answer.
  • Among accredited bodies, most of the price difference is audit days, and duration follows Annexes C and D rather than a negotiation. Ask for the calculation and compare inputs.
  • Price all four engagements in the cycle together. A cheap Stage 2 with the cost recovered across surveillance is a known shape.
  • Competence sits with the named lead auditor, not the brand. Sector fluency matters most where the technology shapes the controls.
  • Agree the nonconformity terms before the audit, including whether a closing revisit is chargeable.
  • The choice is reversible. IAF MD 2 makes transfer between accredited bodies a defined process, so optimise for the first cycle.

Quick check.

  1. A provider offers to write your ISMS documentation and then issue your ISO 27001 certificate. What is wrong?

    1. Nothing, it is efficient
    2. Impartiality rules forbid certifying a system you implemented
    3. It is allowed only for small companies
    4. It is allowed if a different auditor signs
    Check the answer

    B. ISO/IEC 17021-1 requires the certification body to be impartial, and implementing the management system it then certifies destroys that. Rotating which individual signs does not fix it, because the restriction applies to the body. ISO/IEC 17021-1

  2. Which answer tells you most, fastest, about whether a certification body maintains its accreditation?

    1. How many clients it has
    2. Whether its accreditation is current under ISO/IEC 27006-1:2024
    3. Whether it offers a discount
    4. How quickly it can schedule Stage 2
    Check the answer

    B. The 2024 edition replaced the 2015 one and the IAF transition deadline of 31 March 2026 has passed. A body that keeps its accreditation current answers in one line, and a body that does not will answer a different question. IAF MD 29:2024

  3. Spot the mistake. A company picks the cheapest quote, is certified on schedule, and budgets nothing further for three years.

    Check the answer

    Only the first of four engagements was priced.. The cycle is Stage 1 and Stage 2, then two surveillance audits, then recertification. A low initial price with the cost recovered across surveillance is a recognised commercial shape, so all four should be quoted together before you appoint anyone. How long a certificate lasts

Sources.

Last checked against the ISO catalogue, the IAF’s published mandatory documents, and NABCB’s accreditation criteria on 9 November 2026.

Questions people ask.

Can the consultancy that built our ISMS also certify it?
No. ISO/IEC 17021-1 requires the certification body to be impartial, and a body cannot audit a management system it designed or implemented. Any provider offering to do both is either not accredited or is describing two separate organisations without making that clear. The separation is a feature, because a certificate signed by the people who did the work evidences nothing.
Does it matter whether the certification body is based in our country?
Less than people expect. What matters is that its accreditation body is a signatory to the IAF multilateral arrangements for the ISMS sub-scope, because signatories undertake to recognise each other’s accredited certificates. A local body is often easier for site visits and timezone reasons, and that is a practical preference rather than a recognition requirement.
Is a well-known certification body worth paying more for?
Sometimes, and not for the reason usually given. The accreditation is what makes the certificate valid, and that is binary. What a larger body may add is auditor availability, sector depth and a recognisable name in procurement files. Decide whether those are worth the difference for your buyers rather than assuming brand equals validity.
How far ahead should we appoint a certification body?
Early enough to book Stage 2 where you want it, which in practice means while readiness work is still running rather than after it finishes. Lead auditor availability, not your preparation, is usually what sets the certificate date.
Can we change certification bodies after we are certified?
Yes. IAF MD 2 sets the minimum criteria for transferring an accredited certificate from one accredited body to another, and the receiving body must be accredited for the standard and must verify that the issuing body was accredited too. It is a normal process rather than a last resort.
The cheapest quote is a third of the others. What explains that?
Usually one of three things: materially fewer audit days, no accreditation for ISO/IEC 27001, or a low initial audit with the cost recovered across surveillance. All three are discoverable in about twenty minutes by asking for the audit-day calculation and searching the accreditation directory.
Do we have to use the certification body our consultant recommends?
No, and you should understand the basis of any recommendation. A consultancy that coordinates audits works alongside several bodies and should be able to explain why a particular one fits your sector, scope and timeline. A recommendation you cannot get a reason for is not a recommendation.

Get in touch

Book a free consultation or send us your requirements. We respond within 24 hours.

Send us your requirement.

01Your details
02What is it about?
ISO 27001
03Send
Asking about: ISO 27001