Cloud computing

This document establishes commonly accepted control objectives, controls and guidelines for implementing measures to protect Personally Identifiable Information (PII) in line with the privacy principles in ISO/IEC 29100 for the public cloud computing environment.
In particular, this document specifies guidelines based on ISO/IEC 27002, taking into consideration the regulatory requirements for the protection of PII which can be applicable within the context of the information security risk environment(s) of a provider of public cloud services.
This document is applicable to all types and sizes of organizations, including public and private companies, government entities and not-for-profit organizations, which provide information processing services as PII processors via cloud computing under contract to other organizations.
The guidelines in this document can also be relevant to organizations acting as PII controllers. However, PII controllers can be subject to additional PII protection legislation, regulations and obligations, not applying to PII processors. This document is not intended to cover such additional obligations.
 
The standard can be bought here: https://www.iso.org/standard/76559.html
The informative sections of this standard are publicly available here: https://www.iso.org/obp/ui/#iso:std:iso-iec:27018:ed-2:v1:en

ISO/IEC 27017 gives guidelines for information security controls applicable to the provision and use of cloud services by providing:

• additional implementation guidance for relevant controls specified in ISO/IEC 27002;
• additional controls with implementation guidance that specifically relate to cloud services.

This Recommendation | International Standard provides controls and implementation guidance for both cloud service providers and cloud service customers.
 
The standard can be bought here: https://www.iso.org/standard/43757.html
The informative sections of this standard are publicly available here: https://www.iso.org/obp/ui/#iso:std:iso-iec:27017:ed-1:v1:en

This standard defines topology, functions, and governance for cloud-to-cloud interoperability and federation.
Topological elements include clouds, roots, exchanges (which mediate governance between clouds), and gateways (which mediate data exchange between clouds).
Functional elements include name spaces, presence, messaging, resource ontologies (including standardized units of measurement), and trust infrastructure.
Governance elements include registration, geo-independence, trust anchor, and potentially compliance and audit.
The standard does not address intra-cloud (within cloud) operation, as this is cloud implementation-specific, nor does it address proprietary hybrid-cloud implementations.
 
Under development
Working documents can be found here (prior registration required): https://ieee-sa.imeetcentral.com/2302/home

Status :  Under development

ICS : 35.210 Cloud computing

In addition to interoperability and security that are two recognized key enablers to the development of large IoT systems, a new one is emerging as another key condition of success: virtualization. The deployment of IoT systems will occur not just within closed and secure administrative domains but also over architectures that support the dynamic usage of resources that are provided by virtualization techniques over cloud back-ends.

This new challenge for IoT requires that the elements of an IoT system can work in a fully interoperable, secure and dynamically configurable manner with other elements (devices, gateways, storage, etc.) that are deployed in different operational and contractual conditions. To this extent, the current architectures of IoT will have to be aligned with those that support the deployment of cloud-based systems (private, public, etc.). Moreover, these architectures will have to support very diverse and often stringent non-functional requirements such as scalability, reliability, fault tolerance, massive data, security.

This will require very flexible architectures for the elements (e.g. the application servers) that will support the virtualized IoT services, as well as very efficient and highly modular implementations that will make a massive usage of Open Source components. These architectures and these implementations form a new approach to IoT systems and the solutions that the present document investigates also should be validated: to this extent, a Proof-of-Concept implementation involving a massive number of virtualized elements has been made.

