WEBVTT

00:00:00.000 --> 00:00:01.820
Hello again, and welcome back.

00:00:01.850 --> 00:00:03.430
So as a network professional,

00:00:03.430 --> 00:00:06.340
there may be times where you need to quickly get a sense of a specific

00:00:06.340 --> 00:00:09.490
type of activity that could be occurring on your network.

00:00:09.630 --> 00:00:12.870
This could be for troubleshooting network outages or simply just

00:00:12.870 --> 00:00:15.970
trying to visualize source and destination connections.

00:00:16.200 --> 00:00:20.530
Luckily ELK, along with Packetbeat, can help solidify those needs.

00:00:21.050 --> 00:00:24.780
Now even though we just have Packetbeat configured on a local Windows machine,

00:00:24.790 --> 00:00:28.120
you can actually set up Packetbeat on networking devices as a

00:00:28.120 --> 00:00:32.900
span collector to collect DNS and flow‑related activity as it

00:00:32.900 --> 00:00:35.270
progresses over a networking switch.

00:00:35.280 --> 00:00:36.120
All right,

00:00:36.130 --> 00:00:38.670
so let's dive into some quick wins that are offered

00:00:38.670 --> 00:00:40.610
within ELK for a networking professional,

00:00:40.620 --> 00:00:44.870
as well as we're going to quickly verify that Packetbeat is actually logging.

00:00:45.360 --> 00:00:47.530
So the first thing we're going to do in order to verify

00:00:47.530 --> 00:00:49.300
the raw events within the ELK solution,

00:00:49.310 --> 00:00:52.830
we're going to navigate to the Discover section in the left drop‑down,

00:00:53.350 --> 00:00:56.870
which is going to pull up our base event search.

00:00:56.880 --> 00:01:00.790
We're going to ensure that we have this top index filter just set to a

00:01:00.790 --> 00:01:03.880
wildcard so that we're seeing everything that we need to see.

00:01:03.890 --> 00:01:06.730
You may get a couple of pop‑up alerts, but that's okay,

00:01:06.740 --> 00:01:08.260
you can just exit out of those.

00:01:08.260 --> 00:01:12.870
And then all I'm doing here is searching for this Packetbeat wildcard.

00:01:12.870 --> 00:01:14.300
And once you do that,

00:01:14.300 --> 00:01:18.810
that'll just give you a quick sense of all the total count of

00:01:18.820 --> 00:01:23.080
Packetbeat‑related logs that you have flowing within your instance.

00:01:23.470 --> 00:01:26.400
Okay, now that we've verified our Packetbeat logs,

00:01:26.410 --> 00:01:31.930
let's go ahead and head on over, if you go to this left drop‑down, to the

00:01:31.940 --> 00:01:36.910
Network section under Security. Now it's time for the fun part.

00:01:36.920 --> 00:01:41.280
We really get to dive into some of these use cases that can be used on a

00:01:41.290 --> 00:01:44.920
reoccurring basis for any network or security professional.

00:01:44.930 --> 00:01:49.430
So the first thing you'll see once you load this page up is a quick

00:01:49.440 --> 00:01:52.990
overview of your networking logs if you scroll down a little bit,

00:01:53.670 --> 00:02:00.040
including all events like Flow Logs, DNS, TLS handshakes,

00:02:00.040 --> 00:02:04.340
etc. I do have it filtered on that specific Windows host,

00:02:04.340 --> 00:02:05.930
which is the Desktop 123.

00:02:05.940 --> 00:02:09.280
So as you can see here, we can see our networking events, just overall

00:02:09.280 --> 00:02:13.360
counts, DNS queries, any potential TLS handshakes,

00:02:13.370 --> 00:02:18.720
unique flow IDs, and then any source and destination connections.

00:02:19.110 --> 00:02:23.870
You'll also get an overall sense if you scroll down a little bit more

00:02:23.880 --> 00:02:28.410
around some of the flows that are occurring within your assets. This

00:02:28.410 --> 00:02:32.850
view provides us a more in‑depth look at the bytes in and out specific

00:02:32.860 --> 00:02:34.330
to these hosts and domains.

00:02:34.330 --> 00:02:39.110
So we look at these source and destinations, we can see more in depth.

00:02:39.110 --> 00:02:39.490
Okay,

00:02:39.500 --> 00:02:42.870
what's happening on the network between interactions between

00:02:42.870 --> 00:02:46.540
different sources on our side in different destinations that could be

00:02:46.540 --> 00:02:51.020
on our side or that could be external to the enterprise? There's also

