WEBVTT

00:00:01.740 --> 00:00:04.780
Arkime is the other component of the integration that

00:00:04.780 --> 00:00:06.750
we're working on in this module.

00:00:07.340 --> 00:00:10.610
If you've been around for a while, you may know it as Moloch.

00:00:10.610 --> 00:00:14.560
It's an open‑source packet capture and search tool that gives us the

00:00:14.560 --> 00:00:17.440
ability to integrate with other tools like Zeek,

00:00:17.460 --> 00:00:21.160
utilize APIs, and scale over a clustered deployment.

00:00:22.640 --> 00:00:23.860
You may be thinking already,

00:00:24.340 --> 00:00:27.840
why doesn't Arkime cover Zeek's use cases, since

00:00:27.840 --> 00:00:29.560
it's a full packet capture tool?

00:00:30.240 --> 00:00:31.650
Well, in some ways it does,

00:00:32.140 --> 00:00:36.330
but it's not typical for us to do full packet captures in every

00:00:36.330 --> 00:00:38.940
single instance that we may need information for,

00:00:38.940 --> 00:00:42.750
or we may not want to utilize that much storage for the captures.

00:00:43.440 --> 00:00:46.240
Zeek does a lot of great analysis on the traffic

00:00:46.240 --> 00:00:48.820
already, and so it can fill in the blanks,

00:00:48.820 --> 00:00:52.750
so to speak, in the instances where we aren't doing full pcaps.

00:00:53.840 --> 00:00:57.860
Okay, then what's this integration actually going to do for us?

00:00:59.140 --> 00:01:03.410
We're going to map Zeek's fields with Arkime's schema and enrich the

00:01:03.410 --> 00:01:08.060
data so that we can view it and search it in Arkime.

00:01:09.140 --> 00:01:13.420
This will give us a one‑stop shop for seeing the data and being

00:01:13.420 --> 00:01:16.380
able to correlate both data types during analysis,

00:01:16.430 --> 00:01:18.950
which will help us out in our cyber operations.

00:01:19.740 --> 00:01:24.720
We'll be able to essentially link Zeek's logs to Arkime's sessions to

00:01:24.720 --> 00:01:28.300
view both and get a better idea of what's happening.

00:01:28.300 --> 00:01:33.030
Enough of the explanations of the tools and integrations we'll be doing.

00:01:33.030 --> 00:01:37.320
Let's talk about what we need to actually get this going.

00:01:37.320 --> 00:01:40.310
We need to have our Zeek instance up and running,

00:01:40.310 --> 00:01:44.360
we need the ELK Stack installed and receiving the Zeek logs

00:01:44.840 --> 00:01:47.260
with Logstash ingesting and stashing them,

00:01:48.040 --> 00:01:50.820
and we need Arkime installed and operating smoothly,

00:01:50.820 --> 00:01:52.660
or at least operating.

00:01:53.140 --> 00:01:55.860
If you need to get an understanding of how to set up Arkime,

00:01:56.240 --> 00:01:58.170
then check out the docs here.

00:01:58.170 --> 00:02:02.060
Also, if you're interested in learning how it can support network

00:02:02.060 --> 00:02:04.860
analysis activities mapped to the MITRE framework,

00:02:05.240 --> 00:02:08.310
then check out the blue team tools skill path and,

00:02:08.310 --> 00:02:14.150
more specifically, the course, Network Analysis with Arkime by Josh Stroschein.

00:02:15.540 --> 00:02:16.950
So here's what we have going on.

00:02:17.440 --> 00:02:21.940
We have a platform known as Malcolm, which was developed by the CISA,

00:02:21.940 --> 00:02:26.360
or the Cybersecurity and Infrastructure Security Agency, in

00:02:26.360 --> 00:02:28.730
partnership with the Idaho National Lab.

00:02:28.730 --> 00:02:30.660
And what exactly is this?

00:02:31.140 --> 00:02:35.560
Well, it's a platform that also has many different tools in it,

00:02:35.940 --> 00:02:37.350
similar to Security Onion,

00:02:38.040 --> 00:02:43.930
but much more robust with allowing us to analyze logs and files. What I really

00:02:43.930 --> 00:02:47.630
like about this one is that it comes with everything that we need for this use

00:02:47.630 --> 00:02:51.280
case built in. We have Arkime installed and running,

00:02:51.580 --> 00:02:54.760
we have Zeek installed and running, as well as the ELK Stack.

00:02:56.540 --> 00:03:00.740
What we'll do in the next few clips is this. We'll look at the configurations

00:03:00.740 --> 00:03:05.560
for the Logstash parses and make any necessary modifications,

00:03:06.640 --> 00:03:11.080
we'll grab all of the Arkime field definitions so that we know what to map the

00:03:11.080 --> 00:03:15.060
Zeek fields to, we'll actually view the mappings needed,

00:03:15.740 --> 00:03:18.860
then enrich the logs for things like GeoIP lookups.

00:03:19.540 --> 00:03:24.890
After that, we create the WISE data source in Arkime and validate that we can

00:03:24.890 --> 00:03:29.280
see the sessions for both and correlate the network activity between the two.

00:03:29.280 --> 00:03:34.880
In the next clip we'll get started with it. If you want to follow along with

00:03:34.880 --> 00:03:38.750
your own installation of Malcolm or want to try the mappings with your own

00:03:38.750 --> 00:03:42.950
installation of the tools instead, check out these links. They'll at least

00:03:42.950 --> 00:03:47.010
get you started, and you can follow along in the lab to view it all inside of

00:03:47.010 --> 00:03:47.550
Malcolm.

00:03:48.540 --> 00:03:52.230
Since we've already walked through the basic setup of getting the Zeek logs

00:03:52.230 --> 00:03:56.190
shipped over to Logstash, you should be able to follow along with your own tool

00:03:56.190 --> 00:03:58.560
if you don't want to download the Malcolm platform.
