WEBVTT - This file was automatically generated by VIMEO

0
00:00:04.400 --> 00:00:07.600
Hello and welcome to this lesson in this

1
00:00:07.600 --> 00:00:10.500
 lesson. We are going to understand how you can rate limit

2
00:00:10.500 --> 00:00:13.400
 your request when you are using this powerful tool like

3
00:00:13.400 --> 00:00:14.000
 nuclei.

4
00:00:14.800 --> 00:00:17.400
It could be overwhelming sometimes when you are

5
00:00:17.400 --> 00:00:20.400
 scanning a lot of host and running a lot of templates on a Target.

6
00:00:21.100 --> 00:00:24.700
Due to which the target might go unnecessarily down or

7
00:00:24.700 --> 00:00:27.200
 if there is a WAFF it might also block you.

8
00:00:28.500 --> 00:00:31.300
Due to which you would not be able to further perform any testing on

9
00:00:31.300 --> 00:00:34.200
 that Target until the cooling of period has been

10
00:00:34.200 --> 00:00:34.700
 loaded.

11
00:00:35.900 --> 00:00:39.600
Now to avoid that you can also tune nuclei

12
00:00:38.600 --> 00:00:41.100
 Aspire choice.

13
00:00:42.500 --> 00:00:45.800
As you can see over here. There are three different options

14
00:00:45.800 --> 00:00:48.600
 of flags that you can use in nuclear to tune

15
00:00:48.600 --> 00:00:51.200
 your request. The first is

16
00:00:51.200 --> 00:00:54.300
 the rate limit which controls the number of requests that

17
00:00:54.300 --> 00:00:57.100
 you want to send per second to any specific given Target.

18
00:00:58.200 --> 00:01:01.800
The second is bulk size which controls the number of parallel host

19
00:01:01.800 --> 00:01:03.700
 that you want to run simultaneously?

20
00:01:05.300 --> 00:01:08.800
For example, if you have a list of subdomains, let's say hundred

21
00:01:08.800 --> 00:01:11.300
 you control the parallel number of

22
00:01:11.300 --> 00:01:15.100
 hosts that you want to test with nuclei.

23
00:01:16.300 --> 00:01:20.200
This would avoid the target to be getting overwhelmed

24
00:01:19.200 --> 00:01:22.900
 for all the subdomains coming the request

25
00:01:22.900 --> 00:01:25.400
 from your IP address, which would avoid blocking.

26
00:01:27.400 --> 00:01:31.100
The third one is the C flag, which is the concurrent templates

27
00:01:30.100 --> 00:01:32.600
 that you want to run onto a Target.

28
00:01:34.900 --> 00:01:37.200
Is the Practical name and let's see how we can use

29
00:01:37.200 --> 00:01:39.500
 these options practically.

30
00:01:42.200 --> 00:01:45.600
So I went to the official repository of nuclei and I'm going to first quickly

31
00:01:45.600 --> 00:01:46.400
 search for rate limit.

32
00:01:48.300 --> 00:01:51.000
So you can see over here in the rate limit option we can

33
00:01:51.000 --> 00:01:51.100
 see.

34
00:01:52.400 --> 00:01:55.400
The rate limit flag says the maximum number of requests to

35
00:01:55.400 --> 00:01:57.800
 be sent per second is default 150.

36
00:01:58.400 --> 00:02:01.700
You can tune this to be more or less as

37
00:02:01.700 --> 00:02:02.000
 well.

38
00:02:03.900 --> 00:02:06.800
The next option is bulk size before doing

39
00:02:06.800 --> 00:02:09.300
 that. Let's run rate limit on our

40
00:02:09.300 --> 00:02:09.800
 Target.

41
00:02:12.500 --> 00:02:15.300
So this time I'm going to specify that. I want to run a

42
00:02:15.300 --> 00:02:18.400
 severity low. And also I want

43
00:02:18.400 --> 00:02:20.200
 to rate limit my request to

44
00:02:21.200 --> 00:02:23.200
50 only and hit enter.

45
00:02:27.400 --> 00:02:30.500
You can see over here. It has started scanning but this

46
00:02:30.500 --> 00:02:34.400
 would take more time as I have rate limited the request

47
00:02:33.400 --> 00:02:36.200
 per second that needs to be

48
00:02:36.200 --> 00:02:37.300
 sent to the Target.

49
00:02:38.400 --> 00:02:41.300
This can be useful if the target is unable

50
00:02:41.300 --> 00:02:44.600
 to handle a lot of requests that you are sending at once

51
00:02:44.600 --> 00:02:45.800
 to that specific Target.

52
00:02:49.100 --> 00:02:50.800
Let us see the next flag, which is

53
00:02:52.900 --> 00:02:53.800
bulk size

54
00:02:55.400 --> 00:02:58.700
Which is the maximum number of host that you want to analyze in

55
00:02:58.700 --> 00:02:59.100
 peril?

56
00:02:59.900 --> 00:03:02.300
Per template by default is 25

57
00:03:02.300 --> 00:03:04.300
 you can increase that count as well.

58
00:03:05.300 --> 00:03:08.000
So I'm going to specify bulk size as

59
00:03:08.900 --> 00:03:10.400
2 and hit enter

60
00:03:16.600 --> 00:03:20.300
now, let's see the third option which is the concurrency.

61
00:03:20.900 --> 00:03:23.600
Concurrency can be super useful for you if you

62
00:03:23.600 --> 00:03:25.100
 want to execute.

63
00:03:26.300 --> 00:03:30.300
A lot of templates on a Target in parallel. Definitely.

64
00:03:29.300 --> 00:03:32.700
 Yes, this can be much faster

65
00:03:32.700 --> 00:03:35.400
 for nuclei to complete

66
00:03:35.400 --> 00:03:38.700
 the scan and give you output quickly, but

67
00:03:38.700 --> 00:03:41.300
 it could also send a huge request

68
00:03:41.300 --> 00:03:44.600
 on that Target by default nucleus only

69
00:03:44.600 --> 00:03:47.900
 executes 25 templates in

70
00:03:47.900 --> 00:03:50.200
 parallel, but you can tune that as well.

71
00:03:51.500 --> 00:03:54.100
So I'm going to specify hyphen C

72
00:03:54.100 --> 00:03:57.800
 and I'm going to say execute 50 templates in parallel.

73
00:03:58.500 --> 00:04:01.300
This could be much faster and I would be getting

74
00:04:01.300 --> 00:04:03.700
 the scan completed very quickly.

75
00:04:04.700 --> 00:04:07.500
Let us specify this to 500 and

76
00:04:07.500 --> 00:04:08.300
 it entered.

77
00:04:09.600 --> 00:04:13.000
Keep in mind that this concurrency would

78
00:04:12.500 --> 00:04:16.100
 consume much more system resources.

79
00:04:15.100 --> 00:04:18.400
 So do not specify

80
00:04:18.400 --> 00:04:21.000
 very high number of concurrency for your

81
00:04:21.900 --> 00:04:24.200
scan or it would consume a

82
00:04:24.200 --> 00:04:25.700
 lot of resources in your system.

83
00:04:27.100 --> 00:04:29.100
I hope you guys understood. Thank you.
