Okay, we're getting some of the basics out of the way and making sure that we
have a full understanding of who is responsible for what and
In order to do that we have to be able to go through those different cloud
infrastructure types and make sure that we understand for this part the shared
Responsibility now there are three different types of shared responsibility
that we're going to be going through for this portion of the skill
And I've broken it down in some nice little drawings that I am totally not good
with with crayon so I made them a PowerPoint
But I'm going to be explaining these one by one so sit back and relax and let's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But I'm going to be explaining these one by one so sit back and relax and let's
do it to it now shared responsibility is basically a split between what the
cloud service provider is
Responsible for and whatever the client is responsible for as well and because
we have three different cloud types or
Infrastructure types that we're dealing with software as a service platform as
a service and infrastructure as a service the shift in
Responsibilities change but the responsibilities are all the same between the
three it just really depends on who is looking at what for that actual WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
three it just really depends on who is looking at what for that actual
Responsibility role and we're going to be doing these one by one and I'm going
to be following along with you are you ready?
So the first one that we have up on the screen is S a S or software as a
service the shared responsibilities now
You can see this is broken down easily into the customers and the provider's
responsibility
Now in this type of environment the customers for responsibility is kind of
minimal and you can see that they're only really responsible for the people and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
minimal and you can see that they're only really responsible for the people and
the data to be able to shuffle them over to get them to use the actual cloud
service itself
And when we take a look at what the provider is actually taking care of it's
basically everything else that's behind the scenes because that software is a
service as we recall is something that we can generally access over a web
browser
Generally and to make sure that everything is as easy as possible for the user
so things like application runtime middleware hardware operating systems
hardware and everything that's behind the scenes to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
hardware and everything that's behind the scenes to
requires that maintenance and detailed attention to detail is the provider's
responsibility and making sure that ease of use is maintained and also services
are still provided.
Now that changes when we start going over to platform as a service because
there's a little bit more configuration that the customer can actually do on
their end remember we're talking about building out applications and that's why
in this particular model the applications is moved over to the customers
responsibility.
Everything else behind the scenes include the runtime for that application WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Everything else behind the scenes include the runtime for that application
platform is still the providers responsibility, but you can see that the
customers responsibility is slowly starting to creep up.
Now it may be that for the customers they're end users may still access
everything through that web browser to make it as easy as possible, but you can
see that we're starting to get a little bit more creative in our implementation
of applications and then finally when we go into infrastructure as a service.
You can see that the customers responsibility drastically increases by them WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
You can see that the customers responsibility drastically increases by them
taking over not only the applications, but also the runtime, the middleware,
the operating system virtual and virtual network basically everything but the
actual hardware itself, which is still the providers responsibility.
The hypervisor server storage and physical network the only way that this would
be the customers responsibility is if they had that private cloud
infrastructure environment that we talked about earlier in the skill and they
remain in everything themselves, but we're also kind of looking at this through WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
remain in everything themselves, but we're also kind of looking at this through
the lens of a public clown, if you will, so I just wanted to point that out as
well.
Now also this is not just something that Cisco came up with all on their own it
's actually in conjunction with the AWS platform and AWS Amazon Web Services
created the shared responsibility model and is incorporating it inside.
Our Cisco is incorporating inside of how they look at the overall roles and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Our Cisco is incorporating inside of how they look at the overall roles and
responsibilities to be able to provide that secure platform before we start
going into the software platform infrastructure as a service models and more in
depth detail going into the actual security for them.
So I just wanted to point that out as well and make sure that we were all on
the same sheet music because in the next portion of this we're going to be
breaking this down again and taking a look at actually who's responsible for
patch management because that's something that we briefly touched on in the
earlier portion of the skill, but I don't want to give everything away just yet WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
earlier portion of the skill, but I don't want to give everything away just yet
.