Hello and welcome. My name is Keith Barker and I'd like you to think with me
for a moment.
If we had to call a company for an issue that we're having, it could be an
insurance company,
it could be utility company, it could be whatever, if we call them about a
problem or an issue
and they need to, you know, find out more about it and get back to us, how in
the world do they
track that? And the answer many times is they would open a ticket or open up a
service request or
some entity, something that could be tracked to the problem that we're having
so they could research WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
so they could research
it, get information and then hopefully resolve it for us. Now wouldn't it be
great on the 40
analyzer if we had some option like a ticket or a service request that we could
use when we're
investigating or analyzing some issue or problem that's happening on the
network, especially if
it's security related with information that's pouring in from our firewalls.
Well the good news is we
have something like that in 40 analyzer but they don't call it a service
request, they don't call it a
ticket, what they do call it is an incident. And in this set of videos that's
exactly what we get WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
exactly what we get
to focus on. What is an incident? How can it be created and used to help
identify problems and
triangulate with many firewalls when needed down to the exact problems and
security issues that we're
having on our network so we can solve them. So also you my friend in the next
video if you take a big
picture look at the wonderful world of incidents on the 40 analyzer.