WEBVTT

00:00:01.540 --> 00:00:06.010
Logstash, if you're working with the ELK Stack, could be your best friend.

00:00:06.010 --> 00:00:07.800
As I've mentioned previously,

00:00:07.810 --> 00:00:11.660
it's what stashes and parses the log information that we're ingesting.

00:00:12.340 --> 00:00:14.790
It is its own tool inside of the suite,

00:00:14.920 --> 00:00:17.260
and the configurations can get pretty robust.

00:00:17.640 --> 00:00:20.700
Let's take a look at this before we get into our use case of using

00:00:20.700 --> 00:00:23.660
Logstash to enrich the Zeek logs for Arkime.

00:00:24.840 --> 00:00:28.460
Logstash has the ability to perform several actions on your data.

00:00:29.040 --> 00:00:32.130
It can ingest multiple input formats and sources.

00:00:32.130 --> 00:00:38.050
It can parse and transform the data as it's being ingested or on the fly.

00:00:38.940 --> 00:00:43.080
It also has a selection of outputs that allow you to be flexible

00:00:43.080 --> 00:00:45.560
with where you're stashing or sending your data.

00:00:46.940 --> 00:00:51.450
It also has the ability to use extensions so that we can get or build

00:00:51.450 --> 00:00:55.250
Logstash plugins to help us add to the capabilities.

00:00:56.640 --> 00:00:59.060
So what are we doing with Logstash, exactly?

00:00:59.940 --> 00:01:00.430
Well,

00:01:00.570 --> 00:01:04.480
right now we only have a basic configuration of the

00:01:04.480 --> 00:01:07.350
tools set up to ingest our Zeek logs.

00:01:08.240 --> 00:01:09.660
The configuration is here.

00:01:09.660 --> 00:01:11.860
It's too much to display on the screen,

00:01:11.890 --> 00:01:15.550
but this is pretty much the default setup to use with Logstash.

00:01:16.140 --> 00:01:19.070
If you have the ELK Stack currently running in your environment,

00:01:19.070 --> 00:01:23.400
you can pull up the logstash.yml file and just validate that there's not

00:01:23.400 --> 00:01:26.090
too many settings to tweak in this one specifically.

00:01:26.090 --> 00:01:30.940
We're just defining our path variables in it for our instance.

00:01:30.940 --> 00:01:35.150
Defaults use the localhost address and the standard ports on this.

00:01:35.540 --> 00:01:38.400
We'll look deeper into more advanced configurations

00:01:38.400 --> 00:01:40.370
when we hop into the lab in a minute.

00:01:40.370 --> 00:01:44.340
But we do have a sample config for the Metricbeat and

00:01:44.340 --> 00:01:46.660
Apache logs already set up here.

00:01:48.440 --> 00:01:52.460
This configuration has inputs, filters, and outputs.

00:01:52.840 --> 00:01:56.750
We saw it a little bit in the previous demo when we added our

00:01:56.750 --> 00:01:59.490
input filters and outputs for the Zeek logs.

00:01:59.500 --> 00:02:02.300
This is a little bit more advanced using the grok filter,

00:02:02.310 --> 00:02:07.060
which helps us parse the logs better, and we also have our output going

00:02:07.060 --> 00:02:12.800
directly to Elasticsearch. When we hop into the demo we'll see a lot more of

00:02:12.800 --> 00:02:15.560
these pipeline configurations that are much more advanced.

00:02:16.440 --> 00:02:21.180
This one is pretty simple, and as you saw in the demo, with our Zeek input,

00:02:21.180 --> 00:02:23.660
we're using the JSON filter to help us with the data.

00:02:24.540 --> 00:02:27.750
Let's explore how we can parse and enrich the data for use with

00:02:27.760 --> 00:02:31.740
Arkime. And we need to figure out what exactly we're going to be

00:02:31.740 --> 00:02:35.060
using for this coming demo as our platform.

00:02:35.540 --> 00:02:36.760
More to follow on that.
