ISO 27001 vs ISO 27002: what each standard covers

Key takeaways

  • ISO 27001 sets requirements for an information security management system and allows certification, while ISO 27002 offers control guidance and has no standalone organizational certificate.
  • ISO 27002:2022 covers 93 controls grouped into organizational, people, physical and technological themes, showing that security is not only an IT responsibility.
  • Annex A is a reference set, not a mandate, so organizations justify each included or excluded control in a Statement of Applicability tied to risk.
  • Certification is assessed by a certification body in two stages, with Stage 1 reviewing readiness and Stage 2 examining implementation and effectiveness.

ISO 27001 sets requirements for managing information security, while ISO 27002 provides guidance on selecting and implementing security controls. Organizations can achieve certification to ISO 27001; ISO 27002 supports implementation rather than providing a separate organizational certification route. Understanding their different roles helps you plan security improvements, assign responsibilities, and prepare for assessment without treating the standards as interchangeable. (iso.org)

What is the difference between ISO 27001 and ISO 27002?

The central difference in ISO 27001 vs 27002 is management system requirements versus control guidance. ISO 27001 specifies how an organization must establish, operate, maintain, and improve an information security management system, or ISMS. ISO 27002 explains information security controls that can support that system, including their purposes and implementation considerations. (webstore.iec.ch)

These information security standards serve complementary purposes. One establishes an accountable approach to managing risk; the other helps teams translate security decisions into working practices. ISO 27002 can also be used independently by organizations seeking control guidance without pursuing certification. (iso.org)

Comparison point ISO 27001 ISO 27002
Primary focus Requirements for an ISMS Guidance for information security controls
Main application Managing security through a structured, risk-based system Designing and implementing appropriate safeguards
Organizational certification Available against its requirements Not a standalone organizational certification standard
Control coverage Annex A provides a reference set Provides detailed guidance for the corresponding controls
Relationship Establishes management obligations Supports practical control implementation

The table summarizes the standards’ relationship: ISO 27002 supports the control layer, but does not replace ISO 27001’s management requirements. (ascb.com)

What ISO 27001 covers beyond security controls

ISO 27001 addresses more than firewalls, passwords, or written policies. Its requirements cover the organizational arrangements needed to make security decisions, carry them out, evaluate results, and improve. Clauses 4 through 10 address context, leadership, planning, support, operation, performance evaluation, and improvement. (nqa.com)

For security management systems to remain useful, responsibilities and review processes need to survive staff changes, new suppliers, and changing business priorities. ISO 27001 provides the management structure for that ongoing work rather than treating security as a one-time implementation project. (webstore.iec.ch)

Its coverage includes:

  • Context and scope: Define the boundaries of the ISMS and understand relevant organizational needs and interested parties.
  • Leadership: Establish policy, responsibilities, and management commitment so security has direction and support.
  • Risk assessment and treatment: Evaluate information security risks consistently and decide how to address them.
  • Resources and operation: Provide competence, awareness, communication, documentation, and processes needed to operate the system.
  • Evaluation and improvement: Monitor performance, conduct internal audits and management reviews, and address nonconformities. (nqa.com)

A practical starting point is to map each area to an owner and existing evidence. Record gaps as actions rather than drafting disconnected policies. This keeps implementation focused on how the organization actually works.

What ISO 27002 covers in practice

ISO 27002:2022 provides guidance for 93 controls organized into four themes: organizational, people, physical, and technological. It expands on control statements with explanations of purpose and implementation guidance, helping teams understand how a safeguard can address a security need. (committee.iso.org)

The four themes demonstrate that information security is not exclusively an IT responsibility:

  • Organizational controls: Topics such as security policies, supplier relationships, incident management, and information classification. These concern how security is directed and coordinated.
  • People controls: Areas including awareness, training, confidentiality obligations, and remote working. These address responsibilities and behavior throughout working relationships.
  • Physical controls: Safeguards for facilities, equipment, and physical access. These help protect information wherever physical exposure creates risk.
  • Technological controls: Topics such as authentication, backups, logging, vulnerability management, and secure development. These address protection within systems and technical operations. (committee.iso.org)

For example, imagine a business reviewing access to customer records. It could use the guidance to develop a process covering access approval, changes when responsibilities shift, and removal when access is no longer justified. The implementation should fit the organization rather than become a copied procedure that nobody follows.

