Eavesdropping on the Visitor Session
The attacker tries to intercept communication between the visitor and the agent to learn passwords, session information, cookie settings or confidential information between visitor and agent that can be used in a subsequent attack. While an attacker can attempt to eavesdrop on communications at any point, some attack points are more obvious than others, such as when the visitor accesses the company’s web site using an unsecured wireless network.
How we Prevent Eavesdroppers
The collaboration server transmits all data over your secure network connection. It does not make any network connections on its own, and it does not change or restrict the way your secure connection works. In addition, unblu takes these precautions:
We never transmit the content of a password field.
We use two independent session IDs, one for the session between the server and the visitor, and one for the session between the server and the agent. If an attacker learns one ID, he or she cannot use it to guess the other.
The client application does not require cookies. This means that you can use a secure proxy server that stores cookies internally and does not hand them out to the client.
All session IDs are created using the Java Security SecureRandom class, a widely-accepted way to create secure session IDs.
Note: If an attacker manages to compromise the safety of the network connection (for example, by hacking the visitor’s computer and logging the keyboard input), using unblu does not introduce any additional security concerns. We recommend using https connections for client sessions. Even if you do use unsecured connections, using unblu does not introduce additional security concerns.
Can Eavesdropping Succeed in a Cloud Setup?
The collaboration server blocks this type of attack in a cloud setup in the same way as for in an on-premises setup. However, an on-premises setup allows you to introduce an advanced security architecture customized to your specific needs, which is not possible in a cloud setup.