WEBVTT

1
00:00.000 --> 00:04.480
Hello and welcome. My name is Keith Barker and I'd like you to think with me

2
00:04.480 --> 00:05.200
for a moment.

3
00:05.200 --> 00:09.040
If we had to call a company for an issue that we're having, it could be an

4
00:09.040 --> 00:10.080
insurance company,

5
00:10.080 --> 00:13.970
it could be utility company, it could be whatever, if we call them about a

6
00:13.970 --> 00:15.360
problem or an issue

7
00:15.360 --> 00:19.040
and they need to, you know, find out more about it and get back to us, how in

8
00:19.040 --> 00:19.840
the world do they

9
00:19.840 --> 00:24.350
track that? And the answer many times is they would open a ticket or open up a

10
00:24.350 --> 00:25.520
service request or

11
00:25.520 --> 00:29.670
some entity, something that could be tracked to the problem that we're having

12
00:29.670 --> 00:30.880
so they could research
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

12
00:29.670 --> 00:30.880
so they could research

13
00:30.880 --> 00:34.500
it, get information and then hopefully resolve it for us. Now wouldn't it be

14
00:34.500 --> 00:35.520
great on the 40

15
00:35.520 --> 00:40.280
analyzer if we had some option like a ticket or a service request that we could

16
00:40.280 --> 00:41.040
use when we're

17
00:41.040 --> 00:44.910
investigating or analyzing some issue or problem that's happening on the

18
00:44.910 --> 00:46.080
network, especially if

19
00:46.080 --> 00:49.600
it's security related with information that's pouring in from our firewalls.

20
00:49.600 --> 00:50.800
Well the good news is we

21
00:50.800 --> 00:54.130
have something like that in 40 analyzer but they don't call it a service

22
00:54.130 --> 00:55.440
request, they don't call it a

23
00:55.440 --> 00:59.440
ticket, what they do call it is an incident. And in this set of videos that's

24
00:59.440 --> 01:00.560
exactly what we get
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
00:59.440 --> 01:00.560
exactly what we get

25
01:00.560 --> 01:05.080
to focus on. What is an incident? How can it be created and used to help

26
01:05.080 --> 01:06.480
identify problems and

27
01:06.480 --> 01:10.080
triangulate with many firewalls when needed down to the exact problems and

28
01:10.080 --> 01:11.200
security issues that we're

29
01:11.200 --> 01:14.950
having on our network so we can solve them. So also you my friend in the next

30
01:14.950 --> 01:16.080
video if you take a big

31
01:16.080 --> 01:20.880
picture look at the wonderful world of incidents on the 40 analyzer.