Platform as a Service: The cloud provider is responsible for the security of the platform, while the cloud consumer is responsible for everything they implement on the platform, including how they configure any offered security features. For example, when using a Database as a Service, the provider manages fundamental security, patching, and core configuration, while the cloud consumer is responsible for everything else, including which security features of the database to use, and managing accounts as well as authentication methods. Infrastructure as a Service: The provider is responsible for foundational security, while the cloud consumer is responsible for everything they build on the infrastructure. This places far more responsibility on the cloud consumer. For example, the IaaS provider will likely monitor their perimeter for attacks, but the consumer is fully responsible for how they define and implement their virtual network security based on the tools available on the service. CSA provides further guidance233 for various aspects of cloud security across the above service models, including good practices such as the use of multi-factor authentication (MFA) for privileged access, “architecting for failure” to Identify requirements Define architecture Select provider, service and deployment models ensure business continuity, carefully understanding the responsibilities and contract of the cloud provider, and using appropriate encryption and key management to ensure the protection of sensitive data. CSA also suggests a simple high-level process for implementing cloud security, as shown below. As an example, Google Cloud Platform servers use a variety of technologies to ensure that they are booting the correct software stack, including cryptographic signatures over low-level components like the BIOS, bootloader, kernel, and base operating system image234. This security is based on the Titan security chip which was also discussed in the previous section. ENISA describes235 security challenges that arise from the convergence of cloud computing and IoT, including the fact that the security requirements depend on the industry vertical being served, the vulnerability of edge devices that can then be used to gain access to the cloud, and the difficulty of securing heterogeneous communication protocols between devices and cloud. Identify control gaps Assess security controls Manage changes Design and implement controls Figure 22: Cloud Security Process Model (Source: Cloud Security Alliance) 70 233 Cloud Security Alliance’s Security Guidance for Critical Areas of Focus in Cloud Computing v4.0, 2017 234 https://cloud.google.com/blog/products/gcp/titan-in-depth-security-in-plaintext 235 Towards secure convergence of cloud and IoT, ENISA, Sept 2018

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents