With Step 1, you know what your ISMS will cover. Now the next question is: how far are you from an ISMS that meets ISO 27001 within that scope? That’s the gap analysis.
ISO 27001 doesn’t require one. You won’t find a clause for it, and no auditor will ask you for it. So why do it? Because of what comes next. In Step 3, you ask top management to commit to the ISMS: the project, the people, the budget and the timeline. Without a gap analysis, nobody knows how much work is ahead, so the answer is typically either “we’ll see” or a number someone made up. The gap analysis gives you the real answer, and that’s what turns the commitment in Step 3 into a real one.
It’s a short step, typically a few weeks. This article shows you how to run it, how a company does it in practice, and the tasks you can work through for your own organization.
What a gap analysis is
A gap analysis compares two things: where your organization stands today and where it needs to be, here an ISMS that meets ISO 27001. What lies in between are the gaps, in your people, your processes and your documents.

So you answer three questions, in this order: where do we want to be, where are we today, and what’s in between?
One distinction saves you trouble later: a gap analysis is not a risk assessment. The gap analysis is requirements-based. It measures how far current practice is from what the standard requires. The risk assessment in Step 7 is threat-based and weighs likelihood and impact. Keep the two apart from the start.
1. Define the desired state
Start with the business vision and objectives, not with the standard. That’s not a formality. If your organization wants to grow in a new market or launch a connected product, your ISMS has to support that, and it’s also the language top management listens to.
Then the desired state itself, and here it’s quite concrete: an audit-ready ISMS within your scope. That means meeting 234 requirements: 141 in clauses 4 to 10, which you can’t exclude, and the 93 controls of Annex A you compare against. On top of that come the requirements of your interested parties from Step 1, for example a customer who wants an annual penetration test.

2. Analyze the current state
To find out where you stand, you typically combine four methods: interviews with the people who run things, from the management board to IT and HR, a review of the documents you already have, a walkthrough of your sites, and a few technical checks for IT, for example whether MFA is really switched on.

The document review is usually where you spend most of your time, and you check three things. Is it complete: does the document exist and cover what the standard asks for? Is it accurate: does it describe what actually happens? And is it consistent: does the IT policy say the same as the HR handbook? A procedure that nobody follows isn’t a head start. It’s a gap.
And you rarely start from zero. If you already run a management system like ISO 9001, you have document control, internal audits and a management review. That’s a real head start.
Look beyond the documents
Interviews and documents tell you a lot, but some gaps are harder to see. The 7-S model by Tom Peters and Robert Waterman helps here. It looks at an organization through seven elements. Strategy, structure and systems are the hard ones: you find them on paper. Shared values, staff, style and skills are the soft ones: hard to pin down, but they decide whether your ISMS will actually work.

Let’s say you find a perfect access control policy, but the style is “we trust each other, so we share passwords”. On paper, there’s no gap. In reality, there is.
3. Rate every requirement and name the gaps
For every requirement, you decide: fulfilled, partly or missing. Fulfilled means it’s in place and you can show it. Partly means something exists, but it’s incomplete or there’s no evidence. Missing means there’s nothing yet. Rate the Annex A controls too, but see it as a first indication. Which controls you actually need, you decide after the risk assessment.
There are more detailed scales, like a six-level maturity model from “non-existent” to “optimized”. They’re useful if you want to measure progress over the years. For a first gap analysis, three levels are enough.
Then be precise about the gaps. “Access control: partly” doesn’t help anyone. “No MFA for remote access and admin accounts” does, because now you know what to do. For each gap, estimate the effort (low, medium or high) and note who could own it. And look out for quick wins: things you can fix in a few days that close a real risk.

