WEBVTT

00:00:01.240 --> 00:00:02.860
Let's talk about packages now.

00:00:03.540 --> 00:00:06.500
Zeek has a package manager that allows us to install

00:00:06.500 --> 00:00:08.760
third‑party scripts and plugins.

00:00:09.440 --> 00:00:13.240
This package manager makes it very easy to get add‑ons and

00:00:13.240 --> 00:00:16.460
integrations into the Zeek system for use with the tool.

00:00:17.240 --> 00:00:21.210
Let's take a look at some of these things that we can do with the packages.

00:00:21.210 --> 00:00:25.560
We can find the packages to download in a few different places,

00:00:25.940 --> 00:00:30.590
but the main two are at Zeek's official website and in their GitHub repo.

00:00:30.590 --> 00:00:34.260
When downloading the packages using the Zeek Package Manager,

00:00:34.640 --> 00:00:36.120
they're pulled from GitHub.

00:00:36.120 --> 00:00:40.850
You can install your own packages or other third‑party ones as well if needed.

00:00:41.440 --> 00:00:43.440
This gives us even more capability,

00:00:43.620 --> 00:00:46.830
as we can develop our own and manually add them into Zeek.

00:00:48.940 --> 00:00:51.460
So what kind of packages are available?

00:00:52.340 --> 00:00:54.260
Why would we add any of these?

00:00:54.740 --> 00:00:56.420
Well, out of the box,

00:00:56.430 --> 00:00:59.940
Zeek does a really good job with a lot of traffic processing,

00:00:59.940 --> 00:01:04.150
but each of the packages helps expand its capabilities by

00:01:04.150 --> 00:01:06.950
adding additional use cases that it can support.

00:01:07.840 --> 00:01:11.710
Take this one, for example, the Zeek plugin for IKEv2.

00:01:11.710 --> 00:01:16.810
This package enables Zeek to parse IKEv2 protocol traffic and

00:01:16.810 --> 00:01:20.700
give us insight into the initial SA set up and tells us the

00:01:20.700 --> 00:01:23.460
ciphers being used and the SPIs as well.

00:01:24.640 --> 00:01:26.160
Or what about this one?

00:01:27.140 --> 00:01:31.260
Collaboration software has been increasing in popularity as

00:01:31.260 --> 00:01:34.060
remote work and meetings have become more common.

00:01:34.740 --> 00:01:38.000
This one detects Zoom traffic and gives us

00:01:38.010 --> 00:01:39.960
information about the initial connection.

00:01:40.940 --> 00:01:43.510
It'll tell us about the Zoom connection and the servers

00:01:43.510 --> 00:01:45.890
that the clients are connecting to.

00:01:45.890 --> 00:01:51.500
Or we can go a completely different direction and use a plugin that

00:01:51.510 --> 00:01:54.660
adds the GeoIP data and the reputation scores.

00:01:55.840 --> 00:01:59.710
We can add this information to generate notices if thresholds are crossed for

00:01:59.710 --> 00:02:04.140
the reputations of the places that we're visiting on the net.

00:02:04.140 --> 00:02:07.030
Before we can download the packages,

00:02:07.030 --> 00:02:11.360
we'll need to install the zkg, or Zeek Package Manager.

00:02:12.340 --> 00:02:15.550
You can do this by either manually installing and configuring

00:02:15.940 --> 00:02:17.950
or using the preinstalled version of it.

00:02:18.940 --> 00:02:22.080
The documentation here can help you identify the steps

00:02:22.080 --> 00:02:23.860
to take for your specific deployment.

00:02:24.640 --> 00:02:28.160
I'm going to be using the default installation for zkg that

00:02:28.160 --> 00:02:32.590
comes with Zeek 4.0 and later, and with that, as long as the

00:02:32.590 --> 00:02:34.060
other dependencies are okay,

00:02:34.540 --> 00:02:40.080
I'll use the command zkg autoconfig. In the next clip, we'll

00:02:40.080 --> 00:02:43.560
go through and look at some of what we just discussed and see

00:02:43.560 --> 00:02:45.360
the package manager in action.
