ISO 27036 vs ISO 27001

ISO 27036 vs ISO 27001: Scope, requirements, key differences

An organization can have a strong information security management system (ISMS) and still face security risks through its suppliers. A third-party provider may handle sensitive information, connect to internal systems, or support critical business operations. If its security practices fall short, the organization may face risks that extend beyond its own environment.

ISO 27001 and ISO 27036 address different aspects of this problem. ISO 27001 provides requirements for establishing and maintaining an organization-wide ISMS. ISO 27036 focuses on information security in supplier and acquirer relationships.

Understanding the difference helps you decide how to manage supplier risks within your wider information security program. It also shows why using both standards can provide a more complete approach to information security.

ISO 27036 vs. ISO 27001: At a glance

Both standards support information security, but they differ in scope, purpose, and application.

ISO 27001ISO 27036
Focus Establishing, implementing, maintaining, and continually improving an information security management system (ISMS).Addressing information security risks and requirements within supplier and acquirer relationships.
Scope Covers the organization’s information security management, including people, processes, technology, and relevant external relationships.Focuses on security across supplier relationships involving products and services, including ICT supply chains and cloud services.
Main objective Helps organizations manage information security risks through a systematic, risk-based management approach.Helps organizations define, implement, monitor, and maintain security requirements throughout supplier relationships.
Structure A management-system standard with requirements for establishing and improving an ISMS, supported by Annex A reference controls.A four-part series covering supplier relationship concepts, requirements, ICT supply chain security, and cloud services.
Implementation Establish an ISMS, assess and treat risks, select relevant controls, monitor performance, and improve the system.Define supplier security requirements, establish responsibilities, assess supplier capabilities, and address security throughout the relationship.
Certification Organizations can obtain ISO 27001 certification through an independent certification process.The series is not a certifiable management-system standard. Organizations can use its requirements and guidance without obtaining ISO 27036 certification.

The main distinction is that ISO 27001 establishes the broader management system, while ISO 27036 addresses the security requirements and responsibilities that apply to supplier relationships. However, the two are not unrelated: supplier security is already part of the wider information security management approach covered by ISO 27001.

Related: ISO 27034 vs ISO 27001: Key differences, controls, implementation

Key differences between ISO 27001 and ISO 27036

Let’s look at how each one addresses information security.

1. Scope: Organization-wide security vs. supplier relationships

ISO 27001 takes an organization-wide approach to information security. It helps you establish an ISMS that covers the information, processes, people, and systems within its defined scope. This includes risks arising from external parties and suppliers.

ISO 27036 has a narrower focus. It addresses information security within relationships between organizations that acquire products or services and the suppliers that provide them.

For example, an organization may use ISO 27001 to manage risks across its internal systems, employee access, business processes, and external service providers. ISO 27036 helps it address the specific security expectations and responsibilities involved in working with those providers.

2. Approach: Managing ISMS risks vs. managing supplier security requirements

ISO 27001 requires organizations to establish a risk assessment and treatment process. They identify information security risks, determine how to address them, and select appropriate controls. The organization then monitors and improves its ISMS.

Supplier-related risks are part of this process. ISO 27001:2022 Annex A includes controls for addressing information security in supplier relationships, ICT supply chains, and the use of cloud services.

ISO 27036 provides a more focused approach to those relationships. It addresses how suppliers and acquirers define security requirements, establish responsibilities, and maintain security expectations throughout their interactions.

For example, an organization may identify unauthorized access to customer information through a supplier as an information security risk under its ISMS. It can then use ISO 27036 to structure the requirements it communicates to that supplier, including access restrictions, evidence of security controls, and incident communication arrangements.

3. Implementation: ISMS processes vs. supplier relationship management

Implementing ISO 27001 involves establishing the processes needed to operate an ISMS. This includes defining its scope, assigning responsibilities, assessing risks, applying controls, conducting internal audits, and reviewing performance.

Applying ISO 27036 involves addressing security throughout the supplier relationship. This starts with defining requirements for the products or services being acquired and continues through implementation, operation, monitoring, review, and improvement.

The difference becomes clearer when you consider a supplier that processes sensitive business information.

Under ISO 27001, the organization identifies and treats the risks associated with that supplier as part of its ISMS. Under ISO 27036, it can establish how the supplier must protect the information, what evidence it must provide, how both parties handle security incidents, and how they address changes to the relationship.

4. Certification: Certifiable standard vs. supplier security requirements and guidance

ISO 27001 is a certifiable management-system standard. Organizations can undergo an independent audit to demonstrate that their ISMS meets its requirements. Certification provides external assurance about the ISMS within the defined certification scope.

ISO 27036 serves a different purpose. It provides requirements and guidance for information security in supplier relationships, but it does not define a separate management system for organizations to certify against.

An organization can use ISO 27036 to strengthen its supplier security practices without pursuing a separate certification. It can also use the series alongside an ISO 27001-certified ISMS.

How ISO 27001 and ISO 27036 work together

ISO 27001 and ISO 27036 are complementary. The first provides a broader structure for managing information security, while the second helps you address security requirements in supplier relationships.

Consider an organization that uses a third-party cloud provider to store and process customer information. The organization already has an ISO 27001-based ISMS, but it needs to ensure that the provider can meet its security expectations.

Here is how the two standards can support that process.

Identify how the cloud provider’s services affect your organization’s information security. Consider the type of information it handles, the access it requires, and the impact of a service disruption or security incident.

