WEBVTT

00:00:01.440 --> 00:00:04.560
I am so glad that we were able to see the Intelligence

00:00:04.560 --> 00:00:06.450
Framework in action in this module.

00:00:06.840 --> 00:00:10.850
We were able to configure Zeek to flag on some basic intelligence information,

00:00:11.060 --> 00:00:14.530
as well as configure the JA3 package to give us our

00:00:14.530 --> 00:00:17.050
hashes on our secure communications.

00:00:17.050 --> 00:00:21.150
We can then feed that into the Intelligence Framework to match on

00:00:21.540 --> 00:00:24.800
similarly to how we did with the defendthenet URL.

00:00:24.800 --> 00:00:28.360
This course covered quite a bit of content,

00:00:28.370 --> 00:00:32.590
so let's take a few minutes to review what we've learned and see some additional

00:00:32.590 --> 00:00:36.050
resources that we can use to help solidify this knowledge.

00:00:37.040 --> 00:00:41.350
We started out the course by looking at the extensions and a few of the

00:00:41.350 --> 00:00:44.560
frameworks that we use to expand the Zeek ecosystem.

00:00:45.440 --> 00:00:48.460
We learned about the input framework and how we can ingest data

00:00:48.460 --> 00:00:52.260
differently and took a look at how to use Zeek packages here.

00:00:52.840 --> 00:00:57.060
Remember, there are a lot of use cases that have these packages prebuilt for,

00:00:57.440 --> 00:01:00.860
so check out the Zeek repository if needed for ideas.

00:01:02.140 --> 00:01:04.580
We then moved into using Security Onion,

00:01:04.580 --> 00:01:09.280
and we had a great module about how Zeek is used within it and what we

00:01:09.280 --> 00:01:12.360
can use in order to view and consume the Zeek logs.

00:01:13.440 --> 00:01:17.650
This is one of the more popular security operations platforms out there.

00:01:17.650 --> 00:01:18.800
After that,

00:01:18.800 --> 00:01:23.150
we detailed another use case of ingesting the logs natively into the ELK

00:01:23.150 --> 00:01:26.350
stack and then using that information with Arkime.

00:01:27.440 --> 00:01:31.230
We used another security platform known as Malcolm in order for us to

00:01:31.230 --> 00:01:33.820
see how the Zeek fields are mapped to Arkime's,

00:01:33.820 --> 00:01:37.940
how to enrich the data with additional information such as GeoIP

00:01:37.940 --> 00:01:43.130
and MAC OUI information, and how to view and pivot to and from the

00:01:43.130 --> 00:01:45.760
Zeek logs within Arkime's dashboards.

00:01:46.440 --> 00:01:50.960
We detailed the configurations for RockNSM and how it uses Zeek as well,

00:01:51.540 --> 00:01:54.800
emphasizing the ECS standard for the logs being passed

00:01:54.800 --> 00:01:56.850
over to Logstash and the ELK stack.

00:01:57.840 --> 00:02:02.510
We also took a look at how Zeek is able to see and extract entire

00:02:02.510 --> 00:02:06.050
files from the network stream in order to either save,

00:02:06.050 --> 00:02:08.560
quarantine, or send them off for analysis.

00:02:09.340 --> 00:02:12.790
After that, we covered more information about the Zeek

00:02:12.800 --> 00:02:17.240
Intelligence Framework and included SSL/TLS fingerprinting

00:02:17.250 --> 00:02:19.560
using JA3 into the conversation.

00:02:20.340 --> 00:02:24.060
Now that we have that review done, let's close out this course.

00:02:25.040 --> 00:02:28.060
Zeek is such a great tool that we can use to help identify

00:02:28.060 --> 00:02:31.440
potentially malicious activity on the network and gives us

00:02:31.450 --> 00:02:34.060
information to investigate it properly.

00:02:35.040 --> 00:02:38.270
Here's some additional resources that you can use in order to

00:02:38.270 --> 00:02:42.050
help facilitate your own implementations of Zeek and integrating

00:02:42.050 --> 00:02:43.950
it with other tools and products.

00:02:44.840 --> 00:02:46.960
Now this is not an all‑inclusive list,

00:02:47.440 --> 00:02:50.940
but it should help you get moving in the right direction when it comes to

00:02:50.950 --> 00:02:55.540
Zeek integrations and platforms that have it built in especially. As

00:02:55.540 --> 00:02:58.410
always, if you have any questions or need clarity,

00:02:58.620 --> 00:03:03.390
feel free to reach out. Course ratings and constructive feedback

00:03:03.390 --> 00:03:06.350
are always welcomed and very much appreciated.

00:03:07.040 --> 00:03:11.060
I take all of the feedback that I receive and actively try

00:03:11.060 --> 00:03:12.850
to use it to make my content better.

00:03:13.740 --> 00:03:14.510
So please,

00:03:14.520 --> 00:03:18.270
if you have time, give my courses that you've seen a rating, and let

00:03:18.270 --> 00:03:22.420
me know what you think. On top of this, you can also subscribe to me

00:03:22.420 --> 00:03:26.290
as an author here at Pluralsight so you can be notified whenever my

00:03:26.290 --> 00:03:27.650
future courses are released.

00:03:28.540 --> 00:03:33.940
There are and will be many cybersecurity and cyber operations courses here, at

00:03:33.940 --> 00:03:37.060
Pluralsight, so be sure to check out the other ones as well.

00:03:37.740 --> 00:03:40.950
I have a lot of courses on Splunk and machine data in general

00:03:41.840 --> 00:03:45.100
as do other great authors here, so you can dig down into

00:03:45.100 --> 00:03:50.820
learning about the data itself. Now, it's time to close out the course.

00:03:51.340 --> 00:03:54.530
I really appreciate you sticking with me throughout the entire

00:03:54.530 --> 00:03:56.950
course, and I hope that you've learned something new.

00:03:58.040 --> 00:04:01.440
The hope is that you've increased your Zeek knowledge and have leveled

00:04:01.440 --> 00:04:06.310
up your skills. Remember, we are community of professionals, and

00:04:06.310 --> 00:04:08.550
sharing knowledge is the key to our success.

00:04:09.040 --> 00:04:11.760
It helps build up a stronger InfoSec community.

00:04:12.440 --> 00:04:15.460
Thanks for viewing this course, and I will see you in the next one.
