WEBVTT 00:00:00.440 --> 00:00:05.440 Spiderfoot is very configurable. In this demonstration, we'll take a look at the 00:00:05.440 --> 00:00:08.460 various Spiderfoot settings available in the web interface. 00:00:08.940 --> 00:00:11.140 Some of the settings are global and apply across 00:00:11.140 --> 00:00:14.090 Spiderfoot in its modules. There is also an important 00:00:14.090 --> 00:00:16.149 configurable storage option to consider. 00:00:16.640 --> 00:00:19.660 We'll look at how modules are configured, and how to enter API 00:00:19.660 --> 00:00:21.760 key information for some of those modules. 00:00:22.690 --> 00:00:26.350 These may not seem too interesting or important; however, 00:00:26.400 --> 00:00:28.610 as we continue to work with Spiderfoot, 00:00:28.650 --> 00:00:32.680 we can enhance our data collection process by enriching are collected data 00:00:32.680 --> 00:00:39.210 from other information sources accessible through those APIs. We start here 00:00:39.210 --> 00:00:44.190 on the main page in the Spiderfoot web interface. Let's move over to the 00:00:44.190 --> 00:00:47.840 Settings tab. On the left side of the page, 00:00:47.850 --> 00:00:50.830 there are various modules listed. At the top of the 00:00:50.830 --> 00:00:52.860 list, there are Global Settings. 00:00:53.740 --> 00:00:57.750 Most of these settings affect how Spiderfoot itself operates or connects to 00:00:57.750 --> 00:01:02.660 the Internet. In Storage, there's a single setting for storing information 00:01:02.660 --> 00:01:07.180 retrieved. In order to save space, the default setting limits the amount of 00:01:07.180 --> 00:01:09.760 data stored in the database to 1 MB. 00:01:10.140 --> 00:01:13.510 We can override that value or set it to 0 to store 00:01:13.520 --> 00:01:17.070 everything. Unlimited storage will definitely affect our 00:01:17.070 --> 00:01:19.860 database size and probably its performance. 00:01:20.840 --> 00:01:25.920 The first module here is abuse.ch, which is a malware and botnet tracking 00:01:25.920 --> 00:01:30.770 service. Abuse.ch has several threat tracking services available through 00:01:30.770 --> 00:01:32.960 Spiderfoot, which can be configured here. 00:01:33.940 --> 00:01:37.150 The modules with a lock icon are modules that take either 00:01:37.150 --> 00:01:39.660 API keys or some other credentials. 00:01:40.640 --> 00:01:47.130 The AbuseIPDB module takes an API key in this field. Modules with the right 00:01:47.140 --> 00:01:51.110 API keys or credentials will allow Spiderfoot to gather information that may 00:01:51.110 --> 00:01:53.660 be limited to registered users of that service. 00:01:54.040 --> 00:01:56.350 Some of these services have free accounts though. 00:01:57.240 --> 00:02:02.350 Let's enter an API key and save it. Now the AbuseIPDB 00:02:02.350 --> 00:02:04.260 service can be used in future scans. 00:02:05.240 --> 00:02:08.250 If we entered our API key information into Spiderfoot, 00:02:08.400 --> 00:02:12.280 we can export those keys and credentials from this Spiderfoot instance to a 00:02:12.280 --> 00:02:18.470 text file, and then import them into another Spiderfoot instance. That saves us 00:02:18.470 --> 00:02:21.060 a lot of time moving to another Spiderfoot system. 00:02:21.440 --> 00:02:24.690 We can also edit that file, add in new API keys, 00:02:24.700 --> 00:02:27.460 replace existing ones, and import them as needed. 00:02:28.440 --> 00:02:31.650 Here's something to consider about APIs. You won't need to go out and 00:02:31.650 --> 00:02:34.290 sign up for every service that Spiderfoot supports. 00:02:34.740 --> 00:02:38.250 You should consider your information needs and selectively get accounts on 00:02:38.260 --> 00:02:41.160 those information sources that provide the details needed. 00:02:42.140 --> 00:02:46.550 Finally, if we run into issues that could be caused by configuration problems, 00:02:46.560 --> 00:02:50.050 we can reset everything back to the original Spiderfoot configuration 00:02:50.060 --> 00:02:54.310 with the Reset to Factory Defaults button. Note that the message 00:02:54.310 --> 00:02:56.910 indicates that this will affect any future scans. 00:02:57.340 --> 00:03:01.040 Any scan already running will continue to run with those settings that 00:03:01.040 --> 00:03:05.190 were in place when the scan started. In the next demo, 00:03:05.200 --> 00:03:08.060 we'll focus on controlling Spiderfoot from the command line.