WEBVTT

00:00:00.380 --> 00:00:02.090
Hello there, and welcome.

00:00:02.150 --> 00:00:04.270
I'm your instructor today, Owen Dubiel,

00:00:04.270 --> 00:00:07.550
and we'll be covering everything you need to know around detecting

00:00:07.550 --> 00:00:11.320
anomalies and events with Packetbeat and a live environment.

00:00:11.590 --> 00:00:12.550
Let's dig right in.

00:00:14.290 --> 00:00:14.610
Okay,

00:00:14.610 --> 00:00:17.140
so what you can expect to learn in this course is all the

00:00:17.140 --> 00:00:20.390
components needed to properly set up, configure,

00:00:20.400 --> 00:00:23.730
and implement Packetbeat within an ELK SIEM environment.

00:00:23.740 --> 00:00:24.550
Also,

00:00:24.550 --> 00:00:27.140
we will cover at a high level how Packetbeat can be tied

00:00:27.140 --> 00:00:29.380
to the NIST Cybersecurity Framework.

00:00:29.420 --> 00:00:30.120
Lastly,

00:00:30.120 --> 00:00:35.120
we'll identify some networking and security practical use cases and demonstrate

00:00:35.130 --> 00:00:38.470
how to set up and enable custom alerts within the solution.

00:00:40.420 --> 00:00:42.720
All right, so what is it anyway?

00:00:42.750 --> 00:00:47.340
Packetbeat is a real‑time network packet analyzer that is commonly used

00:00:47.340 --> 00:00:51.420
within the Elasticsearch platform or the ELK Stack to gather metrics

00:00:51.420 --> 00:00:54.170
around application performance and analytics.

00:00:54.740 --> 00:00:57.390
Packetbeat is part of the overall Beats offering,

00:00:57.400 --> 00:01:00.910
which is an open source method to ship data to Elastic.

00:01:00.910 --> 00:01:03.860
Other examples you may be familiar with within the

00:01:03.860 --> 00:01:06.950
Beats platform include Auditbeat, Filebeat,

00:01:06.960 --> 00:01:09.320
Metricbeat, and Winlogbeat.

00:01:09.320 --> 00:01:14.470
Packetbeat focuses on network protocols like HTTP and MySQL to

00:01:14.470 --> 00:01:18.170
give you an insight into how your application, hosts or even your

00:01:18.170 --> 00:01:20.240
overall network may be performing.

00:01:20.290 --> 00:01:23.270
Packetbeat captures metrics like latency,

00:01:23.280 --> 00:01:25.290
error, response times,

00:01:25.300 --> 00:01:29.570
SLA performance, as well as user access patterns and trends.

00:01:29.650 --> 00:01:34.530
Packetbeat allows users to pick from a handful of prebuilt protocols like

00:01:34.530 --> 00:01:41.150
HTTP, DNS or even Flow Logs, or if needed, you could even create your own.

00:01:41.150 --> 00:01:44.740
With Packetbeat, you don't have to worry about doing too much manual work

00:01:44.740 --> 00:01:48.990
to configure your network logs as Packetbeat does it all for you. That's

00:01:48.990 --> 00:01:49.990
what makes it special.

00:01:50.340 --> 00:01:54.290
The overall flow is as follows. Packetbeat captures

00:01:54.290 --> 00:01:59.440
the network traffic on a given host, decodes the specified network protocols,

00:01:59.730 --> 00:02:03.070
correlation is completed between requests and responses,

00:02:03.590 --> 00:02:08.590
extracts the fields required, and then bundles everything into a JSON file to

00:02:08.590 --> 00:02:14.350
send to Elastic. Once shipped to Elastic or Logstash, you can then begin

00:02:14.350 --> 00:02:19.630
working on creating visualizations of your data within Kibana by utilizing the

00:02:19.630 --> 00:02:24.670
full ELK Stack, as you will see in our demo. Packetbeat can also be paired

00:02:24.670 --> 00:02:28.730
with other Beats like Metricbeat or Winlogbeat to help enrich and improve

