Cybernion
← Insights

ISO 27001

ISO 27001 Implementation Checklist

19 Oct 2026 · Updated 19 Oct 2026

Implementing ISO 27001 means defining the scope of the information security management system (ISMS), assessing risk, selecting and applying Annex A controls, documenting policies and procedures, running an internal audit and management review, then completing a two stage certification audit. Most organisations take six to eighteen months depending on size, existing maturity and how much work is done internally versus with external help.

ISO 27001 implementation usually goes wrong on sequencing rather than on the standard itself. Teams write policies before scope is agreed, or select controls before the risk assessment is finished, and then redo the work once an auditor points out the gap. A checklist run in the right order avoids most of that.

What are the main steps in implementing ISO 27001?

Implementation follows a fairly fixed sequence because each step depends on the one before it. Leadership commitment comes first, someone senior needs to own the ISMS and its budget, because ISO 27001 requires visible top management support, not just a delegated project. Next is scope, deciding which parts of the business, which locations, systems and information the ISMS covers, since everything else is built on top of that boundary. Risk assessment and treatment follow, identifying information security risks against the defined scope and deciding how each will be treated. From the treatment decisions comes the Statement of Applicability, which selects and justifies controls from Annex A. Implementation of those controls, supporting documentation, staff awareness and training come next, followed by internal audit and a formal management review. Only once all of that is operating does the organisation go to external certification audit. Skipping ahead on any of these steps is the most common cause of delay.

What should an ISO 27001 implementation checklist include?

A working checklist groups the tasks by phase so nothing gets missed.

Foundation

  • Secure management commitment and a budget owner for the ISMS
  • Define the ISMS scope in writing, see how to define your ISMS scope
  • Identify interested parties and their information security requirements, including customers, regulators and partners
  • Write and approve the information security policy

Risk

  • Choose a risk assessment methodology and document it
  • Identify information assets, threats and vulnerabilities within scope
  • Assess likelihood and impact, and set risk acceptance criteria
  • Decide risk treatment for each risk, accept, avoid, transfer or reduce
  • Select applicable controls and produce the Statement of Applicability, referencing the ISO 27001 Annex A controls
  • Write the risk treatment plan

Controls and documentation

  • Implement the selected technical, organisational and physical controls
  • Write required policies and procedures, including access control, acceptable use, password management and incident response
  • Set measurable information security objectives
  • Roll out staff awareness training and record completion

Operating the ISMS

  • Run an internal audit against the full standard and Annex A scope
  • Hold a management review covering audit results, risks, objectives and incidents
  • Record and close out nonconformities and corrective actions
  • Keep evidence, logs and records that demonstrate the ISMS is operating, not just documented

Certification

  • Select an accredited certification body
  • Complete the Stage 1 audit, a documentation review against the standard
  • Complete the Stage 2 audit, where the auditor tests whether the ISMS operates as documented
  • Address any nonconformities raised before certification is issued
  • Plan for the annual surveillance audits and the three year recertification cycle

How long does ISO 27001 implementation take, and what does it depend on?

Most organisations take six to eighteen months from a standing start to certification. The main drivers are the size and complexity of the ISMS scope, how mature existing controls already are, how much of the work can be done by internal staff without pulling them off other priorities, and how quickly management decisions get made on risk acceptance and budget. A small organisation with a tightly drawn scope and dedicated effort can move toward the shorter end. An organisation bringing multiple business units, cloud environments and third party suppliers into scope, or starting from limited existing documentation, should plan for longer. Rushing the risk assessment or the internal audit to hit a date tends to surface as nonconformities at the certification audit, which costs more time overall than doing it properly the first time.

What documents are mandatory for ISO 27001?

The standard requires a defined set of documented information, though the exact document titles are up to the organisation. At a minimum the set covers: the ISMS scope statement, the information security policy, the risk assessment and risk treatment methodology, the risk assessment results and risk treatment plan, the Statement of Applicability, information security objectives, evidence of staff competence and awareness, internal audit programme and results, management review records, and records of nonconformities and corrective actions. Beyond these, most of Annex A’s control areas expect supporting policies or procedures, such as access control, acceptable use, incident management, business continuity and supplier security, sized to the organisation rather than copied from a template unread. An auditor is checking that the documents reflect what actually happens, not that a folder is full.

For an organisation scoping an ISO 27001 project, Cybernion’s ISO 27001 services cover gap assessment, implementation support and audit preparation.

Frequently asked questions

What is ISO 27001 implementation?

ISO 27001 implementation is the work of building an information security management system (ISMS) that meets the requirements of the ISO/IEC 27001 standard. It covers defining scope, assessing risk, selecting controls from Annex A, writing policies and procedures, training staff, and running internal audits and a management review, all before an external certification body assesses the system.

How long does ISO 27001 certification take?

Most organisations take six to eighteen months from starting implementation to certification, depending on size, how mature existing security practices already are, and how much internal capacity is available to do the work. A small business with simple systems and dedicated effort can move faster, while a larger organisation with many business units, legacy systems or a wide ISMS scope will need longer.

What is a Statement of Applicability?

The Statement of Applicability (SoA) is a mandatory ISO 27001 document that lists every control in Annex A, states whether it is applied or excluded, and gives the reason for that decision. It is the single document an auditor uses to trace the link between the risk assessment, the chosen controls and what has actually been implemented, so it needs to be accurate and kept current.

Do we need a consultant to implement ISO 27001?

A consultant is not mandatory, ISO 27001 can be implemented internally with the standard, ASD guidance and enough time. In practice most organisations use some external help, either to run the risk assessment and gap analysis, write core documentation, or prepare for the certification audit, because doing it well the first time avoids a failed audit and a repeat cycle of nonconformities.

What is the difference between ISO 27001 implementation and certification?

Implementation is the internal work of building and operating the ISMS, including risk assessment, controls, documentation and internal audit. Certification is the external step, where an accredited certification body conducts a two stage audit and issues a certificate if the ISMS meets the standard. An organisation can run an ISMS to ISO 27001 without ever certifying it, but certification is what a third party can independently verify.

Sources:

  1. ISO/IEC 27001:2022, Information security management systems, International Organization for Standardization, 2022
  2. Information security manual (ISM), Australian Signals Directorate, 2026
  3. Small business cyber security guide, Australian Signals Directorate, 2026

Last updated: 30 August, 2026

Related serviceISO 27001 ReadinessSee the service →

Talk to us about your engagement

A scoped proposal within one business day.