WEBVTT

1
00:00.000 --> 00:03.370
One of the main purposes behind this skill is making sure that we can

2
00:03.370 --> 00:04.800
understand how to secure

3
00:04.800 --> 00:11.850
our better secure our platform as a service model inside of a Cisco environment

4
00:11.850 --> 00:12.320
. And that's

5
00:12.320 --> 00:17.640
what brings us to where we're at right now. Because we had to kind of build up

6
00:17.640 --> 00:18.560
to be able to get to

7
00:18.560 --> 00:24.940
this point and show you that here inside of our Cisco ice that we teased in the

8
00:24.940 --> 00:26.000
last portion of

9
00:26.000 --> 00:30.010
this skill, we can actually go through and take a look at vulnerability and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:26.000 --> 00:30.010
this skill, we can actually go through and take a look at vulnerability and

10
00:30.010 --> 00:31.360
threat assessment

11
00:31.360 --> 00:36.400
inside of our platform as a service model. Now why is it easier to do here?

12
00:36.400 --> 00:38.240
Well, that's because

13
00:38.240 --> 00:43.640
we have control over the actual application and can scan more deeply inside of

14
00:43.640 --> 00:44.480
what's actually

15
00:44.480 --> 00:49.590
going on within the organization and its network and systems. So if we go over

16
00:49.590 --> 00:51.120
to the vulnerability

17
00:51.120 --> 00:55.570
tab and click over, now keep in mind, this is a sandbox environment where

18
00:55.570 --> 00:56.880
limits are based on the

19
00:56.880 --> 01:03.040
actual usability and over the counter licensing we have with Cisco on this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

19
00:56.880 --> 01:03.040
actual usability and over the counter licensing we have with Cisco on this

20
01:03.040 --> 01:05.360
example. We can see that

21
01:05.360 --> 01:12.660
we have different areas of importance for our vulnerability assessment. And we

22
01:12.660 --> 01:13.440
have total

23
01:13.440 --> 01:18.630
vulnerable endpoints, which is based on CVSS scoring. And if you don't know

24
01:18.630 --> 01:20.240
what CVSS scoring is,

25
01:20.240 --> 01:25.430
I can actually put a link below that goes more in depth over the importance of

26
01:25.430 --> 01:26.240
CVSS score,

27
01:26.240 --> 01:31.280
and how that score is actually calculated, look below. And it gives us
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:26.240 --> 01:31.280
and how that score is actually calculated, look below. And it gives us

28
01:31.280 --> 01:34.080
basically a low medium at high

29
01:34.080 --> 01:39.440
on all three of those are all all of our devices and in a numerical score

30
01:39.440 --> 01:42.080
between 0.0 and 10.

31
01:42.080 --> 01:47.840
So you can get like a 6.1 somewhere in there. So based on that, we can actually

32
01:47.840 --> 01:49.040
go over and see

33
01:49.040 --> 01:54.280
our vulnerable endpoints over time top vulnerabilities that make up that CVSS

34
01:54.280 --> 01:57.520
score and vulnerability watchlist.

35
01:57.520 --> 02:00.980
Like what vulnerability is actually coming to end that we need to be on the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

35
01:57.520 --> 02:00.980
Like what vulnerability is actually coming to end that we need to be on the

36
02:00.980 --> 02:02.480
lookout for because

37
02:02.480 --> 02:07.600
I'm on to you. And then that leads us into threat because we actually have to

38
02:07.600 --> 02:08.880
know what threat

39
02:08.880 --> 02:13.400
actually is in order for us to be able to understand what the CVSS score is

40
02:13.400 --> 02:14.880
reporting to us as a

41
02:14.880 --> 02:20.040
top vulnerability. See, when we break down the actual threat cycle of what's

42
02:20.040 --> 02:21.840
actually going on,

43
02:21.840 --> 02:27.540
we look at our vulnerabilities as being an entry point into the system by an

44
02:27.540 --> 02:28.720
actual threat on the

45
02:28.720 --> 02:33.480
outside of our organization or could be inside who knows, but the vulnerability
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

45
02:28.720 --> 02:33.480
outside of our organization or could be inside who knows, but the vulnerability