The purpose of this technical report is to expand on the description of the interactions between cloud service partners (CSNs) and cloud service customers (CSCs), and between CSNs and cloud service providers (CSPs).
Cloud computing is in a position to offer solutions to many emerging technologies, and it offers many benefits to all cloud service users (CSUs) and CSCs.  The broader requirement for cloud solutions is to ensure organizations have the best capabilities to fulfil their business missions.  This has helped to drive the adoption of cloud services and the marketplace is adjusting to the increasing demands.
In finding and applying appropriate solutions and leveraging the many benefits of using cloud services, many CSCs use multiple CSPs and various deployment models, and include a global network.  In using, sharing, and assessing data, an understanding and clarification of roles, activities and responsibilities will help to maintain the security, privacy, confidentiality and confidence of cloud services.
Interactions of CSCs and CSPs with the various CSNs have caused a degree of concern and confusion in the cloud service marketplace, in some cases causing harm to CSCs through inappropriate security controls and the lack of proper cloud service agreements relating to the cloud services being used. This is in part caused by an inadequate understanding of the relationships involved and by the lack of standards which might apply to those relationships.
Interactions between CSCs and CSPs have been described in detail in standards documents – ISO/IEC 17789 [2], 19941 [7], 27017 [11], 27018 [12] and the 19086 series. Interactions of CSNs, a key role in the cloud service environment, with CSCs and CSPs have not been described in similar detail. This TR is to provide guidance and descriptions for those interactions.
This document provides clarification of the concepts provided in ISO/IEC 17789, 19086, and 19941 regarding CSNs, and CSN interactions with CSCs and CSPs with the help of a few of exemplary market scenarios.  Building on an expanded description of sub-roles and activities, this document provides guidance on using cloud service agreements (CSA) and cloud service level agreements (cloud SLAs) to provide more clarity for CSN interactions. 
This document provides an overview of and guidance on interactions between cloud service partners (CSNs), specifically cloud service brokers, cloud service developers and cloud auditors, and other cloud service entities. In addition, the document describes how cloud service agreements (CSAs) and cloud service level agreements (cloud SLAs) should be used to address those interactions including the following:
Define Terms and concepts, and provide an overview for interactions between CSNs and CSCs and CSPs 
Description of types of CSN interactions
Description of interactions between CSNs and CSCs
Description of interactions between CSNs and CSPs
Elements of CSAs and Cloud SLAs for CSN interactions, both with CSPs and with CSCs
 
Under development

The CSA Open Certification WG is an industry initiative to allow global, accredited, trusted certification of cloud providers. It is a program for flexible, incremental and multi-layered cloud provider certification according to the CSA’s industry leading security guidance and control objectives. The program will integrate with popular third-party assessment and attestation statements developed within the public accounting community to avoid duplication of effort and cost.

Privacy Level Agreement - Version 2 is intended to be used as an appendix to a Cloud Services Agreement, and to describe the level of privacy protection that the CSP will provide. While Service Level Agreements (“SLA”) are generally used to provide metrics and other information on the performance of the services, PLAs will address information privacy and personal data protection practices.

The PLA [V2] is based only on EU personal data protection mandatory legal requirements. Coherently, the Working Group has stripped away elements derived from best practices and recommendations from the PLA [V1] (see further the ‘Methodology’ section of the standards document), and further clarifies core mandatory legal requirements.

The goal of CloudAudit is to provide a common interface and namespace that allows cloud computing providers to automate the Audit, Assertion, Assessment, and Assurance (A6) of their infrastructure (IaaS), platform (PaaS), and application (SaaS) environments and allow authorized consumers of their services to do likewise via an open, extensible and secure interface and methodology. CloudAudit provides the technical foundation to enable transparency and trust in private and public cloud systems.

The Cloud Trust Protocol (CTP) is designed to be a mechanism by which cloud service customers can ask for and receive information related to the security of the services they use in the cloud, promoting transparency and trust.

The CTP document focuses on the definition of the CTP Data Model and Application Programming Interface (API), including:

• The format of CTP messages exchanged between cloud service customers and providers.
• The modelling of concepts such as “security attributes”, “objectives”, “measurement results” and “triggers” in machine readable  format.
• The means to define the scope of the service to which CTP monitoring queries apply.

However, the document does not provide a specification of the “security attributes” (and associated metrics) that are queried by CTP. Such a specification will be provided by the Cloud Security Alliance in a separate document, and will likely be influenced by upcoming standards such as [ISO_19086]. CTP also offers implementers the choice to define and adopt their own set of security attributes and related metrics. This document is organised as follows.
Section 2 provides some key terms and definitions that are used throughout this document, borrowing from relevant key standards.
Section 3 offers a general introductory overview of CTP.
Section 4 describes the CTP data model, defining the main concepts that are used to represent security information related to cloud services in CTP.
Section 5 specifies the RESTful CTP API that implements the model described in section 4. It also specifies the CTPScript language used in “triggers” and “objectives” and describes when they should be evaluated.
Section 6 provides requirements and recommendations for securing the CTP API.

