← All insights

ISO 27001

Implementing ISO 27001: the critical success factors

What separates an ISMS that sails through Stage 2 from one that stalls in month four — and how to set yours up to be the first kind.

Trigun Advisory · October 2026 · 9 min read

ISO/IEC 27001 is the most widely recognised standard for information security. Getting certified tells customers, regulators and investors that security is run as a managed system — with an owner, a risk process, measurable objectives and regular review — rather than as a collection of tools.

Most organisations that start an ISO 27001 programme do eventually get certified. The difference is in how long it takes, how much it costs, and whether the management system is still alive a year later. In our experience, a handful of factors decide which way it goes.

First, what the standard actually asks for

ISO 27001:2022 has two parts. Clauses 4 to 10 describe the management system: understanding your context, leadership commitment, planning and risk assessment, support (people, competence, documentation), operation, performance evaluation and continual improvement. Annex A lists 93 reference controls, grouped into four themes — organisational, people, physical and technological.

The clauses are mandatory. The Annex A controls are not a checklist: you select the ones your risk assessment says you need, and justify each inclusion or exclusion in a Statement of Applicability (SoA). Certification itself happens in two stages — a Stage 1 documentation and readiness review, then a Stage 2 audit of whether the system actually operates — followed by annual surveillance audits and recertification every three years.

Critical success factor 1: a scope that matches the business case

Scope is the single biggest lever on cost and timeline. Too broad and you are certifying parts of the business no customer asked about; too narrow and the certificate doesn't answer the question your customers are actually asking.

Critical success factor 2: leadership that does more than sign the policy

Clause 5 is not a formality. Auditors look for evidence that top management sets security objectives, provides resources, reviews performance and acts on the results. In practice this means:

Critical success factor 3: a risk assessment people can use

The risk assessment is the engine of the ISMS — it drives control selection, the SoA and the treatment plan. The most common failure is a spreadsheet with hundreds of generic threats that nobody reads after the audit.

Critical success factor 4: right-sized documentation

Template policy packs are tempting. They also produce policies that describe controls you don't operate, which is exactly what a Stage 2 auditor is trained to find. Write fewer, shorter documents that describe what you actually do — then do it.

A useful test: could a new joiner in the relevant team read the procedure and follow it? If not, it is either too generic or too long.

Critical success factor 5: controls owned by the people who operate them

Security teams design controls; engineering, IT, HR and operations teams run them. Every Annex A control you include needs a named owner who understands what evidence it produces and when. Access reviews, joiner-mover-leaver, change management, backups and supplier reviews are where evidence gaps most often appear.

Critical success factor 6: integrate, don't duplicate

If you also need SOC 2, ISO 27701 for privacy, ISO 22301 for continuity or compliance with India's DPDP Act, design one control framework and map it across all of them. A single access review can satisfy several requirements at once. Organisations that run parallel programmes for each framework pay for the same work multiple times — and confuse the teams who have to produce the evidence.

Critical success factor 7: an internal audit with teeth

Before Stage 2 you must complete at least one internal audit and one management review. Treat the internal audit as a dress rehearsal: test whether controls operate, not just whether documents exist, and close nonconformities with genuine corrective action. Auditors pay close attention to how you handle your own findings.

A realistic timeline

PhaseWhat happensTypical duration
Gap assessment & scopingContext, scope, current-state review against clauses and Annex A2–4 weeks
ISMS buildRisk assessment, SoA, policies and procedures, treatment plan4–8 weeks
OperateControls run and produce evidence; awareness and training6–12 weeks
Internal audit & management reviewTest operation, raise and close nonconformities2–4 weeks
Certification auditStage 1, then Stage 2 by an accredited certification body4–8 weeks

Most mid-sized technology organisations can move from gap assessment to certification in four to eight months, depending on scope and how much already exists.

After the certificate

Certification is the start of the cycle, not the end. Surveillance audits each year check that the system is still operating and improving. Keep the risk register live, run management reviews on schedule, and treat incidents and customer questions as inputs to continual improvement. An ISMS that is used day to day is far cheaper to keep certified than one rebuilt before every audit.

Schedule a meeting