Home  /  Insights  /  ISO 27001 vs ISO 27002: what’s the difference?
Insights

ISO 27001 vs ISO 27002: what’s the difference?

ISO 27001 and ISO 27002 are published as a pair and share the same 93 controls, so they are easy to mix up. One tells you what you must do to be certified. The other explains how to do the control part well. Here’s how they relate and how to use both.

Cyber Veda

Quick answer: ISO/IEC 27001 is the requirements standard: it defines the information security management system you must run and lists 93 controls in Annex A, and it is the standard you are certified against. ISO/IEC 27002 is guidance: it explains each of those 93 controls, its purpose and how to implement it, and adds attributes for sorting them. You can’t be certified to ISO 27002; you use it to implement ISO 27001 well.

The short answer

ISO/IEC 27001 says what you must have. ISO/IEC 27002 explains how to implement the controls. ISO 27001 is written as requirements, the things an auditor checks. ISO 27002 is written as recommendations, the things good practice suggests. Certification bodies audit you against ISO 27001; ISO 27002 is a reference you use while building the system.

Side by side

ISO/IEC 27001:2022ISO/IEC 27002:2022
TypeRequirements standardGuidance standard
LanguageRequirements (“shall”)Recommendations (“should”)
Can you be certified to it?Yes, by an accredited certification bodyNo
Main contentClauses 4 to 10 for the management system, plus Annex A listing 93 controlsThe same 93 controls, each with purpose, implementation guidance and attributes
Management system requirementsYes: context, leadership, risk, support, operation, evaluation, improvementNo
Detail per controlA sentence or twoTypically several paragraphs
PublishedOctober 2022, amended 2024 for climate changeFebruary 2022
Who uses itOrganisations seeking certification, certification auditors, buyers checking scopePeople designing and implementing controls, internal auditors, and organisations using it as a control framework without certifying

What ISO 27001 does

ISO 27001 defines an information security management system (ISMS): a way of running security that sets scope and objectives, assesses risk, chooses controls, measures how they work and improves them. Clauses 4 to 10 are mandatory and can’t be excluded. Our guide to ISO 27001 clauses 4 to 10 explains each one.

Annex A lists 93 controls. Clause 6.1.3 requires you to determine the controls your risk treatment needs, then compare them with Annex A so nothing necessary is overlooked. The result is recorded in your Statement of Applicability. Annex A gives each control a number, a title and a one- or two-sentence statement of what the control is, and that’s all. It doesn’t tell you how to implement it. For how the controls are organised, see ISO 27001 Annex A controls explained.

What ISO 27002 does

ISO 27002 takes each of those 93 controls and expands it. For every control it gives:

  • The control itself, matching Annex A.
  • A purpose, explaining why the control exists and what risk it addresses.
  • Guidance on implementation: what a well-designed control covers and the practical points to consider.
  • Other information, such as related standards and considerations for particular situations.
  • Attributes, a set of tags for viewing the controls in different ways (more on these below).

Because it is guidance, nothing in ISO 27002 is mandatory. It is written for a wide range of organisations, so some recommendations won’t fit yours. You take what is relevant, adapt it to your risks and size, and add your own where needed. ISO 27002 can also be used on its own as a control catalogue by organisations that want good security practice without certification. That is a legitimate choice, but it gives you nothing a buyer can verify.

How the 2022 editions are structured

The 2022 editions replaced the 2013 structure of 114 controls in 14 domains with 93 controls in four themes: organisational (clause 5 of ISO 27002, 37 controls), people (clause 6, 8 controls), physical (clause 7, 14 controls) and technological (clause 8, 34 controls). Control numbers and titles are the same in both standards, so control A.8.13 (information backup) in ISO 27001 is control 8.13 in ISO 27002. The 2022 edition of ISO 27002 also changed its title from “Code of practice for information security controls” to simply “Information security controls”, and added an annex mapping the new controls to the 2013 ones, which helped organisations through the transition.

Attributes

Attributes are the main new feature of ISO 27002:2022. Each control is tagged with values in five attribute types:

Attribute typeValuesUseful for
Control typePreventive, detective, correctiveChecking you can detect and recover, not just prevent
Information security propertiesConfidentiality, integrity, availabilityLinking controls to the properties your risk assessment uses
Cybersecurity conceptsIdentify, protect, detect, respond, recoverMapping to frameworks built on those functions, such as the NIST CSF
Operational capabilitiesPractitioner areas such as governance, asset management, identity and access management, and supplier relationships securityAssigning control ownership to teams
Security domainsGovernance and ecosystem, protection, defence, resilienceReporting to leadership in plain groupings

The cybersecurity concepts come from ISO/IEC TS 27110, which uses the same five functions as the original NIST Cybersecurity Framework. NIST CSF 2.0 has since added a sixth, Govern, so the mapping is close but not exact; see ISO 27001 vs NIST CSF. Attributes are optional. You can use them, ignore them or define your own, and the standard says so.

