WEBVTT

1
00:00.000 --> 00:04.850
In our last skill, we went over software as a service as we started working our

2
00:04.850 --> 00:08.000
way up through the as a service platforms.

3
00:08.000 --> 00:13.000
And now we are on platform as a service. See what I did there.

4
00:13.000 --> 00:20.360
And we increase the customer's responsibility from just the people in data now

5
00:20.360 --> 00:23.000
along to the applications.

6
00:23.000 --> 00:27.990
And the vendor is still responsible or the provider is still going to be

7
00:27.990 --> 00:32.430
responsible for everything from runtime all the way to the actual physical
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

7
00:27.990 --> 00:32.430
responsible for everything from runtime all the way to the actual physical

8
00:32.430 --> 00:33.000
network.

9
00:33.000 --> 00:37.540
But when we take a look at utilizing a platform as a service, it allows us as

10
00:37.540 --> 00:41.990
the customers and more importantly, the actual technicians and administrators

11
00:41.990 --> 00:47.660
of our organization to take more of a hands on approach with utilizing actual

12
00:47.660 --> 00:49.000
applications.

13
00:49.000 --> 00:53.820
See, before as software as a service, it was more about if we can access

14
00:53.820 --> 01:00.140
software through things like web browsers, which was most common way to be able
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

14
00:53.820 --> 01:00.140
software through things like web browsers, which was most common way to be able

15
01:00.140 --> 01:06.000
to access those think like Gmail and other software web browser based services

16
01:06.000 --> 01:09.000
that exist across the internet.

17
01:09.000 --> 01:14.520
Even social media to a certain extent is software as a service because we're

18
01:14.520 --> 01:20.210
still access that through a web browser or some sort of application that's pre

19
01:20.210 --> 01:22.000
configured for us.

20
01:22.000 --> 01:26.870
Now it gets a little bit different inside of platform as a service because we

21
01:26.870 --> 01:32.000
actually own the application maintenance and responsibility on our end.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
01:26.870 --> 01:32.000
actually own the application maintenance and responsibility on our end.

22
01:32.000 --> 01:37.120
Now, as we start to dive into this, we need to know that we can actually focus

23
01:37.120 --> 01:42.640
on doing implementations for customizations inside of our applications to make

24
01:42.640 --> 01:47.520
things like Gmail, for instance, a little bit more user friendly or tailored

25
01:47.520 --> 01:49.000
for our organization.

26
01:49.000 --> 01:54.070
Now, we may we're not going to be using Gmail as an application administrator

27
01:54.070 --> 01:58.960
in our platform as a service because that's owned by somebody else, but we

28
01:58.960 --> 02:04.890
could very easily install programs in that virtual cloud infrastructure to be
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

28
01:58.960 --> 02:04.890
could very easily install programs in that virtual cloud infrastructure to be

29
02:04.890 --> 02:09.000
able to modify and customize for our user base.

30
02:09.000 --> 02:14.220
And there are many different ways that we're going to see that be done inside

31
02:14.220 --> 02:19.000
of that Cisco world as we go throughout the entirety of the skill.

32
02:19.000 --> 02:23.120
We reviewed when we looked at software as a service Cisco, a secure network

33
02:23.120 --> 02:24.000
analytics.

34
02:24.000 --> 02:27.850
And now we're diving a little bit deeper into how we can kind of configure some

35
02:27.850 --> 02:30.000
of those things on the application side.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

36
02:30.000 --> 02:35.420
We're not using network analytics for this one will be covering a couple of

37
02:35.420 --> 02:40.250
different options here in a little bit, but we kind of look at focusing our

38
02:40.250 --> 02:45.510
role away from being an actual organizational user to death net and getting

39
02:45.510 --> 02:47.000
into things like app dynamics.

40
02:47.000 --> 02:51.420
Now, when I mentioned app dynamics, I'm talking about being able to monitor the

41
02:51.420 --> 02:55.830
actual application performance and that may have been something we were able to

42
02:55.830 --> 03:00.020
do in software as a service, but now that we have the responsibility of owning
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

42
02:55.830 --> 03:00.020
do in software as a service, but now that we have the responsibility of owning

43
03:00.020 --> 03:05.660
and maintaining our actual application in platform as a service, we have more

44
03:05.660 --> 03:11.000
detailed analytics that we can pull from those different types of applications

45
03:11.000 --> 03:13.000
and be able to tweak performance.

46
03:13.000 --> 03:17.950
For instance, we might be able to go inside and allocate more system resources

47
03:17.950 --> 03:22.220
or work with our provider to allocate more resources for that actual

48
03:22.220 --> 03:27.260
application because we can actually provide live real time monitoring for that

49
03:27.260 --> 03:29.000
actual application.

50
03:29.000 --> 03:32.030
So let's say it's running a little sluggish. We need a little bit more
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
03:29.000 --> 03:32.030
So let's say it's running a little sluggish. We need a little bit more

