Skip to content

Guide · Choosing an ISO 27001 consultant

How to choose an ISO 27001 consultant.

Choose an ISO 27001 consultant by testing the ISMS work itself, not the sales deck: how they would draw your scope, which risk method they use, how each line of the Statement of Applicability traces to a risk treatment decision, and what they will do versus what your engineers will do. Then check their ISMS auditor credential with the body that issued it, and rule out anyone who promises the certificate.

Last verified October 30, 2026

The first decision
Scope. It sets audit time, cost and how much of your stack needs controls.
The document that shows competence
The Statement of Applicability, and how it traces to risk treatment.
The edition
ISO/IEC 27001:2022. 2013 certificates ended with the transition on October 31, 2025.
What no consultant can promise
The certificate. The certification body decides.

1. Scope: the first test

The ISMS scope decides which products, systems, teams, locations and suppliers the certificate covers. It also sets the people count the certification body uses for audit time, and the number of systems that need controls and evidence. Customers read the scope statement on the certificate, so it has to cover what they are buying from you.

What to judge. A strong consultant starts from the product or service your customers ask about, then works outward: the production environment, the teams with access to it, the supporting corporate systems, remote staff and the suppliers that touch in-scope data. They show where the boundary meets things outside it and how those interfaces are controlled. Ask them to sketch your scope on the first call. A firm that answers "the whole company" without asking questions has not started thinking. See our scope of certification entry.

2. Risk assessment and treatment

ISO 27001 is risk-driven: the controls you run are supposed to follow from the risks you found and the decisions you made about them. The method has to give consistent, comparable results when your team repeats it, and the people who own each risk make the treatment decisions.

What to judge. Ask which method they use and how your team will run it next year without them. Ask who will own the risks. It should be your managers, not the consultant. Ask to see how a risk moves from the register to a risk treatment plan to a control. A register that arrives pre-filled, with every risk scored "medium", is a template, and auditors find it quickly by asking your people why a score was chosen.

3. The Statement of Applicability and Annex A

The Statement of Applicability is the one ISMS document where competence shows on paper. Under clause 6.1.3 d) it lists the controls you need, the reason for each, whether each is implemented, and why any Annex A control is left out. In the 2022 edition, Annex A holds 93 controls in four groups: 37 organizational, 8 people, 14 physical and 34 technological.

  • Traceability. Each applicable control links to a risk treatment decision. A control with no risk behind it costs you every year.
  • Defensible exclusions. A fully cloud-hosted company may exclude physical controls it does not operate, with the reason recorded, while still managing its cloud providers as suppliers.
  • Evidence per line. For every implemented control, someone should be able to point to the record that proves it runs.

What to judge. Ask for an anonymized Statement of Applicability. Pick three controls that apply to you and ask what an auditor would see for each. Red flags: all 93 marked applicable, a Statement of Applicability delivered before the risk assessment, or exclusions with no reasons.

4. Management-system work versus engineering work

An ISMS has two halves. The management system is scope, risk, policy, the Statement of Applicability, internal audit and management review. The controls themselves are things your engineers and IT staff configure and run: identity and access, logging, backups, change management, vulnerability handling, secure development. Get the line between the two clear before you sign.

What to judge. Get the split in writing: what the consultant writes and reviews, what your engineers configure, and how many hours a week your team carries. Good ISMS designs pull evidence from systems you already run instead of adding parallel records. Ask how they treat your cloud and SaaS providers: what you rely on them for, and how you manage them as suppliers. A compliance platform can hold evidence, but it does not choose your scope or make your risk decisions; ask who tailors what it produces.

5. Independence and credentials

The consultant and the certification body must be separate. Under ISO/IEC 17021-1, an accredited certification body may not provide management system consultancy, may not outsource its audits to a consultancy, and may not market its certification as linked to a consultancy's work. Choose and contract the certification body yourself. The ISO 9001 buyer's guide covers these rules in full.

"Lead auditor" on a profile can mean a course or a current certification. Two ISMS credentials can be checked:

  • Exemplar Global certifies auditors who conduct third-party ISMS audits based on ISO/IEC 27001:2022, under a program built to ISO 19011, and links a public "Find a Certified Professional" directory.
  • CQI|IRCA runs an ISMS auditor certification scheme for auditors using ISO/IEC 27001. Grades depend on audit experience logged after training, and the competence areas include ISMS scope, risk assessment and treatment, and the Statement of Applicability.

Ask for the issuer, the grade and the number, then look it up. A course certificate alone does not show audit experience.

6. The edition, and frameworks next to it

Build to ISO/IEC 27001:2022, which now includes its 2024 amendment on climate action changes. Under IAF MD 26:2023, the transition from the 2013 edition ended on October 31, 2025, and 2013 certifications expired or were withdrawn at the end of the transition. Material that still uses 2013 control numbers is out of date.

Many buyers also face customer questionnaires and other frameworks. Ask how the consultant would organize ISMS evidence so it can be reused elsewhere. SOC 2 attestation is specialist work outside our scope; our ISO 27001 vs SOC 2 comparison explains how the two differ.

The scorecard

Score each consultant 0 (red flag), 1 (unclear) or 2 (strong) on each row. A zero on risk treatment to Statement of Applicability, or on independence, rules a consultant out, whatever the total.

