Getting Started
/
ISO 27001 Overview

Getting Started

var(--variable-QsTa4u5mL)

What Is ISO 27001? The Standard Explained

var(--variable-Cl6cRG5u3)

Written by

Aron Lange

Published

Nov 6, 2026

Getting Started

var(--variable-QsTa4u5mL)

What Is ISO 27001? The Standard Explained

var(--variable-Cl6cRG5u3)

Written by

Aron Lange

Published

Nov 6, 2026

“We need ISO 27001.” You’ll hear that sentence in many organizations, often because a customer asked for it. But what exactly do they need: a system, a standard or a certificate? Usually all three.

ISO/IEC 27001 is the international standard for information security management systems. It sets out the requirements for an ISMS: a structured way of deciding what needs protection, treating the risks, and proving that the whole arrangement works. It doesn’t prescribe firewalls, tools or specific technology. And organizations of any size and sector can get certified against it.

So let’s take the three apart: the system, the standard and the certificate. And then I’ll show you how to read ISO 27001 the way an auditor does, so you can tell exactly what’s mandatory.

The system: what an ISMS is

An ISMS is a management system for information security. In practice, you’ll often hear people say “our ISMS is this software tool” or “our ISMS is our firewall setup”. That’s not what it is. An ISMS is a management system, like the quality management system many organizations already have, with policies, processes, people, technology and resources. A tool can support it, but it isn’t the ISMS itself.

How an ISMS works: policy and objectives for confidentiality, integrity and availability, the ISMS with its structure, roles, culture and processes plus risks and controls, and protected information as the result, monitored, reviewed and improved

It works like any management system. Top management sets the information security policy and objectives, and they’re all about the confidentiality, integrity and availability of information. Then the elements of the ISMS do the work: the structure, the roles, the culture and the processes, plus two things specific to information security, the risk assessment and the controls. The result you want is protected information, and it’s measured against the objectives. If you miss them, you review and improve.

The purpose of an ISMS has two parts. It preserves the confidentiality, integrity and availability of information by managing risks. And it gives interested parties confidence that those risks are adequately managed. Keep that second part in mind. It’s what the certificate is for.

The standard: ISO 27001

ISO 27001 says what an ISMS has to look like. The last word of its full title is the important one: requirements. They’re generic and apply to any organization, whatever its type, size or nature, from a ten-person startup to a global bank.

ISO/IEC 27001:2022/Amd 1:2024 decoded: ISO/IEC is the publisher, 27001 the standard, and 2022 with Amd 1:2024 the revision

The full name tells you a lot. ISO and IEC are the publishers: the International Organization for Standardization and the International Electrotechnical Commission, which work together on information technology. Then comes the number, and after the colon, the year of the edition. The current edition is from 2022, and an amendment in 2024 added climate change: organizations now have to determine whether climate change is a relevant issue for their ISMS. In practice, practically everyone just says ISO 27001.

The standard has its roots in a British standard from 1995, BS 7799. It had two parts: a code of practice with good security practices, and a specification for an ISMS you could be certified against. Both parts still exist today. The specification became ISO 27001 in 2005, and the code of practice became ISO 27002.

What does ISO 27001 require?

The requirements sit in clauses 4 to 10. An organization that wants certification has to meet all of them. They follow the same structure as every other ISO management system standard, like ISO 9001 for quality, which is why many organizations can integrate their ISMS with a system they already run.

Clause

Requirement area

4

Context of the organization, including the ISMS scope

5

Leadership, the information security policy, roles

6

Planning, risk assessment, risk treatment, objectives

7

Support: resources, competence, awareness, communication, documented information

8

Operation of the processes planned in clause 6

9

Performance evaluation: monitoring, internal audit, management review

10

Improvement: nonconformity, corrective action, continual improvement

The 12-step implementation roadmap in this guide walks through these requirements in the order a real project follows.

What vs. how: the ISO 27000 family

ISO 27001 doesn’t stand alone. Search for ISO 27000 standards, and you’ll find dozens of them. Do you need all of them? No. A typical project gets by with a handful.

The key is one distinction. ISO 27001 contains requirements: they’re written with “shall”, an auditor checks them one by one, and you can get certified against them. Most other members of the family give guidance: they’re written with “should”, and nobody audits you against them. ISO 27001 tells you what you have to do. The guidance standards help you figure out how.

