Request a quote
Emergency SectorsCareers About us Blog Get in touch
Meeting room with a wall covered in yellow sticky notes and two colleagues at a long table

ISO 27001 implementation: from gap analysis to certificate, and what IT has to supply

ISO 27001 implementation is not a project you finish but a management system you show is running. That is why it follows a fixed order: decide what is in scope, measure where you stand, only then put controls in place, and gather evidence for a while before an auditor arrives. This piece walks through that order, with what IT has to supply at each step.

7 min read Written by the ITproposal team
Short answer

The scope decides everything that follows; start there, not with a template pack of policies.

A certification body wants to see that your management system has been running for a while, including an internal audit and a management review. That evidence cannot be produced in a week.

Much of it comes out of your IT: access rights, logging, restore tests, patch reports. We supply that side; certification is done by an accredited body.

What ISO 27001 certification is, and who issues it

ISO/IEC 27001 describes an information security management system, an ISMS: how an organisation identifies its risks, chooses controls, checks they work and adjusts. The certificate says an independent party has established that this system exists and works, within a defined scope.

That party is a certification body accredited to do so, in the UK by UKAS. Ask about accreditation with every quote; many clients and tenders will not accept a certificate from an unaccredited body.

A certificate is valid for three years, with a surveillance audit every year. Since the end of October 2025 only the 2022 version applies, with 93 controls in its annex. It is also something different from Cyber Essentials, the government-backed scheme for basic technical controls: useful, often asked for in UK public sector contracts, but not a substitute. And ISO 27001 is not an NIS2 certificate, because no such thing exists, as we explain in NIS2 certification does not exist.

Step 1: the scope, before you measure anything

The scope states which part of the organisation the certificate covers: which sites, which processes, which systems. It is every auditor’s first question and the one that drives the whole programme, because everything inside it has to be evidenced later.

  • Start with the outside request. Which client or tender is asking for the certificate, and for which service? A scope that covers exactly that service is smaller and quicker than “the whole company”, and gives the client what they asked for.
  • But do not shrink it artificially. A scope that leaves out the service desk while the service desk can reach every client record falls over at the first question.
  • Draw the boundaries with IT in the room. Which Microsoft 365 tenant, which cloud subscriptions, which office networks and which suppliers belong in it. Only IT can draw up that list.

Step 2: the gap analysis

A gap analysis sets the requirements of the standard against what already exists. The aim is not a score but a work list: what is in place, what is half in place, and what is missing.

Do it in two parts. The requirements in clauses 4 to 10 concern the management system itself: context, leadership, risk assessment, objectives, documentation, internal audit, management review and improvement. In an organisation without an ISMS these are almost always missing. The controls in the annex concern what actually happens, and an organisation with well-managed IT is often further along there than it thinks.

For every control, ask not only “do we do this?” but also “can we show that we do it?” MFA that is switched on everywhere but that nobody can produce an overview of counts for half in an audit.

Step 3: risk assessment, Statement of Applicability and treatment plan

Only after the gap analysis comes the heart of the standard: the risk assessment. You decide which information and systems are in scope, what can go wrong, how likely it is and what it would cost. That determines which controls you apply.

  • The Statement of Applicability lists every control in the annex: which you apply, which you do not, and why. The auditor reads it alongside your risk assessment.
  • The risk treatment plan says, per risk, what you will do, who does it and when. This is the plan for the rest of the programme.
  • The board accepts the residual risk, in writing. No supplier can do that for you.

Which controls typically come out of your IT, and what evidence goes with them, is covered in our ISO 27001 checklist.

Step 4: implementing controls and letting the evidence build up

This is the longest step, and the reason ISO 27001 implementation is measured in months rather than weeks. Putting a control in place is one thing; an auditor wants to see that it has been working for some time. An access review you have done once proves you can do it, not that you do.

