WEBVTT

00:00:01.740 --> 00:00:02.450
All right,

00:00:02.450 --> 00:00:06.270
now that we have our local Zeek configuration built from the Salt file,

00:00:06.280 --> 00:00:10.890
we need to go through and see its operations in Kibana.

00:00:10.890 --> 00:00:14.470
Let's hop into the lab and validate that we can see the Zeek data

00:00:14.480 --> 00:00:17.530
and see how we can view or use it in Kibana.

00:00:17.530 --> 00:00:19.160
Let's go check it out.

00:00:20.840 --> 00:00:24.340
All right, here I am in my Security Onion dashboard.

00:00:24.340 --> 00:00:25.860
And from here,

00:00:25.860 --> 00:00:30.440
I'm able to just hop straight into Hunt or Kibana or whatever

00:00:30.440 --> 00:00:32.360
tool that I want to use within the suite.

00:00:32.840 --> 00:00:36.260
This is really cool because it gives us a simple dashboard to get a

00:00:36.260 --> 00:00:40.340
lot of data and do our threat hunting to work on case management

00:00:40.340 --> 00:00:41.960
through Hive and so on and so forth.

00:00:43.340 --> 00:00:45.710
So I'm going to go ahead and open Kibana.

00:00:45.710 --> 00:00:47.240
And at this point,

00:00:47.240 --> 00:00:51.020
the configurations were already reset back to their default ones.

00:00:51.030 --> 00:00:54.590
Those changes that we made in the previous demo were just to show

00:00:54.590 --> 00:00:58.100
the Salt configuration changes taking effect with the local site

00:00:58.100 --> 00:01:00.680
script and the Zeek control file.

00:01:00.680 --> 00:01:04.319
So the Salt configuration was able to update those for

00:01:04.319 --> 00:01:06.920
us when we restarted Security Onion.

00:01:06.920 --> 00:01:08.370
Here in Kibana,

00:01:08.370 --> 00:01:11.560
we have such a cool dashboard that just pops up

00:01:11.560 --> 00:01:13.380
automatically as soon as we launch it.

00:01:13.380 --> 00:01:17.020
It gives us an overview of a lot of the data that we

00:01:17.020 --> 00:01:20.350
have going through our network, where that data is coming from,

00:01:20.940 --> 00:01:26.410
what some of the log files are, and what tools we're using to get this data.

00:01:26.410 --> 00:01:29.550
And since Zeek is the focus of this course,

00:01:29.550 --> 00:01:33.440
as you can see, we have a lot of the connection logs and everything like that,

00:01:33.450 --> 00:01:38.960
the SSL logs, the HTTP logs that Zeek handled and provides Security Onion.

00:01:40.140 --> 00:01:42.760
And we can filter, we can change colors in Kibana.

00:01:42.760 --> 00:01:48.290
So this is really cool the type of visualizations that we can create in here.

00:01:48.300 --> 00:01:50.010
Like I was saying in the previous clips,

00:01:50.010 --> 00:01:52.000
it's pretty much like a SIEM,

00:01:52.010 --> 00:01:56.250
and it adds a lot of visualizations and capabilities and stuff like that.

00:01:57.240 --> 00:01:59.660
And this defaults to the last 24 hours.

00:02:00.740 --> 00:02:03.290
Now I'm going to go ahead and just click the connection log dataset

00:02:03.290 --> 00:02:06.140
just to talk through what we're seeing real quick.

00:02:06.140 --> 00:02:09.840
When we click that, the connection log is specific to Zeek.

00:02:09.850 --> 00:02:13.050
So all of these logs are similar to the ones that we'll find in

00:02:13.050 --> 00:02:15.820
the connection log in the Zeek nsm folder.

00:02:15.820 --> 00:02:18.970
And it's giving us a lot of data on the IP addresses and

00:02:18.970 --> 00:02:20.690
the ports and everything like that.

00:02:20.700 --> 00:02:25.650
We can filter on different alerts or different files or hosts or networks.

00:02:25.650 --> 00:02:29.910
We see the top protocols, the conversations that we see,

00:02:29.920 --> 00:02:32.600
and then this overview of the logs right here.

00:02:32.600 --> 00:02:37.280
And we can expand any of these to go ahead and look at more of that data.

00:02:37.280 --> 00:02:40.660
And we can look at it in either table format or JSON format.

00:02:41.940 --> 00:02:45.800
So Kibana gives us some pretty cool capabilities from this perspective.

00:02:45.800 --> 00:02:49.150
And with the Security Onion implementation itself,

00:02:49.640 --> 00:02:52.510
what's really cool about this is we can go ahead and

00:02:52.520 --> 00:02:55.990
create cases in our case management tool,

00:02:55.990 --> 00:02:58.210
TheHive, straight from these logs.

00:02:58.220 --> 00:03:00.160
So I think that's a really cool capability.

00:03:02.140 --> 00:03:05.170
I'm going to go ahead and go back to the previous tab and

00:03:05.170 --> 00:03:07.150
just click on the Zeek module over here.

00:03:08.440 --> 00:03:10.740
And let's see what pulls up with that dashboard.

00:03:10.750 --> 00:03:13.880
It's a similar setup where we're seeing the top protocols,

00:03:13.880 --> 00:03:17.820
the IP addresses, the different datasets that Zeek's providing us,

00:03:17.820 --> 00:03:20.200
the ports and all of that information.

