WEBVTT

00:00:00.440 --> 00:00:04.059
We start with a demonstration of the Spiderfoot web user interface.

00:00:04.059 --> 00:00:06.230
To get started quickly with Spiderfoot,

00:00:06.340 --> 00:00:10.420
we will use Kali Linux. Spiderfoot needs to be started from the command

00:00:10.420 --> 00:00:13.750
line, so we'll execute this command to get it started.

00:00:14.240 --> 00:00:17.940
We'll configure a Spiderfoot scan and then launch it. While

00:00:17.940 --> 00:00:20.000
the scan is running, we'll check its status.

00:00:20.440 --> 00:00:23.350
We will round out this demo with a quick look at the settings.

00:00:23.840 --> 00:00:30.850
So let's get started. Here we are in a default installation of Kali Linux. A

00:00:30.850 --> 00:00:35.350
version of Spiderfoot is already installed in Kali, so we'll use it. In the

00:00:35.350 --> 00:00:39.600
Kali menu, there's a group of applications for information gathering, and at

00:00:39.600 --> 00:00:41.460
the bottom of that list is Spiderfoot.

00:00:42.440 --> 00:00:45.970
Like most of the command line tools started from the Kali menu, we

00:00:45.970 --> 00:00:50.110
get a new terminal with the help documentation listed. In this case,

00:00:50.150 --> 00:00:53.790
Spiderfoot has a web‑based interface, but we have to start it using

00:00:53.790 --> 00:00:55.360
the command line by default.

00:00:57.440 --> 00:01:01.730
This command will start Spiderfoot, and its internal web server will listen,

00:01:01.810 --> 00:01:06.910
that's the ‑l, on the system's loopback address on port

00:01:06.910 --> 00:01:11.080
5001. As scans are running and we access the web UI, this

00:01:11.080 --> 00:01:13.050
terminal will have lots of log data.

00:01:13.540 --> 00:01:16.570
We don't need to see all of that right now, so let's run this in the

00:01:16.570 --> 00:01:21.430
background and minimize the terminal window. Now we will open a

00:01:21.430 --> 00:01:24.510
browser and go to the Spiderfoot web interface.

00:01:26.640 --> 00:01:34.860
The URL includes the loopback or localhost address of 127.0.0.1:5001.

00:01:36.440 --> 00:01:40.630
Here's the starting point in Spiderfoot, the Scans page. As

00:01:40.630 --> 00:01:43.980
this is our first time using Spiderfoot, there are no scans

00:01:43.980 --> 00:01:45.650
here yet, so let's start one.

00:01:46.640 --> 00:01:49.800
The New Scan page has a very simple interface to configure

00:01:49.800 --> 00:01:51.950
reconnaissance scanning based on our needs.

00:01:52.440 --> 00:01:56.060
For now, let's start with a simple email address that we have.

00:01:56.440 --> 00:01:59.300
The first input box needs a name for the scan.

00:01:59.740 --> 00:02:01.150
We'll call it First Scan.

00:02:01.640 --> 00:02:05.080
We'll talk more about seed targets later. For now, we'll use

00:02:05.080 --> 00:02:07.660
this example email address as our target.

00:02:09.139 --> 00:02:11.870
We want to just focus on getting quick results, so

00:02:11.870 --> 00:02:13.550
we'll make this a Passive scan.

00:02:15.040 --> 00:02:17.600
We start the scan with the Run Scan button, and it

00:02:17.600 --> 00:02:20.050
drops into the First Scan results page.

00:02:20.540 --> 00:02:23.450
This page will refresh with data as it's collected.

00:02:23.940 --> 00:02:26.550
Since scanning can take a while, we'll check back in a bit.

00:02:28.140 --> 00:02:32.310
Let's take a quick look at the Spiderfoot Settings. Here we find all of the

00:02:32.310 --> 00:02:36.440
configuration for Spiderfoot in its modules. Selecting items on the left

00:02:36.440 --> 00:02:39.060
side will take it to that specific configuration.

00:02:39.540 --> 00:02:42.750
We can enter the changes needed and save them with this button.

00:02:44.240 --> 00:02:46.550
Let's go back real quick and check on our first scan.

00:02:48.040 --> 00:02:54.020
It looks like it has not completed yet, so let's go back to Settings. Notice

00:02:54.020 --> 00:02:57.510
that some of the modules have names that are associated with some specific

00:02:57.520 --> 00:03:04.340
online services like AbuseIPDB or AlienVault OTX. Here we can set the

00:03:04.340 --> 00:03:06.370
configuration of that individual module,

00:03:06.380 --> 00:03:11.730
which will be applied to any scan executed after we save. In a later

00:03:11.730 --> 00:03:14.360
demonstration, we'll explore Settings a little more.

00:03:15.940 --> 00:03:17.860
Let's check again on our running scan.

00:03:18.840 --> 00:03:22.510
It's now completed. In the next demonstration,

00:03:22.510 --> 00:03:24.310
we'll take a look at those results.