How do Annex A and the Statement of Applicability connect the standards?

Annex A connects the standards by providing the reference controls that ISO 27002 explains in greater detail. Under ISO 27001, organizations determine necessary controls through risk treatment, compare them with Annex A to check for omissions, and document their decisions in a Statement of Applicability, commonly called the SoA. (bsigroup.com)

Annex A is not a requirement to implement every control regardless of context. Organizations must justify their choices, and they may need controls drawn from other sources or designed for their own circumstances. Being listed in Annex A does not, by itself, establish that a control is necessary for every organization. (committee.iso.org)

The SoA records necessary controls, the reasons for including them, whether they are implemented, and justifications for excluding Annex A controls. Treat it as a decision record rather than a spreadsheet assembled immediately before an audit. Its value is the connection it creates between business risks and actual safeguards. (committee.iso.org)

As an illustrative example, a company using a hosted platform might need to distinguish its own access responsibilities from those handled by its provider. Recording those boundaries makes the control decision more useful than simply marking “implemented.” It also gives the team something concrete to revisit when the service changes.

ISO 27002 vs ISO 27001 in the certification process

The ISO certification process concerns ISO 27001’s requirements for the ISMS, not a separate certificate for following ISO 27002. Certification is optional, and ISO itself does not issue an organization’s certificate; assessment is performed by a certification body. An accredited certification body provides an additional level of independently assessed competence. (iso.org)

A typical certification journey includes preparation followed by a two-stage external assessment:

  1. Establish and operate the ISMS. Define its scope, assess risks, implement the necessary processes and controls, and retain evidence of operation.
  2. Evaluate readiness internally. Use internal audits and management review to identify gaps and organize corrective work before external assessment.
  3. Complete Stage 1. The certification body reviews readiness, including relevant management system documentation and preparation for the next stage.
  4. Complete Stage 2. The assessment examines implementation and effectiveness, rather than relying solely on the existence of procedures. (bsigroup.com)

ISO 27002 is useful during preparation because it supports effective control implementation. However, reading its guidance or adopting technical safeguards does not replace the wider management system work required by ISO 27001. (bsigroup.com)

Which standard should your organization start with?

Start with ISO 27001 when your objective is to establish an ISMS or pursue organizational certification. Start with ISO 27002 when your immediate need is guidance on specific security controls, while recognizing that control improvements alone do not establish conformity with ISO 27001. The standards can also be used together from the outset. (webstore.iec.ch)

For teams weighing ISO 27002 vs 27001, the most useful first step is to clarify the intended outcome. A customer request for certification points toward a management system project. A need to improve a particular safeguard may call for a narrower implementation task.

Use this planning checklist to turn that distinction into action:

  • Confirm the outcome: Record whether you need certification, stronger controls, or both, and identify who owns that decision.
  • Set workable boundaries: List the services, information, teams, and suppliers the project will address before assigning tasks.
  • Review existing practices: Gather current policies and operational records so useful work is retained rather than recreated.
  • Turn guidance into ownership: For each proposed improvement, name an owner, define completion evidence, and decide how effectiveness will be reviewed.
  • Separate preparation from proof: Distinguish a drafted procedure from a process that has actually operated and produced records.

This approach avoids framing the standards as competing purchases. It also gives leadership and implementation teams a shared explanation of what the project is intended to deliver.

The practical takeaway

In the ISO 27001 vs ISO 27002 comparison, what each standard covers determines how you use it: ISO 27001 supplies the management requirements, while ISO 27002 supports control implementation. Use the first to structure accountability and improvement, and the second to inform safeguards suited to your risks. They are complementary tools, not interchangeable routes to certification. (webstore.iec.ch)

Sources

  1. iso.org
  2. ISO/IEC 27001:2022 | IEC
  3. iso.org
  4. ISO/IEC 27001: requirements for an information security management system | Standards Library | ASCB
  5. nqa.com: NQA ISO 27001 Implementation Guide
  6. committee.iso.org: ISO IEC%20JTC%201 SC%2027 N22755 SC27%20Journal%20Vol%202%20Issue%202%20%28update%20Dec%202022%29
  7. Accelerating Progress Towards a Sustainable World - Indonesia | BSI
  8. committee.iso.org: ISO IECJTC1 SC27 WG1 N3298 Auditing%20Practices%20Note%20 %20SoA
  9. bsigroup.com: Iso27001 stepbystep guide implementation