ISO 27001 provides the risk management structure for identifying and treating these risks. The organization can assess the potential impact of unauthorized access, data loss, service interruptions, or weaknesses in the provider’s security controls.

2. Define security requirements for the supplier

Once you understand the risks, translate them into specific security requirements for the supplier.

ISO 27036-2:2022 is particularly relevant here. It specifies fundamental information security requirements for defining, implementing, operating, monitoring, reviewing, maintaining, and improving supplier and acquirer relationships.

For the cloud provider, your requirements may cover:

  • Access to customer information and administrative accounts.
  • Protection of information during storage and transmission.
  • Security incident notification and communication.
  • Data retention, return, and deletion.
  • Security responsibilities and subcontractor arrangements.

These requirements should reflect the services the provider delivers and the risks associated with the relationship.

3. Establish responsibilities between both parties

Security responsibilities should be clear to both the organization and the supplier. An agreement should explain which party manages specific controls, what information must be shared, and how security issues will be handled.

For example, the cloud provider may be responsible for securing its underlying infrastructure, while the customer remains responsible for configuring user permissions and managing access to its own accounts.

The exact division depends on the service and agreement. ISO 27036 helps address these responsibilities within the supplier relationship, while ISO 27001 provides the wider management context for the organization’s security obligations.

4. Assess and verify supplier security practices

After defining the requirements, determine whether the supplier can meet them. Request relevant evidence, review certifications and assurance reports, and assess the controls that apply to the services you use.

For example, you may request evidence of access reviews, encryption practices, vulnerability management, or incident response procedures.

This process helps you compare the supplier’s actual security practices against the requirements you established. It also gives you a basis for identifying gaps and agreeing on corrective actions.

Related: How to implement ISO 27036 in your supplier security program

5. Monitor the relationship and address changes

Supplier security does not remain static. A provider may change its infrastructure, introduce new subcontractors, experience an incident, or modify how it processes your information.

Establish how the supplier will communicate relevant changes and how your organization will review their impact. Track unresolved findings, request updated evidence when needed, and reassess the relationship when significant changes occur.

ISO 27001 supports ongoing risk monitoring and improvement through the ISMS. ISO 27036-2 addresses monitoring, reviewing, maintaining, and improving the supplier relationship itself.

Together, the standards help you connect changes in supplier security with your organization’s broader information security risk management process.

Related: Third-party security assessment checklist: Questions to ask and evidence to review

Should you use ISO 27001, ISO 27036, or both?

Your choice depends on what you need to address. The standards serve different purposes, so adopting one does not automatically make the other unnecessary.

Use ISO 27001 if:

  • You need to establish or improve an organization-wide ISMS.
  • You want a structured process for identifying, assessing, and treating information security risks.
  • You need to demonstrate that your information security management system meets an internationally recognized set of requirements.
  • You want to pursue independent ISMS certification.

Use ISO 27036 if:

  • You need a structured approach to information security in supplier and acquirer relationships.
  • You want to define security requirements for suppliers and service providers.
  • You need to clarify security responsibilities between your organization and external parties.
  • You want to address risks across supplier relationships, ICT supply chains, or cloud services.

Use both if:

  • You want supplier security requirements to support your wider ISMS.
  • Your organization depends on external providers to handle sensitive information or deliver critical services.
  • You need to connect internal risk assessments with supplier requirements, evidence reviews, and ongoing oversight.
  • You want a consistent approach to managing information security across internal operations and external relationships.

For many organizations with significant supplier dependencies, using both standards provides a more connected approach. ISO 27001 establishes the information security management structure, while ISO 27036 helps address the requirements and responsibilities that apply to supplier relationships.

Manage information security and supplier risks with CyberArrow

Managing information security across an organization and its supplier relationships involves tracking risks, controls, assessments, and corrective actions. CyberArrow helps bring these activities together through its GRC platform.

With CyberArrow, you can:

  • Manage information security risks: Identify, assess, and track risks across your organization.
  • Conduct supplier assessments: Use third-party assessments and security questionnaires to evaluate supplier practices.
  • Track vendor risk: Use vendor scoring and risk tracking to maintain visibility into supplier risk.
  • Monitor remediation: Document security gaps and follow corrective actions.
  • Support compliance activities: Keep compliance requirements, evidence, and related activities organized in one platform.

Schedule a demo to see how CyberArrow can support your information security and third-party risk management activities.

FAQs

Is ISO 27036 part of ISO 27001?

No. ISO 27036 is a separate series of standards focused on information security in supplier relationships. ISO 27001 establishes requirements for an organization’s ISMS. The two standards complement each other.

Does ISO 27001 cover supplier security?

Yes. ISO 27001 addresses supplier-related information security risks through its risk management requirements and Annex A controls. These include controls for supplier relationships, ICT supply chains, and cloud services. ISO 27036 provides more detailed requirements and guidance for supplier relationships.

Can an organization get certified against ISO 27036?

No. ISO 27036 is not a certifiable management-system standard. Organizations can apply its requirements and guidance to strengthen information security in supplier relationships, but it does not offer a certification equivalent to ISO 27001.

Do you need ISO 27001 before implementing ISO 27036?

No. You do not need ISO 27001 certification to use ISO 27036. However, ISO 27036-2 expects organizations to have foundational processes, including risk management, business management, and information security, in place or actively planned.

Avatar photo
CyberArrow team