ISO 27001 Implementation Checklist: 12 Steps From Scoping to Certification Audit
A month-by-month plan for a mid-size company: who owns each step, what evidence auditors sample, where budgets slip, and how to pick a certification body that won't stall your Stage 2.
The 12 steps at a glance: owners, evidence and a 10-month timeline
If a large customer, a regulator or an underwriter has asked for ISO 27001 within the year, your hard problem is sequencing, not effort. Most projects that slip did the steps out of order. They bought a tool before fixing scope, wrote policies before the risk assessment, or booked Stage 2 before there were any records to sample. This ISO 27001 implementation checklist assumes a mid-size company of roughly 150 to 500 people, one or two offices plus cloud infrastructure, and no existing management system. Smaller firms can go faster. Multi-country groups should add a few months.
| Step | Owner | Key evidence | Month |
|---|---|---|---|
| 1. Mandate and roles | Executive sponsor | Signed security policy, roles matrix | 1 |
| 2. ISMS scope | ISMS lead | Scope statement, interested-party register | 1 |
| 3. Gap assessment | ISMS lead or consultant | Gap register with owners | 1–2 |
| 4. Risk method | ISMS lead, CISO | Approved methodology, acceptance criteria | 2 |
| 5. Risk assessment and treatment | Risk owners | Risk register, treatment plan, sign-offs | 2–3 |
| 6. Statement of Applicability | ISMS lead | Versioned SoA | 3 |
| 7. Implement controls | IT, HR, legal, procurement | Policies, configurations, procedures | 3–8 |
| 8. Operate and train | All control owners | Logs, reviews, training records | 4–9 |
| 9. Internal audit | Independent auditor | Audit report, nonconformities | 8–9 |
| 10. Management review | Leadership team | Minutes, decisions, corrective actions | 9 |
| 11. Certification body and Stage 1 | ISMS lead | Contract, Stage 1 report | Book by 5; audit 9–10 |
| 12. Stage 2 and certificate | ISMS lead, sponsor | Stage 2 report, closed findings | 10–12 |
On budget, treat these as typical 2026 market ranges. They vary widely by country and contract, so confirm them with vendors. Certification body fees for the first Stage 1 and Stage 2 cycle often fall between $10,000 and $40,000, and each surveillance year usually costs noticeably less than that. Consultants commonly charge $20,000 to $80,000 depending on how much they build for you. Compliance automation platforms such as Vanta, Drata, Secureframe or Sprinto typically run $10,000 to $40,000 a year. Day rates tend to be lower in India, Southeast Asia and parts of Latin America and higher in Western Europe and North America. Internal time is the biggest cost: budget a half to full-time ISMS lead, plus a meaningful slice of your IT and security leads' time.
Steps 1 to 3: Secure the mandate, fix the scope, measure the gap
Step 1: Mandate. Clause 5 requires visible leadership from top management, and auditors will interview them. Name an executive sponsor, an ISMS lead and a budget before anything else. The evidence is a signed information security policy and a roles-and-responsibilities matrix.
Step 2: Scope. Clauses 4.1 to 4.3 ask you to define internal and external issues, interested parties and the scope boundary, including interfaces with anything outside it. A narrow scope, such as one product and its platform, gets certified faster. But customers read the scope statement printed on the certificate, and a scope that's too narrow can undercut the sales case you're certifying for. For most SaaS and services firms, the right scope is the customer-facing product, the infrastructure it runs on, and the teams that build, run and support it.
Leaving out HR or IT operations when they administer in-scope systems is a red flag, and auditors will challenge it. Also list your legal and contractual requirements in the interested-party register. They differ by country: GDPR in the EU and UK, India's DPDP Act, the data protection laws of Saudi Arabia and the UAE, Brazil's LGPD and Singapore's PDPA are common examples.
Step 3: Gap assessment. Compare your current state with clauses 4 to 10 and the 93 Annex A controls in ISO/IEC 27001:2022. Expect a few weeks. The output is a gap register with an owner and a target month on every item. It becomes your project plan.
Steps 4 to 6: Risk method, ISO 27001 risk assessment and the Statement of Applicability
Step 4: Risk method. Clause 6.1.2 requires documented risk criteria, including acceptance criteria, and a process that gives consistent, valid and comparable results. The standard doesn't mandate an asset-based approach. For most mid-size companies, a scenario-based method with a 5x5 likelihood-and-impact matrix is enough, and business owners actually understand it. Write down the acceptance threshold and who can accept residual risk.
Step 5: Run the risk assessment and treatment plan. Hold short workshops with each in-scope function rather than having one person write the register alone. Every risk needs a named owner, a treatment decision (modify, avoid, share or retain) and planned controls. Under clause 6.1.3, risk owners must approve the treatment plan and accept residual risk. Get those sign-offs in writing, because auditors check them.
Step 6: Statement of Applicability. The SoA lists all 93 Annex A controls. For each, it records whether the control applies, why it's included or excluded, and whether it's implemented. Here's a hypothetical: say a 220-person fintech builds its software in-house and runs entirely on public cloud. It can justify excluding 8.30 (outsourced development) if no development is outsourced. It can't exclude the physical controls, because its offices still hold laptops and people. Instead, it applies them to the offices and points to the cloud provider's own certification for the data centers. An SoA that excludes controls as "not relevant" with no link to scope or risk is a red flag. Version-control it, because it will change.
Steps 7 and 8: Implement Annex A controls and start producing records
Step 7: Implement. Work from the risk treatment plan, not straight down the Annex A list. At mid-size companies, the heavy lifts are usually:
- Access control and periodic access reviews (5.15 to 5.18)
- Supplier and cloud-service security (5.19 to 5.23)
- Incident management (5.24 to 5.28)
- Backup, logging and monitoring (8.13, 8.15, 8.16)
- Controls new in 2022, such as threat intelligence (5.7) and configuration management (8.9)
Keep the mandatory documents in one place: scope, policy, risk method, risk assessment and treatment results, SoA, security objectives, competence evidence, monitoring results, internal audit and management review records, and nonconformity records. Automation platforms help collect evidence and track policies. They won't do your risk assessment or make your access reviews meaningful.
Step 8: Operate and train. Stage 2 auditors sample records from a period of real operation, such as access reviews, change tickets, supplier assessments and incident logs. Our position: aim for at least three months of operating records before Stage 2, and treat about six weeks as the bare minimum. Run security awareness training for everyone in scope and keep the completion records.
Steps 9 and 10: ISO 27001 internal audit and management review
Step 9: Internal audit. Clause 9.2 requires an objective, impartial audit, so nobody audits their own work. You can train someone from another department (lead auditor courses typically cost a few thousand dollars), or outsource the audit, often for $5,000 to $15,000 at mid-size scope. Both are 2026 ranges that vary by region. Before a first certification, cover every clause and every applicable Annex A control. Don't let the consultant who built your ISMS also run the internal audit; that's an independence problem you can easily avoid. Log each finding as a nonconformity or an opportunity for improvement, and handle corrective actions under clause 10.2 with a documented root cause.
Step 10: Management review. Clause 9.3 lists the required inputs: status of earlier actions, changes in issues and interested-party needs, performance (nonconformities, monitoring results, audit results, objectives), and opportunities for improvement. Risk assessment and treatment results are an input too. Hold the review after the internal audit and before Stage 1, and minute the decisions, not just the attendance. Auditors look for leadership choices about resources and risk.
Steps 11 and 12: ISO 27001 certification body selection, Stage 1 and Stage 2
Step 11: Choose a certification body and pass Stage 1. Book several months ahead, because good auditors fill up. Selection criteria:
- Accreditation by an IAF-member body, such as UKAS, ANAB, DAkkS, NABCB, JAS-ANZ or ENAC. Check that issued certificates can be found in IAF CertSearch.
- Auditors with experience in your sector and cloud stack, in your languages and regions.
- A quote that shows audit days calculated under ISO/IEC 27006, plus travel and surveillance fees.
Well-known accredited options include BSI, Bureau Veritas, SGS, TÜV SÜD, DNV, LRQA, Schellman and A-LIGN, and many strong regional bodies exist. Red flags: a certificate promised within weeks, no verifiable accreditation, a guaranteed pass, or a body that offers to build your ISMS and then certify it. Stage 1 is a documentation and readiness review. Fix its areas of concern in the weeks before Stage 2.
Step 12: Stage 2. Auditors interview control owners and sample evidence. Minor nonconformities need an accepted corrective action plan. A major nonconformity blocks certification until it's corrected and verified, within a deadline the certification body sets. The certificate lasts three years, with surveillance audits in between.
The decision rule: if you reach month 8 without a signed risk treatment plan, an approved SoA and at least six weeks of operating records, move Stage 2 back. Rebooking costs less than failing the audit. Start this week by drafting the scope statement and getting your sponsor to sign it.
Frequently asked questions
How long does ISO 27001 certification take for a mid-size company?
With no existing management system, plan on roughly 9 to 12 months from mandate to certificate. That includes about three months of operating records before Stage 2. Companies with mature IT controls or another ISO management system can sometimes finish faster. Multi-country scopes usually take longer.
Do we need a consultant, or is a compliance automation platform enough?
A platform handles evidence collection, policy templates and control monitoring well, but someone still has to own the scope, the risk method and the Statement of Applicability. If no one on your team has run an ISMS before, a limited consulting engagement focused on scoping, risk assessment and audit readiness is usually money well spent. Don't hire the same firm to do your internal audit.
Will ISO 27001 certification lower our cyber insurance premium?
Sometimes, but there's no standard discount. Underwriters mostly price on specific controls like MFA, tested backups, endpoint detection and incident response plans, plus your loss history and sector. Certification can make the application easier and support better terms, and that varies by insurer and market. Ask a licensed broker how carriers in your region treat it.
Written by the Auditcover Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.