I know my company is testing something called "SSL Inspection" based on Websense, which is our proxy. I can not provide more detail about this, but does this mean that in principle all my SSL traffic, for example my web bank password or security PIN, could be actually read by WebSense ?
|
|
Yes. With that configuration WebSense can decrypt and analyze data. Here is what WebSense does as a proxy with ability to inspect SSL connections.
|
|||||
|
|
Yes, SSL Inspection is essentially a man-in-the-middle "attack" (except it's not really an attack since it's being done by the infrastructure owner) with the intention of being able to read all traffic originating from your company machine or crossing your company network, even if SSL is being used. Consequently, you should not send anything from your company issue machine, or over your company network, that you do not want your corporate security team to read. (Which is a good general rule in any case.) Some other points to bear in mind:
If an organization has to implement a robust Data Loss Prevention system, they're going to have to look at everything - so even though they are implementing SSL Inspection it doesn't mean they have evil intent. Not much fun for their employees, of course, which is why transparency is so important. |
||||
|
|
|
Some Security.SE links on this site that may help you: |
|||||
|