WEBVTT

00:00:01.440 --> 00:00:05.560
We're going to be using this demo to go over the RockNSM configs for Zeek,

00:00:05.560 --> 00:00:09.000
see some of the visualizations and configurations in Kibana,

00:00:09.000 --> 00:00:12.430
and see what differences are included in this setup to give it the

00:00:12.430 --> 00:00:15.350
ability to interact with other tools in this setup.

00:00:16.040 --> 00:00:17.860
Let's hop in and get started.

00:00:19.340 --> 00:00:22.630
All right, and here we are in our lab ready to go.

00:00:22.640 --> 00:00:23.930
I'm logged into my Zeek box,

00:00:23.930 --> 00:00:27.130
but what I need to do is just go ahead and open a connection into my

00:00:27.130 --> 00:00:29.450
RockNSM box so we can go ahead and look at that.

00:00:30.540 --> 00:00:32.250
All right, and here we are.

00:00:33.540 --> 00:00:37.290
So a couple important things to note about RockNSM is that the most

00:00:37.290 --> 00:00:41.250
recent version is build 2.6 as of this recording.

00:00:42.440 --> 00:00:45.480
Not too much has gone on on the development side,

00:00:45.490 --> 00:00:47.880
at least publicly on the web page anyway,

00:00:47.890 --> 00:00:49.200
but the package is still there.

00:00:49.200 --> 00:00:52.390
The tools are still interacting with each other and work.

00:00:52.390 --> 00:00:55.880
But like I said, the most recent version is 2.6, and it's there.

00:00:55.880 --> 00:00:57.730
They've upgraded to Zeek 3.0,

00:00:57.730 --> 00:01:01.840
and a lot of the tools are included in this package automatically.

00:01:01.840 --> 00:01:04.310
You can go through the installation of the tool.

00:01:04.319 --> 00:01:06.400
It's fairly straightforward.

00:01:06.410 --> 00:01:09.940
The instructions that are provided on Rock's website are clear and provide

00:01:09.940 --> 00:01:13.610
you a step‑by‑step process, and you can go ahead and turn on or off

00:01:13.610 --> 00:01:15.760
different tools if you need them or don't need them.

00:01:16.940 --> 00:01:19.280
But remember, with a lot of these platforms,

00:01:19.290 --> 00:01:23.570
you can help develop the tools or experiment with them to get it working for

00:01:23.570 --> 00:01:26.420
your specific use cases or your specific environments.

00:01:26.420 --> 00:01:30.870
If you are following along or intending on downloading RockNSM

00:01:30.880 --> 00:01:34.550
to try to see if it can work in your environment or see if it

00:01:34.550 --> 00:01:37.380
would benefit your organization, go ahead and download it.

00:01:37.380 --> 00:01:41.120
It's free. And then you can spin it up in a virtual machine or put it on

00:01:41.120 --> 00:01:43.930
a hardware box and just dive into the configurations,

00:01:43.940 --> 00:01:46.780
see the functionality of it, see the use cases,

00:01:46.780 --> 00:01:49.160
and validate that it can suit your needs.

00:01:50.240 --> 00:01:53.730
So before we get into the actual configurations in the CLI,

00:01:53.740 --> 00:01:56.900
I'm going to jump into Kibana so we can talk through some of

00:01:56.900 --> 00:01:59.080
the index patterns and stuff like that.

00:01:59.090 --> 00:02:03.660
So what RockNSM is doing for us is it's standardizing a

00:02:03.660 --> 00:02:06.920
lot of our indexes and our logs so that a lot of the tools

00:02:06.920 --> 00:02:08.960
can all use the information.

00:02:09.240 --> 00:02:11.370
This is a little bit similar to Malcolm,

00:02:11.370 --> 00:02:12.830
like we saw in the previous module,

00:02:12.830 --> 00:02:16.970
that platform where we were mutating a lot of the Zeek fields to map to Arkime

00:02:16.970 --> 00:02:22.300
and then also to be able to be used in other situations as well or other tools

00:02:22.310 --> 00:02:25.460
inside of Malcolm. And this is a similar case.

00:02:25.840 --> 00:02:30.210
So RockNSM implements the ECS standard for the logging.

00:02:30.220 --> 00:02:36.670
So as you can see, we have our ecs‑ as the prefix for the indices here or the

00:02:36.670 --> 00:02:40.400
index patterns here. And if we're looking then at these index patterns in

00:02:40.400 --> 00:02:43.630
Kibana, we can see that we have Zeek index patterns,

00:02:43.630 --> 00:02:47.830
we have Suricata index patterns. And then if we wanted to create more based

00:02:47.830 --> 00:02:52.380
off of some of the other indices, we could. If we hop over Index Management,

00:02:52.380 --> 00:02:55.030
we can see all of our different indices here.

00:02:55.040 --> 00:02:59.400
We have the file analysis index. We have different indices for Zeek

00:02:59.410 --> 00:03:05.240
and, like I said, Suricata as well. And each Zeek index is here for a

00:03:05.240 --> 00:03:07.740
specific use case or specific reason.

00:03:07.750 --> 00:03:11.540
So for example, we have a detection index here. We have

00:03:11.540 --> 00:03:14.240
observation indexes. We have file indexes as well.

00:03:14.240 --> 00:03:18.560
So each one of these is for a different use of Zeek's logs.

00:03:19.540 --> 00:03:22.060
I also wanted to show you some of the sample dashboards that come with

00:03:22.060 --> 00:03:26.580
RockNSM. There's a whole bunch more, but some of these are good at gauging

00:03:26.590 --> 00:03:30.890
metrics for the system and validating that it's operational and that it's

00:03:30.890 --> 00:03:33.730
actually capturing traffic and so on and so forth.

00:03:33.730 --> 00:03:37.450
So this first one is just a simple dashboard that comes with it. It's

00:03:37.450 --> 00:03:41.670
source versus destination bytes over time. And it just gives us a nice

00:03:41.680 --> 00:03:45.260
little chart here, and then we can switch the visualizations if we wanted

00:03:45.260 --> 00:03:48.960
to gauge or table or just seeing the metrics.

00:03:49.440 --> 00:03:53.750
So this is a pretty decent dashboard for us to be able to use for metrics

00:03:53.750 --> 00:03:57.430
at least. We also have record counts for Zeek as well.

00:03:57.440 --> 00:04:01.440
So we're able to view this visualization and see the

00:04:01.450 --> 00:04:03.860
cumulative sum of the record count.

00:04:04.640 --> 00:04:08.060
So this is all about the underlying system and how Zeek processes it.

00:04:08.540 --> 00:04:12.210
And then we also have Suricata logs and the alerts over time.

00:04:12.220 --> 00:04:15.180
So here we have a couple spikes for actual alerts.

00:04:15.180 --> 00:04:16.630
And this is the lab environment,

00:04:16.630 --> 00:04:19.360
so it's not going to generate a whole bunch of alerts out of the box.

00:04:20.640 --> 00:04:23.710
And what's really cool about all of the tools being included in here,

00:04:23.710 --> 00:04:27.550
similarly to Malcolm and other platforms like Security Onion,

00:04:27.560 --> 00:04:31.150
is that we can use a lot of this information collectively

00:04:31.150 --> 00:04:34.880
between the tools. So we can pivot from Zeek logs and go

00:04:34.880 --> 00:04:40.010
investigate the event that occurred, see if Suricata saw anything or vice versa.

00:04:40.010 --> 00:04:41.760
If we get an alert in Suricata,

00:04:42.040 --> 00:04:45.460
we can go look at the actual connection logs in Zeek and so on and so forth.
