WEBVTT

00:00:01.240 --> 00:00:05.050
Welcome back to the course, and welcome to the final module.

00:00:05.540 --> 00:00:08.270
We spent the entire course so far talking about how

00:00:08.270 --> 00:00:10.290
Zeek can integrate with other tools,

00:00:10.380 --> 00:00:14.520
how it's used in combined platforms, and how to use some of its more

00:00:14.520 --> 00:00:18.350
hidden capabilities like file carving. In this module,

00:00:18.360 --> 00:00:20.460
the focus is on intelligence.

00:00:22.140 --> 00:00:25.610
Zeek's Intelligence Framework is designed to consume data

00:00:25.800 --> 00:00:27.750
and make it available for matching.

00:00:28.740 --> 00:00:31.910
It's a handy framework that we can use for both static

00:00:31.910 --> 00:00:34.760
intelligence and dynamically downloaded intelligence.

00:00:35.740 --> 00:00:38.540
The intel that we use can be something static in

00:00:38.540 --> 00:00:41.430
nature like a domain, IP address,

00:00:41.440 --> 00:00:44.920
email address, or something else that can be used to

00:00:44.920 --> 00:00:47.160
identify something or someone.

00:00:47.640 --> 00:00:50.820
Those static intelligence items could contain additional

00:00:50.820 --> 00:00:53.660
context or metadata that we can use.

00:00:54.440 --> 00:00:59.690
Take an IP address, for example. Using something like the GeoIP database

00:00:59.700 --> 00:01:03.730
that we saw in a previous module, we can stitch the location information

00:01:03.730 --> 00:01:08.650
about the IP address and even look up who the owners are and if the IPs are

00:01:08.650 --> 00:01:14.920
part of any malicious domain. All of that info is additional context data

00:01:15.110 --> 00:01:19.700
that we can use to help us detect threats or match specific criteria that

00:01:19.700 --> 00:01:20.560
we're looking for.

00:01:21.440 --> 00:01:22.970
As I've mentioned previously,

00:01:23.210 --> 00:01:27.370
we can create an alert if our outside traffic is going to something like

00:01:27.370 --> 00:01:30.160
another country that we may not want it to be communicating with.

00:01:30.940 --> 00:01:36.400
Another use of this is hashing. We have the File Analysis Framework that we

00:01:36.400 --> 00:01:42.600
talked about earlier and JA3 data that we'll cover later on in this module that

00:01:42.600 --> 00:01:45.860
we can use for matching traffic to potential threats.

00:01:46.940 --> 00:01:51.330
We can take the file hashes and the file analysis that Zeek does and

00:01:51.330 --> 00:01:53.860
attempt to match them to known malicious files.

00:01:54.840 --> 00:01:59.770
We can use the JA3 data from the SSL and TLS connections to identify

00:01:59.820 --> 00:02:04.560
potentially malicious data streams that are encrypted, matching them

00:02:04.570 --> 00:02:07.960
to known JA3 hashes. More on that later.

00:02:08.740 --> 00:02:12.760
The Zeek Intelligence Framework is relatively simple to get started with.

00:02:13.640 --> 00:02:17.160
We can take a basic intelligence file or, as I mentioned, we can

00:02:17.160 --> 00:02:22.340
download our own dynamic intelligence data and format it to align with

00:02:22.340 --> 00:02:28.410
Zeek's framework. Then, load the intel framework and match the traffic

00:02:28.410 --> 00:02:30.160
that we see to that intelligence.

00:02:30.840 --> 00:02:35.140
The data that matches can be flagged in the intel log, or we can raise a

00:02:35.140 --> 00:02:42.130
notice or webhook or any of Zeek's other actions that we have available to us

00:02:42.130 --> 00:02:47.940
to use. With the Intelligence Framework, we have this list of intel types that

00:02:47.940 --> 00:02:50.160
we can match on in our intelligence file.

00:02:50.940 --> 00:02:54.890
We have things like the email address, IP address,

00:02:54.900 --> 00:02:55.730
software names,

00:02:55.730 --> 00:03:00.460
file hashes, domain names, URLs, usernames, and

00:03:00.460 --> 00:03:02.850
certificate hashes to name a few.

00:03:03.840 --> 00:03:07.930
Each of these gives us different matching abilities that gives us some pretty

00:03:07.930 --> 00:03:12.840
cool flexibility within Zeek. Now I'm not going to go through and read each

00:03:12.840 --> 00:03:17.800
function and type and event that we have available to us, but you can find

00:03:17.800 --> 00:03:23.110
more information about the framework at this link. We have three functions for

00:03:23.110 --> 00:03:25.370
intelligence built in, seen,

00:03:25.380 --> 00:03:30.260
insert, and remove. And we have a few events and hooks here as well.

00:03:31.340 --> 00:03:35.220
What I really like about the Intelligence Framework is the ability to create

00:03:35.220 --> 00:03:40.680
more complex matches using the functions and events and variables that we have.

00:03:40.680 --> 00:03:45.660
Similar to the rest of Zeek's scripts, we can make the intelligence handling as

00:03:45.660 --> 00:03:48.400
simple or as complex as we need it to be.

00:03:49.440 --> 00:03:52.640
My philosophy is that as long as it's used effectively,

00:03:52.940 --> 00:03:58.100
context and metadata is very important to have. Let's check out how to

00:03:58.100 --> 00:04:01.050
configure the intel framework with a simple matching item.
