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 delivery1
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. 1An 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.
With the emergence of Cloud Services spanning one or many cloud infrastructures managed by various providers, it is imperative that a checklist be developed that provides cloud services lifecycle guidance/requirements for service providers/developers as they integrate these lifecycle functions.
The goal driven checklist is to be developed with the purpose to facilitate the following six lifecycle functions from a cloud service provider. These lifecycle functions can be aggregated in the three categories of build, capture, and modify to facilitate a simpler description of the goals.
Assessment and acceptance (i.e., build) of services onto the cloud platform/infrastructure.
Ongoing audit (i.e., capture) of services on the cloud platform/infrastructure.
Augmentation, abridging, and annulment (i.e., modify) of services within the cloud platform/infrastructure.
The goal of the checklist is to realize greater efficiencies through formalization and automation of integrations between cloud service providers and their corollary actors during the cloud services lifecycle. While the focus in this document is on the cloud services lifecycle, note that the unique goal oriented approach and related paradigms described herein could also be applied elsewhere.
Virtual desktop services enable enterprise IT organizations to logically centralize desktop resources so as to reduce desktop management costs and support any-device, any-network access to desktops by end-users. The emergence of Virtual Desktop Infrastructure as a service additionally allows enterprise IT organizations to take advantage of cloud resources instead of building their own infrastructures. As a result, enterprises can further reduce IT costs.
This document describes the virtual desktop (VD) requirements for enterprise services and specifies a federation framework for deploying VD services across multiple networks and administrative domains. In particular, the framework allows cloud service providers to host VD services for enterprises and at the same time maintain seamless network connectivity to enterprise resources. For the sake of end-user experience, it is essential that VD sessions can be transparently moved between data centers or between service providers without compromising security and isolation. Such transparent migration of VD session poses significant requirements on the underlying networks, which are also addressed by this document.
The ATIS Cloud Services Forum is examining a number of services that establish the foundation for development, operations, deployment, and management of cloud-based services. These include content delivery, telepresence, and virtual desktop. Video services, including the already-present one-way and growing two-way communications, will be a substantial catalyst for additional growth and expansion of the Internet. Telepresence services provide a business model and architectural model that are foundational to cloud services, and provide important elements of the Cloud Services Data Model for Cloud Service Enablers. This specification focuses on telepresence services, recognizing that telepresence services are an integral part of a broader unified communications solution set.
There are many aspects of the telepresence service. This is an evolving document establishing a foundation for continuing work efforts. The specification explores a provider-agnostic and product-agnostic implementation, and will consider two primary aspects of the telepresence service that are detailed here by the examination of use cases deployed today and those resulting in the application of "the cloud" and other aspects of business and technology architecture guiding service evolution in the future. First, a description of the telepresence service is provided. Second, a more detailed description of the two key aspects of the telepresence service is provided. Topics 2f and 2g detail aspects of telepresence interconnectivity which will be addressed in a future specification.
The concept of a Federated Cloud comprised of interconnected Service Providers (SP) was introduced in ATIS Standard ATIS-0200003, CDN Interconnection Use Case Specifications and High Level Requirements [https://global.ihs.com/doc_detail.cfm?&csf=ASA&input_doc_number=%20&inpu.... This initial standard described the role of the SPs in the cloud as distributors of content from Content Providers (CP) to End Users (EU). Thus, SPs serve as Content Distribution Network (CDN) Providers. The set of content delivery Life Cycle interactions between two CDN Providers is defined in ATIS-0200003. The method for content distribution in ATIS-0200003 was limited to Unicast Cache-based distribution.
Under certain conditions depending on network configurations and type of content, it may be advantageous to distribute content via Multicast methods. From a network perspective, Multicast is scalable and results in significant savings in efficiencies and capacity utilization.
The purpose of this ATIS Standard is to introduce Multicast-based content distribution. This standard provides the following:
Overview of the Multicast delivery mechanism
Set of content types that are suitable for delivery via Multicast methods
Description of various Multicast methods that can be deployed to interconnect two CDN Providers and distribute content.
The scope of this Standard is limited to use cases and requirements to support the interactions between two CDN Providers for content distribution via Multicast. The Use Cases describe:
Generic interactions supporting Life Cycle Multicast use between two CDN Providers.
Specific Multicast configurations/scenarios that can be deployed for interconnection and content distribution.
Multicast related specifics to support Billing, Provisioning, Reporting, and other network functions will be covered in future ATIS documents. Multicast-based content delivery to mobility-based End User devices is for further study.
Cloud computing is described at a high, conceptual level in the two foundational standards ISO/IEC 17788 Cloud computing – Overview and vocabulary and ISO/IEC 17789 Cloud computing – Reference Architecture.
However, as the use of cloud computing has grown, a set of commonly used technologies has grown to support, simplify and extend the use of cloud computing alongside sets of commonly used techniques which enable the effective exploitation of the capabilities of cloud services. Many of these common technologies and techniques are aimed at developers and operations staff, increasingly linked together in a unified approach called DevOps. The aim is to speed and simplify the creation and operation of solutions based on the use of cloud services.
This document aims to describe the common technologies and techniques which relate to cloud computing, how they relate to each other and how they are used by some of the roles associated with cloud computing.
This document describes a series of technologies and techniques commonly used to build applications and systems using cloud computing. These include:
- Virtual Machines (VMs) and Hypervisors
- Containers and Container Management systems
- “Serverless" computing
- Microservices architecture and automation
- Platform as a Service systems and their architecture
- Storage services
- Security, Scalability and Networking as applied to the above cloud computing technologies
Regional cloud providers that operate data centers and associated wide-area networking across their region are well positioned to cooperatively build a global cloud infrastructure with other regional cloud providers, and thus, become a valuable party for Content and Application Providers (CPs and APs). We call the formalization of such cooperation a federated cloud. In a federated cloud, application and/or content requests placed to a cloud provider can be served locally -- e.g., by a supporting cloud provider, even when this supporting cloud provider only has an indirect relationship to the AP or CP by way of a primary cloud provider. In this case, a primary cloud provider is defined as the cloud provider with which an AP or CP has a direct contractual arrangement for cloud services. A federated cloud member simultaneously acts as a primary cloud provider and a supporting cloud provider as defined by their relationship with different APs and CPs.
In a federated cloud, part or all of each individual provider's compute, storage, and networking resources become part of a federated pool of cloud resources. Management systems of these individual (regional) cloud providers are linked to facilitate end-to-end cloud services capability. By definition, a federated cloud includes a clearing house to settle expenditures and revenues of the end-to-end cloud services based on agreed methods, interfaces, and procedures for settlement.
The acute need of the multitude of smart, end-user IoT devices and near-user edge devices to carry out, with minimal latency, a substantial amount of data processing and to collaborate in a distributed way, triggered technology advancements towards adaptive, decentralized computational paradigms that complement the centralized cloud computing model serving IoT networks.
Researchers, computer scientists, system and network engineers developed innovative solutions to fill the technological gaps. These solutions provide faster approaches that gain better situational awareness in a far more timely manner. Such solutions or computational paradigms are referred to as fog computing, mist computing, cloudlets4, or edge computing5,6. Since no consensus exists on distinction among these concepts at the time this document was created, the authors considered it imperative to provide a conceptual model that can be used by practitioners and researchers to facilitate meaningful conversations on the topic.
This document provides the conceptual model of fog computing and its subsidiary mist computing, and aims to place these concepts in relation to cloud computing7 and edge computing.
Additionally, the document introduces the notion of a fog node and the nodes federation model composed of both, distributed and centralized, often hierarhical clusters of fog nodes operating in harmony. This model is introduced as a building-block architectural approach for constructing, enhancing or expanding the fog and mist computing layers.
Furthermore, the document characterizes important aspects of fog computing and is intended to serve as a means for broad comparisons of fog computing capabilities, service models and deployment strategies, and to provide a baseline for discussion of what fog computing is and the way it may be used.
The capabilities, service types and deployment models form a simple taxonomy that is not intended to prescribe or constrain any particular method of deployment, service delivery, or business operation.
