WEBVTT - This file was automatically generated by VIMEO

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

1
00:00:07.300 --> 00:00:10.700
So now we are going to learn about nuclei config

2
00:00:10.700 --> 00:00:12.000
 or configuration.

3
00:00:13.100 --> 00:00:16.200
So what exactly is nucleic config? This can be

4
00:00:16.200 --> 00:00:19.800
 super useful for you? If you want to set some

5
00:00:19.800 --> 00:00:22.400
 configuration that should run by default when

6
00:00:22.400 --> 00:00:24.200
 you start using nuclei.

7
00:00:24.900 --> 00:00:27.500
What does that mean? If you would to

8
00:00:27.500 --> 00:00:30.400
 save specific options, that could

9
00:00:30.400 --> 00:00:33.400
 be a Target that could be at template if you

10
00:00:33.400 --> 00:00:36.500
 want to exclude severity a specific templates need

11
00:00:36.500 --> 00:00:39.400
 to be done Etc. You can set that into

12
00:00:39.400 --> 00:00:42.200
 a configuration file and nuclei will always

13
00:00:42.200 --> 00:00:46.400
 read that file to execute itself. Isn't

14
00:00:45.400 --> 00:00:47.800
 that awesome? Yes.

15
00:00:48.700 --> 00:00:51.500
The default path of the nuclear configuration file

16
00:00:51.500 --> 00:00:54.700
 is inside your home directory inside a

17
00:00:54.700 --> 00:00:57.800
 DOT config hidden directory nuclei called

18
00:00:57.800 --> 00:00:59.400
 as config Dot. Yml.

19
00:01:00.700 --> 00:01:03.500
Let us see this quickly in the Practical time.

20
00:01:06.700 --> 00:01:09.500
So I'm on to my terminal right now, and I'm going

21
00:01:09.500 --> 00:01:11.900
 to open my configuration file now.

22
00:01:12.700 --> 00:01:14.600
So I'm going to say Nano.

23
00:01:15.500 --> 00:01:18.500
The users in my system. The current user

24
00:01:18.500 --> 00:01:22.700
 is Rohit. I'm going to go inside the config hidden

25
00:01:21.700 --> 00:01:22.900
 folder.

26
00:01:23.500 --> 00:01:26.300
For nuclei and I'm going to edit this

27
00:01:26.300 --> 00:01:29.500
 file, which is config Dot yaml.

28
00:01:30.500 --> 00:01:34.000
For your system, you might need to change the username

29
00:01:33.400 --> 00:01:36.800
 that could be specific for your system.

30
00:01:38.100 --> 00:01:41.900
Now when I hit enter you can see this is the nuclear configuration

31
00:01:41.900 --> 00:01:44.400
 file. You can specify the target you

32
00:01:44.400 --> 00:01:46.200
 can specify the list.

33
00:01:47.400 --> 00:01:51.000
New templates automatic scan template URLs templates

34
00:01:50.900 --> 00:01:53.400
 workflows Etc. And that's really awesome.

35
00:01:54.500 --> 00:01:57.600
So let's try to play with this the target URLs or

36
00:01:57.600 --> 00:02:00.800
 host to scan you can see currently this

37
00:02:00.800 --> 00:02:03.400
 field is been commented with a hash.

38
00:02:04.200 --> 00:02:05.100
You have to remove that.

39
00:02:06.200 --> 00:02:08.600
And I'm going to specify a Target here right now.

40
00:02:09.800 --> 00:02:12.800
Let's say for instance. I'm going to use this target to

41
00:02:12.800 --> 00:02:14.700
 show the request that we are going to send.

42
00:02:16.400 --> 00:02:17.600
I'm going to add this target over here.

43
00:02:18.700 --> 00:02:20.600
And let's save this file.

44
00:02:21.500 --> 00:02:24.700
Now I do not need to specify

45
00:02:24.700 --> 00:02:27.200
 any specific Target. I'm just

46
00:02:27.200 --> 00:02:29.100
 going to send a request right now.

