- Cloud service providers like Azure and AWS
and Google Labs platform have no choice
but take their security
and compliant responsibilities very seriously.
For example, Amazon created a shared responsibility model
that is actually used to describe
what are the responsibilities of the AWS customers
and Amazon responsibilities in detail.
And you can access the Amazon share responsibility model
from the link that I'm highlighting in the screen.
Now, the share responsibility
depends on the type of cloud model.
Whether you actually have software as a service,
platform as a service, or infrastructure as a service.
So starting with software as a service,
the customer responsibility is basically people and data
and then the cloud service provider responsibility
includes from the physical network,
all the way to the application.
Now here, I'm showing the responsibility
of a platform as a service environment
on where the customer responsibility
or the consumer responsibility is people data
and applications is basically you're developing applications
on top of their infrastructure and their platform.
And then the cloud provider responsibility
includes from the physical network,
all the way to the actual run time,
including things like middleware, the operating system,
virtual network, hypervisor, the actual servers
and the overall infrastructure.
And then finally, I'm showing the infrastructure
as a service responsibility model
and where now you are running virtual networks
and VMs and containers and basically
the cloud service provider responsibilities
the hypervisor, the servers, the storage,
the physical and underlying network.
And then the customer responsibility includes
from people data applications, the run time
the middleware operating systems, the virtual networks
and the virtual appliances that are running
in those environments.
Patch management in the cloud
is also a shared responsibility
in infrastructure as a service
and platform as a service environments.
In SaaS environments,
or the Software As A Service environments,
basically the cloud service provider
is the one responsible for patching all software
and all hardware vulnerabilities.
However, in infrastructure as a service environment,
the cloud service provider is responsible
for only patching the hypervisors
and also the physical compute and storage servers, right?
Including physical network and so on.
You are the one responsible for patching the applications,
the VMs and the operating systems running
on top of those VMs and of course, your containers, as well.
And if you deployed any virtual networks,
you also are liable for patching
and making sure that those virtual networks
are deployed in a secure manner.