WEBVTT

00:00:01.540 --> 00:00:05.650
Zeek has been a staple in the Security Onion suite for some time now.

00:00:06.140 --> 00:00:10.060
But with the ability to containerize applications gaining popularity,

00:00:10.440 --> 00:00:12.550
more applications have been added,

00:00:12.550 --> 00:00:16.650
and new abilities have been created to improve the uses of the suite.

00:00:17.540 --> 00:00:21.090
Let's take a look at how Zeek can be used with some of the Security Onion

00:00:21.090 --> 00:00:24.860
components before we dive into the lab and see it first hand.

00:00:26.340 --> 00:00:31.160
Zeek now is installed automatically with Security Onion and is containerized.

00:00:32.040 --> 00:00:35.440
It's used within the platform to provide network visibility,

00:00:35.440 --> 00:00:38.360
and the logs are parsed and sent to be stored.

00:00:39.540 --> 00:00:42.220
They are then available to view in other tools.

00:00:42.220 --> 00:00:44.950
Those tools are Kibana and Hunt.

00:00:45.540 --> 00:00:49.720
We'll talk more about the ELK stack in Kibana more in the next modules as well.

00:00:49.760 --> 00:00:55.260
But within Security Onion, Elasticsearch is what parses and stores the Zeek logs.

00:00:56.040 --> 00:00:59.120
Kibana and Hunt then pull the logs for their use.

00:00:59.940 --> 00:01:03.330
Kibana can be thought of as your front end to the ELK stack,

00:01:03.330 --> 00:01:06.150
the SIEM GUI so to speak.

00:01:06.150 --> 00:01:10.320
Hunt is a similar interface that allows you to essentially

00:01:10.320 --> 00:01:13.200
hunt through your data in Elasticsearch.

00:01:13.200 --> 00:01:17.810
It's already tuned fairly well and gives you a lot

00:01:17.810 --> 00:01:19.450
of great information off the bat.

00:01:20.740 --> 00:01:25.340
Zeek has the ability to use the Intelligence Framework in order to add

00:01:25.350 --> 00:01:28.260
threat intelligence and additional context to your data.

00:01:29.040 --> 00:01:32.840
Security Onion supports this capability as well and allows you

00:01:32.840 --> 00:01:35.440
to add your own intel to the deployment.

00:01:35.440 --> 00:01:39.650
We'll cover the Intelligence Framework in a later module for this course.

00:01:40.240 --> 00:01:42.360
But as we'll find out here in a few minutes,

00:01:42.360 --> 00:01:46.060
we'll need to program the Intelligence configurations using

00:01:46.060 --> 00:01:49.350
the Salt scripts and monitor the logs to ensure that it's

00:01:49.350 --> 00:01:51.360
being added appropriately afterwards.

00:01:52.640 --> 00:01:54.580
As with a typical Zeek installation,

00:01:54.580 --> 00:01:58.850
we're able to add our own custom scripts to the deployment as well.

00:01:59.640 --> 00:02:03.410
This is handy for being able to deploy a solid Zeek implementation in

00:02:03.410 --> 00:02:08.070
your network within Security Onion while also not being constrained to

00:02:08.070 --> 00:02:10.449
the preconfigured parameters that they provide.

00:02:11.440 --> 00:02:14.160
You can do things like add and remove scripts,

00:02:14.540 --> 00:02:19.490
modify the local.zeek script, turn on and off protocol analyzers,

00:02:19.490 --> 00:02:21.410
and so much more.

00:02:21.410 --> 00:02:26.900
So Security Onion gives us a lot of flexibility with using Zeek while

00:02:26.910 --> 00:02:29.760
also giving us a standardized build of it as well.

00:02:31.040 --> 00:02:32.350
So as I mentioned,

00:02:32.640 --> 00:02:35.510
we use something called Salt to manage the Zeek

00:02:35.510 --> 00:02:37.460
configurations within Security Onion.

00:02:38.840 --> 00:02:43.910
This actually manages all the processes on all of the Security Onion nodes.

00:02:43.920 --> 00:02:46.490
So if you don't already know about Salt,

00:02:46.500 --> 00:02:49.560
I suggest reading up on it in the documentation.

00:02:49.560 --> 00:02:54.650
What this is used for is for infrastructure management and

00:02:54.650 --> 00:02:56.760
helps us push out configs as needed.

00:02:57.840 --> 00:03:00.970
Salt allows us to change options in Filebeat,

00:03:00.970 --> 00:03:08.110
firewalls, alerting, Suricata, and Zeek as of Security Onion 2.3.

00:03:08.110 --> 00:03:12.790
Salt files are also in YAML format.

00:03:12.790 --> 00:03:17.370
With regards to Zeek, Salt manages the local.zeek,

00:03:17.370 --> 00:03:25.570
node.config, and zeekctl.cfg files so we can use options for redefinitions,

00:03:25.720 --> 00:03:30.980
signatures, and script loading from the local.zeek script in the Salt config.

00:03:30.980 --> 00:03:34.000
We can modify the interface, network,

00:03:34.000 --> 00:03:37.120
and many other options for the other two files.

00:03:37.120 --> 00:03:43.580
Since the opt/so/saltstack/local directory isn't

00:03:43.590 --> 00:03:45.560
overwritten during platform upgrades,

00:03:46.040 --> 00:03:48.350
this is where we'll need to make our Salt files.

00:03:49.140 --> 00:03:54.790
Any configuration that you make here or remove here will override the default

00:03:54.790 --> 00:04:01.670
Salt configs in the default/pillar/zeek/init.sls file. Once saved after the

00:04:01.670 --> 00:04:06.030
changes are made to the Salt files, the container should be restarted for the

00:04:06.030 --> 00:04:12.080
config changes to take effect. In Security Onion's implementation of Zeek, we

00:04:12.080 --> 00:04:16.990
have the same logs that we've seen in our standard Zeek deployment. So we'll

00:04:16.990 --> 00:04:22.350
be able to see the connections and DNS activity and HTTP logs if we wanted to.

00:04:23.340 --> 00:04:27.910
They're in JSON format by default and are collected by a Filebeat for

00:04:27.910 --> 00:04:34.550
processing using Elasticsearch. They'll be in the /nsm/zeek/logs

00:04:34.550 --> 00:04:37.760
directory for you to cat in jq with to view.

00:04:38.840 --> 00:04:42.650
Remember, we'll use Hunt and Kibana as well to look at this information.