How the standards fit together: ISO 27001 in the center with clauses 4 to 10 and Annex A; ISO 27003, 27005, 27004, 27007 and 27008 give guidance on the clauses; ISO 27002, 27017, 27035 and 27036 on the controls; ISO 27000 explains the concepts and ISO 27006 is for certification bodies

The ones you’ll meet most often:

  • ISO 27002 explains all 93 controls of Annex A.

  • ISO 27003 explains the requirements of clauses 4 to 10.

  • ISO 27005 helps you with risk management.

  • ISO 27017 adds guidance and controls for cloud services.

  • ISO 27006 isn’t for you at all. It’s for the certification bodies that audit you, and it defines, for example, how many audit days your certification takes.

ISO 27001 vs ISO 27002

The two are companions and are often confused. ISO 27001 contains the requirements and is the standard you certify against. ISO 27002 contains guidance for the 93 controls: what each control is for and how it’s typically put into practice. You can’t certify against ISO 27002. When a contract asks for “ISO 27001 certification”, it means an accredited certificate for the management system.

How to read ISO 27001

Here are two sentences about the same topic. One says top management shall establish an information security policy. The other says policies should be defined and approved. Only one of them is something an auditor will check you against, and the difference is one little word.

Four verbs: shall is a requirement, should a recommendation, may a permission and can a possibility

ISO writes all its standards with the same drafting rules, and they give four verbs a precise meaning. Shall is a requirement: if you want to conform, you have to do it. Should is a recommendation: good practice, but not required. May is a permission. And can is a possibility. The first sentence is from ISO 27001, so it’s a requirement. The second is from ISO 27002, very good advice, but nobody will audit you against that exact sentence.

A few more things help you read a clause. Every item in a lettered list, a), b), c), is part of the requirement, so you have to fulfill all of them. Notes explain or give examples, but they never contain requirements. And clauses 0 to 3 set the scene: introduction, scope, references and terms. The requirements for your ISMS start in clause 4.

What is Annex A?

Annex A is a reference list of 93 information security controls in four themes: organizational (A.5), people (A.6), physical (A.7) and technological (A.8).

Theme

Controls

Examples

A.5

37

Policies, supplier relationships, cloud services

A.6

8

Screening, terms of employment, remote working

A.7

14

Physical entry, equipment, clear desk

A.8

34

Access rights, logging, secure coding, backups

It isn’t a list you implement in full. ISO 27001 calls it a list of possible controls and says itself that it isn’t exhaustive. And the order in which you use it matters.

How Annex A is used: assess your risks, determine your necessary controls, compare them with Annex A to check nothing necessary is overlooked, and document the result in the Statement of Applicability

You start with your risks. Then you determine the controls you need to treat them, from any source. Only then do you compare them with Annex A, to check that you haven’t overlooked anything necessary. And you document the result in the Statement of Applicability. If you start with Annex A and simply tick off controls, you lose the link to the risks they’re supposed to treat.

Annex A controls also don’t tell you how. Take A.8.5, secure authentication. It doesn’t say which technology, how to configure it or where to use it, because a global bank needs something very different from a small manufacturer. It gives you the goal, and your own controls are how you get there. The Annex A section of this guide covers all four themes.

What is mandatory?

What is mandatory: every shall in clauses 4 to 10, no exclusions; notes and examples are explanation only; compare your controls with every Annex A control and implement what your risks require; the Statement of Applicability is mandatory

So here’s the summary. In clauses 4 to 10, every “shall” is mandatory, and you can’t exclude any of them. Notes and examples help you understand, but they’re never requirements. Annex A: you compare your controls with every one of its controls, but you implement what your risks require. And the Statement of Applicability is mandatory too: it lists your necessary controls, why you need them and whether they’re implemented, and it justifies every Annex A control you exclude. Keep these points in mind, and you’ll read ISO 27001 the way an auditor does.

Watch the full lecture above. It’s “How to Read ISO 27001” from the course, with the four verbs, the anatomy of a requirement and how Annex A is really used.

The certificate

Certification is done by an accredited certification body, not by ISO itself. It audits your ISMS against all requirements of ISO 27001, and if the ISMS conforms, you get the certificate.

