Generally speaking daily transfer is done also through the protocols of the session layer.
Here however various functions are not so clearly distributed among different protocols as was the case
in the lower layers
is generally accepted that all user authentication protocols operate in a session layer.
We will talk about that later.
Either way this fact concerns both operating systems and individual apps.
The typical attack of a session layer consists of taking the identity of an already authenticated user
in the picture above you can see a Firefox add on Coldfire sheet some time ago it was a real hit.
After downloading and starting it you were able to see pictures and personal information of people who
were connected to the same Wi-Fi network as you and happened to be using social networking sites.
To transfer data all network services use the HTP protocol which is stateless.
This means that a server does not know whether an incoming request was sent by the same user or as the
one before
to enable users to browse a Web site.
The server must emulate a stateful protocol.
It does so by attaching a session identifier to each packet.
Usually this is a short text file called a cookie if the cookie is sent back and already authenticated
user will be identified.
The user will then be able to switch through subpage is within one session.
If someone managed to intercept the cookie and send it back to the server you'd be able to impersonate
the user perfectly the attacker wouldn't even have to know log in and password.
That's how fire works.
The main threats connected to the session layer are identity and credentials spoofing.
The latter may include Kerberos tickets and to mail passwords or web cookies
administrators and other people responsible for security can do little to counter these threats.
This is the job of the people that create applications that employ these mechanisms.
Applications should offer secure ways of user authentication or at least use secure authentication protocols.
Let's get back to the picture in the fire she banged on if the communication took place to the TTP as
protocol.
It wasn't so easy to use the cookie anymore because it was encrypted with a session key.
During this lecture we have learned about the threats and vulnerabilities of transport in-session layers
of the OSA model in the transport layer protocols TCAP and UDP provide a lot of information that can
be used to take control over a weekly protected operating system.
It's more difficult to enlist protocols that are specifically connected with the session layer.
Generally this layer is responsible for authentication.
The main threat connected with this layer consists of stealing the identity of Web users.
Thank you for your attention.