An ISO 27001 gap analysis is the best first step in any certification project. It tells you where you stand today against the standard, so your plan, budget and timeline rest on facts, not guesses. Companies that skip it often discover the real size of the work halfway through, when changing plans is expensive.
ISO/IEC 27001:2022 sets requirements for an information security management system (ISMS) and lists controls in Annex A. A gap analysis compares what you do today with those requirements and controls, and records the differences. It is not an audit and it does not produce a certificate, but it is the foundation of a good project.
How do you carry out an ISO 27001 gap analysis?#
- Define the scope. Decide which services, sites, systems and teams the ISMS will cover. A gap analysis against an undefined scope is not meaningful.
- Gather what exists. Collect policies, procedures, records, network diagrams, supplier lists and previous audit reports.
- Review the management system requirements. Check each main requirement: context, leadership, planning, support, operation, performance evaluation and improvement.
- Review the Annex A controls. For each of the controls, record whether it is in place, partly in place or missing, and what evidence you saw.
- Interview people. Talk to the staff who do the work, not only the managers. Their answers show what really happens.
- Rate each gap. Use a simple scale, such as high, medium and low, based on risk and effort.
- Write the action plan. Assign an owner, a date and the expected outcome for each gap.
- Present results to management. Share the findings, the plan and the resources needed.
Evidence is what separates a useful gap analysis from an opinion. If someone says that access reviews are done, ask to see the last one. If a policy exists, check its approval date and ask staff whether they know it. Note the evidence you saw for each item, so the result can be repeated later and defended in front of management.
What should the gap analysis report contain?#
| Item | What to record |
|---|---|
| Requirement or control | The standard requirement or Annex A control being checked |
| Current state | What you found, with evidence such as a document, record or interview |
| Status | In place, partly in place or missing |
| Gap rating | Priority based on risk and effort |
| Action | What must be done to close the gap |
| Owner and date | Who is responsible and when it will be done |
Keep the report short enough to read. A one-page summary for management, supported by detailed sheets for the team, works well.
Choose the depth to match your purpose. A quick gap analysis can take a day or two and suits a first look. A detailed one reviews every requirement and control with evidence and interviews, and suits a project that is about to start. Either way, write down the method you used so that results from different times can be compared.
What gaps appear most often?#
- No formal risk assessment method, or one that is not followed.
- No Statement of Applicability, or one based on the old 2013 control list.
- No internal audit programme or management review.
- Policies that exist but are not approved, communicated or followed.
- No regular access reviews, or leavers who keep access.
- Little control of suppliers that handle data.
- No tested backup restore, incident process or continuity plan.
- Staff awareness that depends on a single induction.
Most organisations find that technology is the smaller part of the gap and management system routines are the larger part.
Be realistic about effort. Some gaps need a document, some need a tool, and some need a change in habits. Habits are the hardest to change, so give them time and management support. A control that depends on people remembering a rule will fail without training and reminders, however well the rule is written.
How do you turn the gap analysis into a plan?#
Group the gaps into work packages, such as risk assessment, policies, access control, supplier management and audit routines. Put the high-risk, low-effort items first, since they bring quick benefits. Add dependencies, such as risk assessment before the Statement of Applicability. Then work backwards from the audit dates you want, leaving margin.
A ready-made checklist makes the analysis quicker. Our ISO 27001 toolkit includes a gap assessment checklist and editable documents, with one year of e-mail support and a free upgrade within 6 months. If you prefer an independent assessment, see our ISO 27001 consulting in India. A gap analysis shows the work needed, but no one can promise an audit result, because the certification body decides.
Repeat the analysis before the Stage 1 audit. A short second pass confirms that gaps are closed, evidence exists and nothing new has slipped in.
Finally, share the results with the people who will carry out the plan. A gap analysis that sits in a drawer helps nobody. A short meeting that walks through the findings and agrees owners turns the report into action and builds the team's ownership of the project.
A gap analysis is also a good moment to look at your scope again. If the analysis shows that a system or team in scope is far from ready, you may decide to phase the project, starting with a smaller scope and extending later. Doing so is acceptable if the certified scope still meets your customers' needs.
Frequently asked questions#
Who should perform the gap analysis?#
Someone who knows the standard and can be objective. It can be an internal person with training or an outside specialist.
Is a gap analysis the same as an internal audit?#
No. A gap analysis happens before the system is built and shows the work needed. An internal audit happens once the system is running and checks that it conforms.
How long does it take?#
It depends on your size and scope. A small, focused scope takes much less time than a multi-site organisation. Plan time for interviews and evidence checks.
To learn more read our complete guide to ISO 27001 or contact AdWiser to arrange an assessment.

Leave a Comment