In our previous skill, kicking off this domain, we went over a brief
introduction of the three different types of as a service models that are out
there within that cloud environment.
And the first one that we're going to be diving into in more detail, especially
when it comes to that Cisco methodology, is software as a service.
Now I'm going to be going through these in order and working our way up to more
responsibility overall based on who the customer and provider cover as far as WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
responsibility overall based on who the customer and provider cover as far as
the different services and roles to those different users that are
participating in that cloud service.
Now up on the screen, we have our first model where we're going to take a look
at SAS, our software as a service and the shared responsibility model.
Generally in this model, we're going to be dealing with people and data more
than we are the actual applications and everything else that's involved with
the actual infrastructure of a cloud environment.
It's going to be the provider's responsibility to maintain the physical
infrastructure, including the servers and the storage and all around oper WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
infrastructure, including the servers and the storage and all around oper
ability of the equipment that backs everything that we're trying to do for the
data and the people that is the customer's responsibility.
And we're going to be securing application settings and ensuring compliance
with industry regulations.
This could mean that we're working with GDPR if we're inside of the European
Union or HIPAA for example if we're here in the United States.
Now there's some definite advantages to being able to utilize a software as a
service, especially in that Cisco environment. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
service, especially in that Cisco environment.
Primarily, it's going to come down to a cost factor.
When we're dealing with software as a service, one of the primary
responsibilities of the organization is to maintain a budget.
The cost efficiency side of this is accomplished through reducing the need for
extensive hardware and IT maintenance.
A lot of the maintenance and actual hardware requirements and let's say
something breaks and it has to get replaced is going to be taken care of by the
actual provider in this scenario. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
actual provider in this scenario.
So we could be running, let's say for example inside of the Cisco world, a VoIP
environment where for the end user, for the software as a service, we're going
to be using the VoIP software client on the actual end point workstations.
So who's responsible for fixing the actual VoIP system if the phone service
goes down?
Well, that's on the provider where we're responsible for just maintaining the
phone book, making sure the users get their connectivity on the actual WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
phone book, making sure the users get their connectivity on the actual
application itself through our provider and maintaining the phone book and user
registration.
Now there's way more in-depth this that we'll cover as we go throughout, but
that's just a quick overview of software as a service as we're considering the
Cisco environment.
But the advantages don't just stop at the affordability, respectively depending
on what kind of service we're utilizing.
It also goes into actual software updates.
As we took a look at our model since we're focusing in on the actual data and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
As we took a look at our model since we're focusing in on the actual data and
users, the software updates that are in the application are maintained also by
that provider.
We still have a responsibility as we'll go through throughout the skill in
making sure that vulnerabilities are addressed and found if there are any that
exist out there.
But if something needs to be taken care of on that particular end, it's going
to be the provider that's responsible for it, whereas we're more of a physical
security maintainer in this aspect. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
security maintainer in this aspect.
It kind of leads us to one of the key security concerns of what's actually
going on in software as a service, and it's ensuring that the data of the
customer is protected at all cost.
One of the ways that we do this is by encryption and making sure that the data,
whether it be at-rested motion, is encrypted to make sure that we are
maintaining that CIA triad of confidentiality integrity and accessibility.
Because even though the infrastructure of everything is being ran by the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Because even though the infrastructure of everything is being ran by the
provider, we are still held responsible for ensuring that the CIA triad in
software as a service is maintained.
Because if we get rid of the access to that actual software platform, then we
're kind of cutting off accessibility.
And in security, we do maintain practice through encryption and also through
hashing for that integrity as well.
In more detail, we get into the identity and access management of what's
actually going on because us as the actual administrators in the software as a WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
actually going on because us as the actual administrators in the software as a
service platform, we're maintaining who has access and who has rights and who
has basically every permission that they need, even though we're not
maintaining the actual service themselves, if that makes sense.
Because while the application and above in our model is being dealt with by the
actual provider, who is it that's going to relay that information to the
provider that has a, let's say we have a new employee come in and has to have WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
provider that has a, let's say we have a new employee come in and has to have
certain access.
It's going to be us as the, on the ground technicians, maintaining oversight of
the data and people. And although we don't have too much dealings with the
actual applications as hosting our services, we do have a little bit of deal
ings with the API.
And we'll begin the API a little bit more as the skill unfolds. Just know that
right now that most SaaS platforms provide APIs for integration as far as what WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
right now that most SaaS platforms provide APIs for integration as far as what
kind of programs we're using to incorporate that data and also making an API
security, a critical concern.
So let's go ahead and strap in and do it to it and start looking at Cisco
inside of that software as a service and getting into some of the details and
more importantly some examples.