Skip to content
    Back to Insights
    GRC & Compliance

    Why Your ISO 27001 Certification Shouldn't Take 18 Months

    Jaouhar Mosbahi15 November 20258 min read

    The most common question we hear from organisations considering ISO 27001 certification is deceptively simple: how long will it take? The answer we give often surprises people. For a mid-sized organisation with reasonable maturity, six to eight months from kick-off to Stage 2 audit is entirely achievable. Yet many organisations spend 18 months or more grinding through the process. The difference is not resources, budget, or organisational complexity. It is approach. Having led an ISO 27001:2022 certification from scratch in eight months, building over 46 policies and procedures along the way, I can say with confidence that the timeline problem is almost always self-inflicted.

    The first and most common pitfall is over-documentation. Organisations interpret the standard's requirement for 'documented information' as an invitation to produce a library. They create 80-page policies that no one reads, elaborate procedure documents for every conceivable scenario, and supporting guides that duplicate content across multiple files. The 2022 update to ISO 27001 actually streamlined the Annex A controls from 114 to 93, reorganising them into four clear themes: organisational, people, physical, and technological. This was a deliberate signal from the standard body that less can be more, provided what exists is meaningful and operational.

    The second pitfall is scope creep. Defining the ISMS scope is a strategic decision, not an administrative one. Too many organisations default to 'the entire company' because it sounds more impressive. For a SaaS company, the ISMS scope should focus on the product, the infrastructure it runs on, and the teams that develop and operate it. You do not need to bring every department into scope on day one. A focused, well-defined scope gets you certified faster, and the standard explicitly allows for phased expansion. Start where the risk is highest, certify, then grow.

    Perfectionism is the third timeline killer. Some organisations refuse to move forward until every policy is flawless, every process is optimised, and every control is operating at peak maturity. This fundamentally misunderstands what the certification auditor is assessing. The auditor wants to see a functioning ISMS that identifies risks, implements proportionate controls, monitors their effectiveness, and improves over time. They are looking for a system that works, not a system that is perfect. Your first pass will have gaps. That is what the continual improvement clause is for.

    Right-sizing your ISMS means matching control implementation to your actual risk profile, not to a template you downloaded from the internet. The Statement of Applicability is where this comes to life. Every one of the 93 Annex A controls needs to be considered, but not every one needs to be implemented. If you do not have a physical data centre, physical security controls for server rooms are not applicable, and the auditor will not penalise you for excluding them with a clear justification. The risk assessment drives the SoA, and the SoA drives your implementation effort.

    Speaking of risk assessment: this is where you should invest disproportionate time and attention. Everything in your ISMS flows from the risk assessment. A thorough, well-structured risk assessment makes every subsequent decision easier. It justifies your control selections, explains your exclusions, prioritises your implementation sequence, and gives auditors confidence that your ISMS is genuinely risk-based rather than checkbox-driven. Use a methodology that works for your organisation, whether that is asset-based, scenario-based, or a hybrid. The standard does not prescribe a specific methodology; it requires that yours is systematic, repeatable, and produces comparable results.

    Management commitment is the single greatest predictor of certification success, and the single most common reason for delay. When the C-suite treats ISO 27001 as a strategic business initiative, resources are allocated promptly, decisions are made without protracted debate, cross-functional cooperation flows naturally, and the project maintains momentum. When it is treated as an IT department side project, everything stalls. The standard's Clause 5 on Leadership is not ceremonial. Auditors probe whether top management genuinely understands the ISMS, participates in management reviews, and allocates adequate resources. If leadership engagement is weak, fix that before you fix anything else.

    What does a realistic timeline look like? Here is the breakdown that has worked across multiple engagements. Months one and two: scope definition, risk assessment methodology, initial risk assessment, gap analysis against Annex A. Months two and three: policy and procedure development, prioritised by risk assessment output and gap analysis findings. Month three: begin control implementation, starting with high-risk areas. Months four and five: continue implementation, begin populating evidence, conduct security awareness training. Month five: internal audit. Month six: management review, address internal audit findings. Months six to seven: Stage 1 audit, address any findings. Month eight: Stage 2 certification audit.

    The policy development phase is where many organisations lose weeks or months. The key is to work from a structured framework rather than creating each document from scratch. We typically build a core set of policies covering information security, access control, asset management, cryptography, operations security, communications security, supplier relationships, incident management, business continuity, and compliance. Each policy has supporting procedures and, where needed, work instructions. The 46-plus policies and procedures we built in our eight-month certification covered all Annex A requirements while remaining concise and actionable.

    The Annex A applicability assessment deserves specific attention. With the 2022 update, the controls are better organised, and several new controls were introduced, including threat intelligence, information security for cloud services, ICT readiness for business continuity, and data masking. Walk through each control methodically. For each one, determine whether it is applicable based on your risk assessment, document your justification either way, identify the current implementation status, and define any remediation needed. This exercise typically takes two to three focused sessions with the right people in the room.

    Internal audits are a mandatory prerequisite for certification, and they are frequently left too late. Plan your internal audit programme at the start of the project, not at the end. The audit should cover the ISMS management system clauses (4 through 10) and the applicable Annex A controls. If you do not have qualified internal auditors, engage an external resource. The audit will inevitably surface findings, and you need time to implement corrective actions before the certification audit. Schedule the internal audit no later than month five to give yourself adequate remediation time.

    Management review is another mandatory gate. This is a formal meeting where top management reviews the performance of the ISMS, considers changes in internal and external context, reviews audit findings and risk treatment progress, and makes decisions about improvements. It produces documented minutes and action items. Many organisations treat this as a formality, but a well-run management review demonstrates exactly the kind of leadership engagement that auditors value. Prepare a structured agenda covering all the inputs required by Clause 9.3 and ensure senior leadership attends, not delegates.

    One practical tip that saves significant time: engage your certification body early. Most certification bodies offer a pre-assessment or gap analysis service. While this is an additional cost, it gives you direct insight into what the auditor will expect and where your gaps are. It also establishes a relationship with the audit team and removes surprises from the formal audit process. The Stage 1 audit, which reviews your documentation and readiness, can be scheduled as early as month six if your documentation is solid.

    Evidence collection is the unglamorous but critical work that underpins certification. Every control needs evidence of implementation and operation. Access review logs, change management records, incident reports, training records, risk assessment outputs, meeting minutes: all of these need to be organised and retrievable. Start collecting evidence from the moment you implement each control. Retrofitting evidence at the end of the project is painful and often reveals gaps in process execution. A well-structured evidence repository, whether in a GRC tool or a simple folder structure, pays dividends throughout the audit.

    The certification audit itself should hold no surprises if you have followed a disciplined process. The Stage 1 audit is a documentation review, confirming that your ISMS documentation meets the standard's requirements and that you are ready for Stage 2. Stage 2 is the implementation audit, where the auditor verifies that your controls are operating as described and that your ISMS is functioning as a coherent system. Common Stage 2 findings include inconsistencies between documented procedures and actual practice, missing evidence for specific controls, and insufficient depth in risk assessments. All of these are preventable with proper preparation.

    The bottom line is this: ISO 27001 certification does not need to be an 18-month marathon. With clear scope, proportionate documentation, a genuine risk-based approach, strong management commitment, and disciplined project management, six to eight months is realistic and repeatable. The organisations that take 18 months are not being more thorough; they are being less focused. Start with your risks, build what you need, prove it works, and improve from there. That is what the standard asks for, and it is what gets you certified on a timeline that makes business sense.

    ISO 27001ISMSCertificationGRC