The steps at a glance
This is an outline of what every ISO 27001 implementation has to cover, in a sensible order. It isn’t our project playbook, and in practice the steps overlap rather than run strictly one after another. What it does show is what the certification auditor will expect to find by the end.
| # | Step | Clauses | What you end up with | Relative effort |
|---|---|---|---|---|
| 1 | Confirm the trigger and target date | – | A reason, a date and what the certificate must cover | Low |
| 2 | Leadership commitment and a named owner | 5.1, 5.3 | A sponsor, an ISMS owner and defined roles | Low |
| 3 | Scope and context | 4.1–4.3 | Scope statement, issues, interested parties and their requirements | Low to medium |
| 4 | Gap assessment | All | What exists, what’s missing and a plan | Medium |
| 5 | Risk assessment | 6.1.2, 8.2 | A method, acceptance criteria and a risk register with owners | Medium |
| 6 | Risk treatment and Statement of Applicability | 6.1.3, 8.3 | Risk treatment plan, SoA and owner approval | Medium to high |
| 7 | Policies and procedures | 5.2, 7.5 | An approved, right-sized document set | Medium |
| 8 | Implement controls and collect evidence | 8.1, Annex A | Controls operating, with records to prove it | High |
| 9 | Awareness and competence | 7.2–7.4 | Trained staff and competence records | Low to medium |
| 10 | Monitor and measure | 6.2, 9.1 | Objectives, measures and results | Low to medium |
| 11 | Internal audit | 9.2, 10.2 | Audit programme, report and corrective actions | Medium |
| 12 | Management review | 9.3 | Recorded review with decisions | Low |
| 13 | Choose and book a certification body | – | An accredited body booked for Stage 1 and Stage 2 | Low |
| 14 | Stage 1 and Stage 2 audits | – | Findings closed and a certificate issued | Medium |
Step 13 is listed late because that’s when the audit happens, but you should do it in the first few weeks.
Decide and set up
1. Confirm the trigger and target date
Most businesses implement ISO 27001 because someone asked for it: a tender, an enterprise customer or a partner. Find out exactly what they need. Is certification mandatory or scored? Which product, service or entity must the certificate cover? By what date? Is a commitment to certify enough for now?
Done looks like: a written answer to those questions, agreed with whoever owns the deal. Where it goes wrong: starting without a date, so the project drifts, or assuming the whole business must be in scope when the customer only cares about one service. If you’re working to a tender, see ISO 27001 for government tenders.
2. Get leadership commitment and a named owner
Clause 5 makes top management responsible for the ISMS: setting direction, providing resources, assigning roles and supporting the people doing the work. In practice you need a sponsor who can make decisions quickly and an owner who runs the project day to day.
What the auditor looks for: evidence that leadership is genuinely involved, such as approving the policy, accepting risks and chairing the management review, and that roles and responsibilities are assigned and understood. Where it goes wrong: handing the whole thing to IT. Many risks and controls sit with HR, operations, finance and suppliers. Effort: small in hours, large in influence. A sponsor who answers questions in days rather than weeks keeps the timeline intact.
3. Define scope and context
Clause 4 asks you to understand the internal and external issues that affect your information security (4.1), the interested parties and their requirements (4.2), and then to set the scope of the ISMS (4.3). Interested parties typically include customers, regulators, staff, suppliers and owners. Since Amendment 1 in 2024 you also need to decide whether climate change is a relevant issue, and the standard notes that interested parties may have climate-related requirements. For many offices and SaaS businesses the answer is brief, but it must be considered.
Done looks like: a scope statement that names the services, locations, people and systems covered, with reasons for any exclusions and how you depend on things outside the scope, such as cloud providers. Where it goes wrong: a scope that’s too wide to finish or too narrow to satisfy the customer. Scope also drives how many audit days the certification body quotes; see what drives the cost.
Assess
4. Gap assessment
The standard doesn’t require a gap assessment, but skipping one means planning blind. Compare what you have against Clauses 4 to 10 and the Annex A controls that are likely to apply: existing policies, access reviews, device management, backups, supplier checks, onboarding and offboarding.
Done looks like: a prioritised list of gaps with owners and dates, and an honest view of how much technical remediation is ahead. Where it goes wrong: treating it as a document checklist and missing operational gaps, like backups that have never been restored or MFA that isn’t enforced everywhere. Those are the gaps that take longest to close.
5. Risk assessment method and risk assessment
Clause 6.1.2 requires a defined risk assessment process with criteria for accepting risk, producing consistent and comparable results. You then identify risks to the confidentiality, integrity and availability of information in scope, assign owners, analyse and evaluate them. Clause 8.2 requires you to repeat it at planned intervals and when significant changes happen.
What the auditor looks for: a documented method someone else could follow, risks that reflect your actual business, owners with authority who know their risks, and results kept as records. Where it goes wrong: a generic register copied from a template, everything scored medium, or IT owning every risk. Our risk assessment guide walks through the method in detail.
6. Risk treatment and Statement of Applicability
For each risk above your acceptance level, decide how to treat it and which controls you need (6.1.3). Compare those controls with Annex A so nothing necessary is missed. The results are a risk treatment plan, approved by risk owners along with any residual risk, and a Statement of Applicability recording every Annex A control, whether it applies, why and whether it is implemented.
What the auditor looks for: a clear line from risks to controls, reasoned justifications for exclusions and implementation status that matches reality. Where it goes wrong: including controls just because they’re in Annex A, excluding them because they’re hard, or marking them implemented before evidence exists. Scope, risk and the SoA are where first-time projects most often stall, and they are the part we take on for clients. See the Statement of Applicability guide.
Build and run
7. Policies and procedures, right-sized
Write the information security policy that Clause 5.2 requires, plus the policies and procedures your risk treatment calls for. Clause 7.5 lets the extent of documentation depend on your size, activities and complexity, so a 20-person company needs far less than a bank. Documents need owners, versions, approval and a review cycle.
Done looks like: a short set of documents that describe how you actually work, approved by leadership and available to the people who need them. Where it goes wrong: downloading hundreds of pages of enterprise policy. The auditor tests whether you follow what you wrote, so every unrealistic sentence is a potential nonconformity. Our guide to required documents covers what is mandatory.
8. Implement controls and collect evidence
This is usually the biggest step. Close the gaps from steps 4 and 6: set up or tighten access control, device management, logging, backups, change management, supplier assessments, secure development where relevant, and incident response. Clause 8.1 also expects you to control processes provided by suppliers that fall within your ISMS.
What the auditor looks for: records showing controls operating over time, not set up the week before the audit. Think access review sign-offs, onboarding and offboarding records, change tickets, backup restore tests and supplier reviews. Ask your certification body how much operating history they expect to sample. Where it goes wrong: remediation competing with product work, and evidence that lives only in people’s heads. Effort: heaviest for system owners and IT. A compliance platform can automate much of the evidence in cloud environments; see consultant, platform or both?
9. Awareness and competence
Clause 7.2 requires people whose work affects information security to be competent, with evidence kept. Clause 7.3 requires everyone in scope to know the policy, how they contribute and what happens if they don’t follow it. Clause 7.4 covers what you communicate, to whom and how.
Done looks like: completed awareness training, competence records for key roles, and staff who can explain the policies that apply to them. Where it goes wrong: a one-off video with no record, or a training module nobody can recall when the auditor asks. Stage 2 interviews will test this directly.
10. Monitor and measure
Set information security objectives that are measurable where practicable (6.2), then decide what you will monitor and measure, how, when and who analyses the results (9.1). Good measures are ones you already produce: patching timeliness, training completion, access review completion, incidents and how quickly they were handled.
What the auditor looks for: objectives with owners and plans, results recorded and analysed, and evidence the results feed decisions. Where it goes wrong: vague objectives such as “improve security”, or dashboards nobody looks at.
Check
11. Internal audit
Clause 9.2 requires a planned audit programme that checks the ISMS meets your own requirements and the standard, and is effectively implemented. Auditors must be chosen so the audit is objective and impartial, which means nobody audits their own work. Findings go through Clause 10.2: correct them, find the root cause and act so they don’t recur.
Done looks like: an audit covering the whole scope before Stage 2, a report with clear findings, and corrective actions closed or planned. Where it goes wrong: the person who built the ISMS auditing it, or a rushed audit that finds nothing and gives false comfort. The auditor can be a trained staff member auditing areas they don’t run, or someone external; in a small team where everyone built part of the ISMS, that often means bringing in an outside auditor. This is the other part we take on for clients, with a Lead Auditor who didn’t build what they are auditing.
12. Management review
Clause 9.3 requires top management to review the ISMS at planned intervals. Inputs include actions from previous reviews, changes in issues and interested parties’ needs, performance results, audit findings, risk assessment results, the status of the treatment plan and opportunities to improve. Outputs are decisions on improvements and changes.
Done looks like: recorded minutes showing leadership considered each input and made decisions. Where it goes wrong: holding it before the internal audit so its results are missing, or a meeting with no record. Effort: an hour or two of leadership’s time, prepared well.
Certify
13. Choose and book an accredited certification body early
Only an accredited certification body can issue a certificate that buyers accept. In Australia, look for accreditation by JAS-ANZ or another member of the International Accreditation Forum, and check the body is accredited for ISO 27001 specifically. Certification bodies work to ISO/IEC 17021-1 and ISO/IEC 27006-1, which also bar them from consulting on the system they certify.
Done looks like: quotes that state audit days, a chosen body and booked dates for Stage 1 and Stage 2. Where it goes wrong: booking late. Good auditors are often scheduled weeks ahead, and a late booking can push a finished ISMS past a tender date. Be wary of any certificate from a body that isn’t accredited.
14. Stage 1 and Stage 2 audits
Stage 1 reviews your documentation and readiness: scope, risk assessment, SoA, policies, internal audit and management review. Stage 2, usually a few weeks later, tests whether the ISMS actually operates through interviews and evidence sampling across the business. Major nonconformities must be fixed and verified before certification; minor ones need an accepted corrective action plan.
Done looks like: a certificate valid for three years, followed by surveillance audits in years one and two and recertification in year three. See what to expect at Stage 1 and Stage 2 and the three-year audit cycle.
How long it takes and who is involved
With focused expert support, a small or medium business is typically audit-ready in about eight weeks, with the main contact spending around two hours a week. Doing it alone usually takes longer, mostly because of the learning curve on scope, risk and the SoA, and because remediation and evidence compete with everyone’s day jobs. Leadership approves the policy, accepts risks and holds the management review. System owners and IT carry most of step 8. HR covers screening, onboarding, leaving and training records. For the timeline in detail see how long ISO 27001 takes, and for what each clause requires see ISO 27001 clauses explained.
Next step
If you’re building the ISMS yourselves, plan the internal audit early. ISO 27001 requires it to be objective and impartial, so nobody audits their own work. In a small team where everyone built part of the system, that often means bringing in an outside auditor. Our independent internal audit is run by a Lead Auditor the way the certification body will audit you. If you’d rather have it built with you, see our ISO 27001 service or book a free 30-minute consultation.
