WEBVTT - This file was automatically generated by VIMEO

0
00:00:08.600 --> 00:00:11.600
In this clip. I will mention one report

1
00:00:11.600 --> 00:00:14.300
 that clearly shows the power of Google

2
00:00:14.300 --> 00:00:15.100
 hacking.

3
00:00:16.100 --> 00:00:19.700
Sometime ago a researcher discovered that

4
00:00:19.700 --> 00:00:22.500
 access tokens to Microsoft the

5
00:00:22.500 --> 00:00:25.100
 armor social network where indexed by

6
00:00:25.100 --> 00:00:28.400
 Google and Google hacking could be

7
00:00:28.400 --> 00:00:31.200
 used to learn this very sensitive data.

8
00:00:32.500 --> 00:00:36.000
Yes, it was that simple the attacker

9
00:00:35.200 --> 00:00:38.900
 could create a Google search engine query

10
00:00:38.900 --> 00:00:42.200
 that the returns access tokens to

11
00:00:41.200 --> 00:00:45.100
 Microsoft Yammer and then using

12
00:00:44.100 --> 00:00:48.100
 this access tokens the attacker

13
00:00:47.100 --> 00:00:50.800
 could gain an authorized access to

14
00:00:50.800 --> 00:00:52.200
 the user's accounts.

15
00:00:53.400 --> 00:00:56.700
This critical vulnerability was detected by

16
00:00:56.700 --> 00:01:00.800
 attic Khan from vulnerability laboratory

17
00:00:59.800 --> 00:01:03.600
 research team attic Khan

18
00:01:03.600 --> 00:01:06.800
 reported this vulnerability to Microsoft

19
00:01:06.800 --> 00:01:09.400
 security Response Center, and now

20
00:01:09.400 --> 00:01:11.700
 this vulnerability is fixed.

21
00:01:13.400 --> 00:01:17.300
It clearly shows the power of Google hacking and

22
00:01:16.300 --> 00:01:19.000
 I recommend you to take a look

23
00:01:19.300 --> 00:01:22.600
 at this report to see the details of this

24
00:01:22.600 --> 00:01:23.500
 vulnerability.

25
00:01:24.800 --> 00:01:27.300
Okay. Now we are done with this

26
00:01:27.300 --> 00:01:30.000
 clip and in the next one. I will

27
00:01:30.300 --> 00:01:33.500
 tell you how to prevent the Google indexing from

28
00:01:33.500 --> 00:01:33.900
 happening.
