In brief
How to choose an ISO 27001 implementation partner: provider types, who does the work, what you should keep, questions to ask and red flags before you sign.
An ISO 27001 implementation partner is usually one of four kinds: a traditional consultancy, a Big 4 advisory team, a compliance platform with hands-on implementation help, or your own team doing it in-house. The certification body is not one of them: it audits and issues the certificate, and may not consult for the clients it certifies. Choose on three questions: who does the work, what you keep afterwards, and whether the partner is independent of your auditor.
This guide is for CTOs, engineering managers and security leads at software and IT outsourcing companies looking for help to get ISO 27001 certified. If you are still deciding between a consultant and a platform, read compliance platform vs traditional consulting first; this post is about evaluating a specific provider before you sign.
What kinds of ISO 27001 implementation partners are there?
ISO/IEC 27001:2022 is the standard for information security management systems (ISMS). ISO publishes the standard but does not certify organizations; an accredited certification body issues the certificate after an audit. The work before the audit can go to several kinds of provider, each with its own way of working and its own limits.
| Provider type | What they do | Limits to know | Fits when |
|---|---|---|---|
| Traditional consultancy (man-day or fixed-scope package) | Gap assessment, policies and procedures, training, internal audit, support through the certification audit | Deliverable is often a set of Word and Excel files; quality depends on the people assigned | Nobody on the team knows ISMS and you want someone to lead from day one |
| Big 4 advisory (Deloitte, PwC, EY, KPMG) | Risk assessment and security programme design, often as part of a wider risk or governance project | Large teams and broad scope; often more than a small company needs | Groups, banks or enterprises that need ISO 27001 inside a larger governance programme |
| Certification body | Stage 1 and Stage 2 audits, the certificate, annual surveillance audits | May not provide implementation consultancy to clients it audits (ISO/IEC 17021-1) | Your ISMS is running and ready for audit |
| Compliance platform with implementation help (for example pTrackly Managed Compliance) | Software for controls, risks, SoA, policies and evidence, plus a team that guides each phase | Your team still approves and operates controls; no certificate issued | You want the programme to keep running in one system after certification |
| In-house team | Reads the standard, writes the documents, collects the evidence | Research time; lacks the view of someone who has been through many audits | Someone on staff has run an ISMS or worked with auditors before |
Many companies combine two of these, for example an in-house lead with a few days of expert review. What does not change: the implementer and the certification body must be separate.
Why can't the certification body also implement your ISMS?
Certification bodies must stay impartial under ISO/IEC 17021-1, the standard for bodies that audit and certify management systems. It does not allow a certification body to offer management system consultancy, and it treats a close relationship between a consultancy and a certification body as a threat to impartiality. An auditor cannot objectively assess a system their own organization designed.
The risk is not always visible. Some offers bundle "implementation plus certificate", where the consultancy and the certification body are related companies or share owners. Ask the provider directly which certification body will audit you and whether the two have any ownership link or referral fee. How to check a certification body's accreditation is covered further down; the path from Stage 1 to certificate is in how long ISO 27001 certification takes.
What criteria should you use to choose a partner?
The most important criterion is who does the heavy lifting and whether the result reflects how your company actually operates. General "ISO experience" matters less than experience with companies like yours: an ISMS for a SaaS company on AWS looks very different from one for a factory.
- The people: names and experience of those who will work with you, not only the company profile. Ask how many organizations they have taken through an ISO/IEC 27001:2022 audit (the current edition, 93 Annex A controls).
- Your technical stack: cloud, CI/CD, access management, logging. Most technological Annex A controls need someone who understands your systems.
- A written split of work: who drafts, who approves and who collects evidence in each phase.
- Ownership of deliverables: documents, risk register, SoA and evidence belong to you, in a format you can keep using.
- After certification: who helps with annual surveillance audits and the recertification audit at the end of the three-year cycle.
- Independence: no ownership link or revenue share with the certification body that will audit you.
What questions should you ask before signing?
Send the same scope to two or three providers and ask each the same questions. Vague answers to questions 2 and 5 usually mean the work will land on your team near the end.
- Who exactly will work with our team, and which ISO 27001 projects have they supported recently?
- In each phase, who drafts documents, who makes technical changes and who collects evidence?
- Which risk assessment method do you use, and is the risk register built from our real assets?
- How is the Statement of Applicability (SoA) prepared, and who writes the justifications for excluded controls?
- Who runs the internal audit and the management review, and when relative to the certification audit?
- Which certification bodies usually audit your clients, and what is your relationship with them?
- After certification, how do you support surveillance audits, or does the contract end?
What should you keep when the project ends?
The certificate is the result of an audit; what you need to keep is a working ISMS and the records that prove it. If your team cannot answer the auditor on its own at the next surveillance audit, the handover is not finished.
| Record | ISO/IEC 27001:2022 clause | Note |
|---|---|---|
| ISMS scope | 4.3 | Locations, systems and units in scope |
| Information security policy | 5.2 | Approved by top management |
| Risk assessment process and results | 6.1.2, 8.2 | Risk register with owners, based on real assets |
| Risk treatment plan and Statement of Applicability | 6.1.3 | SoA covers all 93 Annex A controls with inclusion or exclusion reasons |
| Evidence of control operation | 7.5, Annex A | Logs, tickets, minutes, configuration screenshots per control |
| Internal audit report and management review minutes | 9.2, 9.3 | Required before the certification audit |
How to write the SoA is in ISO 27001 Statement of Applicability, and how to run the internal audit is in ISO 27001 internal audit guide.
What are the red flags when choosing a partner?
Some offers sound attractive but lead to a certificate your customers will not accept, or an ISMS that exists only on paper. If you see one of these, ask more questions or look elsewhere.
- A promised certificate. Only the certification body decides on certification after the audit; an implementer cannot promise it on their behalf.
- The consultant is also the auditor, or the consultancy and certification body belong to the same group, against the impartiality rules of ISO/IEC 17021-1.
- A certificate from a non-accredited body. Certificates from bodies not accredited by an IAF MLA signatory are often rejected by international customers.
- A template pack with your name swapped in. Policies that do not match your systems and processes show up when the auditor compares them with evidence.
- Internal audit or management review skipped. Clauses 9.2 and 9.3 are mandatory, not optional extras.
- No risk assessment. ISO 27001 is risk-based; a control list with no link to risks means the work is being done backwards.
How do you check a certification body's accreditation?
An ISO 27001 certificate carries weight when the certification body is accredited for ISMS by an accreditation body that signs the IAF Multilateral Recognition Arrangement (IAF MLA). To check:
- Search the certification body or certificate number on IAF CertSearch, the IAF database of accredited certificates.
- Ask the certification body which accreditation body accredits them, and check that the accreditation scope includes ISO/IEC 27001.
- Confirm the accreditation body is on the IAF list of members and signatories for the relevant scope. In Vietnam, the Bureau of Accreditation (BoA, boa.gov.vn) is an IAF MLA signatory; international certification bodies may work under accreditation from UKAS, DAkkS or others.
If a certificate does not appear on IAF CertSearch, ask why and verify directly with the accreditation body before you sign.
What phases does an ISO 27001 implementation cover?
Whichever partner you choose, the work goes through the same phases. Duration depends on ISMS scope, headcount and the controls you already have, so ask any provider to estimate against your real scope.
- Scope and gap assessment: define what the ISMS covers and compare current practice with the standard.
- Risk assessment and SoA: asset inventory, risk register, risk treatment plan and Statement of Applicability.
- Policies and controls: draft and approve policies; make the technical and organizational changes.
- Evidence, internal audit, management review: show controls operate, check yourself, and have leadership review the ISMS.
- Stage 1 and Stage 2 certification audit: the certification body reviews documentation, then assesses the running system.
- Maintenance: annual surveillance audits and recertification at the end of the three-year cycle.
How does pTrackly help with ISO 27001 implementation?
pTrackly is a compliance platform with a Managed Compliance service for ISO 27001: the pTrackly team guides and works alongside your team through ISMS scope, risk assessment, SoA, policies, evidence, internal audit and preparation for Stage 1 and Stage 2. The handover is not a folder of Word files but a programme running on the platform: controls with owners, scheduled evidence requests and a status you can follow through each surveillance audit.
The limits: pTrackly is not a consulting firm and not a certification body, and it does not issue certificates. Your team approves policies and operates controls; an independent certification body decides on certification. Fees come in two separate parts: the platform fee paid to pTrackly, and the audit fee you pay directly to the certification body. Platform features for ISO 27001 are on pTrackly for ISO 27001.
Frequently asked questions
Is pTrackly an ISO 27001 consulting firm?
No. pTrackly is a compliance platform with a Managed Compliance service: the pTrackly team guides and works with your team on the platform, and your team approves and operates the controls. pTrackly does not issue certificates; an accredited certification body does after the audit.
Can a certification body help me implement ISO 27001?
Not for a client it certifies. ISO/IEC 17021-1 does not allow certification bodies to provide management system consultancy, so that their audits stay impartial.
How do I know an ISO 27001 certificate is accredited?
Look up the certificate or certification body on IAF CertSearch, then check that its accreditation body is an IAF MLA signatory with ISO/IEC 27001 in scope. In Vietnam, BoA is an IAF MLA signatory.
Do I have to hire a partner to get ISO 27001 certified?
No. ISO 27001 does not require outside help; many companies implement it themselves with the right tooling and bring in experts only where judgement is needed. The only required outside party is the certification body, if you want a certificate.
What should an implementation partner hand over?
At minimum the ISMS scope, approved policies, risk register, risk treatment plan, Statement of Applicability, evidence per control, internal audit report and management review minutes, in a format your team can keep updating.