46
02:33.480 --> 02:34.880
invites the threat.

47
02:34.880 --> 02:39.730
And the threat is there to actually take an exploit that vulnerability to be

48
02:39.730 --> 02:40.800
able to monitor

49
02:40.800 --> 02:45.040
everything inside of I says we have here allows us to be able to go and

50
02:45.040 --> 02:47.920
identify on the fly with real-time

51
02:47.920 --> 02:53.910
accuracy based on definitions that we can actually go through and understand

52
02:53.910 --> 02:54.960
how we can better

53
02:54.960 --> 03:02.000
prepare our network for top level security. Having application access inside of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
02:54.960 --> 03:02.000
prepare our network for top level security. Having application access inside of

54
03:02.000 --> 03:03.360
our platform as

55
03:03.360 --> 03:08.340
a service model allows us the freedom to go through as network technicians and

56
03:08.340 --> 03:09.200
work with our

57
03:09.200 --> 03:14.030
cybersecurity specialist inside of our organization to properly identify those

58
03:14.030 --> 03:15.120
vulnerabilities,

59
03:15.120 --> 03:21.170
look at the threats that could potentially exploit those vulnerabilities and

60
03:21.170 --> 03:22.640
develop policies

61
03:22.640 --> 03:27.600
that we can use inside of our Ketalus Center here that we time down and have to

62
03:27.600 --> 03:29.040
re-log back into

63
03:29.040 --> 03:32.860
and develop policies that we can implement to push after those network devices
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

63
03:29.040 --> 03:32.860
and develop policies that we can implement to push after those network devices

64
03:32.860 --> 03:34.720
within the organization

65
03:34.720 --> 03:40.960
and actually go through and better patch all of our systems up. And I'm trying

66
03:40.960 --> 03:42.000
to log in to hear

67
03:42.000 --> 03:46.350
right now to show you the actual policy dashboard and configuration profile

68
03:46.350 --> 03:48.160
that we can use in an

69
03:48.160 --> 03:55.680
order to complete that task. But just know that again that it's very critical

70
03:55.680 --> 03:57.120
for us to be able to go

71
03:57.120 --> 04:01.700
through and have that application access to be able to identify those threats
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
03:57.120 --> 04:01.700
through and have that application access to be able to identify those threats

72
04:01.700 --> 04:03.760
and maintain the CIA

73
04:03.760 --> 04:09.520
triad of confidentiality integrity and availability. So the availability side.

74
04:09.520 --> 04:13.840
Once we're actually inside of our dashboard we go and click on the top left and

75
04:13.840 --> 04:15.120
go into provision

76
04:15.120 --> 04:19.610
and inside of our inventory to see all of our devices. Remember we only have

77
04:19.610 --> 04:20.560
the four available

78
04:20.560 --> 04:25.050
inside of our sandbox environment here and we can click on just one of the

79
04:25.050 --> 04:27.680
switches I picked SW1.

80
04:27.680 --> 04:32.780
We can actually go into run command and it opens up a prompt here and based on
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
04:27.680 --> 04:32.780
We can actually go into run command and it opens up a prompt here and based on

81
04:32.780 --> 04:34.320
the actual restrictions

82
04:34.320 --> 04:38.930
of our policy that's implemented we can even do a show run now show runs

83
04:38.930 --> 04:41.760
available and other

84
04:41.760 --> 04:46.870
commands like going into enable and config or not. But that's all based on

85
04:46.870 --> 04:47.920
policy and this is a

86
04:47.920 --> 04:52.510
way for us to be able to go check policy enforcement and also the configuration

87
04:52.510 --> 04:55.280
. So as we scroll up and

88
04:55.280 --> 04:59.880
look at the configuration we would be able to go through here and ensure that

89
04:59.880 --> 05:00.960
the automation
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

89
04:59.880 --> 05:00.960
the automation

90
05:00.960 --> 05:06.220
services that were incorporated inside of our Cisco environment for the

91
05:06.220 --> 05:07.680
application level

92
05:07.680 --> 05:12.880
is actually being implemented correctly for auditing purposes.