51
03:32.030 --> 03:33.000
processing speed.

52
03:33.000 --> 03:37.780
We can put that request in to be able to do it. Now, don't forget stuff like

53
03:37.780 --> 03:42.460
that comes with a cost and you might want to get with your actual vendor and

54
03:42.460 --> 03:47.000
provider to for that infrastructure as a whole behind the scenes that will get

55
03:47.000 --> 03:52.330
it later to see if there's an increased cost, but that's something else to

56
03:52.330 --> 03:56.490
consider with the difference between software as a service and platform as a

57
03:56.490 --> 04:01.110
service that as we start going through this, that cost will increase because of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

57
03:56.490 --> 04:01.110
service that as we start going through this, that cost will increase because of

58
04:01.110 --> 04:02.000
not only the actual

59
04:02.000 --> 04:07.630
maintenance that has to go into it, but the actual infrastructure that we're

60
04:07.630 --> 04:12.400
having to provide for that service that we want to overall use and provide for

61
04:12.400 --> 04:14.000
our organization.

62
04:14.000 --> 04:18.240
But one of the benefits of using platform as a service and having control over

63
04:18.240 --> 04:22.630
that application side is being able to implement better security before we had

64
04:22.630 --> 04:27.000
to work with that provider to make sure that we can either white list black

65
04:27.000 --> 04:29.000
list inside of that application.

66
04:29.000 --> 04:33.440
But now that we actually have control over the application, we can make our own
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

66
04:29.000 --> 04:33.440
But now that we actually have control over the application, we can make our own

67
04:33.440 --> 04:37.670
security rules and implement our security needs based on, let's say, our

68
04:37.670 --> 04:42.280
organizational policy or any rules and regulations that we have inside of our

69
04:42.280 --> 04:45.000
jurisdiction, whatever that may be.

70
04:45.000 --> 04:50.800
And it allows us to be able to send in more details look at data security

71
04:50.800 --> 04:56.630
because when we looked at software as a service, we need to remember that we're

72
04:56.630 --> 05:01.120
utilizing this over the clown and that we're while our organization's
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

72
04:56.630 --> 05:01.120
utilizing this over the clown and that we're while our organization's

73
05:01.120 --> 05:06.000
responsible for data and transit data and motion or data and rest, my bad.

74
05:06.000 --> 05:11.670
Now we're taking a look at the application side and platform as a service and

75
05:11.670 --> 05:17.430
now we're responsible for now data and motion between the application and the

76
05:17.430 --> 05:23.490
user and also the data and rest for the user and the application because their

77
05:23.490 --> 05:27.540
data, the data is eventually going to have to rest with the actual application

78
05:27.540 --> 05:28.000
itself.

79
05:28.000 --> 05:32.940
So these are different things to consider as we start moving into more detailed
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
05:28.000 --> 05:32.940
So these are different things to consider as we start moving into more detailed

80
05:32.940 --> 05:38.010
security along with role based access control because we're going to be able to

81
05:38.010 --> 05:43.000
assign different access levels to our actual application and usage.

82
05:43.000 --> 05:48.590
We need to be able to assign different technical roles and administrative roles

83
05:48.590 --> 05:53.610
for maintenance and administrative task and security purposes for our

84
05:53.610 --> 05:55.000
organization.

85
05:55.000 --> 05:59.460
It could be that we want to implement multi factor authentication and with

86
05:59.460 --> 06:04.240
access to the actual application itself along with things like the API, which
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

86
05:59.460 --> 06:04.240
access to the actual application itself along with things like the API, which

87
06:04.240 --> 06:08.160
we're going to touch on here in just a little bit, we could actually go through

88
06:08.160 --> 06:12.000
and code in and that's an oversimplification of a term with code.

89
06:12.000 --> 06:17.840
But we can actually implement multi factor authentication instead of having to

90
06:17.840 --> 06:23.190
contact our services provider, let's say like Gmail in our software as a

91
06:23.190 --> 06:28.490
service and work with them, we can do it ourselves because we would have to

92
06:28.490 --> 06:32.810
make sure that whatever multi factor authentication solution that we come up
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

92
06:28.490 --> 06:32.810
make sure that whatever multi factor authentication solution that we come up

93
06:32.810 --> 06:37.400
with is operable with our actual application that we are responsible for in

94
06:37.400 --> 06:39.000
that clown environment.

95
06:39.000 --> 06:43.080
And it may be that we have to get with the provider and see if it's compatible

96
06:43.080 --> 06:47.420
with the hardware or underlining operating systems that run everything, but

97
06:47.420 --> 06:51.420
these are just many different features that we can touch on in more detail

98
06:51.420 --> 06:55.220
inside of that platform as a service as we start to go through the skill

99
06:55.220 --> 06:56.000
together.