Standards Comparison

    REACH

    Mandatory
    2007

    EU regulation for chemicals registration, evaluation, authorisation, restriction

    VS

    ISO 27017

    Voluntary
    2015

    International code of practice for cloud security controls

    Quick Verdict

    REACH mandates chemical safety registration and risk management across EU supply chains, while ISO 27017 provides voluntary cloud security guidance extending ISO 27001. Companies adopt REACH for legal compliance; ISO 27017 for trusted cloud assurance and procurement edge.

    Chemical Safety

    REACH

    Regulation (EC) No 1907/2006 on REACH

    Cost
    €€€
    Complexity
    Medium
    Implementation Time
    18-24 months

    Key Features

    • Shifts chemical risk responsibility to industry
    • Requires registration above 1 tonne/year per entity
    • Authorisation list with sunset dates for SVHCs
    • EU-wide restrictions via Annex XVII updates
    • Mandatory supply-chain SDS communication
    Cloud Security

    ISO 27017

    ISO/IEC 27017:2015 Code of practice for cloud security

    Cost
    €€€
    Complexity
    High
    Implementation Time
    6-12 months

    Key Features

    • Clarifies shared responsibilities between CSPs and CSCs
    • Adds 7 cloud-specific CLD security controls
    • Provides guidance for 37 ISO 27002 cloud adaptations
    • Addresses multi-tenancy and VM segregation risks
    • Integrates into ISO 27001 ISMS audits

    Detailed Analysis

    A comprehensive look at the specific requirements, scope, and impact of each standard.

    REACH Details

    What It Is

    REACH (Regulation (EC) No 1907/2006) is a directly applicable EU regulation governing chemicals lifecycle. Its primary purpose is protecting human health and environment by shifting responsibility to industry for identifying, registering, and managing chemical risks. Scope covers substances, mixtures, and certain articles across manufacture, import, and use. Key approach: tonnage-based data requirements and integrated pillars.

    Key Components

    • Four pillars: Registration, Evaluation, Authorisation, Restriction.
    • 17 technical Annexes (e.g., XIV for Authorisation List, XVII for Restrictions).
    • Core principles: industry-led data generation, SVHC identification, substitution promotion.
    • Compliance model: ongoing dossier submission to ECHA, national enforcement, no central certification.

    Why Organizations Use It

    • Mandatory for EU market access (>1 tonne/year).
    • Mitigates fines, market bans, recalls.
    • Enhances supply-chain transparency, innovation via substitution.
    • Builds stakeholder trust, ESG alignment, competitive edge.

    Implementation Overview

    • Phased: gap analysis, inventory, dossiers, monitoring.
    • Applies to manufacturers/importers/downstream users EU-wide.
    • Cross-functional: procurement, R&D, EHS.
    • Audit readiness via internal checks, national inspections.

    ISO 27017 Details

    What It Is

    ISO/IEC 27017:2015 is an international code of practice providing guidance on information security controls for cloud services. It extends ISO/IEC 27002 within an ISO 27001 ISMS, focusing on cloud-specific risks like shared responsibilities between cloud service providers (CSPs) and customers (CSCs). Adopts a risk-based approach to adapt controls for IaaS, PaaS, and SaaS.

    Key Components

    • Cloud-specific guidance for 37 ISO 27002 controls.
    • 7 additional CLD controls covering segregation, VM hardening, admin operations, monitoring, and asset lifecycle.
    • Built on ISO 27001 ISMS framework.
    • No standalone certification; integrated into ISO 27001 audits.

    Why Organizations Use It

    • Addresses cloud gaps in generic standards.
    • Supports regulatory alignment (e.g., GDPR) and procurement demands.
    • Reduces multi-tenancy risks, builds trust.
    • Competitive differentiator for CSPs and CSCs.

    Implementation Overview

    • Map to existing ISO 27001; conduct cloud risk assessments.
    • Implement technical measures like logging, segregation.
    • Applicable globally across industries and sizes.
    • Joint audits typically 9-12 months.

    Key Differences

    Scope

    REACH
    Chemicals registration, evaluation, authorisation, restriction
    ISO 27017
    Cloud-specific information security controls guidance

    Industry

    REACH
    Chemicals, manufacturing, importers worldwide
    ISO 27017
    Cloud providers, customers, all cloud-using sectors

    Nature

    REACH
    Mandatory EU regulation, legally binding
    ISO 27017
    Voluntary code of practice, ISO 27001 extension

    Testing

    REACH
    Dossier submissions, substance evaluations by ECHA
    ISO 27017
    ISO 27001 audits assess cloud controls

    Penalties

    REACH
    Fines, product seizures by Member States
    ISO 27017
    No legal penalties, certification loss

    Frequently Asked Questions

    Common questions about REACH and ISO 27017

    REACH FAQ

    ISO 27017 FAQ

    You Might also be Interested in These Articles...

    Run Maturity Assessments with GRADUM

    Transform your compliance journey with our AI-powered assessment platform

    Assess your organization's maturity across multiple standards and regulations including ISO 27001, DORA, NIS2, NIST, GDPR, and hundreds more. Get actionable insights and track your progress with collaborative, AI-powered evaluations.

    100+ Standards & Regulations
    AI-Powered Insights
    Collaborative Assessments
    Actionable Recommendations

    Check out these other Gradum.io Standards Comparison Pages