ISO 27001 Certification: Requirements, Process and Cost Drivers

ISO/IEC 27001 certification explained: what an information security management system is, how the 2022 edition is structured, how the audit works and what drives the cost and timescale.

Abstract illustration of a padlock representing cybersecurity

Key points

  • ISO/IEC 27001 is the international standard for an information security management system (ISMS).
  • The current edition, published in 2022, has 93 reference controls in four themes; the transition from the 2013 edition ended on 31 October 2025.
  • Certification is granted by an accredited certification body after a two-stage audit and is maintained through annual surveillance audits over a three-year cycle.
  • It is risk-based: you choose and justify controls, instead of following a fixed checklist.

Customers, regulators and insurers increasingly want evidence that a supplier manages information security systematically. ISO/IEC 27001 is the most widely recognised way to provide it. The standard does not prescribe particular technologies. It requires an organisation to understand its risks, decide how to treat them, and operate a management system that keeps doing so.

What the standard requires

Clauses 4 to 10 set the mandatory management system requirements:

  • Context and scope. Define what the ISMS covers and the needs of interested parties.
  • Leadership. Top management commitment, a security policy, assigned roles.
  • Planning. Risk assessment, risk treatment and measurable objectives.
  • Support. Resources, competence, awareness and documented information.
  • Operation. Carry out the risk treatment plan.
  • Performance evaluation. Monitoring, internal audit and management review.
  • Improvement. Corrective action and continual improvement.

Annex A controls

ThemeNumber of controlsExamples
Organisational37Policies, supplier security, incident management, threat intelligence, cloud services
People8Screening, awareness training, remote working
Physical14Secure areas, equipment protection, physical security monitoring
Technological34Access control, cryptography, logging, secure coding, data leakage prevention

You are not obliged to implement all 93. You must consider each, and record in a Statement of Applicability which apply, which do not, and why. ISO/IEC 27002 gives implementation guidance.

The certification process

  1. Gap analysis and scoping. Decide which sites, services and systems are included. A narrow scope is quicker but may not satisfy customers.
  2. Build the ISMS. Risk assessment, policies, controls, training, records.
  3. Operate it. Auditors need evidence over time, typically a few months, including an internal audit and a management review.
  4. Stage 1 audit. The certification body reviews documentation and readiness.
  5. Stage 2 audit. Auditors test whether the ISMS is implemented and effective. Nonconformities must be addressed before a certificate is issued.
  6. Surveillance. Annual audits in years one and two, and recertification in year three.

Choose a certification body accredited by a national accreditation body, such as UKAS in the United Kingdom or its European counterparts. Certificates from unaccredited bodies are frequently rejected in procurement.

Time and cost

A small organisation with reasonable existing practice can reach certification in about six to twelve months. Larger or less mature organisations take longer. The cost has four parts:

  • Internal time, usually the largest element.
  • Certification body fees, based on audit days, which are determined by headcount in scope, number of sites and complexity under accreditation rules.
  • Consultancy or tools, if used. Compliance automation platforms help with evidence collection but do not replace risk decisions.
  • Remediation, such as new security tooling or testing.

Obtain quotations from several accredited bodies; audit-day calculations are standardised, day rates are not.

How it relates to other frameworks

  • Cyber Essentials is a prescriptive UK baseline of five technical controls, far narrower and quicker.
  • SOC 2 is an attestation report common with North American customers; much of the underlying work overlaps.
  • The NIS2 Directive and DORA are legal requirements. An ISMS provides the structure to meet them, but certification is not proof of compliance.
  • ISO/IEC 27701 extends the ISMS to privacy, supporting GDPR accountability.

Common mistakes

  • Treating it as a documentation exercise; auditors test practice, not paper.
  • Leaving it to IT; risks sit in HR, facilities, suppliers and development too.
  • Copying template policies that do not match how the business works.
  • Weak risk assessment, which undermines every later decision.

Frequently asked questions

Is ISO 27001 a legal requirement?

No. It is voluntary, though often a contractual condition in technology, finance and public-sector supply chains.

Can individuals be certified?

Organisations are certified. Individuals can obtain lead implementer or lead auditor qualifications.

Does it cover cloud services?

Yes. The 2022 edition added a control on the use of cloud services, and cloud suppliers should be included in supplier risk management.

The bottom line

ISO/IEC 27001 is worth pursuing when customers ask for it or when the organisation needs a disciplined way to manage security risk. Scope it honestly, run it as a management system and it will support compliance with most other security obligations.

Sources and further reading

Scroll to Top