WEBVTT - This file was automatically generated by VIMEO

1
00:00:08.700 --> 00:00:09.500
 Welcome back.

2
00:00:10.600 --> 00:00:14.000
 As we'll see throughout this particular training

3
00:00:13.300 --> 00:00:16.800
 that we talked all about season hijacking, different

4
00:00:16.800 --> 00:00:20.100
 prevention, techniques and attack scenarios in

5
00:00:20.100 --> 00:00:23.300
 this case slide. I just want to touch base genetically as

6
00:00:23.300 --> 00:00:25.200
 to what we mean by the term session, hijacking.

7
00:00:26.500 --> 00:00:29.100
 So let's take a scenario where a user is

8
00:00:29.100 --> 00:00:33.200
 trying to communicate with the server and sending out requests. And

9
00:00:32.200 --> 00:00:35.400
 in response. The servo is also going

10
00:00:35.400 --> 00:00:38.800
 to response with the appropriate HTTP Response Code.

11
00:00:40.100 --> 00:00:43.600
 So, when we talk about session, hijacking, we are talking about a scenario

12
00:00:43.700 --> 00:00:46.500
 where we have an attacker, who is trying to get

13
00:00:46.500 --> 00:00:49.100
 into the communication. Because he

14
00:00:49.100 --> 00:00:52.600
 really wants to do is take over the victims session

15
00:00:52.600 --> 00:00:55.700
 itself with the machine, that may

16
00:00:55.700 --> 00:00:59.000
 be simply, you may want to impersonate them. Or

17
00:00:58.100 --> 00:01:01.200
 it may also mean that they want to boot the

18
00:01:01.200 --> 00:01:03.300
 victim out of the connection all together.

19
00:01:04.200 --> 00:01:07.200
 Now this all depends on the style of that tag, the

20
00:01:07.200 --> 00:01:10.100
 tiger is trying to perform over you. You

21
00:01:10.100 --> 00:01:13.400
 could also be the scenario where you would want the victim to

22
00:01:13.400 --> 00:01:16.100
 think that is still logged in and they still have a

23
00:01:16.100 --> 00:01:19.700
 good connection, or it could also be scenarios, patient

24
00:01:19.700 --> 00:01:22.400
 application itself, that he may have

25
00:01:22.400 --> 00:01:25.100
 to log the user off and take over

26
00:01:25.100 --> 00:01:25.700
 the session.

27
00:01:26.700 --> 00:01:29.500
 No, we will cover all the scenarios when we

28
00:01:29.600 --> 00:01:32.500
 go in depth about various attack scenarios and

29
00:01:32.500 --> 00:01:35.200
 the criteria for each of those

30
00:01:35.200 --> 00:01:38.200
 payloads to be executed. So, as we

31
00:01:38.200 --> 00:01:41.800
 have spoken about few times, now, there are different types of session, hijacking.

32
00:01:41.800 --> 00:01:44.300
 So let's go and take

33
00:01:44.300 --> 00:01:47.600
 a look at those as to what are the different types

34
00:01:47.800 --> 00:01:49.700
 in the next particular slide.

35
00:01:51.100 --> 00:01:54.700
 Just to give a brush up again. So that techniques

36
00:01:54.700 --> 00:01:58.000
 that article may use maybe want to

37
00:01:57.400 --> 00:02:01.000
 impersonate the victim, just have a simultaneous access

38
00:02:00.400 --> 00:02:03.400
 or email want to log

39
00:02:03.400 --> 00:02:06.700
 the user out and continue the session button. Either

40
00:02:06.700 --> 00:02:09.700
 ways. This attacker is trying to impersonate

41
00:02:09.700 --> 00:02:10.200
 the victim.

42
00:02:11.700 --> 00:02:14.300
 So in this particular section, we looked at what

43
00:02:14.300 --> 00:02:17.000
 is termed as such an hijacking in which the

44
00:02:17.700 --> 00:02:20.600
 attacker overtakes the victim session and impersonator activities?

45
00:02:22.200 --> 00:02:23.800
 That's it for this video. Thank you.