What to judge Strong answer (2) Red flag (0)
Scope Starts from what your customers buy, names the systems, teams, locations and suppliers inside it, and shows where the boundary touches what is outside. "The whole company" by default, or a scope so narrow your customer's data sits outside it.
Risk method A method your team can repeat next year with comparable results, with named risk owners who make the decisions. A risk register delivered pre-filled, with every risk scored the same.
Risk treatment to SoA Every applicable control traces back to a treatment decision, and every exclusion has a reason you could defend. A Statement of Applicability written before the risk assessment, or all 93 controls marked applicable.
Evidence Evidence drawn from the systems you already run, with an owner and a frequency for each record. A wall of manual spreadsheets nobody will keep up after the audit.
Engineering split Clear lines: what the consultant writes and reviews, what your engineers configure, and how the two meet. Vague promises to "handle the technical side", or policies that ignore how your stack works.
Edition Builds to ISO/IEC 27001:2022 with its 2024 amendment, and Annex A in the 2022 structure. 2013 control numbers or 2013-era templates.
Credentials An ISMS auditor credential you can look up with the body that issued it. "Lead auditor" with no issuer, number or register.
Independence You choose and contract the certification body yourself. A bundle that includes the certificate, or any offer to certify you.

Eight questions for the first call

  1. Walk me through how you would draw our ISMS scope. What would you leave out, and why?
  2. Which risk assessment method do you use, and how will our team run it next year without you?
  3. Show us an anonymized Statement of Applicability. How does each line link to a risk treatment decision?
  4. Pick three Annex A controls that apply to us. What evidence would an auditor see for each?
  5. Which work is yours, and which is our engineers'? Who configures, who documents, who reviews?
  6. How do you treat our cloud and SaaS providers: as inherited controls, as suppliers, or both?
  7. Who runs our first internal audit, and who audits the parts of the ISMS you built?
  8. Which ISMS auditor credential do you hold, from which body, and where can we look it up?

How a sound ISO 27001 engagement is structured

Sound engagements are priced in phases, so you can stop after any one.

  1. Scope and gap analysis. The ISMS boundary, what already runs against Annex A, and a dated plan. A standalone gap analysis is typically in the low five figures.
  2. Risk and Statement of Applicability. Your method, your risk owners, the treatment plan, and a Statement of Applicability that traces to it.
  3. Build and run. Policies people use, controls in operation, evidence flowing, and awareness training for everyone in scope.
  4. Internal audit and management review. Both completed before Stage 1, by people who did not build the part they audit.
  5. Certification audits. You choose the certification body. The consultant prepares your team for Stage 1 and Stage 2.
  6. After certification. Surveillance audits, yearly risk updates and internal audits, and scope changes as the business grows.

The certification body bills separately, and its fees are set by the certification body. Our guide to ISO 27001 certification cost, timeline and steps explains how audit time is set and what has to exist before Stage 2.

How we work

Use the scorecard on us too. Our ISO 27001 consulting starts with a gap analysis you can buy on its own. We then handle the management-system work with your team: scope, risk assessment and treatment, the Statement of Applicability, policies, the first internal audit (staffed so no one audits work they built) and the management review, and preparation for Stage 1 and Stage 2. Your engineers configure the controls, and we review the work and the evidence. You own every document and record. We are headquartered in the Kansas City metro, working with companies across the US and Canada, on site and remotely. Start the conversation.

Common questions

How do I choose an ISO 27001 consultant?

Test them on the ISMS work itself. Ask how they would draw your scope, which risk method they use, and how each line of the Statement of Applicability traces to a risk treatment decision. Ask what they do and what your engineers do, and how evidence will come from systems you already run. Check their ISMS auditor credential with the issuing body. Rule out anyone who promises the certificate or offers to issue it.

What does an ISO 27001 consultant do?

A consultant helps you define the ISMS scope, run the risk assessment and treatment, write the Statement of Applicability, policies and procedures, set up evidence, train your people, organize the first internal audit so that no one audits work they built, support the management review, and prepare for Stage 1 and Stage 2. Your engineers still configure the systems. An accredited certification body runs the audits and makes the decision.

How much does an ISO 27001 consultant cost?

It depends on scope: the people, systems and locations inside it, how many controls already run with evidence, and how much your team carries. A standalone gap analysis is typically in the low five figures. The certification body's audit fees are a separate cost, set by the certification body from audit time under ISO/IEC 27006-1:2024.

Do we need a consultant to get ISO 27001 certified?

No. The certification body runs the same audits either way. Companies that do it in house need someone who knows the standard and has protected time for risk assessment, the Statement of Applicability, evidence and the internal audit. A common middle path is an outside gap analysis and plan, with your team doing the build.

Can an ISO 27001 consultant guarantee certification?

No. The certification decision belongs to an accredited certification body, after its own audit. A consultant can get your ISMS, records and people ready. Treat a promise that you will be certified, or a pass-or-refund offer, as a red flag.

Can a consultant write our Statement of Applicability for us?

A consultant can draft it with you, but the decisions behind it have to be yours. The Statement of Applicability lists every Annex A control, whether it applies and is implemented, and the reasons for each inclusion and exclusion. Those reasons come from your risk treatment decisions, and auditors ask your people to explain them.

Related

Sources

Changelog

  • 2026-10-30 — Published. Edition and transition facts from IAF MD 26:2023 and ISO; Annex A structure from the ISO/IEC 27002:2022 contents; Statement of Applicability from ISO/IEC 27001:2022 clause 6.1.3 d); impartiality from ISO/IEC 17021-1:2015 clause 5.2; credentials from Exemplar Global and CQI|IRCA.