As we start to wrap up this skill together, I wanted to do a slight review and
make sure that we covered some of the bigger points and remember what we
learned along the way.
So when it comes to Cisco and looking at software as a service and the things
that we are provided across that public network, this is a cloud-based
application provided by Cisco or somebody hosting that Cisco application that's
fully managed and developed, delivered over the internet by a service provider.
See, there's that different that will come back to here in a minute of the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
See, there's that different that will come back to here in a minute of the
difference between the customers' responsibilities and the providers'
responsibilities.
Think of this as an application that we can access very easily with just an
internet browser.
And that's one of the distinguishing factors behind software as a service in
general is that it's readily accessible and doesn't require much setup on the
actual clients end of everything.
So the customer's access and used software without needing to manage the under WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So the customer's access and used software without needing to manage the under
lining infrastructure operating system and application updates.
So as a user, there's not that much downtime noticed and there's not that many
updates that are sent out.
See, we're using things like a workstation, let's say like this one that I'm
working on right now, we would normally get notifications for updates every so
often.
But for software as a service in that Cisco environment and we're accessed and
over generally that browser and not responsible for any of the server and under WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
over generally that browser and not responsible for any of the server and under
applications end, it's kind of seamless and transparent to the user that's
accessing those services and doesn't really come up as an issue.
Now the owner/IT manager of the organization is going to be kept afloat of some
of these down times by the actual service provider and that's where we as those
professionals in the IT field need to make sure that we're doing that service
level agreement between us and the organization that we're utilizing for this WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
level agreement between us and the organization that we're utilizing for this
software as a service.
This also means that the service provider is also going to be responsible
primarily responsible for security patches and infrastructure management.
Now when we talk about infrastructure management, we're not talking about
internal to the organization itself.
So anything happens inside of the building as far as like network upgrades and
system upgrades to the overall system that's sitting on our desk does not
involve the actual provider and the applications and infrastructure that's WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
involve the actual provider and the applications and infrastructure that's
running inside of the organization itself.
So that's running inside of that cloud environment. Those are two completely
separate things.
One thing that we are responsible for as a client within that software as a
service provider is making sure that user access control and data security is
maintained and dealt with because whoever we're getting this service from, they
're from providers themselves, they don't know who we need have access to
whatever data is out there and they don't know what kind of information that we
need classified based on the contents of that service provider. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
It's not up to them. They're just the host and make sure that everything
matches their terms of service or user level agreements or whatever
jurisdiction that they're in.
Now I do want to point out obviously that if there's something, let's say we're
here in Texas right now and if there's a law in Texas and states that you can't
store illegal information on a cloud based server, the cloud infrastructure is
responsible to a certain extent to make sure that illegal information is
available.
That illegal information isn't stored on their services and if they notice WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
That illegal information isn't stored on their services and if they notice
something they have to call law enforcement.
I don't want to get into the nitty gritty as far as like determining what is or
isn't illegal information, but I do want to put that out.
And the proper identification falls on us as the client to maintain and use
stuff like IAM, identity access management, data classification, auditing of
services to maintain that security and threat identification in response.
And that's what we're going to kind of start to close out on is our shortened WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And that's what we're going to kind of start to close out on is our shortened
review because identity identifying those threats is something that we have
limited scope and ability to do as far as the actual client is concerned
because we're only responsible for those users and people are excuse me users
and data.
And the actual infrastructure from applications, the hardware, the actual
software that's running in the background can't be really tested or
vulnerability assessed except for the owners of that actual system itself. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
vulnerability assessed except for the owners of that actual system itself.
So the only thing that we're going to be keeping track of is things that are
going in and outside of our organization.
Let's say there's a Millignnet file that's going in and out of our data network
that's going to that cloud infrastructure.
Hopefully we as the security technicians and service managers inside of that
client responsibility realm identified that and have a work and arrangement
with the actual provider to make sure that we can identify those threats. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
with the actual provider to make sure that we can identify those threats.
Because something that's stored inside the cloud that's malicious in nature can
infect our host systems, even though we're just using something as simple as a
web browser to access those services.
Now to close this out and I'm going to put this on screen.
And we're going to take a look at it for just a second and see if we can
identify where our client responsibilities and provider responsibilities split
off at.
Because we started this off at the skill by identifying that this is what
uniquely identifies software as a service. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
uniquely identifies software as a service.
So I'm going to give you just a second and then I'll go ahead and put it on the
screen. Ready? Right there.
Because the customer's responsibility, that's you and I, we're responsible for
the people in data and the provider is responsible for applications, runtime,
middleware, OS, virtual network and all the hardware that is involved with
everything that we do.
We're trying to make this as simple as possible and deliver it as easily as
possible to the actual client, which is why software as a service provides that WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
possible to the actual client, which is why software as a service provides that
quick and easy adaptability for an organization overall.
I hope this has been informative for you and I'd like to thank you for doing it
.