WEBVTT - This file was automatically generated by VIMEO

0
00:00:03.600 --> 00:00:06.600
Hello everyone and welcome to this lesson.

1
00:00:06.600 --> 00:00:10.800
 So in this lesson, we are going to learn about nuclei scan

2
00:00:10.800 --> 00:00:11.500
 metrics.

3
00:00:12.400 --> 00:00:14.500
So what exactly scan metrics?

4
00:00:15.500 --> 00:00:18.200
This can be super useful for you. If you want to

5
00:00:18.200 --> 00:00:21.500
 store and track the details of the scan

6
00:00:21.500 --> 00:00:24.500
 that you're performing on any specific targets.

7
00:00:25.700 --> 00:00:29.300
Now how to activate this specific flag you

8
00:00:28.300 --> 00:00:31.700
 can simply specify hyphen metrics and

9
00:00:31.700 --> 00:00:34.700
 nuclei would now start saving the

10
00:00:34.700 --> 00:00:37.200
 details of the scan that is currently ongoing.

11
00:00:38.500 --> 00:00:41.500
and the really awesome thing is that you can also track

12
00:00:41.500 --> 00:00:44.800
 those metrics directly from your browser by going

13
00:00:44.800 --> 00:00:47.600
 to localhost and a port number which is 9

14
00:00:47.600 --> 00:00:48.600
 0 9 2

15
00:00:49.700 --> 00:00:52.300
So it is the Practical time and let's try to see

16
00:00:52.300 --> 00:00:56.300
 how you can activate this specific flag and

17
00:00:55.300 --> 00:00:58.500
 see the Matrix in real time.

18
00:01:01.500 --> 00:01:04.800
So I'm going to start a scan quickly on a Target URL

19
00:01:04.800 --> 00:01:05.400
 which is

20
00:01:06.800 --> 00:01:07.800
test PHP.

21
00:01:13.200 --> 00:01:15.400
Let's specify our template.

22
00:01:19.200 --> 00:01:22.300
Let's say we run all the technology space templates over

23
00:01:22.300 --> 00:01:22.500
 here.

24
00:01:25.900 --> 00:01:29.000
And you can see in total 312 templates

25
00:01:28.100 --> 00:01:29.600
 have been loaded.

26
00:01:30.400 --> 00:01:31.800
Let's quickly go to localhost.

27
00:01:33.400 --> 00:01:36.600
9092 / Matrix and

28
00:01:36.600 --> 00:01:37.400
 hit enter

29
00:01:38.400 --> 00:01:41.600
and you can see the time duration the errors that we have currently

30
00:01:41.600 --> 00:01:44.400
 in running our scan the number

31
00:01:44.400 --> 00:01:47.400
 of host that we are currently running this scan on which is

32
00:01:47.400 --> 00:01:50.600
 one host which is test php.1 web.com.

33
00:01:51.500 --> 00:01:52.700
matched percentage

34
00:01:54.200 --> 00:01:57.100
In total scan percentage how many requests have been

35
00:01:57.100 --> 00:02:00.000
 sent started at templates that have been

36
00:02:00.500 --> 00:02:03.400
 loaded total templates Etc. So you can

37
00:02:03.400 --> 00:02:06.900
 see in real time. This keeps on updating the number

38
00:02:06.900 --> 00:02:09.500
 of match request total request

39
00:02:09.500 --> 00:02:12.600
 sent and so on and this can be super useful

40
00:02:12.600 --> 00:02:15.700
 for us if you want to track these metrics,

41
00:02:15.700 --> 00:02:18.500
 maybe save it into a file for a

42
00:02:18.500 --> 00:02:20.900
 later period of time as well in real time.

43
00:02:22.300 --> 00:02:25.600
Let me just stop this when you stop this the server

44
00:02:25.600 --> 00:02:28.300
 would also stop and you would no longer be able

45
00:02:28.300 --> 00:02:31.300
 to track the metrics for a current scan that

46
00:02:31.300 --> 00:02:32.200
 has been ongoing.

47
00:02:33.300 --> 00:02:36.300
Let us try to run this once again, and let's try to load this

48
00:02:36.300 --> 00:02:36.800
 once more.

49
00:02:37.800 --> 00:02:40.700
You can see one host again matched six.

50
00:02:41.400 --> 00:02:44.600
A Time duration, which is currently happening and exactly

51
00:02:44.600 --> 00:02:47.800
 the percentage in the request that has been sent from our

52
00:02:47.800 --> 00:02:48.700
 system continuously.

53
00:02:49.400 --> 00:02:52.900
So I hope you guys understood this how you can use effectively

54
00:02:52.900 --> 00:02:55.900
 the metrics flag using nuclei.

55
00:02:55.900 --> 00:02:56.500
 Thank you.