The certificate: audited by an accredited certification body, against all requirements of ISO 27001, valid for three years with an audit every year, confirming that risks are managed systematically

The initial audit has two stages: stage 1 reviews your documentation and readiness, stage 2 examines whether the ISMS actually operates. A certificate is valid for three years, with surveillance audits in year one and year two and a recertification audit in year three. The certification process article explains each stage.

Remember the second part of an ISMS’s purpose: confidence that risks are adequately managed. That’s exactly what the certificate gives your customers.

Why organizations implement ISO 27001

Three drivers appear in almost every project. First, customers: security questionnaires and tenders increasingly accept an accredited certificate in place of lengthy individual audits. Second, regulation: frameworks such as NIS2 and DORA demand structured, risk-based security management, and an ISMS provides exactly that structure. Third, the organization itself: a functioning ISMS replaces scattered, personality-dependent security work with defined responsibilities and repeatable processes.

At Barvello: a system, a standard and a certificate

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. Its largest customer, Ovena, brings in €21.2 million a year, and for the renewal of its framework agreement, Ovena requires an ISO 27001 certificate covering Connect and everything behind it.

Read that requirement carefully, and there are three things in it. An ISMS, the system Barvello has to build. ISO 27001, the standard that says what that system has to look like. And a certificate, the proof that the system meets the standard. Barvello already knows how certification works: it has held an ISO 9001 certificate for quality since 2004. Now Ovena wants the same for information security, and that’s where the project begins.

The 2022 revision and the 2024 amendment

ISO/IEC 27001:2022 restructured Annex A from 114 controls in 14 sections into 93 controls in 4 themes and introduced 11 new controls, including threat intelligence, cloud services security, data leakage prevention and secure coding. Amendment 1, published in 2024, added climate change to the context analysis. The transition period for the 2013 edition ended in October 2025, so all valid certificates now reference the 2022 edition.

From the auditor’s chair

Here’s a distinction that’s important to me: we certify a management system, not the security posture. A certificate doesn’t promise that nothing will ever happen. What it confirms is that the organization manages its information security risks systematically and keeps improving.

And when I read a Statement of Applicability, I look for the link to the risks. If it reads like Annex A with a tick next to every control, the controls have lost the reason they’re there.

Frequently asked questions

Is ISO 27001 mandatory?

No law makes ISO 27001 certification mandatory in general. It becomes binding through contracts and tenders, and regulators increasingly treat it as evidence of the structured security management that laws such as NIS2 require.

Does an ISO 27001 certificate mean we comply with the GDPR or NIS2?

Not automatically. A certification audit isn’t a legal compliance audit. The auditor checks whether your ISMS is able to make sure you meet your legal requirements: that you’ve identified them and included them in your risks and controls. Some obligations, like registering with the authority under NIS2, go beyond the ISMS, so you still check each law on its own.

Who can get certified?

Organizations certify their management system; there is no company size requirement. Individuals earn personal credentials instead, such as the TRECCERT ISO 27001 Lead Implementer certification.

How long does implementation take?

Most organizations need between three and twelve months from project start to certification audit, depending on size, scope and existing maturity. The implementation roadmap covers typical timelines.

Chapter 2 in the course.

Read the standard like an auditor.

8 lectures (51 min) explain management systems, ISO 27001 and the 27000 family, how to read the requirements, and the laws and frameworks around it, with Barvello as the example throughout. Then the course takes you through the 12 steps of the implementation.

ISO 27001: The Standard for an ISMS

07:06

The ISO 27000 Family

07:20

How to Read ISO 27001

08:13

Laws and Regulations

07:28

Where to go next? If you’re about to implement ISO 27001, start with the implementation roadmap. If you want to build a career in it, read about the ISO 27001 Lead Implementer certification.


€690

/ year

incl. 19% VAT · billed yearly

12-hour Video Course

ISO 27001 Toolkit

Practice Exam

Weekly Live Q&A

Exam Voucher + Free Retake

Bundle

Study Guide

Bundle

€690

/ year

incl. 19% VAT · billed yearly

12-hour Video Course

ISO 27001 Toolkit

Practice Exam

Weekly Live Q&A

Exam Voucher + Free Retake

Bundle

Study Guide

Bundle