Guide
Blog
Insights
7 November 2026

What ISO 27001 is and how to get certified

What ISO 27001 is and how to get certified

ISO/IEC 27001:2022 is the international, certifiable standard for information security management systems (ISMS). It sets out how an organisation protects the confidentiality, integrity and availability of its information: a defined scope, a risk assessment, a Statement of Applicability covering the 93 Annex A controls, and an ISMS that is monitored and improved. An accredited certification body issues the certificate after a two-stage audit, valid for three years with annual surveillance audits.

Reviewed by Sven Moritz · As of November 2026

The question usually arrives through sales. A prospect’s security questionnaire asks for an ISO 27001 certificate, an enterprise customer makes it a contract condition, or a partner wants proof before sharing data. This guide explains what the standard requires, how certification works and how it relates to SOC 2, NIS2 and ISO 42001.

Key takeaways

  • ISO/IEC 27001:2022 is the current edition. It was published in October 2022. Amendment 1:2024 added climate change to clauses 4.1 and 4.2.
  • The requirements sit in clauses 4 to 10. These are mandatory. Annex A is a reference list of controls you select from based on risk.
  • Annex A has 93 controls in four themes: organizational, people, physical and technological.
  • The Statement of Applicability is mandatory. Every Annex A control must appear with a decision and a reason.
  • Certificates against the 2013 edition expired on 31 October 2025.
  • ISO 27001 is voluntary. NIS2 does not require certification, but its risk-management measures overlap strongly with Annex A.

What is ISO 27001?

ISO/IEC 27001 specifies requirements for establishing, implementing, maintaining and continually improving an information security management system. It does not prescribe specific technologies. Instead, it requires you to understand your risks, decide how to treat them and prove that your decisions are carried out and reviewed.

The standard applies to organisations of any size and sector. A ten-person SaaS start-up and a multinational can both certify. What differs is the scope, the risks and therefore the controls that apply.

The structure: clauses 4 to 10

ISO 27001 follows the harmonised structure that ISO management system standards share, the same one used by ISO 42001 and ISO 9001.

ISO/IEC 27001:2022, clauses 4 to 10
4 Context
Internal and external issues (including climate change since Amd 1:2024), interested parties, scope of the ISMS
5 Leadership
Top management commitment, information security policy, roles and responsibilities
6 Planning
Risk assessment (6.1.2), risk treatment and Statement of Applicability (6.1.3), security objectives (6.2), planning of changes (6.3)
7 Support
Resources, competence, awareness, communication, documented information
8 Operation
Operational planning and control, carrying out risk assessments and risk treatment
9 Performance evaluation
Monitoring and measurement, internal audit, management review
10 Improvement
Continual improvement, nonconformity and corrective action
ISO/IEC 27001:2022 incl. Amd 1:2024. Clauses 4 to 10 are mandatory; Annex A is selected based on risk.

Annex A: 93 controls in four themes

Annex A lists reference controls. You go through all of them, select those your risk treatment needs and justify every exclusion in the Statement of Applicability. ISO/IEC 27002:2022 gives implementation guidance for each control.

ISO/IEC 27001:2022 Annex A: 93 controls
A.5
Organizational controls
37
A.6
People controls
8
A.7
Physical controls
14
A.8
Technological controls
34
ISO/IEC 27001:2022, Annex A. The 2013 edition had 114 controls in 14 domains.

Eleven controls were new in 2022, among them threat intelligence (A.5.7), information security for use of cloud services (A.5.23), configuration management (A.8.9), data leakage prevention (A.8.12) and secure coding (A.8.28). How to document the decisions for each control is explained in our guide to the Statement of Applicability.

Mandatory documented information

The standard requires a set of documented information. Auditors will ask for each of these:

Documented information required by ISO/IEC 27001:2022
4.3
Scope of the ISMS
5.2
Information security policy
6.1.2
Information security risk assessment process
6.1.3
Risk treatment process, Statement of Applicability (6.1.3 d) and risk treatment plan
6.2
Information security objectives
7.2
Evidence of competence
8.1
Information needed to show processes are carried out as planned
8.2 / 8.3
Results of risk assessments and of risk treatment
9.1
Results of monitoring and measurement
9.2
Audit programme and audit results
9.3
Results of management reviews
10.2
Nonconformities, corrective actions and their results
Clause references to ISO/IEC 27001:2022. Policies required by individual Annex A controls come on top, depending on your Statement of Applicability.

The path to certification

The path to ISO/IEC 27001
1. Scope
Which locations, teams, systems and services are in the ISMS
2. Gap Audit
Against clauses 4 to 10 and the 93 Annex A controls
3. Risk assessment and treatment
Risks, owners, treatment plan, Statement of Applicability
4. Controls and evidence
Policies, technical measures, records
5. Internal audit and management review
The ISMS has to run before it is audited
6. Stage 1 and stage 2 audit
Documentation and readiness first, then effectiveness
7. Surveillance audits
Every year, recertification after three years
Certification bodies are accredited to ISO/IEC 17021-1 and ISO/IEC 27006.

In the stage 1 audit, the auditor reviews your documentation and checks whether you are ready for stage 2: scope, policy, risk assessment, Statement of Applicability, internal audit and management review. In the stage 2 audit, the auditor tests whether the controls work in practice, with interviews, samples and evidence. How long this takes depends on scope and starting point. What drives the cost is explained in What does ISO 27001 certification cost?.