Three mistakes are worth avoiding. The first is rating without evidence: someone says “we do that”, and it’s marked as fulfilled. Ask: can you show me? The second is going too deep. A gap analysis isn’t an audit, and if you spend two days on a single control, you’ve lost sight of the purpose. The third is working alone at your desk. The people who run things know where the gaps are, and as a side effect, they’ll know about the ISMS before it starts.
4. Write the report for top management
The report has one audience: top management. So keep it short: how you did it, the results by area, the main gaps, and what it takes to close them in effort, budget and time. And at the end, the decision you’re asking for. That’s the bridge to Step 3.
At Barvello: 14 percent, and a clear price tag
Barvello Coffee Systems is the fictional company of our ISO 27001 Lead Implementer course: a family-owned maker of professional coffee machines in Munich, with about 500 employees and its own cloud platform, Barvello Connect. In Step 1, project lead Nadia Berger set the scope. Now the management board wants to know what the ISMS will cost before it approves a single euro, and the business case goes to the advisory board on 3 February. So Nadia has about five weeks, with Christmas in between.
She starts with Barvello’s strategy, “Barvello 2030”. Every one of its objectives depends on information security:
Objective | Target | What it means for the ISMS |
|---|---|---|
Connect new professional machines to Barvello Connect | 80% (2025: 61%) | Customers have to trust Connect |
Launch Barvello Pro X, “secure by design” | Q4 2027 | Secure development; Cyber Resilience Act |
Double revenue in North America | €40 m (2025: €19.7 m) | Barvello Inc. in the scope; proof for US customers |
Most reliable partner for chains | 95% first-time fix rate | Connect, production and service keep running |
In January, she runs 14 interviews with the management board and the department heads, reviews the ISO 9001 documentation, an IT usage guideline from 2017 and the supplier contracts, walks through the buildings in Munich, and joins the team in Charlotte by video call. For the technical checks, IT had prepared a self-assessment in October. Nadia goes through it with the head of IT and checks a few points herself. A self-assessment tells you what IT believes. A check tells you what’s actually true.
Her ratings are facts, not impressions: 43 active accounts of former employees, backups in the same server room as the servers, and a full restore of SAP that was never tested. And one finding the management board should hear about: four people know the firmware signing key. “That’s the point,” one of them tells Nadia, “someone has to be able to release.”
The result: of 234 requirements, 33 are fulfilled, 86 partly and 115 missing. That’s 14 percent. Is that bad? Not really, for a company that never had an ISMS. The fulfilled ones sit in clause 4, done in Step 1, and in clause 7, thanks to twenty years of ISO 9001. Most of the missing ones are in clause 6, the whole risk process. That’s typical for a first gap analysis.
The report names ten main gaps, not 115, each with an effort and a priority. Priority 1 is what can’t wait: governance, the risk method, the insurer’s conditions, incident response and backups. And it ends with what top management actually waits for: about 400 internal person-days and 60 days of external support in 2027, a security engineer from April, in total about one million euros, and a certificate by 30 September. Will the CFO like the number? Probably not. But he asked for a clear picture of costs, benefits and risks, and that’s what he gets.
Watch the full lecture above. It’s “Conducting a Gap Analysis” from the course, including the rating scale, the 7-S model and how to write the report.
Your turn: Step 2 in the project plan
In the project plan of our ISO 27001 Toolkit, Step 2 is six tasks and one milestone:
ID | Task | Clause |
|---|---|---|
18 | Understand business vision and objectives | 6.2 |
19 | Define desired state | |
20 | Analyze current state | |
21 | Compare current state with desired state | |
22 | Identify gaps | |
23 | Produce gap analysis report | |
24 | Milestone: Gap analysis is completed |
At the end of Step 2, you have two deliverables, and the toolkit has a template for each: a workbook that already lists all 234 requirements, so you only rate and describe, and a short report for top management.

Neither is required by ISO 27001. Keep them simple. A gap analysis is a means to an end. It doesn’t have to be perfect, it has to be good enough to decide on.
Start your gap list today.
With the free checklist.
All 143 documents and records an auditor expects, each mapped to its clause or Annex A control, with a status column (in place, partial, missing). Fill it in, and you have the document part of your gap analysis.

From the auditor’s chair
A gap analysis and an audit look similar, but they ask different questions. The gap analysis asks what’s missing. The audit asks whether what you say is in place is actually working. That’s why “we do that” is never evidence. In a gap analysis, it should be marked as “partly” until someone can show it.
And a procedure that exists on paper but that nobody follows isn’t a head start. In a certification audit, it would typically be a nonconformity.
Frequently asked questions
Is a gap analysis mandatory for ISO 27001?
No. ISO 27001 doesn’t require one, and no auditor will ask for it. You do it because it tells top management what the ISMS will take, before they commit to it.
What’s the difference between a gap analysis and a risk assessment?
The gap analysis compares you with the requirements of the standard. The risk assessment looks at threats, likelihood and impact. You need both, but at different points: the gap analysis in Step 2, the risk assessment in Step 7.
What’s the difference between a gap analysis and benchmarking?
A gap analysis compares you with requirements and answers “do we meet the standard?”. Benchmarking compares you with other organizations and answers “where do we stand among our peers?”. For the certification, what counts is the standard, not what your competitors do.
Should we rate the Annex A controls?
Yes, but as a first indication. Which controls you actually need, you decide after the risk assessment, and you document that in the Statement of Applicability.
How long does a gap analysis take?
Typically a few weeks. At Barvello, with about 500 employees, it took five weeks, including Christmas.
Step 2 in the course.
Watch Barvello find its gaps.
4 lectures (21 min) show you how to define the desired state, analyze where you stand and rate all 234 requirements. Then you watch Nadia run Barvello’s gap analysis and write the report for the board. Your turn: 6 tasks in the project plan and the templates for the workbook and the report.
Conducting a Gap Analysis
08:12
Case Study: Barvello’s Gap Analysis
07:59
Template: Gap Analysis Workbook
REC-004
Template: Gap Analysis Report
REC-005
With the gap analysis completed, you’re ready for Step 3: management support, where top management commits to the ISMS with the project, the people, the budget and the timeline.


