ISO 27017 certification: cloud security

ISO/IEC 27017 is a code of practice for information security in cloud services. It supplements the controls in ISO/IEC 27002 with points that apply to providers and customers of cloud services.

Sea of fog with dark mountain peaks rising above it, a metal summit marker in the foreground

The standard is aimed at cloud service providers and at organisations that use cloud services. It describes how responsibility for security is divided between both parties and documented.

ISO/IEC 27017 is usually audited together with an information security management system in accordance with ISO/IEC 27001. The certificate shows that the cloud-specific controls are part of your audited system.

Small stone hut on a rocky spur high above a sea of fog

Customers should be able to monitor the parts of the service that matter to them.

  1. Shared responsibility

    In the cloud, the provider and the customer each bear part of the responsibility for security. The standard requires this division to be clearly defined for each service and communicated to the customer.

    This also covers what happens at the end of a contract: the customer's data and systems are returned or deleted, and the customer is informed of how this takes place.

  2. Controls for virtual environments

    The standard adds controls that exist only in the cloud: the separation of different customers' environments, the hardening of virtual machines and the alignment of security between virtual and physical networks.

    Clear procedures apply to administrators so that critical operations remain traceable.

  3. Monitoring and evidence

    Customers should be able to monitor the parts of the service that matter to them. The provider makes logs and information available for this purpose.

    If you process personal data in the cloud, you can extend the system with ISO/IEC 27018 and ISO/IEC 27701.

sides share responsibility: provider and customer
2
additional controls specifically for cloud services
7
joint audit with ISO/IEC 27001, as a rule
1

Who in the cloud takes care of what.

The division is defined for each service and communicated to the customer.

Cloud service provider

  • Separates the environments of different customers
  • Provides logs and information for monitoring
  • Keeps administrator actions traceable
  • Returns or deletes data at the end of the contract

Shared responsibility

Cloud service customer

  • Monitors the parts of the service that matter to them
  • Manages the access rights of their users
  • Protects their data and settings within the service

Audited together with your ISMS.

  1. Application

    You name your cloud services and the scope of your ISMS. SICE prepares the quotation.

  2. Stage 1

    SICE reviews the ISMS documentation and how responsibility between provider and customer is defined for each service.

  3. Stage 2

    On-site audit. SICE examines the cloud-specific controls, such as the separation of customer environments and the procedures for administrators.

  4. Certificate

    Following a positive decision, the certificate shows that the cloud-specific controls are part of your audited system.

  5. Surveillance

    New and changed services are included in the surveillance audits.

Stone steps of a mountain path disappearing into the fog

For providers and for customers.

  • You offer cloud services

    You want to show that the cloud-specific controls are part of your audited system.

  • You use cloud services

    You want to know which part of security you are responsible for yourself.

  • You hold ISO/IEC 27001

    ISO/IEC 27017 adds controls for matters that exist only in the cloud.

  • Customers ask about the end of the contract

    The standard requires that the return or deletion of data is defined and communicated.

Questions about security in the cloud.

Is ISO/IEC 27017 available without ISO/IEC 27001?

ISO/IEC 27017 is a guideline and is generally audited together with an information security management system to ISO/IEC 27001.

What does shared responsibility mean?

In the cloud, the provider and the customer each bear part of the responsibility for security. The standard requires this division to be clearly defined for each service and communicated to the customer.

What happens to the data at the end of the contract?

The customer's data and systems are returned or deleted, and the customer is informed how this takes place.

Which controls exist only in the cloud?

The standard adds seven controls that exist only in the cloud. These include the segregation of different customers' environments, the hardening of virtual machines and the alignment of security between virtual and physical networks.

Can customers monitor the service themselves?

Yes. Customers should be able to monitor the parts of the service that matter to them. The provider supplies logs and information for this purpose.

Sea of fog with dark mountain peaks rising above it, a metal summit marker in the foreground

Let us talk about your cloud services.

In the free initial consultation, we clarify which services belong in the scope.