ISO/IEC 27001 is the certifiable standard: it sets the requirements for an information security management system in clauses 4 to 10 and lists 93 reference controls in Annex A. ISO/IEC 27002 is the companion guidance: for each of those 93 controls it explains the purpose and how to implement it, and nobody is certified against it. You certify to 27001 and use 27002 to decide how each selected control works in practice. The two 2022 editions share the same four themes and numbering, so A.5.7 in Annex A is control 5.7 in ISO 27002.
ISO 27001 and ISO 27002 are complementary standards in the ISO 27000 family. While ISO 27001 defines the requirements for an ISMS, ISO 27002 provides detailed implementation guidance for security controls. When implementing information security management systems, organizations often encounter both ISO 27001 and ISO 27002. While these standards are closely related and part of the same family, they serve different purposes and understanding their relationship is crucial for effective implementation.
This article explores the key differences between ISO 27001 and ISO 27002, how they complement each other, and provides practical guidance on using both standards together to build a robust information security framework.
What is ISO 27001?
ISO 27001 is the specification standard for Information Security Management Systems (ISMS). It defines the requirements that an organization must meet to establish, implement, maintain, and continually improve an ISMS. It's the standard against which organizations can be certified.
Key characteristics of ISO 27001:
- Requirements-based: Specifies what must be done, not how to do it
- Certifiable: Organizations can achieve third-party certification
- Management system focus: Emphasizes the overall management approach
- Risk-based: Built around risk assessment and treatment
What is ISO 27002?
ISO 27002 is a code of practice that provides detailed guidance on implementing information security controls. It offers best practice recommendations for information security management and is designed to be used alongside ISO 27001.
Key characteristics of ISO 27002:
- Guidance-based: Provides detailed implementation guidance
- Not certifiable: Cannot be certified against directly
- Control-focused: Detailed information about specific security controls
- Practical implementation: Shows how to implement controls effectively
Key Differences Between ISO 27001 and ISO 27002
1. Purpose and Scope
ISO 27001: Defines the requirements for establishing and maintaining an ISMS. It's about creating a systematic approach to managing information security risks.
ISO 27002: Provides detailed guidance on implementing specific information security controls. It's about the practical application of security measures.
2. Structure and Content
ISO 27001: Contains 10 main clauses covering the management system requirements, plus Annex A with 93 controls organized into four themes — organizational, people, physical and technological.
ISO 27002: Organized into the same four themes as ISO 27001's Annex A, with a purpose and detailed implementation guidance for each of the 93 controls, plus attributes that let you view the set by control type, security property or operational capability.
3. Certification
ISO 27001: Organizations can be certified against this standard by accredited certification bodies.
ISO 27002: Cannot be certified against directly, but its guidance helps organizations meet ISO 27001 requirements.
4. Level of Detail
ISO 27001: High-level requirements and management system elements.
ISO 27002: Detailed, practical guidance on implementing specific controls.
How ISO 27001 and ISO 27002 Work Together
These standards are designed to be used together as a comprehensive information security management approach:
1. ISO 27001 Sets the Framework
ISO 27001 establishes the management system structure, requiring organizations to:
- Define the scope of their ISMS
- Conduct risk assessments
- Select appropriate controls from Annex A
- Implement and monitor the selected controls
- Continuously improve the system
2. ISO 27002 Provides Implementation Guidance
When organizations select controls from ISO 27001's Annex A, ISO 27002 provides detailed guidance on:
- How to implement each control effectively
- What specific measures to take
- Best practices for control implementation
- Common pitfalls to avoid
Practical Example: Access Control
Let's look at how both standards work together for access control:
ISO 27001 Approach:
- Lists the access controls in Annex A: A.5.15 to A.5.18 for the access control policy, identities, authentication information and access rights, and A.8.2 to A.8.5 for privileged access, information access restriction, source code and secure authentication
- Requires the selection of those controls to follow from the risk assessment, with the decision recorded in the Statement of Applicability
- Requires monitoring and review of access controls
ISO 27002 Guidance:
- Provides detailed guidance on user access management
- Explains how to implement privileged access management
- Offers specific recommendations for access control policies
- Details technical and administrative controls
Implementation Strategy
To effectively use both standards together:
1. Start with ISO 27001
- Establish the ISMS framework
- Define scope and objectives
- Conduct risk assessment
- Select relevant controls from Annex A
2. Use ISO 27002 for Implementation
- Reference ISO 27002 for detailed control implementation
- Adapt guidance to your specific environment
- Use as a checklist for control effectiveness
- Leverage for training and awareness programs
3. Maintain Alignment
- Ensure implemented controls meet ISO 27001 requirements
- Regularly review and update based on both standards
- Use ISO 27002 guidance for continuous improvement
Benefits of Using Both Standards Together
- Comprehensive Coverage: Management system requirements plus detailed implementation guidance
- Risk-Based Approach: Systematic risk management with practical control implementation
- Best Practices: Access to industry best practices and proven methodologies
- Flexibility: Can be adapted to different organizational contexts
- Certification Path: Clear path to ISO 27001 certification
Common Misconceptions
Misconception 1: "ISO 27002 is just a newer version of ISO 27001"
Reality: They are complementary standards designed to work together, not different versions of the same standard.
Misconception 2: "You only need ISO 27001 for certification"
Reality: While only ISO 27001 is certifiable, ISO 27002 provides essential implementation guidance that helps achieve certification.
Misconception 3: "ISO 27002 controls are mandatory"
Reality: ISO 27002 provides guidance on controls; the specific controls to implement are determined by your risk assessment.
Conclusion
ISO 27001 and ISO 27002 are designed to work together as a comprehensive information security management approach. ISO 27001 provides the management system framework and requirements, while ISO 27002 offers detailed implementation guidance for security controls.
Organizations that understand how to leverage both standards effectively can build more robust, practical, and certifiable information security management systems. The key is to use ISO 27001 to establish the framework and ISO 27002 to guide the practical implementation of controls.
By combining the systematic approach of ISO 27001 with the practical guidance of ISO 27002, organizations can create information security programs that are both compliant and effective in managing real-world security risks.
How Noru Simplifies ISO 27001 and ISO 27002 Implementation
Implementing both ISO 27001 and ISO 27002 doesn't have to be a complex, time-consuming process. Noru integrates with your existing systems — AWS, GCP, Azure, GitHub, Entra ID and more — to gather evidence continuously and map it to the Annex A controls it satisfies, so each control carries a current status and a dated evidence history. Controls no system can observe, such as most physical controls, are evidenced with uploaded documents instead.
Cortex, Noru's AI layer, drafts the policies ISO 27001 expects, grounded in the evidence already in your program, and people review and approve them. Vulnerability and pen-test findings are tracked to resolution and linked to risk, so when the certification audit arrives the evidence for each applicable control is already dated and in place.