The ISO 27001 certification process runs in seven steps: scope and gap analysis, build and operate the ISMS, internal audit and management review, a Stage 1 documentation and readiness audit, a short fix window, a Stage 2 operating-evidence audit, and the certification decision. The certificate then runs a three-year cycle of annual surveillance audits and a recertification audit.
Two things most guides get wrong: the two-stage audit model is not defined by ISO 27001 itself but by ISO/IEC 17021-1, the standard certification bodies are accredited against, and the number of audit days is computed from your in-scope headcount under ISO/IEC 27006-1, not negotiated (Cybernion, checked 13-08-2026; standard pages: ISO/IEC 17021-1:2015, https://www.iso.org/standard/61651.html, and ISO/IEC 27006-1:2024, https://www.iso.org/standard/82908.html, both checked 13-08-2026).
The whole process in one table
| Phase | What happens | Who does the work | Rough duration |
|---|---|---|---|
| 1. Scope and gap analysis | Define what the ISMS covers (clause 4.3) and score current practice against every requirement | Founder or first security hire, with ops and engineering leads | No honest published figure; fastest for teams already documenting |
| 2. Build and operate the ISMS | Write the policies, run the risk assessment and treatment (clauses 6.1.2, 6.1.3), produce the Statement of Applicability, and let the system generate records | The same internal owner, often with outside help on design | 2 to 6 months for implementation (IS Partners, checked 13-08-2026) |
| 3. Internal audit and management review | A full internal audit (clause 9.2) by someone independent of the build, then a formal management review (clause 9.3) | An independent internal auditor; top management in the room | 4 to 8 weeks (IS Partners, checked 13-08-2026) |
| 4. Stage 1 audit | The certification body reviews your documented ISMS and decides whether you are ready to be tested | The certification body, with your team answering questions | Days, not weeks; day count scales with in-scope headcount (Cybernion, checked 13-08-2026) |
| 5. Fix window between stages | Close the areas of concern Stage 1 raised | Your team | Usually a few weeks to a couple of months (Cybernion, checked 13-08-2026) |
| 6. Stage 2 audit | The certification body samples evidence and tests whether the documented system is the system you run | The certification body | Days, scaled to headcount (Cybernion); the audit stages together typically run 4 to 8 weeks elapsed (IS Partners, checked 13-08-2026) |
| 7. Certification decision and issue | Nonconformities closed and verified, then the certificate, valid for three years | The certification body | Certificate valid three years, subject to annual surveillance (Cybernion, checked 13-08-2026) |
| 8. Surveillance and recertification | Lighter surveillance audits in years one and two; a recertification audit in year three renews the cycle | The certification body, with your team | Three-year cycle, repeating (Cybernion, checked 13-08-2026) |
Why listen to us
Atoro is an Irish AI governance and cyber compliance consultancy for software companies, and the first consultancy in Europe certified against ISO 42001. Our own certificate is AIMS-AT-120224, issued by A-LIGN under ANAB accreditation, and atoro.io states more than 200 certifications delivered across security and compliance (atoro.io, checked 08-08-2026). We deliver ISO 27001 implementation and independent ISO 27001 internal audits for software companies across Ireland and the UK, and this guide is the sequence we work to.
Phase 1: Scope and gap analysis
Start with a scope statement and a gap assessment, in that order. The scope (clause 4.3, “Determining the scope of the information security management system”, confirmed in the official EN ISO/IEC 27001:2023 table of contents, checked 13-08-2026) decides which people, products and systems the certificate will cover, and the in-scope headcount later sets your audit day count.
A Lead Auditor on r/ISO27001 frames the gap assessment as a scoring exercise: “You need to first perform a gap assessment. Document each requirement in the standard, including those defined in the Management Clauses, and simply measure yourself against how you meet each control. 1: Not Ready 2: We’re there 3: We’re there and have evidence.” (u/dogpupkus, r/ISO27001 practitioner forum language, language source only, ~2025, ). The distinction between “we’re there” and “we’re there and have evidence” is the one that matters, because only the second survives Stage 2.
Keep the scope narrow on a first certification. The pressure behind most projects is specific: enterprise customers asking for the certificate. Scope to what those buyers care about: the product they are buying, the team that runs it, and the data it holds.
Phase 2: Build the ISMS and start the evidence clock
Allow 2 to 6 months for implementation (IS Partners, a US CPA and audit firm publishing its own ranges, checked 13-08-2026).
This phase is where the standard’s actual requirements live: context and scope under clause 4, leadership commitments under clause 5, risk assessment and treatment under clauses 6.1.2 and 6.1.3, operation under clause 8 (structure confirmed via the official EN ISO/IEC 27001:2023 table of contents, checked 13-08-2026). The deliverable pile at the end includes the risk assessment, the risk treatment plan, and the Statement of Applicability, the document the whole audit hangs off: “The Statement of Applicability has to exist before Stage 1” (Cybernion, checked 13-08-2026).
Build for evidence from day one. Every control should produce records as a by-product of doing the work: access reviews, incident records, change logs, meeting minutes. Cybernion’s warning is blunt: “You cannot certify a system that has existed for a fortnight, because there is no operating record to sample.” (Cybernion, checked 13-08-2026.)
No, the ISMS does not need three months of operation before Stage 2
This is printed as fact by ranking pages and it is wrong. Elevate Consult states it verbatim: “The ISMS must have operated for at least three months before Stage 2 to demonstrate consistent functionality.” (Elevate Consult, checked 13-08-2026.) ISO 27001 sets no such fixed minimum.
The correct position, stated plainly by Australian consultancy Cybernion (named author Gaurav Vikash, an IRAP assessor): “ISO 27001 sets no fixed minimum operating period, but Stage 2 needs evidence the system has run, at least one full internal audit and one management review, plus the day to day records the controls generate.” (Cybernion, checked 13-08-2026.) What the auditor needs is an operating record to sample, not a calendar period. A system that has run cleanly for six weeks with a completed internal audit and management review has more certifiable substance than a three-month-old paper system that never operated. Our research found no certification body publishing a fixed minimum operating period for ISO 27001; if yours states one, treat it as that body’s own policy and ask for it in writing before you book.
Phase 3: Internal audit and management review
Before any certification body will audit you, the standard requires a completed internal audit (clause 9.2) and a management review (clause 9.3); clause titles confirmed via the official EN ISO/IEC 27001:2023 table of contents (checked 13-08-2026). The same Lead Auditor puts it in checklist form: “you’ll need to have an Internal Audit performed by a competent 27001 auditor before you can get certified, it’s a requirement of the management clauses” (u/dogpupkus, r/ISO27001 practitioner forum language, language source only).
The internal audit must be genuinely independent of the people who built the system, or it marks its own homework. One implementer’s advice from the trenches: “Take your internal audit seriously. You don’t need to hire a third party, but if you’re doing it yourself, act like the auditor.” (u/watchdogsecurity, r/ISO27001, language source only, ~2025, https://old.reddit.com/r/ISO27001/comments/1ktu7z9/what_tripped_you_up_the_most_during_an_iso_27001/). The management review is a formal meeting with minutes and named outputs, not a corridor chat.
Internal audit depth, including who can do it and how often it must run after certification, is covered in our companion guide (ISO 27001 internal audit requirements).
Phase 4: Stage 1 audit
Stage 1 is the documentation and readiness review: the certification body confirms your ISMS exists on paper and decides whether you are ready to be tested. Stage 2 is the certification audit proper. As Cybernion puts it, “Stage 1 checks the paperwork and readiness. Stage 2 checks reality”, and “The split is set by ISO/IEC 17021-1, the standard certification bodies are accredited against, not by ISO 27001 itself.” (Cybernion, checked 13-08-2026; ISO/IEC 17021-1:2015 standard page, iso.org, checked 13-08-2026.)
A practitioner framing worth holding onto: “Stage 1 is a ‘readiness assessment’ and document audit. There are very few documents that ISO 27001 actually mandates – like, about 12. The auditor will be checking that you have those required docs, and that you have any docs that you have said you need.” (u/larksanon, r/ISO27001 practitioner forum language, language source only, ~Sep 2025, https://old.reddit.com/r/ISO27001/comments/1kqf7k7/iso_27001_stage_1/.) The usual outcome is not failure but “a list of areas of concern the auditor expects closed or matured before Stage 2” (Cybernion, checked 13-08-2026).
One simplification to correct: a UK platform page answers “Can you fail Stage 1?” with a flat “No” (Hicomply, https://www.hicomply.com/blog/iso-27001-stage-1-vs-stage-2-audit-whats-the-difference, checked 13-08-2026). The accurate version is Cybernion’s: “Stage 1 rarely ends in outright failure, but the auditor can decide you are not ready and delay Stage 2 until documentation and records are in place.” A fundamentally deficient ISMS stops the process at Stage 1; a merely imperfect one proceeds with a fix list.
Phase 5: The fix window between Stage 1 and Stage 2
Plan for a gap of a few weeks to a couple of months between the two stages. “The gap exists so you can close the concerns Stage 1 raised; it is not dead time.” (Cybernion, checked 13-08-2026.)
Cybernion adds the two failure modes of the interval: “Too short a gap and you walk into Stage 2 with the gaps the auditor already flagged. Too long and Stage 1 findings go stale and may need rechecking.” Teams that ran an honest internal audit in phase 3 spend this window on a short, known fix list. Teams that treated Stage 1 as a formality spend it scrambling.
Phase 6: Stage 2 audit
Stage 2 tests whether the ISMS works in practice: “The auditor moves from reading documents to sampling evidence, interviewing people, and checking that the controls you selected are actually operating.” (Cybernion, checked 13-08-2026.) This is where the operating records from phase 2 carry you.
Expect “Tell me” and “Show me” questions, and expect the evidence to be ordinary business records. One implementer who had just been through it wrote: “The auditor was perfectly happy to see audit evidence as PDFs or screenshots. In fact, he found screenshots much more understandable than JSON files… The audit was still filled with ‘Tell me…’ and ‘Show me…’ discussions.” (u/chrans, r/SaaS, language source only, ~Aug 2025, https://old.reddit.com/r/SaaS/comments/1msx6ts/what_we_learned_from_our_iso_27001_audit/; the account is tied to a compliance software vendor, so read with that interest in mind, but the content argues against over-relying on tooling, not for it.)
Findings are graded. “A major nonconformity is a requirement that is absent or has broken down… The certificate is withheld until you correct it and the auditor confirms the fix. A minor nonconformity is a single lapse against a requirement that is otherwise met; you submit a root cause and corrective action plan, and it is checked at the next surveillance audit.” (Cybernion, checked 13-08-2026.) Corrective action is a formal requirement, sitting at clause 10.2, “Nonconformity and corrective action”, in the 2022 edition; note for anyone reading older material: the 2022 edition flipped clause 10’s order, so 2013-edition guides put nonconformity at 10.1 (official EN ISO/IEC 27001:2023 table of contents, checked 13-08-2026).
Two pieces of practitioner reassurance for the week before. First: “Remember that all you need to do is avoid any majors. A few minors mean you’ll get your certificate and have a few things to fix by next year. … Majors are nearly always raised against the management clauses, so once you get through that part of the audit (the first day or two) then you can breathe out.” (u/whiteharbourandy, consultant, r/ISO27001 practitioner forum language, language source only, ~Dec 2025, https://old.reddit.com/r/ISO27001/comments/1p57uq3/external_audits_next_week/.) Second, the top-rated answer on Stage 2 preparation: “‘I don’t know but I can find out’ is a perfectly acceptable answer to any question.” (u/Haudyerwhist, same thread.) Do not bluff an auditor; find out and come back.
Phase 7: The three-year cycle: surveillance and recertification
The certificate is valid for three years, subject to annual surveillance audits, and a recertification audit in year three renews it for another three years (Cybernion, checked 13-08-2026).
The shape of the cycle: “After the two stage initial audit, certification runs on a three year cycle, with lighter surveillance audits in years one and two and a recertification audit in year three… Surveillance audits in the following two years sample part of the ISMS rather than the whole, confirming it is still running and improving.” (Cybernion, checked 13-08-2026.) Certification is not a one-off project; it is a three-year operating commitment with an auditor checking in every year.
The misconception to kill here, from a consultant’s vent thread: “they asked chat gpt whether they needed an internal audit for second year or not. Chat gpt said no so they didn’t do it. It’s surveillance audit and the auditors said they can’t go further after Stage 1 because this is a major non-conformity.” (u/wannabeacademicbigpp, r/ISO27001 practitioner forum language, language source only, ~Oct 2025, https://old.reddit.com/r/ISO27001/comments/1nzf6qt/vent_my_dumbass_client_forgot_their_second_year/.) Clause 9.2 requires internal audits at planned intervals across the cycle, certified or not. Skipping the year-two internal audit is a major nonconformity at surveillance. The ongoing obligations are covered in our ISO 27001 internal audit requirements guide.
How long does the whole process take?
Plan for months, not weeks. A named US audit firm publishes an end-to-end range of 3 to 12 months (IS Partners, checked 13-08-2026), and the practitioner consensus on the forums sits inside that: “be realistic about the timeline (around 6-12 months is typical)” (u/lexicalmatt, consultant and lead auditor, r/SaaS, language source only, ~2025, https://old.reddit.com/r/SaaS/comments/1h45waz/about_time_to_get_iso_27001_certificationneed/).
The distortion worth naming honestly: the market contains offers that promise certification in 30 days for USD 1,000. A real buyer-side observation: “I saw this job posted on Upwork today. How is it possible that folks are looking for ISO in 30 days and paying 1,000 USD” (u/ActNo331, r/ISO27001, language source only, ~2025, https://old.reddit.com/r/ISO27001/comments/1m0nsca/iso_in_30_days/). The practitioner answers are the honest costing: “$33 a day for a garbage ISMS implementation? No thanks. Like a proper risk assessment, asset reconciliation and internal audit alone can each take a week’s time.” (u/dogpupkus, Lead Auditor, same thread) and “Having one complete isms copied from another company and just exchange names? Possible. If the auditor sucks or is corrupt enough. But they will have a completely useless heap of (digital) paper and maybe/probably fail the recertification.” (u/LeckerBockwurst, same thread.) A certificate bought that way is a paper ISMS that fails at surveillance, and it will not survive an enterprise procurement check of the kind described in the next section.
What actually sets your timeline is the build phase and the certification body’s calendar, not the audit days themselves. The audit day count is computed from your in-scope headcount under ISO/IEC 27006-1, “not with your revenue” (Cybernion, checked 13-08-2026); the audit-time calculation rules sit in that standard, with the 2024 edition updating them (IAF notice on IAF MD 29, iaf.nu, checked 13-08-2026).
What an accredited certificate means in the UK and Ireland
An ISO 27001 certificate is only as strong as the accreditation behind it. In the UK, UKAS accredits certification bodies for ISO/IEC 27001 (ukas.com information security accreditation page, checked 13-08-2026). In Ireland, INAB accredits management systems certification bodies against EN ISO/IEC 17021-1:2015 and publishes a directory of accredited bodies (inab.ie management systems certification page, checked 13-08-2026).
This matters commercially because enterprise procurement teams increasingly check, and the accreditation bodies tell them how. UKAS’s own FAQ sets out the three checks for a suspect certificate: “Check that the accreditation has been provided by an internationally recognised and authoritative accreditation body (i.e. signatory to the EA MLA or IAF MLA); Check that the certification body does hold valid accreditation from this accreditation body, and that its accredited scope includes the management system standard of concern; Check that the certification body has issued the certificate.” (UKAS FAQ 16, https://www.ukas.com/faqs/, checked 13-08-2026.) UKAS also states that “Increasingly public and private organisations are specifying accredited certification in contracts to ensure traceability of complex supply chains” (UKAS certification body accreditation page, checked 13-08-2026). An accredited certificate travels: UKAS’s FAQ notes certificates issued under an accredited scope “should be recognised in those countries whose accreditation body is signatory to the EA, IAF & ILAC multilateral agreements” (UKAS FAQ 17, checked 13-08-2026). With over 70 000 ISO/IEC 27001 certificates reported across 150 countries in the ISO Survey 2022 (figures as shown on the ISO/IEC 27001 page, iso.org, checked 13-08-2026; later survey editions may exist), verification of the accreditation behind a certificate is routine, not paranoid.
For Irish companies, one equivalence worth knowing: NSAI, Ireland’s national standards body, states verbatim: “In Ireland, ISO/IEC 27001:2022 is adopted as a national standard and published as I.S. EN ISO/IEC 27001:2023.” and “Certification to ISO/IEC 27001:2022 is therefore equivalent to certification to I.S. EN ISO/IEC 27001:2023.” (NSAI ISO/IEC 27001 page, https://www.nsai.ie/certification/management-systems/iso-iec-27001-information-security-management-system/, checked 13-08-2026.)
Finally, check the edition on any certificate you are shown or quoted. The IAF set the transition deadline from ISO/IEC 27001:2013 to ISO/IEC 27001:2022 at 31 October 2025 under IAF MD 26 (iaf.nu, “Changes in the Scope of the IAF MLA During 2024”, checked 13-08-2026), so every current certificate should read ISO/IEC 27001:2022.
Where the certification process goes wrong
An auditor on r/ISO27001 listed the four patterns they see repeatedly, and they are more specific than anything the ranking guides publish (u/SophisticatedMouse42, r/ISO27001 practitioner forum language, language source only, ~2025, https://old.reddit.com/r/ISO27001/comments/1ktu7z9/what_tripped_you_up_the_most_during_an_iso_27001/; note the poster’s claim about audit volume was challenged in-thread, the failure patterns were not):
The ISMS runs in a parallel universe. “Company choose one person to build and maintain ISMS and this person doesn’t have rights to integrate the system to the actual business processes. The ISMS run artificially and separate from the real business ‘just for the certification audit’.” If the system only exists for the audit, Stage 2 finds out, because there is nothing to sample.
Controls yes, management system no. “Company concentrate on 27002 and Annex A (Controls) but not in high level structure and requirements of the standard.” The majors come at clauses 4 to 10, not at Annex A, which matches the consultant reassurance quoted in phase 6.
Tech knowledge projected onto a management standard. “Company project the tech security knowledge to the ISO certification completely ignoring the ‘management’ and ‘system’ part… Something like: ‘we have penetration test, what else do you want from us?’” A penetration test is one input to a risk treatment, not an ISMS.
The internal auditor marks their own work. “Company doesn’t have good internal audit established structure and processes and the internal audit done by the same person (people) who implemented the processes or standards.”
Add two more from lived experience. Management buy-in failure, told as dark humour: “Auditor: ‘Could not demonstrate management buy-in’. Flashback: ‘Yeah, certification might be good, don’t bother us again’. Me: ‘Don’t bother with the proper audit.’” (u/peterdeg, same thread.) Clause 5 puts named responsibilities on top management; a founder’s signature on the policy is not commitment if nobody can show the minutes. And interpretation gaps: “The difference between my interpretation of a control and the auditing firm’s. There were a few instances where I inferred what the control required and assumed what we had in place was sufficient – only to get hit with a minor NC during our Stage 1 audit because it didn’t exactly meet what they were expecting.” (u/watchdogsecurity, implementer, same thread.) Read the requirement, not the summary of the requirement.
What you can do yourself vs where help earns its fee
You can do yourself: the gap scoring against the clauses, first-pass policies, the evidence habits that make records a by-product of work, the internal audit calendar, and the management review logistics. That needs one internal owner with protected time, which is the scarcest resource in most software companies.
Help earns its fee in four places. Scoping: the judgement of what belongs inside clause 4.3 and what the in-scope headcount becomes, which sets your audit days and therefore your certification body fees. Risk methodology: clauses 6.1.2 and 6.1.3 deliberately prescribe no method, so the design choice and its defence at audit benefit from someone who has defended one before. The independent internal audit: clause 9.2 demands objectivity and impartiality, which rules out the build team, and an experienced internal auditor finds your interpretation gaps before the certification body does. Certification body selection and audit management: checking a body’s accredited scope against the UKAS or INAB directories, and managing the sampling and scheduling, changes both cost and elapsed time.
One separation to hold onto whoever you hire: a consultancy prepares you, and only an accredited certification body can audit and certify you. ISO/IEC 27006-1 exists precisely to govern “bodies providing audit and certification of information security management systems” (ISO/IEC 27006-1:2024 standard page, iso.org, checked 13-08-2026). Any provider offering preparation and certification in one contract is grading its own homework.
What the certification itself costs is a separate question with its own market ranges, covered in our ISO 27001 certification cost guide.
FAQs
How do we get ISO 27001 certified: where do we even start?
Start with a scope statement (clause 4.3) and a gap assessment scored against every requirement in clauses 4 to 10, separating “we’re there” from “we’re there and have evidence”. Then build and operate the ISMS, complete an internal audit and management review, and only then book Stage 1. The phase table at the top of this guide is that sequence with who does the work and rough durations.
How long does ISO 27001 certification take?
Published end-to-end ranges from a named US audit firm run 3 to 12 months (IS Partners, checked 13-08-2026), and practitioner forum consensus sits at around 6 to 12 months for a typical build. The build phase and the certification body’s calendar set the timeline, not the audit days, which are computed from your in-scope headcount. Offers of certification in 30 days exist on freelance marketplaces; practitioners describe what those produce as a paper ISMS that fails at surveillance or recertification.
What happens at Stage 1 vs Stage 2?
Stage 1 is a documentation and readiness review: the auditor reads the scope, policy, risk assessment and treatment, Statement of Applicability and early records, and decides whether you are ready to be tested. Stage 2 is the certification audit proper, where the auditor samples operating evidence and interviews control owners. The two-stage split is set by ISO/IEC 17021-1, the standard certification bodies are accredited against, not by ISO 27001 itself (Cybernion, checked 13-08-2026).
Can we pass Stage 1 if we are not fully ready?
Yes, in practice: the purpose of Stage 1 is to decide whether proceeding to Stage 2 is worthwhile, and the usual outcome is a list of areas of concern to close first (Cybernion, checked 13-08-2026). A fundamentally deficient ISMS is different: the auditor can decide you are not ready and delay Stage 2 until documentation and records exist. Claims that you “cannot fail Stage 1” are a simplification.
Does the ISMS have to run for at least three months before Stage 2?
No. ISO 27001 sets no fixed minimum operating period; what Stage 2 needs is evidence the system has run, meaning at least one full internal audit, one management review, and the day-to-day records the controls generate (Cybernion, checked 13-08-2026). The “three months minimum” line printed on ranking pages is not in the standard. If a certification body applies its own minimum, ask for it in writing before booking.
Do we still need internal audits after we are certified?
Yes. Clause 9.2 requires internal audits at planned intervals throughout the three-year cycle, and skipping one is a major nonconformity at surveillance. One consultant’s vent thread describes a client who skipped the year-two internal audit on bad chatbot advice and could not proceed past Stage 1 of their surveillance audit (r/ISO27001, language source only, ~Oct 2025). The ongoing requirements are covered in our ISO 27001 internal audit requirements guide.
What will the auditor ask at Stage 2, and what evidence do they accept?
Expect “Tell me” and “Show me” questions walked through your controls end to end: access reviews, management review minutes, incident records, risk treatment follow-through. Ordinary business records are accepted as evidence; one implementer reported their auditor preferred PDFs and screenshots to raw system exports (r/SaaS, language source only; vendor-linked account). “I don’t know but I can find out” is a perfectly acceptable answer; bluffing is not.
How much does the ISO 27001 certification process cost?
Cost is a separate question with its own market ranges, covered in our ISO 27001 certification cost guide. The structural driver worth knowing here: audit days are computed from your in-scope headcount under ISO/IEC 27006-1, not your revenue, so a narrow first scope reduces certification body fees (Cybernion, checked 13-08-2026).
If this guide has shown you the shape of the work, the honest next step is a scoped start date rather than a generic quote. Atoro delivers ISO 27001 implementation for software companies on a fixed scope agreed before work begins, so the phase plan, the calendar and the certification body booking are settled up front.
Sources
- ISO, ISO/IEC 27001
- ISO, ISO/IEC 17021-1:2015
- ISO, ISO/IEC 27006-1:2024
- EN ISO/IEC 27001:2023 (CEN-CENELEC adoption of ISO/IEC 27001:2022), clause titles
- IAF, Changes in the Scope of the IAF MLA During 2024
- IAF, IAF Publishes MD for Transition to ISO/IEC 27006-1:2024
- UKAS, Information security accreditation
- UKAS, Frequently asked questions
- UKAS, Certification body accreditation
- INAB, Management systems certification
- NSAI, ISO/IEC 27001 Information Security Management System
- Cybernion, ISO 27001 Stage 1 vs Stage 2 audit
- IS Partners, How Long Does ISO 27001 Certification Take