How to use ISO 27002 when implementing ISO 27001

  • After the risk assessment, not before. Your risk assessment decides which controls you need. Starting with ISO 27002 and implementing everything in it produces an expensive, generic ISMS that doesn’t match your risks.
  • To understand what a control really means. A one-line Annex A statement can be read narrowly or broadly. The ISO 27002 purpose and guidance show what a complete implementation covers, which helps you decide whether what you already do is enough.
  • To write better justifications. Your Statement of Applicability must say why each control is included or excluded. Knowing the control’s purpose makes it much easier to justify an exclusion properly, or to see that an exclusion doesn’t hold.
  • To right-size policies and procedures. Use the guidance as a checklist of topics to consider, then write in your own words what you actually do. Copying ISO 27002 text into a policy creates commitments you may not keep, and the auditor tests whether you follow what you wrote. Our guide to required documents covers what has to exist.
  • To prepare for the auditor’s questions. Auditors know ISO 27002 well and use it to interpret controls. If you deliberately depart from the guidance, be ready to explain why your approach still meets the control and treats the risk. A good example is penetration testing, which the guidance mentions but ISO 27001 doesn’t mandate.

Reading the guidance is straightforward. Judging which parts apply to a business your size, and where a lighter approach is still defensible at audit, is where experience counts, and it is the part we take on for clients in our ISO 27001 implementation.

The rest of the ISO 27000 family

ISO 27001 and 27002 sit in a larger family of related standards. Only a few are certifiable; most are guidance. The ones you are most likely to meet:

StandardWhat it coversCertifiable?
ISO/IEC 27000Overview of the family and the vocabulary used across itNo
ISO/IEC 27001ISMS requirements and the Annex A control listYes
ISO/IEC 27002Implementation guidance for the 93 controlsNo
ISO/IEC 27005Guidance on information security risk management, supporting clauses 6.1 and 8.2No
ISO/IEC 27017Cloud-specific guidance on the ISO 27002 controls, with additional cloud controls, for providers and customersNo, but often added as an extension to an ISO 27001 certificate
ISO/IEC 27018Protecting personal information in public clouds where the provider acts as a PII processor (current edition 2025)No, but often added as an extension to an ISO 27001 certificate
ISO/IEC 27701Privacy information management system requirements; since the 2025 edition a standalone management system standardYes

For cloud and SaaS businesses, our guide to ISO 27001 for SaaS explains when ISO 27017 and 27018 are worth adding. For privacy, see ISO 27001 vs ISO 27701 and our ISO 27701 internal audit. ISO 27005 is useful background for the risk method but not required; your method only has to meet clause 6.1.2.

Common misunderstandings

  • “We follow ISO 27002, so we’re nearly certified.” Good controls are only part of it. Without the management system in clauses 4 to 10, including a risk assessment, objectives, internal audit and management review, there is nothing to certify.
  • “Annex A is a checklist of 93 things to implement.” It is a reference list to compare against. You include the controls your risks and obligations call for and justify the rest.
  • “Every ‘should’ in ISO 27002 is a requirement.” None of them are. They are a strong starting point, adapted to your size and risks.
  • “The 2013 guidance still works.” The control set, numbering and structure all changed in 2022. Work from the current editions.

Which one do you need?

If a customer, tender or partner is asking for proof of your security, you need ISO 27001 certification; nothing else in the family substitutes for it. ISO 27002 is the companion you use to implement the controls well. If nobody is asking for a certificate and you want a structured set of good practices, ISO 27002 alone is a reasonable reference, and you can certify to ISO 27001 later without starting again, because the controls are the same. Also check what the buyer will accept: some accept SOC 2 or the Essential Eight instead.

Next step

If you’re implementing ISO 27001 yourselves, ISO 27002 will be your most-used reference. Plan the internal audit early too: ISO 27001 requires it to be objective and impartial, so your staff can audit only areas they didn’t build, which is why many small teams bring in an independent internal auditor. If you’d rather have the ISMS built with you, see how our ISO 27001 service works or book a free 30-minute consultation.

FAQ

Common questions

Can you be certified to ISO 27002?

No. ISO/IEC 27002 is a guidance standard with no requirements to audit against, so no accredited certification body can certify you to it. Certification is to ISO/IEC 27001. A claim to be “ISO 27002 certified” or “ISO 27002 compliant” has no independent verification behind it.

Do I need to buy ISO 27002 to get ISO 27001 certified?

It isn’t required. ISO 27001 contains everything you are audited against, including the Annex A control list. But each Annex A control is only a sentence or two, and ISO 27002 explains what it means and how to implement it, so most people building an ISMS find it worth having.

Is ISO 27002 the same as Annex A?

They cover the same 93 controls with the same numbers and titles. Annex A in ISO 27001 lists each control in brief. ISO 27002 adds a purpose, implementation guidance, other information and a set of attributes for each one.

Can an auditor raise a nonconformity for not following ISO 27002?

Not on its own. The auditor audits against the requirements of ISO 27001 and your own ISMS. If you implement a control differently from the ISO 27002 guidance, that is acceptable as long as it meets the control and treats your risks. Auditors know the guidance well, though, and will ask why you departed from it.

Which version of ISO 27002 is current?

ISO/IEC 27002:2022, published in February 2022. ISO/IEC 27001:2022 followed in October 2022 with an Annex A aligned to it. The transition from the 2013 editions ended on 31 October 2025.

Talk to someone who has taken companies like yours to audit.

Book a free 30-minute consultation. Tell us what is driving the need, and leave with a realistic timeline and the first three things to do.