Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is ISO/IEC 27002?

ISO/IEC 27002 is the implementation guidance companion to ISO 27001. It explains each of the 93 information security controls in detail, with purpose, guidance, and attributes for filtering.

Illustration for the cybersecurity term ISO/IEC 27002
Home / Blog / Cybersecurity Terms / What Is ISO/IEC 27002?
17 November 2026

What Is ISO/IEC 27002?

What Is ISO/IEC 27002?

ISO/IEC 27002 is the reference manual that sits behind ISO/IEC 27001. Where 27001 lists controls in Annex A as a single line each, 27002 devotes one to three pages to every control: what it is, why it exists, how to implement it, and what to consider in doing so. Nobody is certified against it, and nobody should try to implement 27001 without it.

The current edition, ISO/IEC 27002:2022, was a substantial rewrite. The 2013 version had 114 controls across 14 clauses; the 2022 version consolidated and modernised them into 93 controls across four themes, and the corresponding Annex A of ISO/IEC 27001:2022 follows the same structure.

The Four Themes

ThemeControlsScope
Organisational37Policies, roles, supplier relationships, cloud services, threat intelligence, incident management, continuity
People8Screening, terms of employment, awareness, disciplinary process, remote working, reporting events
Physical14Perimeters, entry controls, equipment siting, cabling, maintenance, secure disposal, clear desk
Technological34Endpoints, privileged access, cryptography, logging, monitoring, secure coding, data masking, web filtering

The Eleven New Controls

These are the ones organisations transitioning from the 2013 edition had to add, and they tell you how the threat landscape moved between 2013 and 2022:

Control Attributes: The Quietly Useful Addition

Each control in the 2022 edition carries five attributes, allowing the set to be filtered and sorted for different audiences:

In practice this matters more than it sounds. A security manager can produce a view of every detective control, or every control supporting the respond function, which makes gap analysis against another framework considerably faster and makes reporting to different audiences possible from one control set.

How to Use It Properly

Treat 27002 as guidance, not as a checklist to be implemented in full. The standard says so explicitly: controls are selected based on the risk assessment, and the Statement of Applicability records which apply. Implementing all 93 regardless of risk is both expensive and a sign that the risk assessment is not driving anything.

The implementation guidance is written generically, which is its strength and its limitation. Control 8.8 on management of technical vulnerabilities tells you to obtain information about vulnerabilities, evaluate exposure, and take appropriate measures; it does not tell you what remediation window is appropriate for your estate. That decision is yours, and the standard expects you to document it.

Where It Sits Among Other References

For organisations that want prescriptive technical detail, CIS Controls and CIS Benchmarks are more directive, and NCSC guidance is more specific to UK conditions. The sensible combination is 27002 for the control narrative that auditors read, and CIS or vendor hardening guidance for the configuration engineers apply.

Sector extensions exist where the generic guidance is insufficient: ISO/IEC 27017 for cloud services, ISO/IEC 27018 for personal data in public clouds, ISO/IEC 27019 for energy utilities, and ISO 27799 for health informatics. Each adds or refines guidance rather than replacing it.

Whichever reference you build from, the control text describes intent; only testing shows whether the implementation achieves it, which is what our penetration test services establish.

FAQ – Frequently Asked Questions

What Is the Difference Between ISO 27001 and ISO 27002?

ISO 27001 specifies the requirements for an information security management system and is certifiable; its Annex A lists controls as brief statements. ISO 27002 is guidance that explains each of those controls in depth, with purpose, implementation advice, and attributes. You certify against 27001 and use 27002 to work out how to implement what it requires.

Do We Have to Implement All 93 Controls?

No. Controls are selected on the basis of your risk assessment, and the Statement of Applicability records which apply, why, and how. Excluding a control is legitimate when justified and consistent with the risk assessment, for example physical controls in a fully remote organisation with no premises. Implementing everything regardless of risk wastes resources.

What Changed in the 2022 Version?

The 114 controls across 14 clauses became 93 controls across four themes: organisational, people, physical, and technological. Many controls were merged, and eleven were new, including threat intelligence, cloud services security, ICT readiness for continuity, configuration management, data masking, data leakage prevention, web filtering, and secure coding. Five attributes were added to every control.

Can We Be Certified Against ISO 27002?

No. ISO/IEC 27002 is a guidance document with no requirements to audit against, so no certification exists. Certification is against ISO/IEC 27001. Any provider offering ISO 27002 certification is selling something that does not exist in the accredited certification system, which is itself a useful signal about the provider.

Related Terms

You May Be Interested In These

What Is a Deauthentication Attack?

Cybersecurity Terms

17 November 2026

What Is a Deauthentication Attack?

Read More
Why Is Patch Management Difficult in OT?

Cybersecurity Terms

17 November 2026

Why Is Patch Management Difficult in OT?

Read More
What Is a SYN Flood Attack?

Cybersecurity Terms

17 November 2026

What Is a SYN Flood Attack?

Read More