WEBVTT - This file was automatically generated by VIMEO

0
00:00:06.700 --> 00:00:09.600
We are approaching till the end of this course.

1
00:00:09.600 --> 00:00:12.500
 So let me summarize what you have learned in

2
00:00:12.500 --> 00:00:13.300
 this course.

3
00:00:14.400 --> 00:00:17.700
Sensitive data from web applications can be

4
00:00:17.700 --> 00:00:20.800
 indexed by Google and then it

5
00:00:20.800 --> 00:00:23.900
 becomes publicly exposed to everyone on

6
00:00:23.900 --> 00:00:24.300
 the internet.

7
00:00:25.400 --> 00:00:28.700
In this course, you learned about different types

8
00:00:28.700 --> 00:00:31.700
 of sensitive data that can be indexed

9
00:00:31.700 --> 00:00:32.300
 by Google.

10
00:00:33.400 --> 00:00:37.300
What's more you'll learned about the technique known

11
00:00:36.300 --> 00:00:40.400
 as Google hacking Google hacking

12
00:00:39.400 --> 00:00:42.800
 is used by ethical hackers

13
00:00:42.800 --> 00:00:45.800
 and professional penetration testers for

14
00:00:45.800 --> 00:00:48.800
 finding security weaknesses in web

15
00:00:48.800 --> 00:00:49.400
 applications.

16
00:00:50.400 --> 00:00:53.500
If you know the special syntax of Google search

17
00:00:53.500 --> 00:00:56.400
 engine queries, then Google can help

18
00:00:56.400 --> 00:00:59.900
 you identify many security weaknesses in

19
00:00:59.900 --> 00:01:02.600
 web applications. And this is exactly what

20
00:01:02.600 --> 00:01:04.500
 I presented in this course.

21
00:01:05.800 --> 00:01:08.500
First I demonstrated how you

22
00:01:08.500 --> 00:01:12.100
 can use Google hacking to find the directory listings

23
00:01:11.100 --> 00:01:14.200
 and SQL syntax errors.

24
00:01:15.100 --> 00:01:18.800
After that, I presented how you can find publicly

25
00:01:18.800 --> 00:01:21.900
 exposed the backup files and internal

26
00:01:21.900 --> 00:01:24.100
 server errors by means of

27
00:01:24.100 --> 00:01:25.000
 Google hacking.

28
00:01:26.100 --> 00:01:29.200
What more I demonstrated how you can use

29
00:01:29.200 --> 00:01:32.400
 Google hacking to find sensitive data in

30
00:01:32.400 --> 00:01:35.800
 the URL and insecure HTTP web

31
00:01:35.800 --> 00:01:36.200
 pages?

32
00:01:37.800 --> 00:01:40.700
I also briefly discussed Google hacking

33
00:01:40.700 --> 00:01:44.000
 database this database includes

34
00:01:43.500 --> 00:01:47.300
 special Google search engine queries also

35
00:01:46.300 --> 00:01:49.300
 known as Google Docs.

36
00:01:49.900 --> 00:01:52.800
There are many Google search engine queries

37
00:01:52.800 --> 00:01:54.800
 in Google hacking database.

38
00:01:55.500 --> 00:01:58.800
You can take them directly from this database or

39
00:01:58.800 --> 00:02:01.500
 you can treat them as inspiration for

40
00:02:01.500 --> 00:02:05.000
 creating your own special Google search engine

41
00:02:04.000 --> 00:02:05.700
 queries.

42
00:02:07.100 --> 00:02:10.600
What more I mentioned one report that

43
00:02:10.600 --> 00:02:13.500
 clearly shows the power of Google hacking.

44
00:02:14.400 --> 00:02:17.500
Some time ago a researcher discovered that

45
00:02:17.500 --> 00:02:20.500
 access tokens to Microsoft the armor

46
00:02:20.500 --> 00:02:23.700
 social network where indexed by Google and

47
00:02:23.700 --> 00:02:26.600
 Google hacking could be used to learn this

48
00:02:26.600 --> 00:02:28.300
 very sensitive data.

49
00:02:29.200 --> 00:02:33.100
This vulnerability was reported to Microsoft security

50
00:02:32.100 --> 00:02:36.400
 Response Center by Atik Khan

51
00:02:36.400 --> 00:02:39.700
 from vulnerability laboratory research team.

52
00:02:39.700 --> 00:02:42.300
 And now this vulnerability is

53
00:02:42.300 --> 00:02:42.900
 fixed.

54
00:02:44.100 --> 00:02:48.000
Last but not least. You don't want sensitive data

55
00:02:47.400 --> 00:02:50.200
 from your web application to be

56
00:02:50.200 --> 00:02:53.500
 publicly Exposed on the internet as a

57
00:02:53.500 --> 00:02:56.400
 result of Google indexing and you don't want

58
00:02:56.400 --> 00:02:59.600
 other people to find this sensitive data

59
00:02:59.600 --> 00:03:02.600
 by means of Google hacking. That's why

60
00:03:02.600 --> 00:03:05.700
 you also learned how to prevent Google

61
00:03:05.700 --> 00:03:07.600
 indexing from happening.

62
00:03:09.200 --> 00:03:12.200
I hope this course has been informative for you.

63
00:03:12.200 --> 00:03:15.600
 And I do believe that you will benefit from this

64
00:03:15.600 --> 00:03:17.100
 course as much as possible.

65
00:03:18.100 --> 00:03:21.800
Let me wish you good luck in your web application

66
00:03:21.800 --> 00:03:24.800
 security testing with Google hacking and

67
00:03:24.800 --> 00:03:26.700
 thank you for watching this course.