00:02:51.020 --> 00:02:54.700
other countries that we just don't have geodata currently flowing in,

00:02:54.710 --> 00:02:58.460
but you can add in geodata as well that may help provide that

00:02:58.460 --> 00:02:59.600
additional context.

00:02:59.650 --> 00:03:02.040
So as a network engineer,

00:03:02.220 --> 00:03:05.260
you may be tasked with determining latency or

00:03:05.260 --> 00:03:07.370
connectivity issues between two hosts.

00:03:07.400 --> 00:03:10.870
Maybe you're currently configuring a new firewall policy that

00:03:10.870 --> 00:03:13.380
needs to ensure connection has been established.

00:03:13.390 --> 00:03:16.720
So by using these overview charts that we just looked

00:03:16.720 --> 00:03:19.000
at and narrowing down your sources,

00:03:19.010 --> 00:03:22.810
you can get a quick sense of the flows that are being sent, as well as

00:03:22.810 --> 00:03:26.470
any maybe TLS connections attempting to be established.

00:03:26.470 --> 00:03:31.430
So another use case also would be if you're attempting to restrict network

00:03:31.430 --> 00:03:36.470
activity by country, if you were to enable geolocation tracking, these

00:03:36.470 --> 00:03:41.010
dashboards would also provide some quick insight into where in the world

00:03:41.010 --> 00:03:45.210
your connections are going. If you want to get fancy with it and activate

00:03:45.210 --> 00:03:49.930
this overall graph chart, that might be a good place to start as well.

00:03:49.940 --> 00:03:55.120
Now if you want to dive even deeper, you see that this is just the flow data.

00:03:55.210 --> 00:04:00.120
Let's click on into the DNS data. Click into this tab here and

00:04:00.120 --> 00:04:04.190
scroll down a bit, and we'll see an overview right here of the top

00:04:04.190 --> 00:04:07.240
domains visited by the selected host.

00:04:07.340 --> 00:04:10.550
Now we have this filtered to just our workstation here, but

00:04:10.550 --> 00:04:12.410
you can imagine how this could be expanded.

00:04:12.630 --> 00:04:17.250
So this can be helpful in determining connectivity to specific work‑related

00:04:17.250 --> 00:04:21.910
resources and also help identify sites that are being visited that maybe should

00:04:21.910 --> 00:04:28.640
not be. Just a quick overview. People are visiting Amazon, DNS Google, OneNote.

00:04:28.640 --> 00:04:33.720
Again, now I just typed these in beforehand to trigger these, but this is a

00:04:33.720 --> 00:04:37.800
quick way to get a sense of, okay, what are the top sites being visited?

00:04:38.170 --> 00:04:42.760
Now, if we keep scrolling down here on this DNS tab,

00:04:42.770 --> 00:04:47.800
we will see even more of a verbose dashboard that contains DNS

00:04:47.800 --> 00:04:51.250
records broken down into the number of times visited, as well

00:04:51.250 --> 00:04:54.080
as that by bytes in and bytes out.

00:04:54.080 --> 00:05:00.050
That gives you even more visibility into what your users may be

00:05:00.060 --> 00:05:04.545
experiencing latency on. Now one use case that could be derived from

00:05:04.545 --> 00:05:08.415
this chart also is if a network professional was attempting to upload

00:05:08.415 --> 00:05:13.245
data to a specific domain and was having difficulty. This diagram

00:05:13.245 --> 00:05:17.275
could help verify the network issues that may lie by looking at the

00:05:17.275 --> 00:05:18.485
bytes in/bytes out.

00:05:18.705 --> 00:05:21.585
This may be determined if there's an issue on the corporate

00:05:21.585 --> 00:05:25.035
side or maybe if it's a larger issue with the internet

00:05:25.035 --> 00:05:27.445
service provider on the hosting side.

00:05:27.770 --> 00:05:31.570
So now that we have a good idea of kind of where to visualize and see

00:05:31.580 --> 00:05:35.700
our networking logging from Packetbeat, in the next video we're going

00:05:35.700 --> 00:05:39.030
to dive into the security side of the house and really pair the

00:05:39.030 --> 00:05:43.930
Packetbeat data with the current Winlog events data and Sysmon data to

00:05:43.930 --> 00:05:47.590
provide us an even more in‑depth look of what intrusions could be

00:05:47.590 --> 00:05:49.100
happening on the network.

00:05:49.110 --> 00:05:50.630
I'll see you in the next video.