The evidence that comes from IT, and that you let accumulate from day one:

  • A current inventory of devices and systems in scope, each with an owner.
  • Accounts and rights: who holds admin rights, and the trail of joiners and leavers, with the date each account was closed.
  • Logging: what is recorded, how long it is kept and who looks at it.
  • Backup: not that it runs, but when a restore was last tested and with what result.
  • Patching and vulnerabilities: reports showing how quickly updates are installed.
  • Incidents and changes: the tickets, with what was done and learned.

Alongside that, start straight away on what does not come from IT: staff awareness, supplier agreements and the policy the board signs off.

Step 5: internal audit, management review and choosing a certification body

Before a certification body arrives, your system has to have completed one full cycle. That means two things almost everyone underestimates.

  • An internal audit across the whole scope, by someone who is not reviewing their own work. That can be an employee or an outside party, but not the person who built the ISMS. The findings must have been followed up.
  • A management review in which leadership looks at the results and takes decisions, recorded in minutes.

Meanwhile, get quotes from two or three accredited bodies and book the audit well ahead; their diaries are often full for months. The certification audit itself runs in two stages, first your documentation and then how it works in practice. What an auditor wants to see from IT at that point is a subject of its own. After that the cycle begins: annual surveillance audits and recertification after three years.

What drives the timeline and the cost

There is no fixed price and no fixed duration for ISO 27001 certification, and anyone who quotes one without knowing your organisation is using an average that is not yours. What drives it:

  • The size of the scope. The number of people in scope sets, through a fixed calculation rule, how many audit days a body must plan, and with that most of the audit cost. More sites means more visits.
  • What is already in place. An organisation with managed IT, fixed joiner and leaver processes and a tested backup is months ahead of one that has to build those first.
  • Who does the work. Someone internal who is given time for it, an outside consultant for the management system, or a mix. Without someone with time and authority, the programme stalls.
  • How complex the environment is. Many separate systems, on-premises servers alongside cloud, or many suppliers with access means more controls and more evidence.

Where our work stops

What we do. We are ISO/IEC 27001 certified ourselves, as well as ISO 9001 and ISO 14001, so we know the process from the inside. For your programme we supply the IT side: helping define which systems are in scope, implementing and running the technical controls, and producing the evidence an auditor asks for, from access reviews to restore tests and patch reports.

What we do not do. We are not a certification body and not an auditor, and we certify no one. We do not set your scope, decide your risk appetite or approve your Statement of Applicability; those are decisions for your board. Our certificate covers us and cannot be transferred to you. And the party that builds your IT should not also carry out your internal audit: that is exactly the independence the standard asks for.

Frequently asked

Questions we get about this

The five that come up most often.

How long does ISO 27001 implementation take?

Think in months rather than weeks. It depends on the size of the scope, on what is already in place and on who has time for it. The step you cannot speed up is the evidence: a certification body wants to see that your management system has been running for a while, including an internal audit and a management review.

How much does ISO 27001 certification cost?

There is no fixed price. Audit cost depends mainly on the number of people in scope, which sets the number of audit days through a fixed calculation rule, and on the number of sites. On top of that comes the time to build the management system and any controls still missing, which depends on how mature your IT already is.

Who issues the ISO 27001 certificate?

A certification body accredited to do so, in the UK by UKAS. A consultant or IT supplier can help you build the system but cannot certify you. Ask about accreditation with every quote.

What is the difference between a gap analysis and an internal audit?

A gap analysis is done at the start: you set the standard against what exists and get a work list. An internal audit is done at the end of a full cycle: someone who is not reviewing their own work checks whether the management system works as described. The internal audit is a requirement of the standard; the gap analysis is not.

Can you certify us to ISO 27001?

No. We are not a certification body and not an auditor. We are ISO 27001 certified ourselves and supply the IT side of your programme: the technical controls and the evidence an auditor asks for. The scope, the risk decisions and the Statement of Applicability remain decisions for your board.

Shall we look at what your IT can already show?

Tell us the scope you have in mind or which client is asking for the certificate. We walk through the technical side and tell you what evidence already exists and what still has to build up.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call