WEBVTT

00:00:01.340 --> 00:00:05.360
And with that, we also need to validate the same for Hunt.

00:00:05.940 --> 00:00:09.630
Let's hop into the lab again and demonstrate that we can see and use

00:00:09.630 --> 00:00:13.550
the information using Security Onion's own Hunt.

00:00:13.550 --> 00:00:17.860
And here I am back at the Security Onion dashboard.

00:00:18.940 --> 00:00:21.660
Now, as I alluded to earlier in this module,

00:00:21.670 --> 00:00:25.100
Hunt is something that we can use for threat hunting and

00:00:25.100 --> 00:00:27.500
managing alerts and events and stuff like that,

00:00:27.510 --> 00:00:30.430
sending them over to TheHive for case management.

00:00:30.440 --> 00:00:34.960
So it can be considered your SOC operations tool or one of your good SOC

00:00:34.960 --> 00:00:37.300
operations tools when you're working with Security Onion.

00:00:37.300 --> 00:00:40.480
What's cool about it is that helps reduce the noise when

00:00:40.480 --> 00:00:44.240
we're trying to identify indicators of compromise and hunt

00:00:44.240 --> 00:00:46.160
for specific issues in the network.

00:00:47.740 --> 00:00:51.030
And so let's hop over there and open up that dashboard.

00:00:51.030 --> 00:00:54.600
And as you can see, it brings up some more visualizations.

00:00:54.600 --> 00:00:57.110
We have the timeline of events.

00:00:57.110 --> 00:01:01.060
We have some graphs with the occurrences that are here and everything like that.

00:01:01.840 --> 00:01:05.200
Now let's go ahead and filter some of this data though instead of just

00:01:05.200 --> 00:01:07.870
looking at the general alerts and everything like that.

00:01:07.870 --> 00:01:09.860
As you can see, we have a lot of the same ones.

00:01:09.860 --> 00:01:11.710
This is out of the box and not tuned,

00:01:11.710 --> 00:01:14.540
so that's why a lot of this stuff is showing up.

00:01:14.540 --> 00:01:18.650
But we can click on this drop‑down and go and try to

00:01:18.650 --> 00:01:22.060
look just for the Zeek dataset, for example.

00:01:22.060 --> 00:01:25.870
And it's looking for the last 24 hours.

00:01:25.880 --> 00:01:27.250
This doesn't appear to have anything,

00:01:27.250 --> 00:01:29.640
so let's go ahead and look for something else.

00:01:29.640 --> 00:01:32.130
Let's look for instead of the general Zeek dataset,

00:01:32.130 --> 00:01:36.120
let's look for the weird logs right here.

00:01:36.120 --> 00:01:37.390
And there we go.

00:01:37.390 --> 00:01:39.400
We have some good information here.

00:01:39.400 --> 00:01:43.060
And then we also have some metrics and alerts.

00:01:43.070 --> 00:01:44.570
We have our events here as well.

00:01:44.570 --> 00:01:49.300
So we have possible split routing, we have unknown RPC authentication types,

00:01:49.300 --> 00:01:50.240
so on and so forth.

00:01:50.240 --> 00:01:51.760
And then if we look at these,

00:01:52.240 --> 00:01:55.390
we see a lot of the information from the logs themselves.

00:01:55.390 --> 00:01:57.000
So this is from that weird log.

00:01:57.000 --> 00:01:59.850
What I really like about Zeek is we can go ahead and

00:01:59.850 --> 00:02:01.860
show that PCAP for that event as well.

00:02:01.870 --> 00:02:07.550
So we have automated pivoting from the logs and alerts themselves to going

00:02:07.550 --> 00:02:11.910
to pull up the PCAPs for these events that are occurring.

00:02:11.920 --> 00:02:15.850
So that's a cool capability that Security Onion provides where Zeek can

00:02:15.860 --> 00:02:19.460
directly pivot from the Zeek logs into the PCAPs for these.

00:02:20.340 --> 00:02:20.820
And then,

00:02:20.820 --> 00:02:24.030
the last thing that I want to show you before we move on to the next

00:02:24.030 --> 00:02:29.470
module is that we can just easily add or escalate these events to

00:02:29.480 --> 00:02:33.200
TheHive so we can assign the cases to individuals.

00:02:33.200 --> 00:02:37.280
So just by the click of that button, that's the escalate button,

00:02:37.280 --> 00:02:39.440
so we can do that straight from the Hunt dashboard.

00:02:39.440 --> 00:02:42.190
And like I said, we are looking at Zeek's logs here.

00:02:42.200 --> 00:02:43.220
So we can just do that,

00:02:43.220 --> 00:02:46.960
and we'll be able to send this off to the different personnel to investigate.

00:02:47.740 --> 00:02:49.200
So this is a really cool tool,

00:02:49.200 --> 00:02:52.660
and it gives us some decent visualizations as well.

00:02:53.640 --> 00:02:56.030
Now if we jump over to the case manager of TheHive

00:02:56.040 --> 00:02:57.640
and log in with our credentials,

00:02:57.650 --> 00:03:00.950
we have that one case escalation that we have here that

00:03:00.950 --> 00:03:03.190
we can go in and we can view the logs,

00:03:03.200 --> 00:03:06.890
investigate it, and add additional information to here, add

00:03:06.890 --> 00:03:10.190
some additional observables if we wanted to or if we found

00:03:10.190 --> 00:03:11.960
anything relating to this as well.

00:03:12.140 --> 00:03:16.460
So, we essentially just pivoted from seeing the Zeek logs in

00:03:16.460 --> 00:03:20.620
Kibana to seeing the alerts from Zeek in Hunt,

00:03:20.630 --> 00:03:24.130
sending them to a case manager and/or downloading the

00:03:24.130 --> 00:03:26.850
PCAPs or viewing the PCAPs for them.
