WEBVTT

00:00:01.340 --> 00:00:02.290
Welcome back.

00:00:02.290 --> 00:00:03.940
In the previous module,

00:00:03.950 --> 00:00:08.270
we focused quite a bit on the Elastic Stack and Logstash so that

00:00:08.270 --> 00:00:11.260
we could really get a feel for some of the possibilities for

00:00:11.260 --> 00:00:13.150
using Zeek in conjunction with it.

00:00:14.040 --> 00:00:18.170
We were also able to get Zeek integrated with Arkime to help fill in the

00:00:18.170 --> 00:00:22.320
blanks and view the Zeek data right alongside Arkime.

00:00:22.320 --> 00:00:24.340
In this module,

00:00:24.340 --> 00:00:29.990
we'll continue the Logstash discussion a bit and also introduce RockNSM.

00:00:29.990 --> 00:00:33.560
What is RockNSM exactly?

00:00:33.940 --> 00:00:36.180
Well, it's a network sensor.

00:00:36.180 --> 00:00:40.160
It stands for response operation collection kit.

00:00:40.840 --> 00:00:45.330
It's a network security monitoring platform that provides us the ability to

00:00:45.330 --> 00:00:48.760
perform threat hunting and incident response operations.

00:00:49.640 --> 00:00:50.860
Does this sound familiar?

00:00:51.840 --> 00:00:56.280
Well, that's because, in this course, we've already seen something similar,

00:00:56.280 --> 00:00:57.650
Security Onion.

00:00:58.440 --> 00:01:01.170
Similarly to how Security Onion combines multiple

00:01:01.170 --> 00:01:03.390
tools into one integrated platform,

00:01:03.390 --> 00:01:07.560
RockNSM gives us the ability to use many different tools as well.

00:01:08.740 --> 00:01:13.060
Here's a list of the various tools that come with a standard RockNSM deployment.

00:01:13.740 --> 00:01:18.520
We have Zeek of course, along with some other familiar names like Elasticsearch,

00:01:18.520 --> 00:01:23.460
Logstash, Kibana, Suricata, and all of these other ones.

00:01:24.240 --> 00:01:29.060
Stenographer can also be used for full packet capture, similar to Arkime.

00:01:30.040 --> 00:01:34.230
We have Suricata as the firewall and the Elastic Stack for logging,

00:01:34.230 --> 00:01:37.860
stashing, and parsing of all the data.

00:01:37.860 --> 00:01:41.710
The question that we need to concern ourselves with for this

00:01:41.710 --> 00:01:45.220
course and module when it comes to Rock is Zeek.

00:01:45.220 --> 00:01:50.050
How does it fit into the picture? Rock deploys Zeek with

00:01:50.050 --> 00:01:54.400
somewhat of a standard configuration, which we'll see in the coming demo.

00:01:54.400 --> 00:01:57.660
Its logs are sent to the designated log directory,

00:01:57.660 --> 00:01:59.560
and we can view them in Kibana.

00:02:00.740 --> 00:02:05.670
Zeek provides the protocol analysis in metadata to the RockNSM cluster.

00:02:05.670 --> 00:02:12.160
Rock is a passive tool, so Zeek fits right into that as it's passive as well.

00:02:13.440 --> 00:02:17.760
I think this diagram says it all about how everything works within Rock.

00:02:18.440 --> 00:02:19.760
So let's talk through it a bit.

00:02:20.640 --> 00:02:23.060
The NIC is receiving the data of course.

00:02:23.640 --> 00:02:27.920
Zeek and Suricata are the main tools processing the information.

00:02:27.920 --> 00:02:30.570
And they feed the logs into Kafka,

00:02:30.640 --> 00:02:34.800
providing them message queuing and distribution into the ELK stack.

00:02:34.800 --> 00:02:39.150
And Google Stenographer is here receiving the raw packets as well,

00:02:39.640 --> 00:02:42.760
feeding them into Docket and the file scanning service.

00:02:44.240 --> 00:02:47.430
If you need additional information on RockNSM,

00:02:47.430 --> 00:02:51.290
visit the website and download it to play around with it and take

00:02:51.290 --> 00:02:54.160
a deeper look at how Zeek is implemented here,

00:02:54.160 --> 00:02:58.160
as well as how you can level up with some of the other tools that's included.

00:02:59.140 --> 00:03:03.730
Here's an example of the local.zeek script that's used in the standard

00:03:03.730 --> 00:03:07.920
Rock installation. As you can see, and we'll dive into this a little

00:03:07.920 --> 00:03:12.510
bit more in detail, Rock adds a new set of script customizations and

00:03:12.510 --> 00:03:17.280
adds the Kafka plugin. These are some of the big differences in this

00:03:17.290 --> 00:03:22.460
versus the default Zeek installation that we've seen before. One of the

00:03:22.460 --> 00:03:25.730
cool features that I like about this is that the deployment is

00:03:25.730 --> 00:03:26.560
templatized,

00:03:26.940 --> 00:03:32.380
making it relatively easy to get up and running. Ansible controls a lot of

00:03:32.380 --> 00:03:36.680
the initial configuration and the deployment and uses the templates for each

00:03:36.680 --> 00:03:39.160
tool to help with the initial configurations.

00:03:40.040 --> 00:03:40.660
All right,

00:03:41.040 --> 00:03:45.320
let's use the next clip to go into the lab and check out some of the scripts

00:03:45.320 --> 00:03:48.860
specific to Rock and how they're used within the system.