The Cloud Security Alliance Cloud Controls Matrix (CCM) is specifically designed to provide fundamental security principles to guide cloud vendors and to assist prospective cloud customers in assessing the overall security risk of a cloud provider. The CSA CCM provides a controls framework that gives detailed understanding of security concepts and principles that are aligned to the Cloud Security Alliance guidance in 13 domains. The foundations of the Cloud Security Alliance Controls Matrix rest on its customized relationship to other industry-accepted security standards, regulations, and controls frameworks such as the ISO 27001/27002, ISACA COBIT, PCI, NIST, Jericho Forum and NERC CIP and will augment or provide internal control direction for service organization control reports attestations provided by cloud providers.

ATIS Standard ATIS-0200003 [https://global.ihs.com/doc_detail.cfm?&csf=ASA&input_doc_number=%20&inpu... provided initial use cases and requirements for Content Distribution Network (CDN) Interconnection between two CDN providers via Cache-based Unicast delivery method – software download was the selected content type to drive these initial use cases and requirements. ATIS Standard ATIS-0200004 [https://global.ihs.com/doc_detail.cfm?&csf=ASA&input_doc_number=%20&inpu... developed use cases and requirements for content distribution via Multicast-based delivery.
In a multi-party Federated environment (multiple Service Providers (SP) acting as CDN Providers), CDN interconnections require additional functionality from service providers beyond the straightforward interconnection of IP transport networks. The interconnection and federation of CDN Providers is expected to evolve through a series of content distribution services. These services can be provided by a variety of different mechanisms including:

• Cache-based http unicast.
• Multicast.
• Publish subscribe mechanisms (e.g., RSS or named-data information-centric content routing).
• Content aggregation (e.g., from machine-machine interconnection).

The selection of the delivery method depends on the nature and type of content that is being requested for delivery¹
Thus, the purpose of this ATIS Standard is to extend the use cases and requirements developed in ATIS- 020000] and ATIS-0200004 for an environment involving multiple CDN providers joining together to form a CDN Federation with multiple available methods of content delivery. The interconnection life cycle use cases and requirements are re-examined for the impact arising from a Federation of multiple CDN providers. Additional emphasis is placed on the interconnection domain functionality such that guidance on the eventual development of Network-Network Interconnect (NNI) architectures and supporting protocol requirements can be derived.
Accordingly, the scope of this document includes the following:

• Multiple SPs forming a CDN Federation for the purpose of distributing content from Content Providers (CP) to End Users (EU) that individually request the content delivery. The multi-party Federation is strictly limited to a fully meshed structure where each SP/CDN Provider directly engages with other SPs/CDN Providers for the purpose of content distribution. Other structures are excluded from consideration in this document. Examples of alternate and/or add-on structures include the presence of a third party broker/exchange as well as the role of SPs who are not Federation members but who have independent agreements for assisting in content delivery with individual Federation members (see section 5). These alternate/add-on structures are for further study.
• Life cycle interactions are re-examined from the perspective of a Multi-Party Federation environment (see section 6)
• The delivery methods are restricted to cache/unicast (section 7) and multicast methods (section 8). All content types that can be delivered by these methods are in scope.
• Logical functionality associated with interconnection domains between pairs of CDN Providers are examined in detail (section 9). Appropriate requirements are derived in support of these functions.

Finally it should be noted that the protocol development work supporting all CDN-I functionality is being developed in the IETF. Appendix A provides a brief summary of this work.
¹An infinite length stream, for example, might be best suited to multicast delivery. Files of various sizes may be suitable for cache-based delivery. Finally, small content units may be appropriate for aggregation and delivery service.