ISO 27001 · 11 MIN

ISO 27001:2022 Gap Analysis — A Practical Template for Australian Teams

A practical guide for Australian ISMS owners to compare existing controls with ISO 27001 requirements, identify evidence gaps and plan the work ahead.

Explore ISO 27001 consulting

What a defensible gap analysis covers

ISO/IEC 27001:2022 includes management-system requirements in clauses 4 to 10 and a reference set of 93 controls in Annex A. A useful gap analysis considers both the ISMS and the controls relevant to your organisation's risks and scope. This guide is a starting structure, not a certification audit or a downloadable template.

The five-step structure

Before starting, name the business owner and agree the services, locations, systems and suppliers in scope. Collect the existing risk register, policies, asset and supplier inventories, operating records and any previous findings. Record unavailable evidence explicitly rather than scoring an untested control as implemented.

Gap analysis sequence

  • Scope & ISMS context. Define the scope statement, interested parties (clause 4) and the boundary that the certification body will audit.
  • Management-system review (clauses 4–10). Leadership, planning, support, operations, performance evaluation, improvement — score each clause against documented evidence.
  • Annex A control coverage. Walk the 93 controls grouped by Organisational, People, Physical and Technological. Mark implemented, partial, planned or not applicable with rationale.
  • Risk treatment & SoA delta. Reconcile gaps to your risk register, update the Statement of Applicability and identify treatments needed before stage-1 audit.
  • Remediation roadmap. Prioritise actions by risk, effort and dependencies, and agree owners and realistic timeframes.

Mapping to the 2022 control changes

ISO 27001:2022 reduced Annex A controls from 114 to 93 and introduced 11 new controls — including 8.23 Web Filtering, 8.28 Secure Coding, 5.7 Threat Intelligence and 5.23 Information Security for Cloud Services. If your last gap analysis predates 2022 you are walking the wrong control set; certification bodies are no longer accepting 2013-aligned SoAs.

Evidence the auditor actually asks for

  • Approved ISMS scope statement with boundaries and exclusions
  • Information security policy approved by top management and reviewed at planned intervals or when significant changes occur
  • Risk assessment methodology, current risk register and risk treatment plan
  • Statement of Applicability with justification for every Annex A control
  • Internal audit programme covering all clauses across the certification cycle
  • Management review minutes with decisions, actions and improvements

A gap register your team can act on

For each gap, record the requirement or applicable control, evidence reviewed, current position, business risk, owner, next action, dependencies and how completion will be verified. Separate a missing document from a control that is not operating: the remediation is different. Agree priorities with the people who can approve and deliver the work.

Gap assessment, internal audit and certification

A gap assessment helps plan the work. An internal audit evaluates the ISMS against its audit criteria with appropriate objectivity and impartiality. Certification is independent assurance from a certification body, not a certificate issued by your adviser or by ISO itself. Completing this guide does not establish compliance or guarantee certification.

Official references: ISO/IEC 27001 overview and ISO guidance on certification. Use the licensed standard for the full requirements and assess them against your own scope.

SHORTCUT FOR ISMS OWNERS

Generate your ISO 27001 policy pack in one mission.

Explore the Platform's policy pack tools to help prepare draft documentation for review and adaptation to your organisation.

Explore the policy pack generator

Anti-patterns we see

  • Annex A-only assessments. Skipping clauses 4–10 fails certification before you start.
  • Mark-all-implemented. Over-claiming coverage creates worse non-conformities at audit than honest gaps.
  • No risk linkage. Gaps that do not feed the risk register and SoA are theatre.
  • One-shot remediation. Treat gap closure as a programme with weekly cadence, not a one-week sprint.

FAQ

What is an ISO 27001 gap analysis?

A gap analysis compares your ISMS against ISO/IEC 27001:2022 management-system requirements and the controls necessary for your risks and scope. Annex A is a reference set, not a requirement to implement every control. The review produces evidence gaps and a prioritised remediation plan; it is not a certification audit.

How long does a gap analysis take?

The time depends on the scope, the evidence available and the people involved. Allow time to collect evidence, assess gaps and agree priorities with the people responsible for the ISMS.

Do we need a gap analysis if we already have SOC 2?

A SOC 2 assessment can provide useful evidence, but it does not replace an assessment against ISO 27001 requirements. Review the overlap and remaining management-system and control gaps for your particular scope.

Should we run the gap analysis ourselves or hire a consultant?

Either approach can work. An internal team brings knowledge of the environment; an advisor can help structure the review and prioritise gaps. An independent certification body performs the certification audit.

Related

Plan your next step with confidence.

Discuss your scope, gaps and certification readiness with a senior advisor.