00:02:28.730 --> 00:02:33.210
visibility and datasets. The best part about Packetbeat is that if there's

00:02:33.210 --> 00:02:36.820
ever a system outage or a network issue that prevents the Beats from sending

00:02:36.820 --> 00:02:37.670
to your SIEM,

00:02:37.680 --> 00:02:41.430
you can temporarily write the logs to disk so that they will

00:02:41.430 --> 00:02:44.470
repopulate once the network is back online again.

00:02:45.100 --> 00:02:49.030
Now let's go ahead and dive into some of the NIST classifications and how

00:02:49.030 --> 00:02:52.690
Packetbeat can help check some of those compliance boxes.

00:02:52.710 --> 00:02:56.950
All right, so taking a quick look at the compliance security side of the house,

00:02:57.100 --> 00:03:00.200
NIST provides guidelines to help companies better align their

00:03:00.200 --> 00:03:03.860
efforts and resources to achieve a greater sense of security

00:03:03.860 --> 00:03:07.900
posture. Today, we'll be focusing solely on the detect realm

00:03:07.910 --> 00:03:10.560
within the NIST Cybersecurity Framework.

00:03:11.110 --> 00:03:12.430
So looking at Packetbeat,

00:03:12.430 --> 00:03:15.700
we can easily determine that by successfully implementing

00:03:15.700 --> 00:03:22.480
Packetbeat within your SIEM solution, you're able to check the box for DE.AE‑3,

00:03:22.700 --> 00:03:25.770
which is event data are collected and correlated

00:03:25.770 --> 00:03:27.880
from multiple sources and sensors.

00:03:28.300 --> 00:03:30.410
As we learned in the previous slides,

00:03:30.580 --> 00:03:34.850
Packetbeat's main function is to capture network traffic logs

00:03:34.860 --> 00:03:38.390
from multiple sources, and then within the SIEM environment when

00:03:38.390 --> 00:03:40.210
we create our alerts and dashboards,

00:03:40.220 --> 00:03:43.610
we are correlating these events further to paint a better picture

00:03:43.620 --> 00:03:46.320
of possible intrusions that could be occurring.

00:03:46.360 --> 00:03:49.830
Another NIST box that can be checked within this implementation of

00:03:49.830 --> 00:03:56.420
Packetbeat is DE.AE‑1, a baseline of network operations and expected

00:03:56.420 --> 00:04:00.690
dataflows for users and systems is established and managed.

00:04:01.220 --> 00:04:05.290
So over time as you collect and create alert rules for your network logs,

00:04:05.300 --> 00:04:08.740
you'll be able to better identify dataflow trends and activity

00:04:08.740 --> 00:04:12.200
spikes that are considered either normal or abnormal.

00:04:13.090 --> 00:04:13.950
For example,

00:04:13.970 --> 00:04:18.310
you may notice authentication type activity occurs mostly in the mornings,

00:04:18.470 --> 00:04:22.760
let's say around 9am, and slowly downturns throughout the day with

00:04:22.760 --> 00:04:25.620
little activity that occurs over the nighttime hours.

00:04:26.160 --> 00:04:29.720
The same thing applies with internet usage. You may notice a spike

00:04:29.720 --> 00:04:33.550
in outbound internet usage activity around lunchtime as employees

00:04:33.550 --> 00:04:37.890
surf the internet while on lunch break, which that may be considered normal,

00:04:38.390 --> 00:04:42.310
but if the same spike was to occur at 3am, it may warrant further

00:04:42.310 --> 00:04:46.150
investigation as this would be considered abnormal behavior.

00:04:46.160 --> 00:04:47.320
Okay,

00:04:47.330 --> 00:04:50.850
so now we have a solid understanding of what Packetbeat is and how it

00:04:50.860 --> 00:04:54.930
is best utilized, let's go ahead and dive into our implementation of

00:04:54.930 --> 00:04:57.760
Packetbeat in a live ELK environment.

00:04:57.770 --> 00:04:59.410
I'll see you in the next video.