00:03:20.200 --> 00:03:24.600
We can filter it further on the different log files.

00:03:24.610 --> 00:03:27.440
We can export any of this information as well,

00:03:27.450 --> 00:03:30.570
which can be really handy if we're needing to import these

00:03:30.570 --> 00:03:34.140
into another tool or if we need to keep them for some

00:03:34.150 --> 00:03:36.500
historical records and stuff like that.

00:03:36.510 --> 00:03:40.000
And we can also click on any of these fields just like a normal SIEM,

00:03:40.000 --> 00:03:46.840
and it'll pull up information on those indicators on those IP addresses what

00:03:46.840 --> 00:03:49.170
kind of traffic we're seeing on them and so on and so forth,

00:03:49.170 --> 00:03:51.560
so similar to traditional SIEM functionality.

00:03:53.140 --> 00:03:53.300
Now,

00:03:53.300 --> 00:03:57.150
this is why Kibana is so powerful with its visualizations and

00:03:57.150 --> 00:03:59.540
stuff like that because it's really dynamic.

00:03:59.540 --> 00:04:01.920
They're fairly easy to create as well,

00:04:01.920 --> 00:04:06.720
and it provides us a lot of nice visuals to be able to have up on a

00:04:06.720 --> 00:04:11.770
monitoring platform or come in and view and click around and come in

00:04:11.770 --> 00:04:15.300
and work through it because we can click in the graphs and jump into

00:04:15.300 --> 00:04:16.620
the actual data in the graphs.

00:04:16.620 --> 00:04:19.959
Instead of it just being a visual, it's actually interactive.

00:04:22.040 --> 00:04:24.570
All right, so let's go back to the Kibana dashboard.

00:04:24.580 --> 00:04:27.270
And the last thing that I want to show is some of the

00:04:27.270 --> 00:04:29.110
SIEM‑type capabilities of Kibana.

00:04:29.110 --> 00:04:32.190
So as you'll see, I went over to the Discover tab.

00:04:32.200 --> 00:04:34.880
And this setup might look a little bit familiar.

00:04:34.890 --> 00:04:38.450
It's reminiscent of our traditional SIEM devices,

00:04:38.540 --> 00:04:41.900
Splunk and QRadar and any other ones that ingest logs.

00:04:41.900 --> 00:04:45.500
We typically have formats like this where we're just displaying the

00:04:45.500 --> 00:04:47.560
logs with the fields and everything like that.

00:04:48.940 --> 00:04:52.480
And what's really cool about this is similarly to those other platforms,

00:04:52.480 --> 00:04:56.920
we can just expand it and see the actual information.

00:04:56.930 --> 00:05:00.280
We can see every single field that is in this log

00:05:00.290 --> 00:05:02.080
and the data that comes with it.

00:05:02.080 --> 00:05:03.380
We can click on them too.

00:05:03.380 --> 00:05:06.710
So if we wanted to jump into some additional OSSEC data we can do

00:05:06.710 --> 00:05:09.850
that just by clicking on that hyperlink right there.

00:05:11.440 --> 00:05:15.470
So this gives us a lot of capabilities to dive from the logs themselves

00:05:15.480 --> 00:05:18.360
into additional tabs to find more data if we wanted to.

00:05:19.540 --> 00:05:22.910
What's cool about this too is a lot of the fields are already

00:05:22.910 --> 00:05:27.070
extracted or populated in the SIEM capabilities here.

00:05:27.070 --> 00:05:32.050
So if we wanted to, we could filter in on specific fields or anything like that.

00:05:32.940 --> 00:05:35.000
We can search for field names as well.

00:05:35.000 --> 00:05:37.260
So if we were looking for a specific port,

00:05:38.240 --> 00:05:42.370
we can go ahead and do that and see if anything comes up with those fields.

00:05:42.370 --> 00:05:45.750
And as you can see, it refreshed the search,

00:05:45.750 --> 00:05:48.350
cleared the current filter that we had on it,

00:05:48.740 --> 00:05:52.710
and now we have all of the logs that are populated with that one.

00:05:52.710 --> 00:05:55.270
So an example of doing a simple search with that is if

00:05:55.270 --> 00:05:57.670
we wanted to just look for port 53.

00:05:57.680 --> 00:05:59.520
It would be a similar syntax to that.

00:05:59.520 --> 00:06:03.040
And it filters the logs for us, gives us only the relevant data.

00:06:03.040 --> 00:06:07.150
So you can use the Kibana query language to create search

00:06:07.150 --> 00:06:09.350
strings similarly to other SIEMs as well.

00:06:10.040 --> 00:06:11.810
We can filter by the fields,

00:06:11.810 --> 00:06:15.090
we can filter by logs that have certain fields like we just did,

00:06:15.100 --> 00:06:17.990
and then we can also do those custom searches and add

00:06:17.990 --> 00:06:19.460
filters and so on and so forth.

00:06:20.140 --> 00:06:22.210
So the capabilities here are really cool.

00:06:22.210 --> 00:06:25.540
And what I like about this right now in this demo is that we're

00:06:25.540 --> 00:06:29.890
validating that we are seeing messages from Zeek.

00:06:29.890 --> 00:06:31.600
And how do I know that?

00:06:31.610 --> 00:06:34.400
Because we have the log file path right there,

00:06:34.410 --> 00:06:39.160
the /nsm/zeek/logs, and then current/http,

00:06:39.160 --> 00:06:40.760
for example, right here.
