WEBVTT 00:00:00.210 --> 00:00:03.350 In this course, we've only scratched the surface of what Recon‑ng can do. 00:00:03.920 --> 00:00:07.180 There are currently over 100 modules in the Recon‑ng marketplace, 00:00:07.920 --> 00:00:10.390 each providing access to new information and opening 00:00:10.390 --> 00:00:12.050 new doors to a potential foothold. 00:00:12.900 --> 00:00:15.640 There's also the ability to script Recon‑ng sessions, 00:00:16.140 --> 00:00:19.680 either within the framework or via an external command line interface. 00:00:20.000 --> 00:00:23.760 This allows for further automation and virtual hands‑off information gathering. 00:00:24.370 --> 00:00:25.660 Talk about a time saver. 00:00:26.840 --> 00:00:29.080 There's a full‑featured, RESTful web API for building 00:00:29.080 --> 00:00:31.210 third‑party integrations for web interfaces. 00:00:31.480 --> 00:00:35.480 There's currently no official GUI for Recon‑ng, but this API provides the 00:00:35.480 --> 00:00:38.330 back‑end capability for that feature to be developed. 00:00:38.620 --> 00:00:40.960 The list simply goes on and on. 00:00:41.840 --> 00:00:44.630 So some parting thoughts as you began to explore information gathering 00:00:44.630 --> 00:00:49.080 with Recon‑ng. Recon‑ng has been featured in many books, 00:00:49.080 --> 00:00:50.050 videos, classes, 00:00:50.050 --> 00:00:53.710 etc., but beware of old content. Recon‑ng has 00:00:53.710 --> 00:00:55.710 changed substantially over the years, 00:00:55.820 --> 00:00:59.110 and much of the content that exists uses old modules, 00:00:59.120 --> 00:01:02.210 old command structures, and old workflows that are no 00:01:02.210 --> 00:01:04.790 longer valid as of Recon‑ng version 5. 00:01:05.040 --> 00:01:08.610 These resources cause more confusion than anything else, so please 00:01:08.740 --> 00:01:11.860 focus on resources that use version 5 or greater. 00:01:12.840 --> 00:01:15.280 Also understand that module statuses change as 00:01:15.280 --> 00:01:17.400 frequently as the resources they leverage. 00:01:17.780 --> 00:01:20.490 A module that worked last week may not work this week, 00:01:20.870 --> 00:01:22.610 not because Recon‑ng is broken, 00:01:22.780 --> 00:01:24.930 but because the third‑party resource changed their 00:01:24.930 --> 00:01:27.000 interface in a way that broke the module. 00:01:27.160 --> 00:01:32.420 Be patient and engage the Recon‑ng team via the issue tracker or Slack in 00:01:32.420 --> 00:01:34.850 accordance with the troubleshooting guidance on the wiki. 00:01:36.540 --> 00:01:39.830 And this leads me to my last thought, developing modules in Recon‑ng 00:01:39.830 --> 00:01:42.750 has been made incredibly simple by the framework. 00:01:43.240 --> 00:01:44.980 In just 15 to 20 lines of code, 00:01:44.990 --> 00:01:47.850 you can have a fully functional module that integrates within 00:01:47.850 --> 00:01:51.100 the framework and transforms data into something useful. 00:01:51.820 --> 00:01:53.600 Recon‑ng is developed in Python, 00:01:53.750 --> 00:01:56.090 which is a popular and easy‑to‑learn language, so if you're 00:01:56.090 --> 00:01:57.910 looking for a reason to learn programming, 00:01:58.020 --> 00:02:00.610 module development may be the perfect opportunity. 00:02:01.160 --> 00:02:02.080 If nothing else, 00:02:02.270 --> 00:02:05.610 Recon‑ng relies on the community, not only for the development of 00:02:05.610 --> 00:02:08.639 new modules, but also for fixing broken ones. 00:02:08.840 --> 00:02:12.030 Your assistance would be much appreciated and the wiki contains 00:02:12.030 --> 00:02:14.950 information related specifically to module development. 00:02:16.600 --> 00:02:20.030 So hopefully what you've seen here and the features mentioned above motivate 00:02:20.030 --> 00:02:22.950 you to dig in and learn more about this powerful tool. 00:02:23.060 --> 00:02:24.070 But at a minimum, 00:02:24.170 --> 00:02:27.100 I hope you've gained enough of an understanding that you can begin 00:02:27.100 --> 00:02:30.610 putting this capability to work for you immediately, making Recon‑ng 00:02:30.610 --> 00:02:33.890 yet one more tool in your red team tool belt. 00:02:34.750 --> 00:02:38.580 Thank you for watching Pluralsight, and I hope you join me and other authors 00:02:38.580 --> 00:02:41.590 to add to your arsenal of red team tools in the future.