Choose a certification body that is accredited for ISO/IEC 27001 by a national accreditation body, in Germany the DAkkS. Certificates from unaccredited bodies are often not accepted by customers.

ISO 27001, SOC 2, NIS2 and ISO 42001

How ISO 27001 relates to other frameworks
SOC 2
An attestation report under AICPA standards, common with US customers. ISO 27001 is a certificate. Many controls overlap. See SOC 2 or ISO 27001?
NIS2
EU law with risk-management and reporting duties. It does not require ISO 27001 certification, but an ISMS covers much of Article 21. See NIS2 in Germany
ISO 42001
The standard for AI management systems. Same clause structure, so both can run as one integrated system with a combined audit. See What is ISO 42001?
TISAX®
The assessment model used in the automotive industry, based on the VDA ISA catalogue, which builds on ISO 27001. See What is TISAX®?
Overlaps reduce effort when controls are mapped once and reused across frameworks.

Getting started

  1. Define the scope together with the customers or contracts that require the certificate.
  2. Get top management on board and approve the information security policy.
  3. Run a Gap Audit against clauses 4 to 10 and Annex A.
  4. Carry out the risk assessment and decide how to treat each risk.
  5. Build the Statement of Applicability with a reason for every included and excluded control.
  6. Implement controls and collect evidence, ideally from connected systems rather than screenshots.
  7. Let the ISMS run, with an internal audit and a management review, before stage 1.
  8. Pick an accredited certification body and book stage 1 and stage 2.

Where ISO 27001 projects go wrong

Starting with Annex A instead of risks. Controls should follow from the risk assessment. A Statement of Applicability that marks all 93 controls as applicable without reasons shows a template, not an ISMS.

A scope that is too wide or too vague. The scope decides the audit effort. It should match what customers actually need covered.

Policies nobody follows. Auditors sample evidence. A policy without records that it is applied is a finding.

Treating certification as the finish line. Surveillance audits come every year, and the ISMS has to keep producing evidence in between.

How GetTeddy helps with ISO 27001

GetTeddy is a compliance platform from Berlin. AI agents support the Gap Audit, draft policies and collect evidence from your tech stack. When an assessment is uncertain, the agents send it to a responsible person on your team for approval. A compliance engineer from our team helps you prepare for the audit, and we introduce you to accredited certification bodies. Controls are mapped once and reused for SOC 2, NIS2, TISAX® and ISO 42001. More on the ISO 27001 page.

Primary sources

FAQ: ISO 27001

How does ISO 27001 certification work?

Certification takes two audits. In Stage 1 the certification body reviews your documentation, such as the scope, the risk assessment and the Statement of Applicability. In Stage 2 it uses interviews and samples to check that the controls work in daily practice. After that, a surveillance audit follows every year.

Who issues the ISO 27001 certificate?

A certification body accredited for ISO/IEC 27001, in Germany by DAkkS. Consultants and software vendors do not issue certificates. GetTeddy puts you in touch with accredited bodies.

What does ISO 27001 certification cost?

It depends mainly on the scope, the number of people in it and your starting point. The audit fee follows the number of audit days. The larger cost is usually the time of your own team. Our article What does ISO 27001 certification cost? explains each cost block.

What is the Statement of Applicability?

The Statement of Applicability (SoA) lists all 93 Annex A controls. For each control it states whether you apply it, why, and whether it is implemented. Auditors usually read it first in Stage 1. More in ISO 27001 Statement of Applicability, explained.

Is ISO 27001 mandatory?

No. It is a voluntary standard. Customers, procurement teams and partners often require it in contracts, and it helps show that measures under laws such as NIS2 are in place.

What is the difference between ISO 27001 and ISO 27002?

ISO 27001 contains the requirements you are certified against. ISO 27002 is guidance on how to implement the Annex A controls. You cannot certify against ISO 27002.

How long is an ISO 27001 certificate valid?

Three years, with a surveillance audit every year. After three years a recertification audit follows.

Is there a new version of ISO 27001?

No. ISO/IEC 27001:2022 with Amendment 1:2024 is current. Details in Is there an ISO 27001:2027?.

Do we need software for ISO 27001?

No, the standard does not require any. Software helps once risks, controls and evidence have to be kept current across teams and frameworks. See ISMS software: what it does and how to choose one.

How GetTeddy handles this

From the first signal to an approved early warning, within 24 hours

GetTeddy links every security event to your product inventory, checks the CRA threshold and the NIS2 and GDPR duties next to it, and drafts the early warning with everything the form asks for. The decision and the submission stay with your named people.

How GetTeddy handles this

A new framework in an afternoon, not a second program

GetTeddy keeps one model of your company and one control set. When a new framework arrives, it reads every requirement against what you already have and labels it full, partial or missing. Only the real gaps become tasks.

How GetTeddy handles this

Agents do the work. You can see every step and stop any of it.

Every result in GetTeddy carries a label: done by an agent, drafted by an agent and approved by a person, or decided by you. Drafts wait for a named approver, connections are read-only unless you allow more, and every action lands in a log your auditor can read.