Welcome back.
As we'll see throughout this particular training
that we talked all about season hijacking, different
prevention, techniques and attack scenarios in
this case slide. I just want to touch base genetically as
to what we mean by the term session, hijacking.
So let's take a scenario where a user is
trying to communicate with the server and sending out requests. And
in response. The servo is also going
to response with the appropriate HTTP Response Code.
So, when we talk about session, hijacking, we are talking about a scenario
where we have an attacker, who is trying to get
into the communication. Because he
really wants to do is take over the victims session
itself with the machine, that may
be simply, you may want to impersonate them. Or
it may also mean that they want to boot the
victim out of the connection all together.
Now this all depends on the style of that tag, the
tiger is trying to perform over you. You
could also be the scenario where you would want the victim to
think that is still logged in and they still have a
good connection, or it could also be scenarios, patient
application itself, that he may have
to log the user off and take over
the session.
No, we will cover all the scenarios when we
go in depth about various attack scenarios and
the criteria for each of those
payloads to be executed. So, as we
have spoken about few times, now, there are different types of session, hijacking.
So let's go and take
a look at those as to what are the different types
in the next particular slide.
Just to give a brush up again. So that techniques
that article may use maybe want to
impersonate the victim, just have a simultaneous access
or email want to log
the user out and continue the session button. Either
ways. This attacker is trying to impersonate
the victim.
So in this particular section, we looked at what
is termed as such an hijacking in which the
attacker overtakes the victim session and impersonator activities?
That's it for this video. Thank you.