47
00:02:30.300 --> 00:02:33.600
Let us just simplify a template for ease because we

48
00:02:33.600 --> 00:02:36.500
 do not want to send a lot of requests to this specific Target.

49
00:02:37.200 --> 00:02:41.700
Let's say Technologies nginx and nginx version

50
00:02:40.700 --> 00:02:43.200
 detect.yeml.

51
00:02:44.100 --> 00:02:47.400
Let's hit enter. Let's go to the

52
00:02:47.400 --> 00:02:49.800
 Target and see what happened over here.

53
00:02:50.700 --> 00:02:53.600
And you can see indeed there was a request which

54
00:02:53.600 --> 00:02:56.900
 came over here request was for nginx detection

55
00:02:56.900 --> 00:02:58.100
 that has come over here.

56
00:03:00.100 --> 00:03:03.500
Let's try to send more requests from the Technologies folder or

57
00:03:03.500 --> 00:03:06.100
 the technology Spath and let's hit enter.

58
00:03:07.900 --> 00:03:10.400
You can see 312 templates have

59
00:03:10.400 --> 00:03:12.800
 been loaded successfully. There is a

60
00:03:13.700 --> 00:03:16.800
issue that has been found under the technology detection.

61
00:03:16.800 --> 00:03:20.100
 Let's go here and see what exactly is happening and

62
00:03:19.100 --> 00:03:22.100
 you can see a lot of request has been

63
00:03:22.100 --> 00:03:25.300
 coming over here as we can. See this is because

64
00:03:25.300 --> 00:03:28.600
 of the templates that have been running on this specific Target, which

65
00:03:28.600 --> 00:03:31.200
 can be seen from here as well. And this will keep

66
00:03:31.200 --> 00:03:34.300
 keep on increasing. Let me just reload this and we

67
00:03:34.300 --> 00:03:37.900
 would see more request coming over here in just a

68
00:03:37.900 --> 00:03:41.000
 matter of time which you can see over here this confirms

69
00:03:40.100 --> 00:03:43.900
 that nuclear is currently running and scanning those

70
00:03:43.900 --> 00:03:46.900
 templates on the given Target. So I

71
00:03:46.900 --> 00:03:49.100
 hope you guys understood I'm going to

72
00:03:49.100 --> 00:03:52.300
 stop this right now and we are going to go back to

73
00:03:52.300 --> 00:03:52.700
 over.

74
00:03:53.800 --> 00:03:56.700
Configuration file to see the specific

75
00:03:56.700 --> 00:03:59.500
 Target that we hard coded

76
00:03:59.500 --> 00:04:01.300
 in our configuration file to run.

77
00:04:01.800 --> 00:04:04.000
You can also add a list of

78
00:04:04.700 --> 00:04:08.400
 templates that needs to be done. For example, our PHP

79
00:04:07.400 --> 00:04:10.700
 detect.yml template the path

80
00:04:10.700 --> 00:04:13.400
 can be specified here, which means every time

81
00:04:13.400 --> 00:04:16.200
 this template would run when you

82
00:04:16.200 --> 00:04:19.800
 start nuclei by default on any Target. Let's

83
00:04:19.800 --> 00:04:22.100
 say you have identified a new issue.

84
00:04:23.200 --> 00:04:26.300
You can quickly create a template for that issue Supply a

85
00:04:26.300 --> 00:04:29.600
 bunch of host that contains your domain name subdomain names

86
00:04:29.600 --> 00:04:32.900
 that would be tested automatically against this

87
00:04:32.900 --> 00:04:35.900
 template. Keep in mind you can supply as

88
00:04:35.900 --> 00:04:38.700
 many as list of templates that you want with the

89
00:04:38.700 --> 00:04:40.500
 help of comma as well.

90
00:04:41.500 --> 00:04:44.900
I hope you guys understood how effective the nuclei

91
00:04:44.900 --> 00:04:47.200
 configuration can be and you should definitely

92
00:04:47.200 --> 00:04:51.100
 use it and Implement into your methodology. Thank

93
00:04:50.100 --> 00:04:51.100
 you.
