Slashdot Mirror


Ask Slashdot: Does Your Employer Perform HTTPS MITM Attacks On Employees?

New submitter Matt.Battey writes "I was recently on-site with a client and in the execution of my duties there, I needed to access web sites like Google Maps and my company's VPN. The VPN connection was rejected (which tends to be common, even though it's an HTTPS based VPN service). However, when I went to Google Maps I received a certificate error. It turns out that the client is intercepting all HTTPS traffic on the way out the door and re-issuing an internally generated certificate for the site. My client's employees don't notice because their computers all have the internal CA pushed out via Windows Group Policy & log-on scripts.

In essence, my client performs a Man-In-The-Middle attack on all of their employees, interrupting HTTPS communications via a network coordinated reverse-proxy with false certificate generation. My assumption is that the client logs all HTTPS traffic this way, capturing banking records, passwords, and similar data on their employees.

My question: How common is it for employers to perform MITM attacks on their own employees?"

572 comments

  1. Yes they did. by funwithBSD · · Score: 4, Interesting

    Yes, that is exactly what my company did. They got ratted out when they let the CA expire, but the argument was "Our hardware, our rules."

    The usage rules stated something along the lines of they had the right to inspect and alter packets on the company owned network, so there you go...

    --
    Never answer an anonymous letter. - Yogi Berra
    1. Re:Yes they did. by Jeremiah+Cornelius · · Score: 5, Informative

      This is very common

      Very.

      Your employer probably does little with this - it is usually a part of the configuration for Microsoft Forefront TMG (Formerly ISA Server). I f you have Outlook Web Access, and do any spend on MS recommended practices, then you have a TMG, and 9 out of 10 times, the "Inspection Proxy for SSL" feature.

      The intent is to scrub the stream for malware attachments and malicious XML, etc. Most are set-and-forget, with little competence to exploit or understand what they have done.

      Bigger corporations, or those aware of data sensitivity issues are another matter. Outbound traffic may be subject to this inspection, for DLP with something like Vontu Network Prevent. These controls are managed by folks who spend 25K on netsec, not 25 C's. :-) Then? Clever operators may be logging and trapping all kinds of info. Reports are very "compliance centric" 'tho. The DLP operator team usually has a fair amount of audit scrutiny. Usually...

      Any way, TLS is irrevocably broken. It is reasonable security, trivially implemented and nearly as easily defeated. You own DNS and the path? You own the world.

      I am involved in defining a new transport security mechanism for my company's products, because TLS/SSL of handwaving, and IPsec brittleness.

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    2. Re:Yes they did. by AK+Marc · · Score: 1

      Yup, most large corporations do this, I've worked for more that did this than didn't.

    3. Re:Yes they did. by joaommp · · Score: 5, Interesting

      And how legal is this over there?

      This January, here in Portugal, things like that just became totally illegal, punishable with prison sentence.

    4. Re: Yes they did. by Anonymous Coward · · Score: 0, Informative

      We do this as well, but just to clarify, it is called proxyin, not a man in the middle attack. You could of course abuse this to perform a man in the middle attack, but it is not an attack, until you abuse it. There are many legit and perfectly good reasons for having proxy servers, such as protecting rhe internal network from malware etc. We do have some metadata logging enabled on our proxy, so if an employee goes to his onlin bank, we can see this, but we cannot see the encrypted communication with the bank, or gain access to their logon credentials.

    5. Re:Yes they did. by hsmith · · Score: 4, Informative

      Using company hardware and resources to do anything is stupid in 2014.

      Want to read your personal email, chat, facebook? Use a phone or tablet.

    6. Re:Yes they did. by DoofusOfDeath · · Score: 4, Interesting

      How does that work with website owner's terms of use, however?

      Suppose I create a website, and say that I'm only authorizing the content on my site to be accessed by username Joe.

      Joe logs into my website from his employer's computer, and his employer logs the content I send him. His employer now has unauthorized, decrypted copies of my data.

      Is the employer now in violation of the laws against unauthorized computer access, and in violation of the DMCA for circumventing my copyright mechanism? Recall that Joe has no authority to loosen my copyright claims.

    7. Re:Yes they did. by alex67500 · · Score: 1

      It was studied for a while at my work but abandonned because in French law it would possibly pass as creating and using a fake identity, which are both punishable by law.

      Also, I'm pretty sure the unions would have minded, then there would have been a general strike and... well you know, the usual ;-)

    8. Re:Yes they did. by JohnFen · · Score: 4, Insightful

      In the US, this is totally legal, although there may be disclosure requirements (I'm not sure). The "my system, my rules" argument wins. My workplace does this, and they informed me that they do this when I was hired.

    9. Re: Yes they did. by JohnFen · · Score: 3, Interesting

      If your company cannot see the contents of HTTPS communications then you're right, they're just proxying and not performing a MITM attack. That is not what we're talking about here, though -- we're talking about actual MITM attacks which let the employer examine the encrypted datastreams.

      And yes, it is an attack -- even if it's legal and you can make a good case for doing it, it's still an attack. It doesn't have to be "abusive" to qualify.

    10. Re:Yes they did. by Anonymous Coward · · Score: 5, Interesting

      My previous company did it to:
      They installed a Blue Coat proxy, and pushed to all windows computers (what normal staff was using) the configuration to use that proxy, and installed a trusted CA certificate so the proxy would be trusted.
      That meant that most people didnt realize about the change, as both Explorer and Chrome used the Windows centralized certificate storage from day one.
      The thing only broke for Firefox users (very few) who started getting not trusted certificate errors, and the linux machines when they set the firewall to prevent any http or htts traffic not thru the proxy. Most of those people simply started clicking on the "trust certificate" button.
      A couple of weeks later they pushed an internal firefox installation and "forbid" people from installing it from the mozilla page.

      Funny notes here:
      a) they did it in an illegal way: in this country a company is allowed to monitor their employees network activity only if they make it very clear to them before starting to do so. They certainly did not. Actually our contracts said specifically that they did not.

      b) after trying all kind of things they needed to give up on the idea of preventing any http(s) traffic off the proxy, as many tools (including EDA tools) required https connections to update and so forth and would not trust the proxy certificates. So eventually the firewall was left open for https. Who knew how to, could just work around the proxy in his own computer. All linux workstations were left connecting straight.

      c) People realized and asked what was it. They lied to them with a straight face, with claims like: we dont unencrypt the proxy connections to banks, health (here we have a portal for online consultations with the public doctor and can access our medical history) or other similar private pages. This was a blatant lie anybody could check by just looking at the certificate issuing authority. They were doing it with _all_ pages.

      d) they claimed this was only so they could scan for viruses in downloads. Not to monitor any activity.

      e) I asked our local HR manager, she didnt have any problem telling the truth: "you are an engineer, you work on IT, you know how easy we can monitor anything we want.." and then made some funny remarks about the kind of pages people was enjoying in her previous company and how detailed usage reports she was getting. At that time I checked the blue coat page for the proxy we got installed, it could certainly log any activity in great detail.

      f) My concern wasnt so much that they would monitor our activity (which was creepy), but the fact that all connections were unecrypted at the proxy. So somebody with bad intentions and access to the proxy could start collecting a lot of information. And this made the proxy a great target for hacking.

    11. Re: Yes they did. by naris · · Score: 2

      We do have some metadata logging enabled

      That's what the NSA said....

    12. Re:Yes they did. by starblazer · · Score: 1

      No, Joe would be... because he was allowing another person to access your private website and store the information. He is using the private computer, and should know the rules regarding data interception on non-owned devices.

      Your argument would be valid if he was on an insecured hotspot and someone was running wireshark and decrypting it from there.

    13. Re:Yes they did. by Andy+Dodd · · Score: 3, Informative

      Yup. Here it's perfectly legal if you're informed. Any time I log into a machine at work I get a banner that my employer reserves the right to monitor anything I do with their network.

      --
      retrorocket.o not found, launch anyway?
    14. Re:Yes they did. by DoofusOfDeath · · Score: 1

      What if the decryption was surreptitious? Would that matter?

      And, would it count as wiretapping, in two-party-consent wiretap states?

    15. Re:Yes they did. by Lumpy · · Score: 2

      This is where a USB LTE stick works wonders....

      --
      Do not look at laser with remaining good eye.
    16. Re:Yes they did. by Anonymous Coward · · Score: 0

      I'm replying to you instead of posting a new thread because you seem to know what you're talking about.
      Two questions, if you (or anyone else) have time to answer:

      1. How can you detect this scenario?
      2. How can you bypass/circumvent such a scenario?

    17. Re:Yes they did. by houghi · · Score: 4, Insightful

      Same in Belgium and I would guess the rest of Europe. In Europe the laws tend to lean more towards users and not companies. Also more towards privacy.

      Several places I worked have been VERY upfront on what they were doing. Most also worked with whitelists. The majority of people do not need any internet access anyway. Next they place several Internet PCs on several places, so people can look up their facebook during their breaks.

      This makes it safer for everybody, although when new staff arrives I tell them that the public PC is not something I would do any banking on, because I have NO idea how safe it realy is and it is THEIR fault if somebody robs their bank by using a public PC.

      Also up front explanation that company mail may not be used for personal use. As the Intenetcmputers are available (obviously seperated from the rest of the network. They even have a seperate internet connection.) there is no excuse to do that.

      What I hate is companies who focus on people looking at porn. Why is watching 4 minutes of porn worse then 4 hours of BBC news? One giggled perhaps a bit and the other did not work for half a day. To me the second is way worse.

      --
      Don't fight for your country, if your country does not fight for you.
    18. Re:Yes they did. by Spritzer · · Score: 1

      Yes, mine does . When they implemented this, they openly informed everyone and held a Q&A session. Certificates were provided along with setup instructions for browsers. I don't have an issue with it for 3 reasons.

      1) They were open about it from day 1.
      2) They do not intercept and inspect connections with certain types of sites(banking, healthcare, etc.) and YES I have verified this.
      3) They have obviously limited the ports being intercepted(kind of pointless) because I can establish HTTPS connections to servers using non-standard ports without the normally required certificate. This also means that I can tunnel all of my internet activity via SSH through my home server when I choose to.

    19. Re:Yes they did. by Anonymous Coward · · Score: 0

      If we let you use such devices on our company owned equipment...

    20. Re: Yes they did. by Oligonicella · · Score: 0

      Attacks are, by definition, abusive.

    21. Re:Yes they did. by l0n3s0m3phr34k · · Score: 1

      After reading this, I think HP is doing stuff like this too at my location. I was wondering why via Firefox SSL sites kept getting "reset" but worked via Chrome and IE, it's only been happening for a few months now. I just thought it was some incompetence somewhere in the firewall / router maze our network is, but this makes much more sense...normally I agree about "privacy violation!" yet without HP I wouldn't really even have a bank account to speak of, so...lol

    22. Re:Yes they did. by Anonymous Coward · · Score: 2, Informative

      1: Windows does log when a machine gets a new network interface and how it is configured. It also logs the unavailability of AD and other services that get communicated back.

      2: Fire the offending employee for unauthorized access.

    23. Re:Yes they did. by SJHillman · · Score: 1

      And preferably not one that you connected to the company's secure wifi

    24. Re:Yes they did. by K.+S.+Kyosuke · · Score: 1

      Using company hardware and resources to do anything is stupid in 2014.

      That's what the BYOD people were telling me all along!

      --
      Ezekiel 23:20
    25. Re:Yes they did. by Teun · · Score: 3, Interesting
      I agree most of Europe is behind the voters = normal employees.

      But the company I work for is Anglo-Saxon and that's a whole different kettle of bad fish...

      Indeed they have a front page telling you it's their network and they reserve the right (any right) to protect it.
      The proxy servers are in the UK and US, although both governments luve to gather anything and either don't have a constitution or no privacy legislation they do serve employees in other more enlightened EU countries.

      One day they'll find out they are overstepping both common decency and laws.
      At least in The Netherlands the Works Counsel is on it and has been able to rectify some of the grossest breaches of privacy like a top banner with a public list (log) of any and all sites visited by any individual employee, at least including the management.

      In hindsight it would have been quite interesting to see who or management is interested in now there's rumour of a billion-Euro take-over :)

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    26. Re:Yes they did. by JohnFen · · Score: 5, Interesting

      Intercepting the network traffic of dishonest employees stealing company time and network access is perfectly legitimate

      Why are you assuming that the employees are dishonest and stealing company time and access? My company specifically allows personal use of their network (within certain limitations), so nobody here is being dishonest.

      as is the company reselling the captured personal data in the open market.

      That's nowhere near legitimate, regardless of whether the employee is honest or not. That's an even greater level of dishonesty than someone checking their bank account on company time. If I found a company did that to me, I'd sue them as hard as I could, and I think I would have a decent shot of winning.

    27. Re:Yes they did. by pr0fessor · · Score: 2

      If it's illegal to police your own network and stop unauthorizes use or activity then how do companies protect themselves from liability there?

      Most American enterprises monitor their networks nothing gets in or goes out without going through something and a proxy is a very popular solution. They also usually include a disclaimer when connecting to the network or logging into a machine about monitoring, authorized use, and the possibility of prosecution for unauthorized use.

      {it's more likely a company will just terminate your employment if they catch you torrenting or streaming from a video service but if you cause an outage and enough revenue loss they may take legal action}

    28. Re:Yes they did. by joaommp · · Score: 1

      They don't and that became a problem. The new law actively permits users to be on facebook in company time using company resources. And for that part I'd love to smack the face of whoever thought that up.

    29. Re:Yes they did. by hax4bux · · Score: 0

      Assuming your LTE provider not play the same game.

    30. Re:Yes they did. by SQLGuru · · Score: 1

      You can't even trust those......it's not impossible for your company to set up their own little cell tower covering their buildings......

    31. Re: Yes they did. by thaylin · · Score: 1

      not according to any dictionary I have seen.

      --
      When you cant win, ad hominem.
    32. Re:Yes they did. by Anonymous Coward · · Score: 0

      Or just do everything on your own mobile device. When they own the hardware, they can do anything. ANYTHING.

    33. Re:Yes they did. by asylumx · · Score: 2

      It's perfectly legal here. As an employee, you are using company provided hardware and have signed an employment agreement stating you will only use it for business purposes. Chances are, your personal bank account, facebook page, or whatever else are not part of business purposes. If they are, then why should they be kept private from the company you're doing business on behalf of? If they aren't then why are you using company hardware & bandwidth to access them?

      I may not like the fact that the company can do this, but they do have every legal right.

    34. Re:Yes they did. by pr0fessor · · Score: 1

      Productivity must be down... facebook addiction +1

    35. Re: Yes they did. by Anonymous Coward · · Score: 0

      "And yes, it is an attack -- even if it's legal and you can make a good case for doing it, it's still an attack. It doesn't have to be "abusive" to qualify."

      Thats like saying hitting yourself is an "attack".

      Its ~their~ network. They own it. Policing and/or capturing packets on their ~own~ network is not an "attack".

    36. Re:Yes they did. by Charliemopps · · Score: 2, Interesting

      Exactly... if you owned a network worth hundreds of millions of dollars would you let ANYTHING traverse it without your knowledge? If you did, and you got compromised, Slashdot would be all over you for being too lax in your security.

      The way it works where I'm at, it's totally transparent. You have to sign something that you're ok with being monitored when you're hired, but other than that they don't really explain anything. Then the proxy gets "hits" based on your activity. Everyone gets a bad email or clicks the wrong link every once in a while so they don't want to nail people for every little thing. But once the proxy gets enough "hits" on someone a ticket is created. They don't view these encrypted files or look at your bank data at all... instead they just remotely record video of your desktop. I don't care what kind of encryption you're using at that point, they've got you if you're doing something wrong. I knew a guy that was VPNing to his home network and doing things he shouldn't off that. I guess he thought that was ok... They walked him out in the middle of his shift.

    37. Re:Yes they did. by aminorex · · Score: 1

      I think that if your employer intercepts and decrypts your bank traffic without prior approval from your bank, they are committing a U.S. felony.

      --
      -I like my women like I like my tea: green-
    38. Re:Yes they did. by maxwell+demon · · Score: 5, Insightful

      For example, I have to pay travel expenses from my own money, and then get them reimbursed afterwards. That is, I may have a legitimate reason to access my bank account in order to e.g. pay my flight. But that doesn't give my employer the right to access my banking password (and possibly look what's going on in my bank account).

      Also, if I'm not allowed to access my bank account from the company network, the right thing is not to decrypt it, but to block it.

      --
      The Tao of math: The numbers you can count are not the real numbers.
    39. Re:Yes they did. by Teun · · Score: 1
      Because the company has a limited liability.

      We Europeans see a distinct difference between what's the companies policy and what's an individual's action.

      Yes I know, the concept of individual is /has disappeared from US corporate law.

      See, if you're on a Company Facebook, Twitter, you name it, account you speak for the company, once you are on your personal account you might be the same prick but it's on your name.

      Pretty easy to distinguish I would say.
      Logging and tracing of IP's is only an issue in places like wikipedia where corporate/ political shills are frowned upon.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    40. Re:Yes they did. by TyFoN · · Score: 2

      Here in Norway they go even further, and the company is not allowed to read your email if it is put in a folder clearly marked private.

      Personally I keep my private and work emails in separate systems, but it seems that a lot of people are using their work email for private stuff.

    41. Re:Yes they did. by buchner.johannes · · Score: 2

      In the US, this is totally legal, although there may be disclosure requirements (I'm not sure). The "my system, my rules" argument wins. My workplace does this, and they informed me that they do this when I was hired.

      That's ridiculous, there must be some limits. The argument "my system, my rules" will not work if you were to whip your employees like slaves, so why should it hold for taking away other rights? Signing them away is a nice try, but you can't sign away all your rights.

      --
      NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
    42. Re:Yes they did. by Teun · · Score: 1
      Why?

      Just as much as they (the company) expects you to check your mail before bedtime you can check your kids/ wife's/ mistress's mail in company time, nothing unusual.

      You have a contract for a job (task), you under-perform you get called in, nothing unusual.
      You do your job, the boss should (will) stay off your back.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    43. Re:Yes they did. by Teun · · Score: 1

      How long would they survive?

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    44. Re:Yes they did. by RocketScientist · · Score: 1

      Yup, and I left a company over this exact problem. They couldn't show me that they weren't recording sensitive information (i.e. logging in to manage my health insurance benefits) so I decided I could better offer my services to another employer.

      Badly architected, badly designed, badly implemented, badly documented, poorly tested, and no security or audit controls. Yeah, gonna take a pass on that, thanks though.

    45. Re:Yes they did. by rk · · Score: 3, Informative

      What I hate is companies who focus on people looking at porn. Why is watching 4 minutes of porn worse then 4 hours of BBC news? One giggled perhaps a bit and the other did not work for half a day. To me the second is way worse.

      I don't know where you are, but in the US, that can be boiled down to 3 words: sexual harassment lawsuit. Way more damaging than someone just working half time.

    46. Re:Yes they did. by joaommp · · Score: 1

      So, the resources your company paid for to be tools for your work should be used for your leisure time?
      And since when does a company expect you to check your e-mail before bedtime? If it is a company e-mail, it's to be checked during work hours.

    47. Re:Yes they did. by Anonymous Coward · · Score: 0

      Slip it in the employment contract and how can it be illegal?

    48. Re:Yes they did. by Anonymous Coward · · Score: 0

      So your employer is then forced to put an unconditional block on anything that uses port 443 whilst proxying anything else other port 80... Old school but it works.

    49. Re:Yes they did. by JWW · · Score: 1, Insightful

      I wonder what the company would say if an unscrupulous network admin steals the bank information from a bunch of employees and robs them?

      I'm not sure "my system, my rules" would go very far in court.

    50. Re:Yes they did. by Bacon+Bits · · Score: 2

      It's legal because the computer isn't the employee's. The company owns the computer sending the transmission, the copper from the computer to the inspection hardware, pays for Internet access, and writes policies that computer and Internet usage is for work-related purposes only and all usage is subject to security measures including traffic inspection.

      The better question is: Why do you think using someone else's computer on someone else's network to transmit secure data over someone else's network connection means that they can't look at what you're doing? If you don't want them to look, don't do it where they can see.

      --
      The road to tyranny has always been paved with claims of necessity.
    51. Re:Yes they did. by pr0fessor · · Score: 2

      If I'm on-call, I'm getting paid. If I'm not on-call, then I'm not checking my email.

    52. Re:Yes they did. by joaommp · · Score: 1

      because regardless of the employment contract, the new law states it that way. in any contract, either employment or others, any clause that goes against the law is automatically void and sometimes, due to the nature of those clauses, the entire contract is void.

    53. Re:Yes they did. by Teun · · Score: 1
      Apparently you don't work for a normal company.

      And you missed the discussion about Volkswagen (and now BMW), they had reason to block access to corporate mail for certain non-working hours.

      Besides, a lot of these things are not 'leisure time', they are a recognised and essential part of a person living or even surviving in the 21st. century.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    54. Re:Yes they did. by Anonymous Coward · · Score: 0

      If it's illegal to police your own network and stop unauthorizes use or activity then how do companies protect themselves from liability there?

      if it's legal to police your own network and stop unauthorized use or activity then how do companies protect themselves from liability when their network admin lets you log into your bank and steals your password?

      For the record, I think it's a perfectly fine thing for a company to be doing with their computers and their network, but waving liability around is the wrong way to excuse it.

    55. Re:Yes they did. by jlv · · Score: 1

      Intercepting the network traffic of dishonest employees stealing company time and network access is perfectly legitimate, as is the company reselling the captured personal data in the open market.

      Management says that sales of captured employee personal data probably recover 75-80% of losses resultant from stolen company time, and increases shareholder value dramatically.

      mod +1 funny

    56. Re:Yes they did. by Anonymous Coward · · Score: 1

      Why is watching 4 minutes of porn worse then 4 hours of BBC news?

      One word: Lawsuits.

      Most companies don't allow those things because they are afraid (and rightly so, based on prior lawsuits) of being sued for having a female "hostile" environment. So no porn for you. No women or dirty jokes at work.

      Most companies don't allow alcohol anymore because someone gets drunk, does something stupid, then sues the company because they... OMG, allowed alcohol! So, no more alcohol at most companies (some still do, like mine.. Yay for wine/beer cart thursdays!)

      And so on. So now nothing that is remotely fun at all is allowed at work because it might hurt the feelings of a few sensitive special people, and we left with the lowest common denominator of what is acceptable.

      Such is life. The 80's and early 90's were a hell of a lot more fun, even at work, but those days are long gone.

    57. Re:Yes they did. by Cammi · · Score: 2

      It is illegal for this to be done in the USA in some cases. For instance, you are typing in your banking information or SSN, etc. Network inspects/capture that information ... the employer is hosed .. AKA 100% screwed in court.

    58. Re:Yes they did. by Solandri · · Score: 1, Insightful

      Why are you assuming that the employees are dishonest and stealing company time and access?

      Likewise, why are you assuming that the employer is dishonest and stealing employee info? As has been pointed out, there is a legitimate reason for doing this (scanning and blocking malware being distributed over https, like in email).

      To reach the conclusion that the employer is doing this because they think the employees are dishonest, you must first arrive at the conclusion that the employer is dishonest. Which seems like a double standard. Either assume they're both honest until proven otherwise, or assume they're both dishonest. Why is one presumed innocent until prove otherwise, while the other is presumed guilty until proven otherwise?

    59. Re:Yes they did. by Anonymous Coward · · Score: 0

      all connections were unecrypted at the proxy. So somebody with bad intentions and access to the proxy could start collecting a lot of information. And this made the proxy a great target for hacking.

      As if that wasn't bad enough, think about this for a moment. How carefully do you think the proxy validates the certificate of the server it is connecting to? Consider that in the past few weeks we have heard about major weaknesses in certificate validation code from multiple vendors. There may be lot of push to get people to upgrade their client software, but if your client is configured to use such a proxy, it is the certificate validation code on the proxy which you are really depending on.

      Also I fear that many such proxies may just skip certificate validation altogether. After all there are enough sites around with self signed certificates, expired certificates, or mismatching names, that browsers do allow bypassing the checks if you really want to. If the browser isn't doing the checking, and the proxy is enforcing checking of certificates, then users will complain about being unable to reach those sites with invalid certificates.

      What do you do, if you want less user complaints about sites not working, and you don't want to draw the users attention to the presence of the proxy in the first place? It's pretty easy to just skip certificate validation on the connection from proxy to server, and everything will appear to be working without a hitch. Of course in doing so, you have totally eliminated the security that SSL was providing in the first place. At that point it doesn't matter if the proxy is secured against intrusion, because an attacker can mount another MITM-attack between the proxy and the server, which will go completely unnoticed.

      How widespread is that sort of weakness on MITM-proxies? I have no idea. The only way to check for it is by visiting sites with deliberately invalid certificates.

    60. Re:Yes they did. by khellendros1984 · · Score: 2

      If the company set up their own cell tower, it'd be easy to notice; my cell phone would display constant certificate problems, similar to the way it does if I connect to the corporate wifi using that same device.

      --
      It is pitch black. You are likely to be eaten by a grue.
    61. Re:Yes they did. by pnagel · · Score: 1

      "Our hardware, our rules"? So, just because a company pays the water bill and thus owns the water, does that mean they can lace the taps in the ladies' bathroom with contraceptives? Just because I own my hi-fi, does that mean I may put the speakers on the balcony, point them at the neighbours, and play it at top volume at midnight? Just because I own a baseball bat, that means I can hit you in the head with it? Since when has the rule "the person who owns an object has total say of any actions performed by or in relation to it" ever applied to any part of society?

    62. Re:Yes they did. by AthanasiusKircher · · Score: 1

      I wonder what the company would say if an unscrupulous network admin steals the bank information from a bunch of employees and robs them?

      Umm, the same thing they would say if a rogue janitor used a masterkey to enter the offices of a bunch of employees after hours and stole stuff? That is, "We're firing the guy, and reporting him to the police." I don't get your point. Lots of employees have access to sensitive information or actual physical items that belong to other employees. Those people can't steal stuff. The HR people can't take your personal info and go open fraudulent accounts in your name either.

      I'm not sure "my system, my rules" would go very far in court.

      You're using someone else's network to send sensitive financial information. Especially if the company explicitly discloses what they do and their network rules and practices, it's your choice to do personal transactions on someone else's network. Unless the company displays actual negligence in employing an admin with a criminal background or something, why should the company be liable for some rogue illegal actions?

    63. Re:Yes they did. by Anonymous Coward · · Score: 0

      sure... as if the device you use would change anything. it's about the path, if you're connecting your "phone or tablet" to your company's wlan it's all the same.

    64. Re:Yes they did. by Matheus · · Score: 1

      Doesn't help as much as you'd think since many users hook up to their company WiFi to make their phones and tablets (especially tablets) work right.

      I have one of my browsers permanently proxied through an SSH tunnel out of the office. Not 100% (nothing is these days... how much to I trust my shell provider really?) BUT at least I know I'm getting out of the government office I'm in where I *presume they are accessing anything and everything they can.

    65. Re:Yes they did. by The_Other_Kelly · · Score: 1

      Mobilkom Austria?

      --
      (R)ule in Hell or (S)erve in Heaven [R]?
    66. Re:Yes they did. by mysidia · · Score: 1

      Why are you assuming that the employees are dishonest and stealing company time and access? My company specifically allows personal use of their network (within certain limitations), so nobody here is being dishonest

      It's just as important to catch ones accidentally leaking company information as it is to catch dishonest folks.

    67. Re:Yes they did. by mysidia · · Score: 1

      I think that if your employer intercepts and decrypts your bank traffic without prior approval from your bank, they are committing a U.S. felony.

      No problem... they are intercepting the session. They are probably not recording anything about the information in the HTTPS session, unless it maches one of their rules as a violation.... even then, they probably only log that a violation occured.

    68. Re:Yes they did. by Headrick · · Score: 1

      Exactly. I have my phone set up as a wifi hotspot over its 4G connection (unlimited data) and connect any personal devices (usually just my tablet) so I can browse, send, and receive personal communications. I can't imagine logging in to any social network, getting my personal email, or anything else that I wouldn't feel free to forward or print out for my boss.

      It's my employer's network and I use it for work.

    69. Re:Yes they did. by Anonymous Coward · · Score: 0

      Want to read your personal email, chat, facebook? Use a phone or tablet.

      Not all personal communications are created equal. For example, phone calls with my doctor, my lawyer, my kid's school are not the same as my bestie calling me up and gossiping with me on company time. And while I agree that using the company phone line to talk with my doctor, my lawyer, my kid's school may be stupid, that does not change the fact that I should be able to make such calls on the company phone line without worrying about being listened in on. I should not be required to buy a cellphone to be able to make and receive such emergency calls while at work.

    70. Re:Yes they did. by Kalriath · · Score: 1

      Except that Google forces all search to HTTPS, so even searching the internet for work-related stuff becomes impossible.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    71. Re:Yes they did. by Threni · · Score: 1

      How do you propose to detect people sending out proprietary information such as documents obtained via NDAs from other companies, personal information, credit cards etc if you can't monitor outgoing traffic? You're going to trust people, right? If someone is upset that their surfing/facebook etc usage on company time is being monitored so there's less of a chance I'm going to be the victim of fraud, identity theft etc then they need to get another job, or surf on their phone, or something.

    72. Re:Yes they did. by bws111 · · Score: 1

      'Liability' is not just being held responsible for something. It is any negative situation - it is a liability to have your face covered with tattoos when applying for the job of bank manager.

      So to restate the question - how does a company protect itself from the negative effects of network traffic (malware coming in, secrets going out) if they can't look at the traffic?

    73. Re:Yes they did. by jez9999 · · Score: 1

      What if work involves logging into websites with passwords? Is it OK for your employer to be able to snoop on them, or should that count as "personal" research even though you need it to do your work?

    74. Re:Yes they did. by Jeremiah+Cornelius · · Score: 1

      Tough to detect with MOST browsers. They don't report cert chaining in a way that's useful for this. You COULD check the trust chain everytime you HTTPS. Firefox has the Lock icon to click. Same for Safari.

      There are plugins for Firefox that alleviate this:

      An indicator of changes in chain-of-trust, etc.
      https://addons.mozilla.org/en-US/firefox/addon/certificate-patrol/

      https://addons.mozilla.org/en-US/firefox/addon/perspectives/ Way cool "web-of-trust" validation infrastructure, with more info here:
      http://perspectives-project.org/
      http://perspectives-project.org/firefox/

      People STILL ask me why I don't use Chrome or Surfari...

      Additionally? Modify your workstations settings to use an authoritative external DNS server. OpenDNS is good... enough. Or your ISP servers from home. Then? Use TOR to browse. Be careful with your bank! They may close web-access to your account if TOR has it appear that you log in from Switzerland and Iceland!

      These are not the best counter measures, and don't handle every case. TOR relies on SSL - but on a proxy-port, not 80, so usually outside the scope of these gateways. Depending how your company has it's CA published, they may still look "right" when using external DNS lookups, too.

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    75. Re:Yes they did. by the_B0fh · · Score: 1

      In some cases, not just legal, but almost legally required (think stock brokers, etc).

    76. Re:Yes they did. by Hognoxious · · Score: 1

      England/Britain (or Prussia/Germany) would have kicked your cheesy asses, again?

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    77. Re: Yes they did. by Anonymous Coward · · Score: 0

      Hitting yourself is an attack.

    78. Re:Yes they did. by tatman · · Score: 1

      Welcome to corporate America. Through hot topic social issues, legal issues like work place harassment laws, DMCA and copyright liabilities, even corporate liability for criminal actions of employees on company property (primarily drug law enforcement), corporate America has assumed every employee is a potential liability. Congress has exempted corporations from liability if the company can prove they did "their due diligence". Oh the wonderful land of the free, unless you have a have job, rent or own anything, or have a bank account.

      --
      I've always said English was my second language. Had Romeo and Juliet been written in C, I might have understood it.
    79. Re:Yes they did. by TWX · · Score: 1

      You compare certificates as-recorded by your computer with certificates retrieved by third-party sites. If they don't match then there's probably this kind of thing going on.

      --
      Do not look into laser with remaining eye.
    80. Re:Yes they did. by rikkards · · Score: 1

      Probably because at one point someone was looking at porn at work, a coworker sued for sexual harrasment and won.

    81. Re:Yes they did. by dnavid · · Score: 2

      I wonder what the company would say if an unscrupulous network admin steals the bank information from a bunch of employees and robs them?

      I'm not sure "my system, my rules" would go very far in court.

      In general, so long as the company took reasonable (not absolute) steps to implement safeguards to prevent such a theft, the law is pretty clear that intercepting and inspecting network traffic for legitimate corporate network management or policy enforcement purposes is legal.

      For those that believe this sort of thing is and should be completely illegal, its not so simple. It is well within any company's prerogative to simply *block* SSL traffic at the perimeter, preventing it from being transmitted (on any port, not just 443). And many companies used to do so, before SSL intercepting technologies became more available. So long as employees are informed its happening, I don't see the controversy. The alternative is no access.

      Having said that, while I don't see a controversy, I always inform clients who are considering using such technologies to think carefully. Its within their legal prerogative, but the responsibility in using it and protecting it correctly is non-trivial, and they should weigh that carefully against any potential benefit. But for many organizations with data leak or malware issues, or who just want to not be overly restrictive with internet usage but do want to regulate where and how much access is granted on corporate resources, SSL intercept is the only way to balance those interests.

    82. Re:Yes they did. by Anonymous Coward · · Score: 0

      No, whether Joe knows it or not he has agreed to allow his work place to copy all of his web content. Thus *he* is circumventing your copyright mechanism, if he didn't want a non-authorized copy made he should not have access your site from his work place/computer.

    83. Re:Yes they did. by cas2000 · · Score: 2

      yeah, and how can a company protect their staplers and other expensive stationary from being stolen if they can't strip and cavity-search their employees as they leave each night?

    84. Re:Yes they did. by Anonymous Coward · · Score: 0

      Your IT is too stupid to disable the USB ports, so far they work in everything your company has.
      Note: I left it in the back of one of the servers just in case I need access later.

    85. Re:Yes they did. by dnavid · · Score: 2, Insightful

      Why is watching 4 minutes of porn worse then 4 hours of BBC news? One giggled perhaps a bit and the other did not work for half a day. To me the second is way worse.

      Straw man. Most organizations don't have a usage policy that says four wasted hours of streaming video is ok. However, many have instituted filters for porn specifically because:

      1. Generic porn sites tend to also have a far higher frequency of adware and malware content than normal.
      2. People have been sued for promoting a hostile workplace environment due to porn, but no one to my knowledge has been sued for promoting an overly British workplace.
      3. Many companies are uncomfortable with overtly adult and pornographic media in the workplace in general, irrespective of lost time.
      4. Its possible to envision situationally justifying viewing BBC news in many corporate environments, putting it in the grey area of possibly legitimate usage. Its almost never possible to envision a similar situation occurring for porn.

    86. Re: Yes they did. by Anonymous Coward · · Score: 0

      Where did you get that info?

    87. Re:Yes they did. by dnavid · · Score: 2

      It's legal because the computer isn't the employee's. The company owns the computer sending the transmission, the copper from the computer to the inspection hardware, pays for Internet access, and writes policies that computer and Internet usage is for work-related purposes only and all usage is subject to security measures including traffic inspection.

      Careful: the first part of that statement is false in the US its only the last part that I've highlighted that makes it legal. The US has wiretapping laws that prevent unauthorized tapping of communications. Nothing in the law refers to ownership: otherwise the phone company could listen to anyone's phone calls whenever they wanted to because they own all the gear. Even in the workplace, when you use the company computer and the company network, there are still protections in place for private communications and businesses can be sued for violating those rights. There are exceptions, and it would be wise for IT professionals to know what they are. For example, there is an explicit exemption for business-related email. However, there isn't the same clear-cut exception for private email. There is an exemption for traffic intercept that is necessary to provide fundamental services, which is why corporate firewalls aren't violating the law every time they inspect a packet. However, if I, a network admin, Wireshark a bunch of packets to troubleshoot a network issue and happen to capture some employee's private chat traffic, so long as I don't deliberately read it more than necessary I'm in the clear. If the boss of the company takes those traces off my computer and uses them to read everyone's chat logs, he could be in violation of the law if he has no specific need to do that as a fundamental part of keeping the network functional. The fact that he's "the boss" means exactly jack-squat.

      The big exception is party-consent. If an employee is required as a part of their job to read and sign an AUP, and that AUP states that the employee must consent to monitoring when corporate assets are used, if the employee consents to that then the law prohibiting wiretapping their traffic would no longer apply. Which is why you should never monitor employees network traffic in secret. You're safer video taping (but not audio recording) them in secret than tapping their network traffic, because one of those is a potential Federal crime.

    88. Re: Yes they did. by joaommp · · Score: 1

      Was all over the news and the national data protection institution circulated a PDF explaining it.

    89. Re:Yes they did. by chris_mahan · · Score: 1

      My company does this, but selectively not on some sites, such as my WellsFargo banking account.

      --

      "Piter, too, is dead."

    90. Re:Yes they did. by Anonymous Coward · · Score: 0

      Maybe because he's replying to "Management says that sales of captured employee personal data probably recover 75-80% of losses resultant from stolen company time, and increases shareholder value dramatically."? Seems pretty illegal to me...

    91. Re:Yes they did. by LordLimecat · · Score: 1

      but the reality was "Our hardware, our rules."

      FTFY. Their equipment, their responsibility. They have a right and duty to police the data leaving the network, for a large number of reasons.

      I would not assume that theyre capturing and / or storing passwords, however, as that quickly passes from "due diligence" to "legally murky", and generally the goal is to REDUCE headaches, not cause them.

    92. Re:Yes they did. by LordLimecat · · Score: 1

      It is generally legal, and according to wikipedia it is legal in MOST countries when notice is given. Generally, notice IS given in the Acceptable Use Policy, but even when it is not it seems like it would be a tough thing to argue that you have any special privacy rights in someone else's network. Claiming that you do would make any kind of IDS /IPS pretty hard to do.

    93. Re:Yes they did. by egarland · · Score: 1

      My previous company did this and I was never comfortable with it. I did not have their certificates loaded, so it prevented me from talking through their proxy when they tried to intercept my traffic. The only connections I saw it attack this way were to google. I did try both of my bank's web sites and the certificates used there were original so the traffic there was not intercepted. That made me feel a bit better, but I'm not all that comfortable with my employer having access to the passwords I use outside the company.

      This company was extremely security paranoid after a widely publicised hack hurt their reputation badly, so I understand the actions, and they're probably on legally solid ground, but a piece of me still considers this hacking and unlawful, and another part of me considers the fact that you can silently hack SSL this way a HUGE hole in security.

      The fact that I have to trust that my employer isn't sniffing my banking passwords tells me SSL isn't doing it's job.

      --
      set softtabstop=4 shiftwidth=4 expandtab nocp worlddomination
    94. Re:Yes they did. by LordLimecat · · Score: 1

      Why are you assuming that the employees are dishonest and stealing company time and access? My company specifically allows personal use of their network (within certain limitations), so nobody here is being dishonest.

      These systems are not for the 99% of honest users. Nor are access controls, privilege restrictions, admin-off-by-default, etc.

      These systems are for A) outside intrusions (detection /prevention), and B) those very few but very dangerous malicious users.

    95. Re:Yes they did. by LordLimecat · · Score: 2

      I'm not sure "my system, my rules" would go very far in court.

      I think you would be surprised, and (IANAL but) I suspect misusing that info and / or capturing it for the purposes of fraud would be a whole different discussion.

      Theres not much difference between this and bugging your own house or having an audio recorder in your own car. Your property, your rules.

    96. Re:Yes they did. by pspahn · · Score: 1

      It might not be illegal, but it might likely be unenforceable.

      A previous employer gave all us employees a new NDA to sign. A cursory read-through and pretty much nobody wanted to sign it. A coworker had a lawyer look at it, and he said there was plenty of items in there that would easily be ruled as unenforeable by a judge. Get just one thing on that contract thrown out and it's likely the entire contract will not be valid.

      --
      Someone flopped a steamer in the gene pool.
    97. Re:Yes they did. by Anonymous Coward · · Score: 0

      Except that Google forces all search to HTTPS

      IIRC that only applies if you have HTTPS Everywhere or you have Always use HTTPS turned on in your Google account

    98. Re:Yes they did. by OneAhead · · Score: 1

      Flamebait? Guess some people left their sense of humor at the door...

    99. Re:Yes they did. by Anonymous Coward · · Score: 0

      Good job you're not my lawyer otherwise I would be in deep shit with 'advice' like that...

    100. Re:Yes they did. by Anonymous Coward · · Score: 0

      They don't and that became a problem. The new law actively permits users to be on facebook in company time using company resources. And for that part I'd love to smack the face of whoever thought that up.

      New law eh? Citation needed, otherwise you're full of crap. The employer owns the equipment, the user agreed to the terms of use, and misuse is punishable by firing. The argument that your privacy may be invaded is moot because you have no reasonable expectation of privacy, especially when you signed a user agreement that consents to monitoring and prohibits personal use of company resources.

      For the OP, he might have been violating company policy by even plugging in his laptop in the first place.

    101. Re:Yes they did. by fluffy99 · · Score: 1

      You do realize that performing https proxying and packet inspection to protect against malware is not the same thing as actively recording the sessions right? Regardless of whether they are proxying via MITM, they can still record the urls visited.

      Also, the exact situation that the OP was attempting (a VPN that could expose the internal network) is one reason for using https proxying and filtering.

    102. Re:Yes they did. by Anonymous Coward · · Score: 0

      Tough to detect with MOST browsers.

      If you have the Microsoft EMET tool installed, you will get warned if the pinned certs don't match. For the typical setup, the root cert of the proxy is shoved into Windows via group policy and other browsers like Firefox don't use the Windows cert store and will flag that the cert isn't trusted.

    103. Re:Yes they did. by cbhacking · · Score: 1

      So... did you blow the whistle on them? Item A, I mean. If my employer blatantly lied to me like that, I'd damn well have walked out of that job and into a courtroom over it.

      Of course, I live in the US, which has a well-deserved reputation for litigiousness. Also, where that kind of shit is generally considered legal anyhow. On the other hand, I *do* have the skills needed to check and see if they're doing it, and so far, that hasn't been a problem. Hell, at my current employer, we have to use a VPN (yes, even on our company-issued machines in the company office) if we want to access *internal* resources. Everything else goes out directly.

      --
      There's no place I could be, since I've found Serenity...
    104. Re:Yes they did. by Anonymous Coward · · Score: 0

      Doesn't help as much as you'd think since many users hook up to their company WiFi to make their phones and tablets (especially tablets) work right.

      I have one of my browsers permanently proxied through an SSH tunnel out of the office. Not 100% (nothing is these days... how much to I trust my shell provider really?) BUT at least I know I'm getting out of the government office I'm in where I *presume they are accessing anything and everything they can.

      Be careful doing that. If/when they notice the ssh tunnel they can prosecute you for circumventing network security. That fact that you can actually ssh out is another issue, because your govt office (assuming US here) is not setup correectly per NIST and DISA standards where ALL outbound traffic is required to be proxied.

    105. Re:Yes they did. by wurp · · Score: 1

      What do you mean by 'own the path'? For TLS to be broken, you need to own *both* a CA on the end-user's machine, *and* DNS.

      People executing arbitrary code on their computers (or just in their browser) is a much bigger problem than someone installing a CA on their browser.

    106. Re:Yes they did. by Anonymous Coward · · Score: 0

      Have you seen my red stapler? I want it back.

    107. Re:Yes they did. by aaronb1138 · · Score: 1

      All of the major vendor firewalls are explicitly designed with SSL inspection as a selling point feature. A competent admin sends the Guest Wifi traffic through a separate network so their traffic is not inspected usually.

      This is standard operating procedure and required in some environments for security reasons. It's also one of the only ways to make Data Loss Prevention (DLP) work, since it is necessary to inspect egressing data against protected data stores.

      Calling it a MITM attack is just being alarmist. I for one like the idea of working in a place where my work is important and valuable enough to be worth protecting. Their network, their rules. Watch YouTube and porn on your own time or at least own dime.

    108. Re:Yes they did. by lister+king+of+smeg · · Score: 1

      Why are you assuming that the employees are dishonest and stealing company time and access?

      Likewise, why are you assuming that the employer is dishonest and stealing employee info? As has been pointed out, there is a legitimate reason for doing this (scanning and blocking malware being distributed over https, like in email).

      To reach the conclusion that the employer is doing this because they think the employees are dishonest, you must first arrive at the conclusion that the employer is dishonest. Which seems like a double standard. Either assume they're both honest until proven otherwise, or assume they're both dishonest. Why is one presumed innocent until prove otherwise, while the other is presumed guilty until proven otherwise?

      I think it is best for both parties to assume the other is a hostle third party when it comes to personal privacy and company security. Employers should use ssl striping or other MITMA on their own equipment to secure it, as long as they inform the users of it AND/OR ban the private use of company equipment. Likewise Users should assume a hostile environment and either use their own device + vpn, ssh tunnel, tor, or other secured proxying method or simple not do do sensitive internet activities on company time/property. Now ideally your employer would have a seprate vlan and wireless provided to their emploies for personal use so that company equipments security and network integrity is not damaged by dumb-asses downloading Fr33!!!!_-_Game_***PR0N***.swf.exe.apk on their tablet at lunch and executing it._

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    109. Re:Yes they did. by lister+king+of+smeg · · Score: 1

      In the US, this is totally legal, although there may be disclosure requirements (I'm not sure). The "my system, my rules" argument wins. My workplace does this, and they informed me that they do this when I was hired.

      That's ridiculous, there must be some limits. The argument "my system, my rules" will not work if you were to whip your employees like slaves, so why should it hold for taking away other rights? Signing them away is a nice try, but you can't sign away all your rights.

      It would be more like You selling their information to identity theives to recoup cost from them stealing you company car at lunch and taking it for a unathorised joy ride slamming it into a phone-post and setting it on fire. Neither party is innocent they are both being dicks. the question is whom is the bigger dick (and not in the good way)

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    110. Re:Yes they did. by Anonymous Coward · · Score: 0

      Right... so that's another employment benefit we can just kiss goodbye to, then?

    111. Re:Yes they did. by funwithBSD · · Score: 1

      Not when they have told you all communications are monitored and it is considered misuse of the companies resources to do banking during the day.

      --
      Never answer an anonymous letter. - Yogi Berra
    112. Re:Yes they did. by funwithBSD · · Score: 1

      In my case, I had both HIPPA and DoD systems access.

      Showing they did everything possible to monitor and detect misuse of that data, particularly the DoD data, was more important than trusting employees.

      I can only imagine how paranoid they are after Snowden.

      --
      Never answer an anonymous letter. - Yogi Berra
    113. Re:Yes they did. by funwithBSD · · Score: 2

      Especially since you can use your damn Smartphone over 3g, or your personal device at a local McDonalds/Starbucks if you can't tether and avoid the whole issue.

      --
      Never answer an anonymous letter. - Yogi Berra
    114. Re:Yes they did. by lister+king+of+smeg · · Score: 1

      "Our hardware, our rules"?

      So, just because a company pays the water bill and thus owns the water, does that mean they can lace the taps in the ladies' bathroom with contraceptives?

      If the employees has signed a legally valid contract and medical waiver after being informed maybe...

      Just because I own my hi-fi, does that mean I may put the speakers on the balcony, point them at the neighbours, and play it at top volume at midnight?

      if you had a magical sound dampening field sure but once those soundwaves cross you property line and they enter public property or other people private property you are violating noise ordnances then no.

      Just because I own a baseball bat, that means I can hit you in the head with it?

      No as I have not given you permission to hit my head and you do not own my head.

      Since when has the rule "the person who owns an object has total say of any actions performed by or in relation to it" ever applied to any part of society?

      Ever since we had the concept of personal property? As long as you are not doing anything with it to some other person without their permission or to some other persons property, you should be able to do what ever the hell you want with it.

      If you agree to a bad policy that is your problem. Don't have another job option then don't use equipment/network. There is plenty of free WIFI out there if you don't have have internet at home. Don't trust the free WIFI then use tor. You have options. The only reason I use the WIFI at work (with my personal device at that) is because I admin the network and know they have no such policy and no such logging. If they were to decide to do so I would simply comply with the policy and only use the internet for what I don't care if they see. So what if they saw my slashdot login? I only use that password for who-gives-a-shit sites with no secret information. I would not use it for banking or health-care (without a ssh proxy to my home network if such a proxying were permitted) period.

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    115. Re:Yes they did. by funwithBSD · · Score: 1

      Your packets are not your body.

      And yes, at some work sites they can do exactly that, the TSA for example, it is part of the job!

      --
      Never answer an anonymous letter. - Yogi Berra
    116. Re:Yes they did. by funwithBSD · · Score: 1

      Just like EULAs?

      --
      Never answer an anonymous letter. - Yogi Berra
    117. Re: Yes they did. by lister+king+of+smeg · · Score: 1

      Attacks are, by definition, abusive.

      So would marshal arts and self defense training then by definition be abusive? If so I sure as hell hope Child Protective Services don't find out or a whole hell of a lot of dojo masters are going to jail for child abuse.

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    118. Re:Yes they did. by funwithBSD · · Score: 1

      To be fair, this was very early in the development of this policy/technology, so I don't think they considered the impact... as corporation's are wont to do.

      --
      Never answer an anonymous letter. - Yogi Berra
    119. Re: Yes they did. by Anonymous Coward · · Score: 0

      It is not just employees that can transmit data encrypted. Companies have to have insight on large volumes of encrypted data leaving the network. Attackers will use encryption to hide their theft.

    120. Re:Yes they did. by Anonymous Coward · · Score: 0

      um, it does actually
      Going on the afore mentioned, my computer, my network, my internet connection my rules argument
      Their argument will be, If you want to access your back account on company time, accept our rules or use your own device.
      I know because i've been through the process of installing this type of kit

      It's legitimate uses are to stop the CFO spending all his time downloading porn and paying with it on the company credit card. (a lot of porn sites use https now to hide the traffic)
      Or Online gambling at work, they also use https

      Basically, you should assume
      Despite what my company tells me, if I'm using my company's property for anything they have a right to do what they want with the data, and that includes your phone calls.

       

    121. Re:Yes they did. by Jeremiah+Cornelius · · Score: 1

      CA?

      You mean "certificate".

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    122. Re:Yes they did. by Anonymous Coward · · Score: 1

      What I hate is companies who focus on people looking at porn. Why is watching 4 minutes of porn worse then 4 hours of BBC news? One giggled perhaps a bit and the other did not work for half a day. To me the second is way worse

      In the USA, BBC, FaceSpace, MyIn, LinkdBook, whatever won't open the company to a sexual harassment/hostile workplace environment law suite but surfing porn will.

      Other countries may see this as puritanical and I agree, but that is the reality. Companies here don't give a shit about productivity or results because the infestation known as HR has successfully staked a claim of ultimate import as far as legal liability is concerned. Couple that with a culture that will sue for money for ANYTHING.

      The only people who think HR is important in the USA are upper executives because HR policy covers their ass and HR themselves who spend their time creating their own necessity. Much like lawyers who write laws that only a lawyer could understand. HR should be about routing applications, processing paperword and administering benifits - all things that can be out sourced (not offshored, but outsourced).

      Everyone else in a company sees HR as a bunch of jocks/cheerleaders that don't have anything to offer - they are just an unneeded middle person that continues to play popularity games just like in High School.

      As far as lawsuits go, sorry, there is a difference between being offended and in seeing an opportunity to get a payout if you claim offense. The difference between the two can't be solved with technology as it's not a technical issue. All that does is compel companies to install filters just so they can point to 'reasonable efforts'. Those filters aren't there to actually prevent 'seedy surfing' - they are just there to create the appearence of effort.

      Example: We were asked to filter certain things categorically. One category was 'lingerie'. Within 24 hours we had to remove that filter as it prevented Victoria's Secret and a staffer needed to do research on a perfume that was for sale though a donation. Example 2: We also were asked to filter 'drugs'. Again, less that 24 hours later we were asked to remove the filter as other staffers needed to do legitemate research on prescription medications.

      How ironic - The same person who asked us to filter and then stop filtering these categories said to me once "I know you like to think in terms of black and white but..."

    123. Re:Yes they did. by trylak · · Score: 1

      Um... The use of Microsoft TMG/ISA for Outlook Web Access publishing is pretty out of date. And that use was usually limited to only that one use; as a proxy for Exchange. Although ISA had web-proxy capability that was VERY rarely utilized. So basically if you have a TMG, 9 times out of 10 that has nothing to do with capturing end-user web traffic. There are plenty of other products that do do that. Websense is an industry leader that can be integrated with Cisco networking gear for example. Paul

    124. Re:Yes they did. by Demonantis · · Score: 2

      I never understood the employer time argument. If you are salaried they are paying you for your work not the time you spent working on it. It always seems like they are happy to take the free overtime and then put the screws to you to make busy work when things slow a bit.

    125. Re:Yes they did. by davidhoude · · Score: 1

      Would Joe not be responsible, as he is the end user who accepted the TOS and is the one disclosing the private information to the company?

    126. Re:Yes they did. by Anonymous Coward · · Score: 0

      No, the employer is not in violation of any laws.

      The short is, the employee is not authorized to act on behalf of the company when visiting . As such, the employee is the only party that has agreed to anything (assuming there is some sort of 'Use Contract'). The employee is also the only party responsible for ensuring they are compliant.

      This is the extent of civil law.

      I believe what you are getting at is something similar to email footers that 'require you to delete this or I'll sue you' if its not for you.
      The short i,s it is unenforceable. It if it was, you would create something called a unilateral contract.
      It would mean I could send you a letter saying 'If you don't tear this up by noon on the 5th you grant me irrevocable power of attorney'

      Criminal law; No. If the company owns the end point, they can do what they want to the machine. Generally companies have broad contracts that say 'we will do what we want with this computer, data, etc; if you object, your only recourse is to quit'.
      These contracts exist to save on any potential legal costs; not because the employer would generally loose, but lawsuits cost money even if you win.

      Now, if the employee is authorized to act on behalf of the company; simply consider it 'electronic record keeping' -- very handy in e-discovery.
      The company has the right to store data sent or received by it's authorized agents (in this case the company is the customer and owns the data).

      As for criminal law; Someone tried it.

      http://www.techdirt.com/articles/20100723/03093210331.shtml

      SSL/TLS is designed to provide confidentiality, verify message integrity and and sender identity ONLY between two end points (transit).
      In this case, there are three end points....... Web proxy computer.
      Your Company computer uses their proxy and trusts the Company as an authorized certificating authority.
      In both hops, the confidentiality is maintained, the integrity is verified and the sender is verified -- The joys of the internets trust system.
      The company is not even breaching the expectations of the protocol--maybe they are breaking your (the user's) expectations of what is being verified by TLS/SSL.

      If you really want to cook your noodle, think of what the government could do with a leaf certificate from RSA--That would be a breach, trust and privacy. But that is a whole different legal hole

      TLS/SSL is not 'licensing' or content protection mechanism of any kind. Good luck with that one; I would enjoy watching.
      Generally the DMCA has two provisions you have to worry about in this case. 1.) circumvention 2.) distribution
      TLS/SSL is not a form of DRM so it is not being circumvented. The company is not distributing the data, they are simply holding a backup (which is allowed) (anyone ever backed something up to drop box of back blaze; are the liable for holding it and not distributing it?)

      The short is 'PC does not stand for Personal Computer; It stands for Property of the Company'.

      Though, every company I have worked for that intercepts ssl does not look at the data without an act of god.
      Typically a staff member had to be caught doing X or had loads of unaccounted for time. Then a C level exec would have to sign off on it.
      All we would give them is a list of URLs and times -- Its actually all we stored.
      Well, thats not quite true, we cached images to save bandwidth but it was ephemeral and aged out in hours.

    127. Re: Yes they did. by Anonymous Coward · · Score: 0

      It can be an attack but not in the case at hand (corporate property/networks). I don't like it but it does not break the exceptions of the protocol (only (possibly) the user exceptions)

      By definition (according the the ever accurate Wikipedia) "[TLS/SSL is] designed to provide communication security over the Internet"

      SSL is only designed to provide confidentiality and integrity verification between endpoints It also has some identity verification (but that doesn't work well)

      The proxy will verify the integrity and identity between it's self and the server. Then your computer will verify the integrity and identity between the proxy and it's self.
      The owner of the machine configured the computer to use the proxy and considers the company a valid Certificating Authority.
      Everything is above board and is not an attack. (though most users have flawed expectations of the protocol)

      If someone other than the owner did this: Attack; yes.
      The lawful owner of all of the equipment in question with disclosure: Attack; no.

      What is broke are the users expectation of how the system works.
      The CA system is pretty busted too but thats mostly because its old and was designed well before the modern internet.

    128. Re:Yes they did. by Anonymous Coward · · Score: 0

      But they do this on the wifi at work.
      Or do you want me to use up my limited data plan?

    129. Re:Yes they did. by Anonymous Coward · · Score: 0

      It's also a very fair security concern. It helps to prevent malware/trojans that are inside of the network from easily sending their payloads outside of the network undetected.

      My company was owned a few years back, at which point they added their MITM as a standard feature of the network in hopes of detecting it in the future. In all honesty though, most companies doing it--mine included--are staffed by people far too incompetent to catch these types of attacks before it's too late. At the same time, they are probably quite competent and unethical enough to use the login details of their unsuspecting peers in deplorable ways.

    130. Re: Yes they did. by Eunuchswear · · Score: 1

      marshal arts?

      ITYM martial - from Mars, the god of war.

      Also, while in full on nitpicking mode, it's normally "damming with faint praise".

      --
      Watch this Heartland Institute video
    131. Re:Yes they did. by cas2000 · · Score: 1

      no, but i have a nice brown stapler i can let you have at a good price

    132. Re: Yes they did. by Eunuchswear · · Score: 1

      aargh! Fucking spellchecker - damning, damned!

      --
      Watch this Heartland Institute video
    133. Re:Yes they did. by Teun · · Score: 1
      Malware coming in is a concious decision when going with certain platforms. ;)

      But to come back on earth, why would your bank/ mail provider/ Facebook have a higher risk than the corporate versions?
      Secrets going out doesn't need to happen during working hours.

      Places that have a standard policy forbidding data carriers like SD cards or USB sticks are a different domain, I sincerely hope they'll have set up their network equally tight, like air-gapped.

      --
      "The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
    134. Re:Yes they did. by Anonymous Coward · · Score: 0

      I work for a Chinese company (big telco equipment manufacturer, you guess which one) in Spain. We have a "proxy" server to access the Internet and it replaces all the HTTPS certificates with a company self-signed one. I'm not sure how legal it is here, but I am sure the company will keep doing it as long as they keep getting away with it ...if such a thing is, in fact, not legal.

      I use Firefox as my default browser and it gives me the invalid certificate everytime I try to access anything via HTTPS. I could tell it to accept the certificate as valid, but I use Private Browsing 100% of the time given how things are "in here". Neither IE nor Chrome give the warning, so my trust in FF grows day by day. It sucks to have to be like this, but it is what it is.

      If you're wondering, the answer is "yes, I am looking for a new job"

    135. Re:Yes they did. by Neil+Boekend · · Score: 1

      1. Generic porn sites tend to also have a far higher frequency of adware and malware content than normal.

      Then they should also block relegious sites because they seem to contain more malware

      --
      Well, I might have a way, but it only works on a semi spherical planet in a vacuum.
    136. Re:Yes they did. by Hypotensive · · Score: 1

      That's an even greater level of dishonesty than someone checking their bank account on company time.

      How is the latter dishonest? Dishonesty is lying, how is checking your bank account lying?

      American corporate ethics are weird. Are you even allowed to go to the toilet while you're "on the clock"? Do you have to get special permission to do it? What about if your kid's school principal phones you up to tell you your kid's been misbehaving, is that a "dishonest" abuse of your employer's time?

    137. Re:Yes they did. by Cederic · · Score: 1

      I haven't checked with my current employer, but at my previous company (a bank) their MITM attacks had a whitelist that they would ignore.

      Major UK banks were on the whitelist. I could log into my bank site through a secure HTTPS link, with no corporate inspection of my packets.

      Of course, people worrying about the MITM attack on their bank details are all ignoring the other obvious vector: Your employer can use (and often has pre-installed, ready for activation) keyloggers and/or screen capture software to monitor your activity. They don't need to 'sniff' your banking details, they can capture them at source.

      It's the employer's network, the employer's PC, the employer's choice what to do with it. Use your own devices on your own networks if you want any security.

    138. Re:Yes they did. by alex67500 · · Score: 1

      As long as I have cheese, wine, bread, women and garlic, they can keep coming and going through the country, I don't care :-P

    139. Re:Yes they did. by Anonymous Coward · · Score: 0

      Yes, that is exactly what my company did. They got ratted out when they let the CA expire, but the argument was "Our hardware, our rules."

      The usage rules stated something along the lines of they had the right to inspect and alter packets on the company owned network, so there you go...

      My old company as well. I used aurora and immediately saw it. I've never used a company asset or network to login to a private email or bank account since. LTE tethering is the solution to this nonsense.

      I joined a new company this year. They explicitly have a privacy policy for personal use of computer and networks. They have an anti-harassment policy which covers porn and such.

      love my new company!

    140. Re:Yes they did. by Anonymous Coward · · Score: 0

      The firewall appliance salesmen advertised this capability as of 5 years ago. It is built right into the firewall appliance. I think they called it deep packet inspection. It is a selling point.

    141. Re:Yes they did. by CKW · · Score: 1

      I wanna be a fly on the wall the day (and it will happen) when a large number of people's bank accounts are drained, and the banks say "it was you, you logged in with your credentials"... then latter on the people hit and/or the banks finally figure out "oh, it was all these employees of company X whose accounts got drained" ... THEN who is up sh*t creek?

    142. Re:Yes they did. by dnavid · · Score: 1

      1. Generic porn sites tend to also have a far higher frequency of adware and malware content than normal.

      Then they should also block relegious sites because they seem to contain more malware

      Perhaps they should. However, in general in the real world people make these decisions based on a combination of all the relevant factors, and the act of blocking all religious sites has other potential issues besides malware filtering.

    143. Re:Yes they did. by niftymitch · · Score: 1

      In the US, this is totally legal, although there may be disclosure requirements (I'm not sure). The "my system, my rules" argument wins. My workplace does this, and they informed me that they do this when I was hired.

      Yes but....
      OK, Their system their rules.
      First, keep all your stuff off company hardware.

      But there are places where things overlap.
      Companies have interactions with your bank and expect you to interact with
      your bank, some credit cards, retirement accounts and any seen
      passwords not specific to the company incur a liability on the company.....

      One important thing to do is draft up a letter to the CTO that you do
      not indemnify them from data breaches involving your personal data that costs
      you and do not relinquish any rights you have under the law. Acknowledge that they
      have rights to protect their property but you feel that some tools
      that implement "Man in the Middle" methods are problematic because
      they impersonate ostensibly secure sites (plural) and should their
      tools be hacked you do not wish to be a victim as well.

      Have it sent by your attorney.
      If they object have them object in writing and keep on working.

      I might note that data breaches like Target can be achieved
      in many ways. If the internal MITM tool intercepted credentials for
      anyone and then were abused to attack the system it would
      be almost impossible to prove that the MITM audit tools were
      the root cause.

      Of interest this is implicit in any expense report procedure and tax law.
      There are tax return deductions an individual can take if and only if
      the company denies them. Many managers forget that they
      have a responsibility to both you and the company. If the company
      policy is no, say so in writing so you can act within the law
      on your own tax return (not a global thing for sure).

      --
      Truth is stranger than fiction, but it is because Fiction is obliged to stick to possibilities; Truth isn't. Mark Twain.
    144. Re:Yes they did. by niftymitch · · Score: 1

      I wonder what the company would say if an unscrupulous network admin steals the bank information from a bunch of employees and robs them?

      I'm not sure "my system, my rules" would go very far in court.

      Yes and.... the problem with man in the middle attacks is that the stolen information is
      stolen in a very stealthy way.

      Stolen data from a dozen employees can be used to push data into another employees
      account then to another and then to some island nation accessed by another
      pile of stolen employee information.

      With enough stolen data tracking some of this down is difficult especially
      if some of the data stolen belongs to folk in IT.

      Hang on to your tin foil hat.

      --
      Truth is stranger than fiction, but it is because Fiction is obliged to stick to possibilities; Truth isn't. Mark Twain.
    145. Re:Yes they did. by Anonymous Coward · · Score: 0

      Using North American internet to do anything is stupid in 2014.

    146. Re:Yes they did. by xkpe · · Score: 1

      Is your company disallowing the use of connected devices, doing full body scan searches and wiping out peoples memories every day when they go home? If it's not, all you said can be done anyway...

    147. Re:Yes they did. by asylumx · · Score: 2

      You don't pay for an airline ticket from your bank's website. That's not how it works. That's not how any of this works.

      Click Here for the reference if you haven't seen it.

    148. Re:Yes they did. by DickBreath · · Score: 1

      > Management says that sales of captured employee personal data probably recover 75-80% of losses
      > resultant from stolen company time, and increases shareholder value dramatically.

      Wouldn't it be easier, not to mention vastly more profitable, to recover these losses by selling organs harvested from employees? Don't they teach this kind of thing in MBA school?

      --

      I'll see your senator, and I'll raise you two judges.
    149. Re:Yes they did. by Anonymous Coward · · Score: 0

      With the current state of advanced persistent threats out there, this kind of monitoring is pretty much required if you want to keep your networks secured, whether we like it or not. Trojans are now communicating via SSL back to their C2 servers, often using compromised "legit" destinations as proxies. So you can't look at SSL traffic based on just the destination IP and know if it's legit, you need to get to the next level.

      It's not about monitoring your surfing habits for excessive ESPN use etc (at least at responsible security-conscious companies), they are worried about one thing, your machine being hijacked by a Trojan using encryption and offloading GB's of proprietary secrets. (This also covers the malicious insider as well so maybe two things).

      A professional organization should also have a system of limits to limit access to those logs. Remember, by storing your bank account username/password, they've also assuming a significant risk... if a co-worker uses your user/pass by stealing it off the logs, and it's traced back, you can potentially sue your company. No corporate manager type is going to WANT to keep those kinds of details that might get them in trouble unless there was a real good reason to (as above).

      My organization does have a whitelist that is unmonitored, and while I haven't checked, I'd bet that they put the major banking websites on it just for that reason.

    150. Re:Yes they did. by dreamchaser · · Score: 1

      I have many clients who use various products to decrypt outgoing SSL/TLS. In virtually all cases they take great pains to exclude things like financial and medical data/sites from such scrutiny, for privacy and often compliance reasons. I don't know of a single case where it's been used maliciously, though I'm sure there are a few out there. In the vast majority of cases it is as you said, for DLP purposes.

  2. Maybe the company's not actually doing it? by ip_freely_2000 · · Score: 1

    I'm not sure why they would need to do that as a routine task. It's fairly broad and consumes resources. It'd be pretty funny if you mentioned it to their IT Director and he replied with "huh?"

    1. Re:Maybe the company's not actually doing it? by houstonbofh · · Score: 1, Interesting

      I'm not sure why they would need to do that as a routine task. It's fairly broad and consumes resources. It'd be pretty funny if you mentioned it to their IT Director and he replied with "huh?"

      Actually, a well configured proxy saves resources. Caching of images can save a lot, and filtering of advertising saves a huge amount of bandwidth. Then there is the filtering of content that could expose the company to lawsuits (Like porn in a harassment suit) and legal issues, and of course, job searches on company time.

      And calling it an attack is a joke. There is no middle, as the company owns everything on the network. If you have private stuff to do, use your tablet.

    2. Re:Maybe the company's not actually doing it? by Anonymous Coward · · Score: 0

      This is trivial to do. In a past life, I worked for a midsize firm which had fairly beefy appliances in place whose job it was, was to store every bit flying through the networks, and if it was SSL/TLS, decrypt it and store it indefinitely so auditors can dig through it later come HR review time and pass a list to managers.

    3. Re:Maybe the company's not actually doing it? by maas15 · · Score: 1

      I know certain commercial products, for example Fortanet firewalls, have this functionality built into them.

    4. Re:Maybe the company's not actually doing it? by AK+Marc · · Score: 1

      Yes, and cheap BlueCoats do it too, and they are common.

    5. Re:Maybe the company's not actually doing it? by JohnFen · · Score: 5, Insightful

      The company does not own the employee, and does not own the server that the employee is talking to, and so it really is a MITM attack. The company is the middle.

      Your advice is on the nose, though. It is impossible to trust any employer run system, and therefore you should never, ever do anything of a personal nature on company systems. Even if, as where I work, using the company systems for reasonable personal use is allowed.

    6. Re:Maybe the company's not actually doing it? by Anonymous Coward · · Score: 0

      Perhaps but the company OWNS the cables in the building, the hardware being used, the environment in the building and offers a mutual agreement to the employee. If the company is in the middle, it's only because two colluding entities (bad employee and outside sever) put said company there unjustly.

    7. Re:Maybe the company's not actually doing it? by JohnFen · · Score: 1

      "Unjustly"? How do you figure that? Regardless of just-ness, it's still a MITM attack,

    8. Re:Maybe the company's not actually doing it? by SJHillman · · Score: 1

      If the company forcibly installed this on end-user's home PCs, you'd have a point. The company owns the PC being used, the network infrastructure, the monitoring gateway... and you can be damned sure the user knows this (or should know it using common sense).

    9. Re:Maybe the company's not actually doing it? by sjames · · Score: 1

      It still fits the pattern of MITM even though it's legal sometimes justifiable and even ethical if employees are duly notified that it is done.

    10. Re:Maybe the company's not actually doing it? by chill · · Score: 1, Insightful

      It isn't an attack, it is a proxy. The company's node (computer) is configured to use the company's proxy to get out to the Internet. The connection to the end system is between the company's proxy and the end system. The user has no equipment in play.

      Where I work (U.S. Gov't Agency) does this, though they exempt links to known online banking addresses.

      Employees are trained annually and sign papers acknowledging they understand what is going on. Don't like it? Don't work here. Or, as most people do, use your own device on a cellular connection and don't use the company's equipment or network.

      --
      Learning HOW to think is more important than learning WHAT to think.
    11. Re: Maybe the company's not actually doing it? by Anonymous Coward · · Score: 0

      Your cell phone provider is doing the same thing for performance reasons. They terminate ssl and cache content.

  3. Evil? by handy_vandal · · Score: 1

    Second question: how evil is this practice?

    --
    -kgj
    1. Re:Evil? by Anonymous Coward · · Score: 1

      Pretty evil when you figure that people routinely think little of jumping onto their bank's website and checking their account balance. I mean it is one thing to disallow that... it makes you a huge prick of course, but to MITM silently so anyone who does it is risking their personal financial data? That is absolutely unconscionable.

    2. Re:Evil? by hawguy · · Score: 3, Insightful

      Pretty evil when you figure that people routinely think little of jumping onto their bank's website and checking their account balance. I mean it is one thing to disallow that... it makes you a huge prick of course, but to MITM silently so anyone who does it is risking their personal financial data? That is absolutely unconscionable.

      Not so evil since the company is responsible for what you do with their equipment and internet connection, so they often monitor your usage for things like preventing data leakage (which could result in large penalties against the employer) and browsing inappropriate web sites (if a coworkers sees you surfing porn, the *company* may be liable for allowing a hostile workplace).

      With modern smartphones and cellular enabled tablets, there's no reason to do your personal browsing on your employer's network. If you don't want your employer to see it, don't do it on their equipment/network.

    3. Re:Evil? by houstonbofh · · Score: 1

      If you jump on your bank website from a system you don't own, you are already way into the risky category here... Use your smart phone for that stuff.

    4. Re:Evil? by Anonymous+Brave+Guy · · Score: 1

      With modern smartphones and cellular enabled tablets, there's no reason to do your personal browsing on your employer's network. If you don't want your employer to see it, don't do it on their equipment/network.

      True up to a point, but the moment anyone mentions the phrase "bring your own device" and anyone from your company touches your employee's private property, a whole bunch of similar issues are going to come up.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    5. Re:Evil? by RatherBeAnonymous · · Score: 4, Insightful

      At my last job I did this to a limited extent. I decrypted filesharing sites and services so that I could scan files for viruses at the gateway before they made it to a computer. However, financial and medical industry sites were specifically excluded from decryption, due to the liability issues, and we publicized the fact that we were scanning encrypted traffic.

      There are genuine uses for the technology. More and more sites are going to SSL all the time. That makes impossible to sniff the traffic for virus and intrusions. For schools and libraries, many of which are required to filter for content, unencrypted SSL prevents the content filters from working correctly. I expect that more employers will turn to this in the near future. Doesn't everyone expect

    6. Re:Evil? by blueg3 · · Score: 2

      Extremely.

      For now, set aside the question of whether it's acceptable to monitor your employees' encrypted traffic on your network.

      Technologically, it's a terrible idea. The client software and the end user no longer have any ability to inspect the actual certificates used for an HTTPS connection. From the client's perspective, all HTTPS connections are really with the MITM device and use the same cert chain. (Well, a dynamically-generated cert for the appropriate site signed by the same trusted CA using, presumably, the same process.) The MITM device is the one doing the actual SSL cert verification, and the client has to simply trust that it's doing it correctly. Moreover, none of the information about the SSL cert used gets transmitted to the client. So, no revoking CAs that are compromised. No noticing that this connection to PayPal is using a cert mysteriously signed by Deutsche Telekom (when it should be Verisign). No using non-default root CAs (say, to connect to DoD sites). No rejecting certs that are only signed with MD5. Let's just hope the MITM device knows not to use functions like strlen() and strcmp() when dealing with certificate fields.

    7. Re:Evil? by tbuddy · · Score: 1

      Many businesses find the idea of people doing their personal banking on the clock unconscionable. The firewall package we have when it has a hiccup reverts back to doing HTTPS interception, so for us turning it off is an option rather than it being defaulted to off.

    8. Re:Evil? by AK+Marc · · Score: 1

      Most places that do it are doing it solely for the cache savings. They don't "inspect" the traffic, though they could.

    9. Re:Evil? by TheCarp · · Score: 5, Insightful

      Honestly I WOULD entirely agree if not for the MITM aspect.

      If they really want to do that, setup a proxy and whitelist allowed sites. Deny SSL connections. Fine. Silent MITM attacks expose people in an unsuspecting manner; in ways that its unrealistic to expect most employees outside of IT to understand.

      --
      "I opened my eyes, and everything went dark again"
    10. Re:Evil? by AK+Marc · · Score: 1

      Secure connections are insecure (for the network). If you SSL into your (infected) home server, and download a virus, how is their AV firewall supposed to catch it? If 1000 people all go to BoA or some other site checking their checking balance every day, how are they supposed to save bandwidth with caching?

      So they have valid reasons to do it. It's company computer, company network, why would you allow unsecured computers full access to your network and configure them to waste resources?

    11. Re:Evil? by cheesybagel · · Score: 1

      Too many websites use SSL all the time now. It makes caching and web filtering nearly impossible.

    12. Re:Evil? by hawguy · · Score: 1, Insightful

      Honestly I WOULD entirely agree if not for the MITM aspect.

      If they really want to do that, setup a proxy and whitelist allowed sites. Deny SSL connections. Fine. Silent MITM attacks expose people in an unsuspecting manner; in ways that its unrealistic to expect most employees outside of IT to understand.

      Blanket SSL blocking won't work -- employees often *need* to use SSL to do their job (i.e. Finance needs to connect to the bank websites, employees need to use SSL protected logins at other sites - most any site that allows logins will require SSL).

      No one has time to compile a big whitelist for every site that an employee might need to connect to, which is why the decrypting proxies are so popular -- if you can inspect and do malware scanning on every site, there's no need to make an employee submit a form and wait for someone to test the site to see if it's a valid work related site. And a whitelist doesn't solve the problem of data leakage if a whitelisted site can enable that leakage. The company may allow access to Gmail so employees can check email (they may even use Gmail themselves for email), but they still want to inspect outgoing data to make sure an employee hasn't inadvertently (or purposely) tried to send an email with protected data.

      A well managed decrypting proxy is a limited risk to employees. While a poorly managed proxy may be a risk, a poorly managed desktop computer is also a risk if it's been infected by Malware. Either you trust your employer's IT department to run a secure network or you don't.... and if you don't trust them, then don't use their network or equipment.

    13. Re:Evil? by hawguy · · Score: 1

      With modern smartphones and cellular enabled tablets, there's no reason to do your personal browsing on your employer's network. If you don't want your employer to see it, don't do it on their equipment/network.

      True up to a point, but the moment anyone mentions the phrase "bring your own device" and anyone from your company touches your employee's private property, a whole bunch of similar issues are going to come up.

      No company should allow employees to use untrusted personal devices on their secure corporate network. If the employee insists to use a personal device on the secure network, then the company should take over the device management through whatever tool they use to manage corporate owned devices.

    14. Re:Evil? by YoungManKlaus · · Score: 1

      rather, how illegal ... I am pretty sure at least in my home country it is, and not just a little bit

    15. Re:Evil? by hawguy · · Score: 1

      Honestly I WOULD entirely agree if not for the MITM aspect.

      If they really want to do that, setup a proxy and whitelist allowed sites. Deny SSL connections. Fine. Silent MITM attacks expose people in an unsuspecting manner; in ways that its unrealistic to expect most employees outside of IT to understand.

      How did this get modded insightful?

      The same people that can't understand that an employer monitors all communications whether SSL or not are the same people that will click on a "Your bank account has been disabled, click here to validate your information" phishing link and happily enter their banking information to re-enable their account because the logo on the https://f1rstfederal.com/ site looks just like the logo at their real bank. So they are the ones that most need a decrypting proxy to try to block these attacks.

    16. Re:Evil? by antsbull · · Score: 0

      So.....the end user wouldn't be checking for those things anyway, and if they were the one in a million user who does check out, they would most likely be using their own devices through paranoia anyway. Its more surprising if a big company doesn't use a proxy server.

    17. Re:Evil? by Creepy · · Score: 1

      My company just flat out says if you bring your own device and want to use it on the corporate network, you need to install remote management software that pushes security updates and such and gives them complete access to the device. On the other hand, they don't care much where you go on the work devices, and part of my job often requires going to internet sites. I don't think I'd ever have Eclipse java dev working with Maven plugin without the internet, for instance. About the worst they do is block some sites (mostly torrent, webcomic and game sites).

    18. Re:Evil? by JohnFen · · Score: 1

      Extremely.

    19. Re:Evil? by Anonymous Coward · · Score: 0

      If it is done for the right reasons, it's NOT evil at all. As a matter of fact, it SHOULD be done. To a large enterprise that is (a) trying to be compliant with regulations like PCI and SOX and (b) trying to do IT Security properly to protect themselves and their customers, watching what goes outbound over TLS is as reasonable and necessary as watching for any other channel for sensitive information that should NOT be going outbound.

      Think about it: If a large financial institution or payroll outsourcer is NOT doing this to find malicious insiders or malware sending your PII and your sensitive financial data outbound to some cybercriminal, then why would you trust them to handle your money? If such a company didn't stop and check some employee wheeling a file cabinet out the door at midnight they would clearly be negligent, so why would you want them to ignore outbound network traffic?

    20. Re:Evil? by JohnFen · · Score: 1

      Conversely, no employee should trust their employer's network so much that they'd be willing to attach their devices to it. And they should absolutely not allow the company to install any software on their devices.

      So, win/win!

    21. Re:Evil? by JohnFen · · Score: 1

      That's funny! I'm still of the opinion that not enough sites require HTTPS. It should be 100% of them.

    22. Re:Evil? by JohnFen · · Score: 1

      This is the single worst reason for doing it.

    23. Re:Evil? by hawguy · · Score: 1

      That's funny! I'm still of the opinion that not enough sites require HTTPS. It should be 100% of them.

      I think he meant "Too many" as in "Too many to whitelist them all", not as in "I wish sites would stop using SSL encryption to protect my data".

    24. Re:Evil? by Anonymous Coward · · Score: 0

      My company installed a cell signal booster near our lunchroom, which is in the middle of the building. Is it possible they could even be monitoring THAT web activity?

      /posting from work, living dangerously

    25. Re:Evil? by hawguy · · Score: 1

      My company installed a cell signal booster near our lunchroom, which is in the middle of the building. Is it possible they could even be monitoring THAT web activity?

      /posting from work, living dangerously

      Unlikely since it's probably either an RF booster, so they have no visibility into the signals at all, or they had the cellular company (or companies) install a mini cell site in the building.

      It's unlikely that a private employer would get permission from the cellular companies to install their own private cellular equipment that connects to the cellular network.

    26. Re:Evil? by Anonymous+Brave+Guy · · Score: 1

      My company just flat out says if you bring your own device and want to use it on the corporate network, you need to install remote management software that pushes security updates and such and gives them complete access to the device.

      That's fine, as long as they also provide dedicated, company-owned and -controlled equipment for all company work. A lot of places don't want to pay that expense and encourage employees to use their own devices, at which point the rules aren't so black and white.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    27. Re:Evil? by SJHillman · · Score: 1

      Assuming you actually own your own smartphone and don't just lease it from Apple, etc like they'd like to think...

    28. Re:Evil? by Anonymous Coward · · Score: 1

      so what is the point of using fucking certs in the first place? was it not to increase security and avoid evasdroping communications oh wait...

    29. Re:Evil? by sjames · · Score: 1

      It MAY not be so evil, depending on how it's handled. Employees should be informed of the practice up front, for example. Some make an effort to whitelist banking sites and such to avoid any potential liabilities for personal information.

    30. Re:Evil? by larko · · Score: 1

      If employees do X, the company may be liable. There's no justification in that reasoning for not telling the employees you're doing the scanning. A company policy that says, "Hey, we have hired experts to watch all your traffic to protect the company" is pretty different from one that reads, "Hey, don't use the company resources for private things."

    31. Re:Evil? by Jaime2 · · Score: 2

      That's a bit of an outdated attitude. Any "secure corporate network" has dozens or even hundreds of compromised client devices on it at any moment (and possibly a compromised employee or two). Not allowing personal devices doesn't increase security all that much. On the other hand, the benefits of BYOD are accepted by most companies that employ knowledge workers. Most places I've worked (some were really big corporations) simply require an employee to sign an acceptable use policy before connecting.

      Let me turn that attitude around: are you willing to be held personally responsible when a client is compromised by a zero-day? Control is an illusion in the twenty-first century, it's way past time to start building networks that are able to function properly even with untrusted devices on them.

    32. Re:Evil? by Z00L00K · · Score: 1

      This also raises the question - can the banks detect this?

      It is a great security hole that would be very attractive to every hacker out there - hack a company firewall and get MITM attack vector for free.

      They probably don't even have to hack it, just subvert the company one way or another.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    33. Re:Evil? by omnichad · · Score: 1

      And Google automatically points all search users to https pages if both are available. In addition to Google itself redirecting to https.

    34. Re:Evil? by hawguy · · Score: 1

      That's a bit of an outdated attitude. Any "secure corporate network" has dozens or even hundreds of compromised client devices on it at any moment (and possibly a compromised employee or two). Not allowing personal devices doesn't increase security all that much. On the other hand, the benefits of BYOD are accepted by most companies that employ knowledge workers. Most places I've worked (some were really big corporations) simply require an employee to sign an acceptable use policy before connecting.

      Let me turn that attitude around: are you willing to be held personally responsible when a client is compromised by a zero-day? Control is an illusion in the twenty-first century, it's way past time to start building networks that are able to function properly even with untrusted devices on them.

      Well, no it's not an outdated attitude -- corporate security is about mitigating risk, not eliminating risk, and part of that mitigation is preventing unmanaged devices from connecting to the corporate "trusted" network through NAC policies -- if your device doesn't pass the NAC check, it's not getting on the network, either let IT manage your device, or you can connect to the guest network.

      A signed AUP does little to protect the network (though it may help in terminating employees that insist on violating policies) - all the signed AUP shows is that the employee knows what he is and isn't *supposed* to do, but since humans are responsible for carrying out the policy, even without malicious intent, it's possible that employees are violating the policy. We may *ask* them to keep their antivirus software up to date in the AUP, but with NAC, we can *force* them to keep their antivirus up to date or they can't connect to the network.

      Part of the IDS system relies on decrypting your network traffic so it can detect and mitigate threats as they happen, rather than waiting until we read about it in the newspaper.

      While I'm not held *personally* responsible when a client has been compromised from a zero-day vulnerability, I'm held *professionally* responsible, and I'm the one that would get called in to explain to senior management why that client has been sending to and outside server for 3 weeks without being noticed, and I can't say "Oh, well it was SSL encrypted and sent the data through a Gmail account, so how could we have known!?" -- even the CEO has read enough management magazines to know corporate IT can have visibility into SSL.

    35. Re:Evil? by hawguy · · Score: 1

      My company just flat out says if you bring your own device and want to use it on the corporate network, you need to install remote management software that pushes security updates and such and gives them complete access to the device.

      That's fine, as long as they also provide dedicated, company-owned and -controlled equipment for all company work. A lot of places don't want to pay that expense and encourage employees to use their own devices, at which point the rules aren't so black and white.

      I don't think those are the places distributing their own root CA certificate to corporate desktops so they can inspect SSL traffic at the firewall.

    36. Re:Evil? by AK+Marc · · Score: 1

      Aren't there still companies on T1 Internet? a lot of money for 1.5 Mbps (as the uptime of the T1 is more important than the bandwidth from other connections). Then they do what they can to get the most from that T1. At least that's where I saw it used most. Well, that and so many routers/firewalls include that function (MITM and caching) and it's "free" to turn it on, so why not? It saves bandwidth and improves performance.

    37. Re:Evil? by Jaime2 · · Score: 1

      Well, no it's not an outdated attitude -- corporate security is about mitigating risk, not eliminating risk, and part of that mitigation is preventing unmanaged devices from connecting to the corporate "trusted" network through NAC policies -- if your device doesn't pass the NAC check, it's not getting on the network, either let IT manage your device, or you can connect to the guest network.

      Corporate security may be about mitigating risk, but IT is about providing services. It shouldn't be security's call to remove a service from the portfolio because they don't want the risk. Your job is to provide the service with as little risk as possible and to provide guidance to the rest of IT. Not allowing BYOD because in the name of security is like wiping everyone's hard drive in the name of security. Sure, you have reduced risk, but also crippled the system.

      Most companies already treat insiders as threats, so BYOD on the corporate network isn't any additional risk. If you don't, then that's the outdated attitude I was referring to.

      I know an AUP isn't security. I brought it up to say that they only require an AUP, meaning that no additional security precautions are taken.

      The "hold you responsible" comment wasn't very clear, sorry about that. What I really meant was that if you are denying functionality then there better be an associated benefit. So, the eventual end of that logic is that if you take an extreme position of "all devices on the network must be controlled by me", then you should be held to an equally extreme consequence of "well, then everything is your fault - not professionally - personally". If you want to only bear professional responsibility then you should have stopped at "here is what it would cost to secure a BYOD environment" and not progressed to "No BYOD here.".

    38. Re:Evil? by bloodhawk · · Score: 1

      they avoid eaves dropping between two parties. in a corporate or managed environment though those 2 parties are the proxy server and the web site, not the desktop computer. As others have stated if you really have a problem with your work scanning your web traffic (which in many areas they actually have a legal obligation not to mention security obligation to do) then DON'T use their network for personal stuff. I don't like my personal traffic being scanned and where I work we advertise the fact we scan everything except banking sites, select medical sites and federal authority websites. So even though they don't really care if w use for reasonable personal use and I know the admins don't even log the data it is merely used for malware scanning and content filtering, I use a personal device for personal browsing.

    39. Re:Evil? by pthisis · · Score: 1

      The client can detect it (on a plain install, view the cert for the page you're on and you'll see who signed it and whether it's a corporate cert or a self-signed cert). The "problem" at work is that once someone else has control of your hardware then it can't be trusted--they could as easily have installed a keylogger and screen scraper, or whatever. Or have installed a browser altered so that "view cert" shows a different cert from the one actually being used. The client isn't trustworthy, which means nothing at all is trustworthy.

      You're relatively safe if you do your own OS install and keep things locked down, though even there the hardware manufacturer(s) could be snooping on things. At some point you have to weigh what is enough trust vs. having the tools you need to accomplish your goal (a powered down, non-networked machine is pretty trustworthy, but also relatively useless).

      --
      rage, rage against the dying of the light
    40. Re:Evil? by LordLimecat · · Score: 1

      Depends who you are.

      If you have no idea what the threat model is, what the legal requirements are, or what the business cases are for the practice, and have generally little IT background-- you will think it is evil (unless you actually read that computer use policy).

      If you deal with IT security regularly and / or have dealt with the threats, legal burdens, etc-- youll generally understand that not only does everyone do it, but its pretty important to do.

      But hey, maybe some people like viruses on their network being able to communicate to their C&C server over SSL unhindered. Cant have the company interfering, right?

    41. Re:Evil? by LordLimecat · · Score: 1

      Technologically, it's a terrible idea. The client software and the end user no longer have any ability to inspect the actual certificates used for an HTTPS connection. From the client's perspective, all HTTPS connections are really with the MITM device and use the same cert chain.

      That is completely incorrect.

      The MITM mechanism is the company creating an internal CA (which they and ONLY they control), and installing it as trusted on your workstation. SSL certs are still validated, its just that your employer can generate legitimately* signed certificates for any website on demand.

      So, no revoking CAs that are compromised.

      Again, thats not really true. A proper SSL proxy is gonna reject a bad SSL connection if the cert was revoked, or the timestamp is wrong, or the CA isnt trusted.

      No using non-default root CAs

      Its your employers machine; id say he has the greater right to decide which SSL certs are and are not trusted. If you need to connect to the DoD, your employer almost certainly knows about it, and if he doesnt you should probably let him know.

      90% of your objections are basically that a dedicated IT team is writing the security policy (what crypto algos to use, what CAs to trust, etc) rather than you getting a say in it. Guess what: thats not your job, and the employer has every right to enforce the security policy of his choosing. It may even be a legal requirement for him to do so.

    42. Re:Evil? by Anonymous+Brave+Guy · · Score: 1

      I don't think those are the places distributing their own root CA certificate to corporate desktops so they can inspect SSL traffic at the firewall.

      Sure they are, at least some of them. As I said, there is a whole industry building up around supporting this specific use case, balancing the degree of access required with the inevitable security implications. There is a whole range of options between having no special access/no control of the device and having the same access you'd have from your company PC that is centrally administered by your IT team.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    43. Re:Evil? by FireFury03 · · Score: 1

      Blanket SSL blocking won't work -- employees often *need* to use SSL to do their job (i.e. Finance needs to connect to the bank websites, employees need to use SSL protected logins at other sites - most any site that allows logins will require SSL).

      (Disclaimer: I run a business that provides web filtering systems for schools)

      In fact, SSL is becoming quite common place on a lot of sites where you'd traditionally not consider security to be a big deal. For example, Google does searches over https(*). For a long time we resisted intercepting HTTPS streams, instead choosing to only whitelist certain sites. However, over the last few years, the number of sites using HTTPS has massively increased, and it's simply not feasible to allow them all through without any kind of automated content inspection. So these days, our filtering systems do perform a MITM attack on all HTTPS sites that aren't whitelisted - as far as we're concerned, there's no other way to reliably filter web traffic now.

      I should take this opportunity to point out that I'm specifically talking about schools, where there is a need for some amount of filtering. I'm of the opinion that performing any kind of web filtering in a normal workplace is counter productive: you'll end up blocking stuff your employees need to access in order to do their jobs, you'll end up pissing your employees off and at the end of the day, if your employees aren't responsible adults, why the hell are you employing them?

      (* Google HTTPS searches can be disabled on a network-wide basis; although it could be argued that MITMing these connections at the proxy is better than disabling encryption entirely since the MITM method only introduces one weak point instead of weakening the entire path).

    44. Re:Evil? by lister+king+of+smeg · · Score: 1

      Conversely, no employee should trust their employer's network so much that they'd be willing to attach their devices to it. And they should absolutely not allow the company to install any software on their devices.

      So, win/win!

      Exactly we all need a healthy level of mutual distrust when it comes to smart devices and networks.

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    45. Re:Evil? by lister+king+of+smeg · · Score: 1

      That's a bit of an outdated attitude. Any "secure corporate network" has dozens or even hundreds of compromised client devices on it at any moment (and possibly a compromised employee or two). Not allowing personal devices doesn't increase security all that much. On the other hand, the benefits of BYOD are accepted by most companies that employ knowledge workers. Most places I've worked (some were really big corporations) simply require an employee to sign an acceptable use policy before connecting.

      Let me turn that attitude around: are you willing to be held personally responsible when a client is compromised by a zero-day? Control is an illusion in the twenty-first century, it's way past time to start building networks that are able to function properly even with untrusted devices on them.

      ...and equally the device owners should act as though the network is hostle. It is just best practises no one should trust anyones else's networks, equipment, or software any farther than absolutely necessary.

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    46. Re:Evil? by blueg3 · · Score: 1

      That is completely incorrect.

      No it's not. Like I said, the MITM device does the cert validation with the actual endpoint. The client does cert validation with the MITM device. The cert chain actually associated with the endpoint doesn't make it to the client unmodified, which means the client can't make any useful security decisions when validating it. All meaningful cert validation decisions are made by the MITM device.

      Its your employers machine; id say he has the greater right to decide which SSL certs are and are not trusted. If you need to connect to the DoD, your employer almost certainly knows about it, and if he doesnt you should probably let him know.

      The real problem was tricky to summarize in one sentence. By having the MITM do cert validation, it means you can only use one set of trusted roots for all connections on your network: the one installed on the device. This is frequently the wrong behavior, though. I have a computer here that needs to make SSL connections to DoD computers, and so I have their root cert installed as trusted. I have another computer here that doesn't need to make such connections and so doesn't have the root cert installed. If I see a connection signed by a DoD root on that machine, it will fail to validate, correctly, because it's an error. This gets uglier if you want to trust, say, a single self-signed cert or internal root cert. It's best to restrict trusting those to as few machines as possible.

      I'm not even trying to get into whether an end user wants to trust things that their employer doesn't. Forget that. It's solely from the perspective of an IT staff trying to minimize the risk of computers on their network making bad SSL connections. A single set of rules at a central location is not ideal.

      90% of your objections are basically that a dedicated IT team is writing the security policy (what crypto algos to use, what CAs to trust, etc) rather than you getting a say in it. Guess what: thats not your job, and the employer has every right to enforce the security policy of his choosing. It may even be a legal requirement for him to do so.

      Well, it is my job, so I get a say in it regardless. But that doesn't matter.

      Despite the fact that most users don't pay attention to these things, delivering bad security information to the user is still harmful. The user has a huge advantage over an automated tool, because they know what their intent was. They can notice (though probably won't) that, for example, their SSL connection to a DoD machine really should have been signed by the DoD root and not by a CA in Turkey (just for example).

      That's the lesser issue, though. The problem is that it breaks the ability for software systems to improve certificate validation security. Does your software application use certificate pinning? Too bad, we're rewriting the cert chain! Does Chrome update its CA revocation list 4 weeks faster than your MITM product's vendor in response to a CA breach? Too bad, you're stuck with whatever CA list is in that product! Does your software happen to know that it should never, ever be communicating with a cert signed by a CA that uses only MD5? (My software does, because I'm buying the certs that's on the other end!) Too bad, they won't disable it in the MITM device because it would break half the Internet, and the trusted internal CA of course uses SHA1, so that validates!

      It's a terrible technological hack that reduces the ability of the client to make important security decisions. If your employer wants to control how you validate certs, fine. They should control the configuration and software on the computer. If they want to monitor your SSL connections, fine. There are legitimate reasons for that. They should use an actual standard for proxying SSL connections that conveys all of the security information back to the client.

    47. Re:Evil? by RatherBeAnonymous · · Score: 1

      What was the point of SSL Certs? Easy. To create an industry to skim money from companies doing e-commerce. There are dozens of certificate authorities that are trusted by web browsers and any number of intermediary signing authorities that chain their certs to the trusted root cert signers. Any one of these signing authorities could be compromised and made to issue certs that pass a web browser's rudimentary security checks. The concept of using trusted third party cert signers is not necessarily a terrible one, but it's out of control. Sure, bad certs get revoked, but that depends on the web browser getting updates; something that can not be assumed. And from my experience, the average user has no idea what a cert is, what it does, and why they get warnings about bad certs, so they just blow through the warnings anyway. At least with an SSL decrypting gateway in place, it can be better trusted to be updated about revoked certs and be configured to reject SSL connections using faulty certs.

      If you go shopping for SSL certs, you will find companies selling all manner of certs with escalating trust levels, and it's all bullshit. Nobody except an IT pro has any idea of what the difference is between a basic $100 cert and a $1000 super-duper platinum trusted true business identity certification. The difference - is more buzz words and a bigger greener status bar at the top of your browser window: A status bar that no one will notice. All it does is bring more money to the cert signers and make the e-commerce vendors THINK they are safer.

  4. No by dskoll · · Score: 5, Interesting

    I own my company, and no... I don't do this to my employees.

    I have warned people who've abused the system (I had some casual employees who spent inordinate amounts of time on Facebook, and I've had to clamp down on music downloads that could have gotten me into trouble) but I generally use HR methods rather than technological methods to take action.

    1. Re:No by 50000BTU_barbecue · · Score: 0

      So you fire them, is that what that euphemism means?

      --
      Mostly random stuff.
    2. Re:No by dskoll · · Score: 2

      I have never fired someone for abusing our Internet policy. I've issued warnings, though.

    3. Re:No by RatherBeAnonymous · · Score: 1

      It doesn't have to be a question of abuse, it's more a question of security. If your firewall/intrusion detection systems don't decrypt SSL, they can't scan it for viruses/malware/intrusions/etc.

    4. Re:No by Anonymous Coward · · Score: 0

      Sometimes, a warning also works.

    5. Re:No by dskoll · · Score: 2

      That's true. All our desktops run Linux so we are at somewhat lower risk for most malware than Windows shops. I understand that it's still not completely foolproof, but so far we haven't had a problem.

    6. Re:No by Anonymous Coward · · Score: 1

      Right, well, I would be surprised if your company is large, has many compute resources, or deals with highly sensitive information. Monitoring the corporate network for viruses, industrial espionage, and other untoward activities is a matter of due diligence at many companies.

    7. Re:No by Anonymous Coward · · Score: 0

      let me understand this you increase security by actually braking it?

    8. Re:No by dskoll · · Score: 1

      You are correct... my company is small (10 people).

    9. Re:No by dbc · · Score: 2

      At some point, why not? Verbal warning #1, verbal warning #2, written warning, written Corrective Action Plan with consequences up to and including termination, and for the *really* slow learners, termination.

      At a manager, at some point you start thinking "Am I better off sinking more of my time into this clown, or with an open hiring req?" I've had a couple of occasions where the open hiring req was the more attractive option.

    10. Re:No by E-Rock · · Score: 1

      Except this is to protect the company from malicious users, not form malware.

      If you're in a company where you want/need to do monitoring of the data leaving your network, you have to be checking the SSL traffic. Of course, you should notify people about this.

      We chose not to do SSL Inspection with our filters, and we still notified people when we put the proxies in place.

    11. Re:No by bill_mcgonigle · · Score: 1

      Do you deal in any trade secrets, monopoly grants, or have NDA's with clients?

      I can see where a company without such worries could have nothing that would need auditing and that would be most excellent for the IT folks.

      --
      My God, it's Full of Source!
      OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    12. Re:No by RatherBeAnonymous · · Score: 1

      You presume SSL is secure in the first place. Is the destination server compromised? Did someone share a virus on your Dropbox share? Is there some malware making an SSL tunnel to the outside and using your machine as a gateway to attack the servers? Is someone using a proxy to download undesirable shit on company time. Is your ISP's DNS cache poisoned and you are being redirected to a fake site using a forged SSL cert from a compromised certificate signing authority? Security is messy.

    13. Re:No by Anonymous Coward · · Score: 0

      That you know of. If you're not looking for one, you won't find it if it's there.

    14. Re:No by cascadingstylesheet · · Score: 1

      I own my company, and no... I don't do this to my employees.

      I have warned people who've abused the system (I had some casual employees who spent inordinate amounts of time on Facebook, and I've had to clamp down on music downloads that could have gotten me into trouble) but I generally use HR methods rather than technological methods to take action.

      Kudos to you!

      Just because something can be done doesn't mean that it should be. You could wiretap every phone call your employees make home ("they're MY phones!") but you don't, because you aren't an evil idiot.

  5. Not MITM by SparkleMotion88 · · Score: 3, Insightful

    This is not a MITM attack -- it is a trusted proxy. The employees all trust the proxy, so everything works as it should. You don't trust the proxy, so you get a certificate validation error, so everything works as it should.

    1. Re:Not MITM by DougOtto · · Score: 0

      This +1

      --
      Solving Unix problems since 1989...
    2. Re:Not MITM by trigeek · · Score: 5, Insightful

      This is a Man-in-the-Middle if the end-user is not notified of it.

      --
      Sometimes I doubt your committment to SparkleMotion!
    3. Re: Not MITM by QuietLagoon · · Score: 1

      trusted proxy

      Trusted by whom? I certainly don't trust a MiTM proxy, even when it has the word "trusted" in its name.

    4. Re:Not MITM by parlancex · · Score: 1

      Well that's all semantics isn't it? The reality is that in many countries regulations prevent snooping of traffic to websites related to health or banking, so your company can write whatever policy it likes, it is still explicitly illegal activity.

    5. Re:Not MITM by Anonymous Coward · · Score: 0

      is this 'trusted' machine running the trustworth windoze os?

    6. Re:Not MITM by Anonymous Coward · · Score: 3, Funny

      Oh the end-user was undoubtedly notified of it, probably somewhere at the bottom of their contract, in tiny writing, after the section about the lavatory and in a sentence beginning with "Beware of the leopard".

    7. Re:Not MITM by houstonbofh · · Score: 1

      This is a Man-in-the-Middle if the end-user is not notified of it.

      But he was notified. He got the broken cert. And employees probably got notice in that packet they did not read.

    8. Re:Not MITM by Anonymous Coward · · Score: 0

      Odds are, the employer, like mine has a policy forbidding the use of company resources for personal usage. So, employees shouldn't be accessing those sites via their employer's computers and network.

    9. Re: Not MITM by houstonbofh · · Score: 1

      trusted proxy

      Trusted by whom? I certainly don't trust a MiTM proxy, even when it has the word "trusted" in its name.

      Trusted by the people who own the computer.

    10. Re: Not MITM by Anonymous Coward · · Score: 0

      Then you shouldn't install its signing certificate on your computer.

    11. Re:Not MITM by Anonymous Coward · · Score: 0

      and most proxys have ssl passthrough for banking and health...

      google maps is neither banking nor health thus not subject to the SSL passthrough

    12. Re: Not MITM by QuietLagoon · · Score: 1

      Then you shouldn't install its signing certificate on your computer.

      In a work environment, I may not have that option.

    13. Re:Not MITM by Adrian+Lopez · · Score: 4, Informative

      A trusted proxy is a "Man in the Middle", so I presume your objection is to the word "attack"? Whatever you choose to call it, the fact is that SSL certificates are transparently being rewritten in order to capture data each website's SSL certificate was meant to stop from being captured. "Trusted proxy" is just a friendly euphemism which attempts to justify what may or may not be a legitimate practice, depending on what's being collected and whether or not the users are, in fact, specifically aware of it.

      --
      "In prison you just have to shut your eyes and take it. Here you have to shut your eyes and give it."
    14. Re: Not MITM by QuietLagoon · · Score: 0

      AT&T's computers are owned by AT&T. Tell me why I should trust them with my phone call metadata.

    15. Re:Not MITM by Adrian+Lopez · · Score: 1

      "and most proxys have ssl passthrough for banking and health..."

      Except, of course, for websites not recognized by the proxy as containing "banking" or "health" information.

      --
      "In prison you just have to shut your eyes and take it. Here you have to shut your eyes and give it."
    16. Re: Not MITM by Adrian+Lopez · · Score: 1

      "Trusted by the people who own the computer."

      As opposed to those whose use it. Those whose information is being encrypted to supposedly protect against interception.

      --
      "In prison you just have to shut your eyes and take it. Here you have to shut your eyes and give it."
    17. Re: Not MITM by AK+Marc · · Score: 1

      Then the answer to "by whom" is "you".

    18. Re:Not MITM by Wootery · · Score: 1

      "Trusted proxy" is just a friendly euphemism which attempts to justify what may or may not be a legitimate practice, depending on what's being collected and whether or not the users are, in fact, specifically aware of it.

      This hits the nail on the head. Very well put.

    19. Re:Not MITM by Rene+S.+Hollan · · Score: 5, Informative

      At a former employer, we produced firewall hardware where this was SPECIFICALLY available as a feature. In fact, I developed the software for it. The certificates provided by the external servers are resigned by a CA cert installed on the appliance which is accepted by client machines behind it. Our equipment allowed the option of generating an internal CA cert, which would then be exported to all clients; generate a Certificate Signing Request, which could be signed by a CA already trusted by clients and imported back to the appliance (if the organization had it's own PKI infrastructure); or allow a resigning certificate and key to be imported.

      The justification is simply this: "Our network, our traffic."

      The practical reasons for this are to permit the firewall to do virus scanning on encrypted web pages and email (I handled SMTP STARTTLS and SMTP/SSL as well).

      At least as far as the work I did went, there was no official way to take the plain text traffic off the appliance - it was not "designed" to snoop on employee traffic, though if someone managed to hack the appliance this would be theoretically possible.

      Of course, if you are a contractor or employee concerned about the confidentiality of your traffic, you should exercise due diligence with regard to the CA's your machine trusts.

      In our case, we DID have the capability to specify domain names for which this resigning would not be done: those that were "trusted" by the organization installing the firewall. This made it possible to go the extra mile and make some banking site traffic secure end-to-end, but it was on a site by site basis.

      As I recall, I left the employ of this company prior to SNI support ever being implemented (we barely supported TLS 1.1, and certainly not TLS 1.2 when I was there, much to my protestations, and SNI is a TLS 1.2 Client Hello extension).

      The appliance could also be used in a reverse-fashion: protecting web servers (but not virtual ones, for lack of SNI support, unless they shared a domain name), where it could just do SSL termination, with the site-specific certificate (presumably signed by a CA trusted by most browsers), though we allowed resigning here as well, in the event the internal traffic had to remain encrypted.

       

      --
      In Liberty, Rene
    20. Re:Not MITM by Rene+S.+Hollan · · Score: 1

      Oh, we also did SPAM filtering on encrypted email with this capability.

      There are non-nefarious reasons for an organization wanting to do this, though it clearly compromises end-to-end security if either end does not trust the organization deploying it.

      --
      In Liberty, Rene
    21. Re:Not MITM by ChromaticDragon · · Score: 5, Informative

      Yup. But proxies cannot handle HTTPS unless... they are acting as a MITM.

      The proxy must either pass it along, block it outright or essentially stand in the middle so as to be able to perform all the usual filtering/sniffing/etc. it would do were the traffic plain ole' HTTP.

    22. Re:Not MITM by cheesybagel · · Score: 2

      He got a broken cert because he used his own computer. If you used a computer of that corporation it would have the cert bundled and you would never know that your SSL connection was being snooped.

      In the limit they could even intercept when you are downloading a browser and inject their own malware version of it. Although this seems like too much trouble.

    23. Re:Not MITM by Anonymous Coward · · Score: 0

      It is a MiTM attack, because they're not proxying secure end-to-end connections, they're breaking them and tapping the conversation without telling their users.

      I don't want the security guys at my company to have my banking and 401k ids/passwords, thank you.

    24. Re:Not MITM by AK+Marc · · Score: 1

      If you are on a company computer, prove they don't have a keylogger on it? "trusted proxy" isn't a euphemism, it's a more accurate description. When the end cert is presented by an unknown party, it's a MITM. If they have bad intentions, it's an "attack". When it's a known activity, it's a "trusted proxy". If you don't trust them, don't use it. When it's done by the computer owner, under explicit ToS you agreed to, what's the complaint? You just don't like it, so you want to use inaccurate terms to make it look worse?

    25. Re: Not MITM by antsbull · · Score: 1

      Tell me why your strawman argument about phone call meta data has any relevance to a proxy server?

    26. Re:Not MITM by Anonymous Coward · · Score: 0

      "The employees all trust the proxy..."

      Oh, really? I wouldn't be too sure about that.

    27. Re:Not MITM by Anonymous Coward · · Score: 0

      Employees would be notified if they actually ready the computer use document that the company gave you and you signed after skimming it for 5 seconds. It is plainly stated in ours that we track and monitor all network traffic, and we do it to protect our data and our networks. Any decent DLP does this and I do not know of any major corporation that does not do it.

    28. Re:Not MITM by JohnFen · · Score: 2

      Technically, it's a MITM attack even if the user is notified of it.

    29. Re:Not MITM by Anonymous Coward · · Score: 0

      Yup. But proxies cannot handle HTTPS unless... they are acting as a MITM.

      Yes, and as the parent pointed out that "Man" you're so desperately trying to find "in the Middle" here "attacking" is a product that your company purchased and voluntarily installed in order to obtain the SAME monitoring capability on SSL traffic as they do on most all other traffic.

      That's not a "Man", nor is that an "attack". It's a product that does exactly what it is supposed to do. Nothing more. Let's drop the l337 haxor-speak already. I grow tired of people outside of IT mislabeling things, I certainly don't need more of it within our own (educated?) groups.

    30. Re: Not MITM by SJHillman · · Score: 1

      If they were just collecting metadata, nobody would have a problem. The issue is in that they can see the data.

    31. Re:Not MITM by Tharkkun · · Score: 1

      This is a Man-in-the-Middle if the end-user is not notified of it.

      It's probably covered in the Corporate Security Policy which the original poster failed to read. Most people don't bother to read these things just like an EULA and then get pissed when they realize what's happening. See NSA.

    32. Re:Not MITM by taikedz · · Score: 1

      Out of curiosity, what was the name of the feature? All I can see on this thread are "mitm" and "proxy" - but how is this feature actually called from a vendor point of view? I doubt it was being called as "SSL defeater" or something alarming like that...

      --
      -- "Simplicity is prerequisite for reliability." --Dijkstra
    33. Re:Not MITM by Rene+S.+Hollan · · Score: 2

      HTTP Proxy, SMTP Proxy "encrypted traffic" features. (There was also an HTTPS proxy, but all it did was drop connections to destinations on a blacklist by domain name as specified by the certificate the remote server provided: it did not decrypt, reencrypt, and resign).

      It properly IS a proxy since it proxies the traffic for you. Whether you consider that a MITM attack on encrypted traffic depends on whether you trust the proxy or not.

      SSL does not prevent MITM attacks: it just makes MITM mangling of encrypted traffic discoverable. IF the "man" is "your man" (or your employer's man) then it presumably is not an attack.

      Realize the target audience of vendors of procducts like these: IT managers who want to "protect" against malicious traffic, whether encrypted or not. Of course we can only do that as a MITM. But they way they see it, all network connections "inside" are "theirs", so our box is "their" man in the middle. Often they are clueless and just ask salesmen "Does it work with HTTPS and SMTP/STARTTLS and SMTP/SSL?" without knowing what that means, only that encrypted traffic is "difficult" to scan.

      --
      In Liberty, Rene
    34. Re:Not MITM by Adrian+Lopez · · Score: 1

      "If you are on a company computer, prove they don't have a keylogger on it?"

      Prove that your personal computer doesn't have one. Unless you've personally reviewed all the code and circuitry that could possibly be used for such a purpose, I shall not believe you.

      "When the end cert is presented by an unknown party, it's a MITM."

      It's a MITM when it's done by any party, known or unknown. If the data is being decrypted and captured as it flows between the endpoints of an HTTPS connection, the party doing so is a Man in the Middle.

      "When it's done by the computer owner, under explicit ToS you agreed to, what's the complaint?"

      Whatever the complaint, it involves the fact that "agree to" and "agree with" are different concepts.

      --
      "In prison you just have to shut your eyes and take it. Here you have to shut your eyes and give it."
    35. Re:Not MITM by ichthus · · Score: 0

      I grow tired of people outside of IT mislabeling things, I certainly don't need more of it within our own (educated?) groups.

      Fatass, donut-glazed cheetos finger douchebag IT guy statement of the day.

      Just because you pay money for it and install it, this does not mean it's not a "Man in the middle." It may be company sanctioned, but it's a MITM nonetheless.

      --
      sig: sauer
    36. Re:Not MITM by Anonymous Coward · · Score: 0

      A proxy IS a MITM.

      A MITM attacker is simply a malicious proxy.

      Oh and to answer the initial question, my employer seems not to do this. I run the perspectives plugin in FF and it seems that my cert is the normal cert (google and their sites however don't seem to HAVE a 'normal' cert, so perspectives is pretty useless there).

    37. Re: Not MITM by Anonymous Coward · · Score: 0

      "Trusted by the people who own the computer."

      As opposed to those whose use it.

      You do realize that no technical solution can make that distinction, right ? Write to your senator to make it illegal, it's not related to computer security.

    38. Re:Not MITM by Anonymous Coward · · Score: 0

      Why was this modded up? If you mean by MITM as just some man the middle then yes. But this is MITM in the ssl security sense which means they are decrypting and re-signing the data. A proxy is just that, a proxy. It can relay HTTPS traffic right through it without knowing what's in it because it's encrypted. Like how the postman delivers your letter but isn't a man in the middle. MITM attacks are when they decrypt the data and resign it like the postman opening your letters and resealing the envelope like nothing happened.

    39. Re:Not MITM by Anonymous Coward · · Score: 0

      technically its a MITM Inspection not an attack

    40. Re:Not MITM by SparkleMotion88 · · Score: 2

      I object to the phrase word "Man in the Middle Attack" because that phrase has a very specific meaning. This is not a MITM attack -- at least not a successful one. The submission suggests that the corporation is exploiting some security vulnerability, when really it is just using trust in a completely appropriate* way.

      *Note that all of my comments are about computer security, not acceptable corporate behavior. Whether this is a case of corporate douchebaggery is a separate issue. I didn't comment on that part of the issue because it doesn't interest me.

    41. Re:Not MITM by Anonymous Coward · · Score: 0

      You don't trust the proxy, so you get a certificate validation error, so everything works as it should.

      And what do you do then? You can check the fingerprint and say "oh okay, my employer changed the certificate so I'll trust this fingerprint". But how do you know there weren't two MITM attacks since you now can't verify against the original fingerprint?

    42. Re:Not MITM by Matt.Battey · · Score: 1

      Only this isn't a proxy in the traditional sense where configuration occurred in the OSI layer 6/7 (Presentation/Application), but in layer 4 (Transport). There was no indication that data was intercepted and re-encrypted other than the certificate being reported in the browser was signed by the client's IT department instead of a public CA.

    43. Re:Not MITM by Burz · · Score: 1

      You allowed the user to think end-to-end security was in place, so the hack you implemented was a MITM attack. If the UI had changed to clearly indicate your proxy was in place then it might be different.

      "Our network, our traffic." -- No... PKI was created because the user can't control intermediary networks, and that's what the app-level Ui signals are geared for.

    44. Re:Not MITM by rvw · · Score: 1

      Yup. But proxies cannot handle HTTPS unless... they are acting as a MITM.

      The proxy must either pass it along, block it outright or essentially stand in the middle so as to be able to perform all the usual filtering/sniffing/etc. it would do were the traffic plain ole' HTTP.

      So if I use a VPN as proxy service, what does that mean? Does this all mean that they could decrypt all traffic and see what I do without me knowing it? How can I be sure that this isn't happening?

    45. Re:Not MITM by Adrian+Lopez · · Score: 1

      The submission suggests that the corporation is exploiting some security vulnerability, when really it is just using trust in a completely appropriate* way.

      The problem is not that there doesn't exist a trust relationship between the client device and the proxy (there does), but that the original trust relationship between the client and the website is being violated by the the proxy's interception and modification of the website's SSL certificate. If a malicious third party somehow struck a deal with a trusted certificate authority and used it to monitor targeted communications (remember, trusted != trustworthy), we wouldn't call it anything other than a Man in the Middle attack.

      --
      "In prison you just have to shut your eyes and take it. Here you have to shut your eyes and give it."
    46. Re:Not MITM by Rene+S.+Hollan · · Score: 1

      Wrong: behind our corporate router, it's our network. The users are in our employ. That's the reasoning.

      And the notice is in the trusted certs installed on the client PCs.

      End to end security was in place AS FAR AS THE CORPORATE ORGANIZATION IS CONCERNED. Security from the standpoint of the employee is a different issue that the employee has to take up with the employer.

      Do you really think your corporate network traffic is secure from your employer? It's easy enough for you to check, you know.

      --
      In Liberty, Rene
    47. Re:Not MITM by cheesybagel · · Score: 1

      Hm yeah. As long as it isn't the bosses computer they do it. I see this happening all the time in corporations. For whatever reason the drones can't be trusted but they can. I am a software developer so this has hampered my productivity more than anything else. I had issues connecting to source code repositories on-site. Ticketing systems. Getting Eclipse plugins to download like someone else said. Doing meetings with developers offsite over Skype. etc. Guess what. Even with all that filtering I saw a lot of people on other teams at the client spending most of their time reading the daily news. What is the damned filter useful for anyway?

    48. Re:Not MITM by Burz · · Score: 1

      Users don't lose their individuality when they come to work. They may not be entitled to end-to-end security on the corporate network, but you tricked them into thinking they had it.

      You have rationalized an attack on Internet protocols because you considered the end users' right to know insignificant. You're a hack and a charlatan.

      Another "Liberty" kneejerk corporatist!

    49. Re:Not MITM by Rene+S.+Hollan · · Score: 1

      No, people do not lose their individuality at work, but they should have a resonable understanding of their use of corporate resources, and most HR departments issue employee handbooks that spell this out, including any monitoring of computing or network resources that may take place.

      As for being "tricked", only a fool would consider equipment not their own to respect their privacy wishes without engaging in some due diligence: either establishing a VPN to trusted equipment, or carefully examining the trust anchors the equipment they use has installed.

      A better complaint might be to question the use of such equipment in public access networks, with forged CA certs. Proper practice would have a captive portal explaining policy, and using a clearly non-standard resigning CA that had to be explicitly accepted. But still, it is ultimately the user's responsibility to establish due diligence with regard to network security.

      There is nothing inherently nefarious about resigning SSL traffic. In fact, in the public access scenario it helps thwart drive-by virus attacks and other malware through secure web sessions, at the expense of end user privacy. Do what us "in the know" do: set up a VPN to trusted servers.

      In any case, the problem only arises when using equipment administered by others wirh prior installation of the trusted resigning CA cert: your own equipment, lacking the cert would CLEARLY indicate signing by an untrusted source. That strikes me as an appropriate balance: you have no expectation of privacy using someone else's computer!

      --
      In Liberty, Rene
    50. Re:Not MITM by cbhacking · · Score: 1

      Bullshit. Proxies handle HTTPS all the time. They can do all kinds of things with it, like see what the outbound IP is, what internal machine it comes from, how much bandwidth is being used (approximate, with an upper bound, but still), what port it's going to (usually 443 of course), how long the connection stays open, and so forth. It can log all that info. It can block connections to undesirable (because of malware / inappropriate user of resources / illegal / whatever) hosts. It can raise flags in the case of too many connections, or too much data, or data at unusual times, or... you get the idea.

      A proxy just routes all the connections through one machine. It doesn't imply a need to be able to read data that flows over those connections. Some *uses* of proxies to require that ability - for example, anti-exfiltration systems that look for sensitive data somebody is trying to sneak out - but those can be fooled by concealing / encrypting the data at the application layer anyhow.

      --
      There's no place I could be, since I've found Serenity...
    51. Re:Not MITM by Burz · · Score: 1

      Only an ass would assume the average employee is going to assess their environment like a network engineer.

      And I don't care what your anti-malware excuses are. You can have your security measures, but should expect lawsuits if you pull a bait-and-switch which is what you're doing if you keep the standard PKI UI elements while changing the nature of the underlying encryption. Those indicators operate in the end-to-end paradigm only!!!

      There is also a significant body of law that does, in fact, state an employee has some expectation of privacy for communication that is personal/private. I have worker at places that provided separate phones and computers for just such a reason.

      The very fact that you're trying to use ownership as the end-all blanket excuse for taking abusive shortcuts with your implementation does itself have a whiff of nefarious intent, because then your motives come under the motive of greed (one that expects their mark to trust them utterly in return).

    52. Re:Not MITM by Kalriath · · Score: 1

      Then don't check your bank and 401k from work. Job done.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    53. Re:Not MITM by Kalriath · · Score: 1

      It's not a hack, nor is it an attack.

      Frankly the only reason that corporates that deploy these include the CA in the policy that they apply to their machines (keyword: not your machines) is because browser vendors have made it next to impossible to access sites if the chain of trust is broken, so the only option left is to inject into the chain of trust.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    54. Re:Not MITM by davidhoude · · Score: 1

      A client does not need to be compromised for a MITM attack to work, I have no idea where you would get such an idea. MITM attacks are network based, and have absolutely nothing to do with the client being compromised.

    55. Re:Not MITM by Anonymous Coward · · Score: 0

      Integrity and identity verification are provided between both hops-- server to proxy; proxy to workstation.
      The protocol provides confidentiality in transit.
      That is what SSL/TLS was designed to do provide confidentiality in transit, verify integrity and provide some identity verification.

      The protocol was not broken or circumvented.
      The user's expectations probably are because most people (even in IT industry) have week cryptography knowledge.

      Should it work like this; probably not. But thats how it was designed to work.

      Is it a middle man; of course, so is every node on the internet-- lots of untrustworthy AS out there.
      It is not an attack of any kind. Everything is functioning as designed and as configured by the property owner.

    56. Re:Not MITM by Anonymous Coward · · Score: 0

      FWIW, companies that do this sort of thing tend to only be interested in a web proxy, so outbound requests to TCP ports 80 and 443. If you want to work around it because you don't trust your employer (which is a sign, by the way!) the slashdot crowd can set up sshd on a machine at home and use it as a socks5 proxy. Nobody is doing DPI on every outbound request for ssh frames, so even if they filter 22 you can pick an innocuous high port to listen on. Unless the lockdown is cripplingly strict, probably so strict as to make casual use of the external internet impossible, you'll be able to get around it.

    57. Re:Not MITM by Rene+S.+Hollan · · Score: 1

      Pfft.

      Your whole privacy argument fails in the legal context because the unencrypted data does not leave the appliance.

      Trust me, my employer and their lawyers went over these issues with great care, and I raised many of the concerns you pointed out. The issue hinges on two points:
      1) enencrypted data does not leave the box (except whent the box actually does SSL termination), and 2) non-modified browsers (such as BYOD equipment) would pop up a Certificate validation error.

      At that point it becomes an HR education issue.

      --
      In Liberty, Rene
    58. Re:Not MITM by Rene+S.+Hollan · · Score: 1

      Furthermore, the mechanism is in the product to NOT decrypt and reencrypt selected sensitive whitelisted sites. The purchaser of the appliance has complete control.

      It also does not work for some web applications which HAVE to be whitelisted because they do not permit import of new trust credentials.

      --
      In Liberty, Rene
    59. Re:Not MITM by Rene+S.+Hollan · · Score: 1

      Really? Adding untrusted sites always struck me as trivial.

      We supported PKI integration simply to avoid the manpower lost in constantly trusting such sites, or having to manually import certs.

      --
      In Liberty, Rene
    60. Re:Not MITM by Kalriath · · Score: 1

      Trivial to a techie, yes. But newer versions of browsers display warning messages so dire you'd forgive the user for immediately logging off and cowering under the desk.

      --
      For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
    61. Re:Not MITM by Rene+S.+Hollan · · Score: 1

      Actually, we'd push the CA on the enterprise desktops to make the "experience" identical to it not being there. because the product was advertised as "transparent" to traffic, for some marketting-speak definition of "transparent".

      The bottom line is "do that which makes customers complain the least".

      If enough employees complained that this interception and certificate resigning was unacceptable, or not disclosed clearly enough, things might change. They don't.

      For my part, I was satisfied that the decrypted traffic would not leave the appliance. Of course, someone could later change things so this was possible, but one can't object to useful, legitimate functions, because another might expend non-trivial effort to twist them to nefarious ends.

      --
      In Liberty, Rene
    62. Re:Not MITM by CodeBuster · · Score: 1

      Unless I've missed my guess the Root CA of the "trusted" certificate of an external site, "Amazon.com" for example, would not be VeriSign in this case but instead the "trusted" Root CA on the appliance doing the MITM. So, wouldn't it be obvious to any moderately sophisticated user that you were intercepting the public certificate and replacing it with a fake one signed by the CA on the appliance, trusted or not? It only takes one smart employee to figure this out before word gets around the office that this is being done. Sounds like a good way to piss off your best employees.

  6. Very common by Anonymous Coward · · Score: 0

    If you don't own/administer the laptop you run, assume that you are being monitored via a client side tool. Even so, my university made their own CA (had a laptop program up to last year; now they use it as part of the installer for the Network Access Control tool they put on, which uses passive TCP fingerprinting & user agent in tandem to tell if you run a PC or Mac & require software installation), and used a Fortinet Analyzer to log HTTPS/IM/email/etc. traffic.

    My current customer issues their own CA and Cisco IronPort and MITMs SSL by default. Broke several sites, including my employer's website (X.509 certificate authentication was interrupted because the CA Changed and it didn't think to present the client side cert - they had to add our domain to the exceptions list for MITM). They do so for logging.

    My own employer does not seem to issue CAs over existing ones, but there's so much management software on the thing I don't expect privacy when using it anyways.

    Don't expect privacy on a work PC.

    1. Re:Very common by houstonbofh · · Score: 1

      >

      Don't expect privacy on a work PC.

      The fact that people still do not get this amazes me!

    2. Re:Very Common by cheesybagel · · Score: 3, Funny

      Let me guess. Your corporation has an 'exception' to the professional conduct guidelines when management computers are involved.

  7. I know my employer does. by Anonymous Coward · · Score: 0

    Furthermore, they do all within their power to block any browser other than IE 8. Even apps like Eclipse are crippled, unless you can figure out the arcane and undocumented settings to use said man-in-the-middle proxies.

    The guest network is not encumbered in that way, though, and that's where I transact all non-work-related business - like this post.

    Essentially, I vote with my e-feet; I don't like the security policy on the corporate net, so I don't use it for non-corporate communication. If their idiotic so-called "security" policies lead to a major data breach, it's their data, not mine, and I'll point and laugh as I leave for the next contract.

  8. Rule #1: Never access non-work related stuff in th by Anonymous Coward · · Score: 0

    And if you really really need to, get yourself a smart phone with a fat data-plan.

  9. I suspect... by msauve · · Score: 3, Informative

    that your assumption is incorrect. Some firewalls do deep inspection, looking for malware coming from websites, via email, etc. They'll do SSL MITM to allow that to work. It doesn't necessarily mean they're doing anything nefarious.

    --
    "National Security is the chief cause of national insecurity." - Celine's First Law
    1. Re:I suspect... by ruir · · Score: 2

      Finaly a sane comment...If the poster doesnt like what they do, he can browse the email/banking at home or via his mobile. Their network, their rules.

    2. Re:I suspect... by jones_supa · · Score: 1

      It doesn't necessarily mean they're doing anything nefarious.

      I either do not expect the company to be doing anything nefarious, but on this day and age of data surveillance, I'm glad that an alarm bell rings in people's minds.

    3. Re:I suspect... by ImprovOmega · · Score: 1

      Exactly. This is how you do a transparent proxy with SSL. It doesn't mean that data is being stored somewhere, it just means you're taking reasonable precautions to protect against malware/spam/internet threats. Yes, you theoretically *could* use this to sniff passwords and stuff, I guess, but that would just open up all kinds of liabilities. The easiest and cheapest thing is to discard the data once it's passed inspection. That's what most of these devices do.

    4. Re:I suspect... by JohnFen · · Score: 1

      This is how you do a transparent proxy with SSL. It doesn't mean that data is being stored somewhere, it just means you're taking reasonable precautions to protect against malware/spam/internet threats.

      But it does mean that users can't trust the system.

    5. Re:I suspect... by DMUTPeregrine · · Score: 1

      Of course. It's a cryptographic attack, even if it's not malicious. But the users don't control the system, and so shouldn't trust it anyway.

      --
      Not a sentence!
  10. HIPAA violations? by Anonymous Coward · · Score: 0

    If they do decrypt personal traffic, would they be responsible for any medical data they intercept, thus triggering HIPAA?

    1. Re:HIPAA violations? by Anonymous+Brave+Guy · · Score: 1

      It's true that his sort of system needs to be set up carefully, and probably with the aid of both technical and legal advice if the administrator isn't an expert in this area.

      Saying that, with a properly configured set of devices, it is possible to pass encrypted traffic through a security device that temporarily decrypts the data to scan it but never logs or discloses the full data set itself, so nothing sensitive is ever recorded or put in front of human eyes. There is also technology available that will cut payloads off packets or mask them out so logging tools only see the packet headers, and this kind of technology is often used for compliance with HIPAA, PCI DSS, and similar sensitive areas.

      Of course, if the administrator didn't choose to use those facilities, or if they set them up incorrectly, their systems could be doing all sorts of things that potentially violate various data protection laws depending on jurisdiction.

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    2. Re:HIPAA violations? by Anonymous+Brave+Guy · · Score: 4, Informative

      Also, it's worth noting that the kinds of devices that do this are often used for compliance with rules like HIPAA or PCI DSS. You can't demonstrate that you aren't allowing sensitive data out of a supposedly secured part of your network if you can't actually see what you're allowing out of it...

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    3. Re:HIPAA violations? by houstonbofh · · Score: 1

      If they do decrypt personal traffic, would they be responsible for any medical data they intercept, thus triggering HIPAA?

      Not if they tell you not to use the corporate network for personal business.

    4. Re:HIPAA violations? by Anonymous Coward · · Score: 0

      If they do decrypt personal traffic, would they be responsible for any medical data they intercept, thus triggering HIPAA?

      Not if they tell you not to use the corporate network for personal business.

      Setting a company policy does not relieve them of following the law if it applies.

    5. Re:HIPAA violations? by Anonymous Coward · · Score: 1

      FINRA rules too.

    6. Re:HIPAA violations? by tgd · · Score: 1

      If they do decrypt personal traffic, would they be responsible for any medical data they intercept, thus triggering HIPAA?

      Note: this is a gross oversimplification, but accurate relative to this story and what you're asking ...

      HIPAA has to do with patient data, not medical data. If you're not a patient of the company doing the deep inspection, then there's no issue, and there's still no issue if you signed an appropriate HIPAA waiver, even if you ARE a patient and the company in question IS a hospital. If you go to HealthVault or some other site with *your* health records in it, and they are decrypting it, that's not HIPAA in the sense you're talking about.

      Hell, even if they were shuffling the SSL traffic to a cloud service hosted by a 3rd party to do the scanning, AND you were a patient, AND the 3rd party was decrypting the data, that is just fine as long as the right paperwork is in place between the two companies.

    7. Re:HIPAA violations? by BenSchuarmer · · Score: 1

      Is it that different than your boss overhearing you discussing your medical conditions on your work phone?

      If you don't want them to know about it, don't use their equipment to communicate about it.

    8. Re:HIPAA violations? by AK+Marc · · Score: 1

      No. Unless they are a medical institution, and the information is available to unauthorized people, then there'd be no question that it's perfectly fine, and HIPAA compliant. It's not a violation of HIPAA to over hear your mother talking about her condition with someone else, then run around telling everyone else about it. There may be other issues with that, but HIPAA isn't on of them.

      That and the last I looked, there were still zero fines for unauthorized sharing of information, just fines for failure to release records when required to do so. HIPAA was *more* about giving you access to your own records than blocking others from it, but they lumped them together because that made sense at the time.

    9. Re:HIPAA violations? by houstonbofh · · Score: 1

      If they do decrypt personal traffic, would they be responsible for any medical data they intercept, thus triggering HIPAA?

      Not if they tell you not to use the corporate network for personal business.

      Setting a company policy does not relieve them of following the law if it applies.

      By your standards, my writing my medical data on the side your house puts you at risk. Sorry, but that is not how it works.

    10. Re:HIPAA violations? by Anonymous Coward · · Score: 0

      Employees are responsible for their employees. If an employee accesses HIPAA data, even if their own, and causes the proxy to run afoul of HIPAA laws, then the employer is still responsible. There is no inherent waving of rights.

  11. More than you think... by Anonymous Coward · · Score: 1

    I lost a client because I refused to setup something similar.

  12. Very Common by Anonymous Coward · · Score: 0

    I encountered the FBI doing this in 2003, and my current company, a Fortune 100 company, also employs this technology.

    We use it to decrypt and scan all HTTPS communication to prevent confidential information from leaking out of the company as well as to enforce professional conduct guidelines (no naughty words or boobies!).

    I would wager this type of proxy with fake certs is fairly common at large companies in the U.S. today.

  13. Maybe it is not the employer. by Anonymous Coward · · Score: 0

    I wonder if the employer even knows? In most firms the employer rarely sets up the network themselves and hold the keys. They usually put the trust of the network in their systems administrators. I have worked at a few firms where the system admins would all treat the network like their little play toy. I would point fingers at whoever set up the proxy before pointing them at management. In my experience management is really not that savvy.

    Birds of a feather flock together.

  14. Of course by Anonymous Coward · · Score: 0

    When I connect to my employer's network I get a pop-up that says: "YOU SHOULD HAVE NO EXPECTATION OF PRIVACY"

  15. It's know as content inspection by Anonymous Coward · · Score: 0

    The greatest avenue for malware infection is from web traffic. Organizations that take security seriously will open the https at a proxy that analyzes the content for malware and then either blocks it or allows it. Who said anything about recording all web traffic? My proxy logs are large enough... nevermind the idea of logging content!

  16. Comment removed by account_deleted · · Score: 3, Insightful

    Comment removed based on user account deletion

  17. Not that uncommon by ZerXes · · Score: 1

    It depends on the company and its policy's of course but this is not that uncommon. I would say that in most cases this is not for spying on the employees rather protecting them by letting IDS/IPS-systems be able to read the network traffic even when using SSL to find botnets, infected hosts and malware. But the solution sure makes it *possible* for the company to spy on the employees and my personal opinion is that a company using this technique should make sure the employees know that SSL is being intercepted.

  18. Yes and no by Anonymous+Brave+Guy · · Score: 2

    It's perfectly legitimate practice on a company network to intercept encrypted traffic. Security devices used for things like intrusion protection and data leakage prevention can't work properly if all you need to circumvent them is an encrypted connection, and you really want that kind of security these days if you're using a large company network, whether you're the company management, the company employees, or the company's customers/clients.

    Doing it without making anyone using the network fully aware of the possibility, however, is quite a different matter, unless employees clearly aren't allowed to use company systems for personal use at all. If you've been told occasional personal use is OK and they're covertly MITMing your online banking session on your lunch break or similar, that is highly inappropriate.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
    1. Re:Yes and no by mlts · · Score: 3, Insightful

      Sometimes watching encrypted traffic may be needed for some regulatory compliance. Of course, the best thing would be to have a terminal server set up to allow people to use their Web browser free and clear, while direct connections to the Internet would be monitored/logged. This way, personal E-mail and banking info isn't touched, while sensitive internal data is well protected.

  19. More likely an IPS by gweeks · · Score: 4, Informative

    It's more likely they are running the traffic through and IDS/IPS rather than logging everything. It's also likely that well know banking sites are excluded and just passed through. It does use quite a lot of resources to scan the traffic after all.

    IDS/IPS https://en.wikipedia.org/wiki/...

  20. Very common in my experience by Anonymous Coward · · Score: 0

    This is very common to protect against exploitation of the SSL hole. Blocking your VPN protocol also protects network resources, as malware can use this technology to bypass firewall systems too.

    Remember, the equipment and bandwidth of your client belongs is theirs to do with as they see fit. Obviously capturing people's banking data, and USING it, is illegal and would prosecutable to the fullest extent of law.

  21. Re:Rule #1: Never access non-work related stuff in by Anonymous Coward · · Score: 3, Informative

    Don't put the actual text of your comment in the title. All the information should be in the body of the comment, and the comment should be fully understandable without the title.

  22. My hardware, my rules by Anonymous Coward · · Score: 0

    We intercept HTTPS proxy here, we just inform our employees about it upfront. Our computers are exclusively meant for work, not personal use. We provide an entirely separate public WiFi network for employees, and guests.

  23. Necessary sometimes by the+eric+conspiracy · · Score: 1

    In some cases you need to know everything that is going out the door. For example if your company is the target of industrial espionage the last thing you want is your trade secrets going out through your firewall.

    I would expect a lot of companies are doing this along with other similar measures.

    1. Re:Necessary sometimes by WaffleMonster · · Score: 1

      In some cases you need to know everything that is going out the door. For example if your company is the target of industrial espionage the last thing you want is your trade secrets going out through your firewall.

      I wonder how many companies install these things thinking they have any chance of being effective against such threats?

    2. Re:Necessary sometimes by Zan+Lynx · · Score: 1

      They shouldn't. A simple second level of encryption such as an encrypted ZIP file defeats any automatic scanning for confidential keywords or anything similar.

    3. Re:Necessary sometimes by the+eric+conspiracy · · Score: 1

      Normally you address this sort of stuff by locking down the user's desktop.

    4. Re:Necessary sometimes by Zan+Lynx · · Score: 1

      Well, if I was really into industrial espionage I might do something like bring a USB stick loaded with my zipper program, but instead of storage set to look like a keyboard. Plug it in, open Notepad and have it type the executable out into a file.

      I've noticed that a lot of places disable USB storage but don't disable file execution from writable directories.

    5. Re:Necessary sometimes by idontgno · · Score: 1

      System logging records the plung and unplug actions.

      The mere fact you plugged something in without authorization of IT puts you on the investigation list.

      That's assuming the USB sockets aren't disabled in software and sealed with epoxy. Except the keyboard and mouse, which are epoxied in place.

      I'm not making this up.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    6. Re:Necessary sometimes by linuxrocks123 · · Score: 1

      Other ways you could defeat this:
      - Take a picture of the screen with your camera phone. Yes, they don't allow camera phones, but you could probably smuggle one in. This obviously doesn't work with anything that's too long.
      - Download an executable with the magic number changed to get past the proxy, edit it in notepad to restore the magic number, and then use it to encrypt the media, then upload it to a server under your control, which won't raise red flags because it doesn't see any "bad keywords" because you encrypted it. XOR encryption would probably work here. This requires you to be able to execute programs, yes, but, uh, you could probably use JavaScript in a browser if you really had to. Local site that uuencodes or similar any binary data that you paste in one window and displays it in the other window. Banned local sites, okay, set up a site outside the firewall that does this and gets past the proxy because the proxy doesn't see anything wrong with it because it's not expecting this.

      It would really be pretty hard to do this so it can't be compromised by a motivated attacker. Impossible? If you consider that the system can't be so locked-down no one can work on it, perhaps yes.

      Other programming possibilities: Macros in Word. Java applets. FLASH (shudder) applets. These would be much easier to get working right than a JavaScript thing. You can't use the Internet without JavaScript. Can you use the Internet without Flash? Maybe. Or maybe it would annoy your employees so much they quit because you're making it too hard to do their jobs.

      Really the hardest part of doing this, now that I'm thinking about it, would be the "hex dump" step. Once you've installed the equivalent of a hex dumper -- some way, some how -- you can manipulate that hex however you want to get it past the proxy. After you can dump the secret data to hex, it's game over.

      --
      vi ~/.emacs # I'm probably going to Hell for this.
    7. Re:Necessary sometimes by cbhacking · · Score: 1

      Right. Steganography, for example - and it really doesn't have to be very good to fool a computer - will easily bypass this. Take a zip of sensitive files. Encrypt it. Wrap a BMP header around it. If needed, embed that "image file" into another document (one containing no sensitive info). Email it to yourself or post it to an externally-accessible website. Retrieve the file at home, strip the image metadata portion, decrypt the data, unzip your lovely exfiltrated files. Of course, there are lots of other and possibly cleverer ways to handle this, but the basic idea is nearly impossible for a computer to detect, and if you can make it look close enough to your usual usage patterns it probably won't even get flagged for human review.

      --
      There's no place I could be, since I've found Serenity...
    8. Re:Necessary sometimes by Zan+Lynx · · Score: 1

      How do you expect the keyboard is attached? USB. I've actually seen this, in person. A machine with sealed USB ports ... and a USB keyboard and mouse. Really. What was IT thinking?

      I bet the IT guy who did the job was a contractor. 'Uh yeah, here's a work order to seal up all the open USB ports.' "What about the keyboard?" "Doesn't say. Don't ask questions: its 20 hours of easy work at $60/hr."

    9. Re:Necessary sometimes by Zan+Lynx · · Score: 1

      Just saw the bit about epoxy. MAYBE the keyboard started out epoxied in place but when I saw it it sure wasn't. IT needs to put in a new keyboard, they probably chipped it out and replaced it. Not much would stop the user from doing that either.

  24. Trusted Proxy. by Anonymous Coward · · Score: 0

    Agreed.

  25. its not uncommon.... by Anonymous Coward · · Score: 0

    My employer (a large community college district in California) does something similar. Using Palo Alto Firewalls they are able to intercept the SSL certificate, decrypt the traffic, inspect it, and put it back together again. Unlike in the OP scenario with no indication to the end user. The rationale is that many viruses and botnets use encryption to prevent detection. While i think their hearts in a the right place I think it can potentially open an organization up to litigation if (when) something goes wrong. Imagine your organization does this MITM (attack) and someone in IT performs a deep packet inspection and your bank details, PII or whatever is viewable. Scary thought that a curious shlub in IT (i say that being a shulb in IT) may be reading your gmail conversations, seeing your banking info, and all the other stuff you'd want to keep private. Obviously though at the end of the day, any organization has the right to monitor employees using company hardware.

    1. Re:its not uncommon.... by andymadigan · · Score: 1

      What you're describing would still be visible to someone using their own device on the network, or if they checked the computer's list of trusted certificates and found the one that allowed the firewall to do this.

      I actually disagree that companies have an absolute right to do this. Whatever your policy may say, employees are going to do personal tasks at work. Some activities would fall in to a grey area:
      - Signing up for direct deposit may involve logging on to your bank to get your acct #
      - Some new health insurance plans incentivise participation in "healthy living" programs, including filling out surveys about your personal habits on your health insurance website, that should not be intercepted
      - Emergency communications (which may still be over e-mail, or SMS via google voice)

      Even logging in to one's personal e-mail is to be expected. Except in cases where such security is legally mandated, I don't think it's ethical to implement something like this. Even in cases where it is mandated, a "secure mode" would be better. Perhaps keep the really secure corporate information in a VM that is subject to SSL interception, but provide non-intercepted browser with no access to the secured data.

      --
      The right to protest the State is more sacred than the State.
  26. It happens here by dave562 · · Score: 1

    We deal with highly sensitive client data. All network traffic is inspected. The employees are well aware of it because it is explicitly mentioned during new hire orientation / on boarding.

  27. Man in the middle? by Anonymous Coward · · Score: 0

    This is a security department looking for people who are browsing porn, or using ssl to hide illegal activity. They aren't looking for banking info. (Although it's there) If you are doing banking on a network not your own, then it’s your bad...

    The work computers are not your property; they belong to the company you work for and are for work, plain and simple. If you don't like the situation you can certainly (and should) move on to another job.

  28. Actually looking for a way to do this... by exabrial · · Score: 0

    Malware is pretty easy to download over HTTPs, since an IDS can't fingerprint it. I've been looking for a firewall that can do this reliably, so I'd love to hear solutions that people have found work reasonably well.

    Management has no interest in employee's personal lives. Hence we don't block facebook, youtube, etc. The goal is to keep the company asset's safe. Employees are made aware during their orientation that we have the ability to monitor their computers in every way. The message has been, if you want privacy, use your mobile device (and don't vote for Democrats and their spy programs).

    1. Re:Actually looking for a way to do this... by Anonymous Coward · · Score: 0

      websense, other FWs do it too but you get a lot of detail with WS. setup as transparent proxy and filter all protocols you wish.

    2. Re:Actually looking for a way to do this... by EvilSS · · Score: 1

      Websense makes devices to do this. I have a couple of customers that use it. It does tend to fuck up some websites though.

      --
      I browse on +1 so AC's need not respond, I won't see it.
  29. We do this... however... by Anonymous Coward · · Score: 0

    All banking, finance, government, health, and some other more private info sites are NOT included and go direct (no MITM proxy)... a company who does do MITM on these sites, especially in the health area could be in line for some serious legal issues...

  30. Will be the norm shortly.... by Wandering_Burr · · Score: 1

    As someone that recently spec'd out new firewall hardware for a medium sized company I found this 'feature' available on the latest, greatest boxes. This is the newest way for companies to run Intrusion Detection (for instance looking for CCs or key words in documents leaving the network) as well as throttling Bit Torrent and other undesirable traffic hidden in encryption. I would expect this to become the norm in the next couple of years as Gartner repeatedly writes that thorough IDS is best practice on networks in this day and age. Personally I felt like a mini-NSA and declined to roll this feature out - but I have the luxury of being the decision maker at a small company. If I was spec'ing gear for an enterprise--I'm pretty sure the hunger for latest and greatest to protect IP from the unwashed masses would prevail.

    1. Re:Will be the norm shortly.... by Rene+S.+Hollan · · Score: 1

      There are non-nefarious uses for this: SPAM and virus filtering of encrypted email and blocking of undesirable encrypted web content.

      As for being a mini-NSA, the appliances that I helped develop to do this did not allow unecrypted traffic to leave the box (unless we were deliberately doing ingress SSL-termination), though theoretically someone could hacl the box to do this.

      The best way to assure users of such a proxy that their content is not being monitored is to disclose the make, model, and confiuration of the appliance and, short of a hacked appliance, decide for themselves if the plain text content is constrained to be in the appliance.

      --
      In Liberty, Rene
    2. Re:Will be the norm shortly.... by omnichad · · Score: 1

      What about web sites with fake/invalid certificates already? On a MITM-proxied connection, the user sees a trusted certificate instead. This might be counterproductive in protecting the users.

  31. I use it to protect us. by Anonymous Coward · · Score: 0

    I have a proxy server at the office which does content filtering and AV scanning on everything that comes in and out of the network. This is purely for security reasons to another layer of prevention for malware so nothing is stored and I don't care about the actual content of the data. I started having to do SSL MIM on our proxy server when some users figured out that if they just put HTTPS in front of whatever they wanted the proxy server wouldn't be able to catch it.

    For us it's also clearly stated in our handbook that work equipment and network traffic is subject to periodic monitoring, we do have a separate network for employees that want to connect their personal phones, tablets and laptops which is not filtered but also does not have access back to the production network.

    1. Re:I use it to protect us. by omnichad · · Score: 1

      What about web sites with fake/invalid certificates? On a MITM-proxied connection, the user sees a trusted certificate instead. That's not protecting you - it gives a false sense of security in situations when the user should be wary.

  32. Yes with some exceptions by Anonymous Coward · · Score: 0

    I have seen organizations implement an SSL proxy like this. I am sure most people don't check to see who the certificate was issue by. The clever thing here is that the certificates are generated on demand by the SSL proxy. The organization would whitelist (to bypass the SSL proxy) some domains(mostly financial institutions). gmail wasn't one that was whitelisted. This organization didn't do it without consent, buried in their acceptable use agreement was the SSL proxy and a method to request a domain get whitelisted.

  33. Paranoia by jbmartin6 · · Score: 4, Insightful

    My assumption is that the client logs all HTTPS traffic this way, capturing banking records, passwords, and similar data on their employees

    A completely baseless assumption. I have worked with several organizations who do this "attack" to protect themselves from malicious traffic. I have not yet seen any that logged content. The legal and regulatory risks in doing this are too high to do this sort of data collection.

    --
    This posting is provided 'AS IS' without warranty of any kind, implied or otherwise.
    1. Re:Paranoia by tommyatomic · · Score: 1

      The legal and regulatory risks in doing this are too high to do this sort of data collection.

      Almost every company I have worked for has operated off of the malicious assumption that its easier to violate their employees and issue apologies later. They almost always assume its only wrong if they get caught.

      Paranoia is only wrong if it is illogical, irrational or lacks a historical precedent.

    2. Re:Paranoia by Anonymous Coward · · Score: 0

      Exactly. There are many "innocuous" reasons for this type of behavior.

      Likewise, it COULD be nefarious, too.

      Safest bet? DON'T DO PERSONAL TASKS ON EMPLOYER-OWNED SYSTEMS OR NETWORKS!

      I *NEVER* do online banking on my work machine (which is funny, since I work for a company that makes online banking software.) Even at home, on my own network. I only do online banking from my personal machine. Same goes for mobile banking. I have a work-provided cell phone - but I never do banking from it.

      Twitter/Facebook/Google+? Sure. I don't do anything on those that is fire-able. (Indeed, my Twitter account is occasionally mentioned/RTed by the official corporate account.) But I don't log in to any forums that I would 'be concerned' if my employer found out about, I don't log in to ANY forums using my "most common handle" - so there is no record of that handle on my work machines/networks. (Hence the reason I'm posting anonymously - I'm not logging in to /. with a handle that I don't want my employer to know I have, since I use it on forums I don't want them to connect me to.)

    3. Re:Paranoia by JohnFen · · Score: 1

      It may be baseless, but it's a necessary assumption. A MITM attack means that, effectively, you are transmitting data in the clear. It is good security practice to assume that all such data is being recorded and/or logged.

    4. Re:Paranoia by tgd · · Score: 1

      It may be baseless, but it's a necessary assumption. A MITM attack means that, effectively, you are transmitting data in the clear. It is good security practice to assume that all such data is being recorded and/or logged.

      Then do work at work, and non-work at home.

    5. Re:Paranoia by Anonymous Coward · · Score: 0

      A completely baseless assumption.

      If you work in IT security, a sufficient criteria to assume somebody is doing something nefarious is this: It is possible.

    6. Re:Paranoia by jbmartin6 · · Score: 1

      Indeed. Of course, you should make the same assumption regardless of what "attack" might be present. Any second party who uses the information could be providing it to any number of third parties. At a certain point, you have to take a chance or else not provide the information.

      --
      This posting is provided 'AS IS' without warranty of any kind, implied or otherwise.
  34. So? by Anonymous Coward · · Score: 0

    If this handle you cannot the job quit.

  35. Assume it by invictusvoyd · · Score: 1

    It's retarded to carry out personal transactions over office hardware. As many have pointed out, once "in" the workplace , you aint got any rights.

    1. Re:Assume it by Anonymous Coward · · Score: 0

      i don't know what country you live in, but here in the USA i don't give up my rights just because i punched the clock for the day

    2. Re:Assume it by gurps_npc · · Score: 1
      In correct.

      You should say:

      Once it's 'in' the workplace it is very very hard to assert your rights.

      You retain your rights.

      --
      excitingthingstodo.blogspot.com
    3. Re:Assume it by invictusvoyd · · Score: 1

      That sounds nice . But in reality it aint true. The reality is, there are no rights in a capitalist society. There is just a clever illusion.

    4. Re:Assume it by Zan+Lynx · · Score: 2

      Of course you have rights. So does your employer. And using your employer's network gives your employer the right to see what is traveling over his network.

    5. Re:Assume it by invictusvoyd · · Score: 1

      Correct . The real issue is when employers take their rights beyond the workplace. Is there any doubt that they dont?

    6. Re:Assume it by Zan+Lynx · · Score: 1

      Mine never has.

  36. ATT by Anonymous Coward · · Score: 0

    I was setting up an ATT cellular extender, and I didn't look at it real thoroughly but it seemed to do the same thing, I didn't inspect a cert to see if it was the original or not but it was definitely routing all the traffic through a proxy of some sort.

  37. Same here by DeathByLlama · · Score: 0

    Yep, mine does the same thing. Always unnerving to know that others have access to -- what should be -- encrypted data / passwords.

  38. Is there a way to route through cell phone? by Anonymous Coward · · Score: 0

    I have a Verizon smartphone grandfathered in with unlimited data. Is there a way I could connect it to my work computer via USB and use it for my internet connection rather than the corporate network?

    1. Re:Is there a way to route through cell phone? by JohnFen · · Score: 1

      Yes, look into tethering.

    2. Re:Is there a way to route through cell phone? by crashumbc · · Score: 1

      Check out "PDAnet" for app that doesn't require to be "rooted". Or google "tethering" for your phone type.
      (note: PDAnet requires the ability to install software on the PC)

      Keep in mind most "unlimited" plans this is against the TOS.

      And depending on your corporation may(probably does) violate their HR policies

  39. given up by Anonymous Coward · · Score: 0

    My employer makes it very clear that they monitor everything. There appears to be need for a CA and proxy etc when they have every form of logging under the sun running on all employee machines. For the sake of convenience I have given up on using my phone for banking, personal email etc when it is so much easier to just use my work laptop. I guess I will change all my passwords when I leave.

  40. Yes my former employer General Dynamics does MITM by Anonymous Coward · · Score: 0

    was funny because overnight they pushed out ca certificates into internet explorer so the users were none the wiser. anyone who had firefox or chrome installed immediately saw what was happening and stopped using the corporate desktop to do anything on the internet. this caused tons of problems, especially working in cyber security a lot of sites like tor and squid and red hats cdn were blocked and or hindered from working properly causing lots of problems in my lab. glad im outta there!

  41. Yes by Anonymous Coward · · Score: 0

    Big company. They tell us outright that they do it.

    1. Re:Yes by realxmp · · Score: 1

      I'm surprised Chrome users don't get errors as a result of Google's hardcoded certificate pinning?

  42. Same here by Anonymous Coward · · Score: 0

    My employer, a big bank, does the exact same thing. Interestingly as you say IE doesn't complain about it but firefox does. Also it's only some sites, google is this way but Twitter for example is just rejected if you try to access it over https.

  43. Beware of the leopard^W lion^w mavericks by tepples · · Score: 3, Funny

    and in a sentence beginning with "Beware of the leopard".

    I don't see why the contract has to declare the version of Apple BSD on which the trusted proxy runs. Otherwise, they'd need to get everyone to sign off on "Beware of the mavericks".

    1. Re:Beware of the leopard^W lion^w mavericks by Anonymous Coward · · Score: 1

      For those of you that are to young to remember a world before Justin Bieber, "Beware of the leopard" is a reference to THGTG (aka "The Hitchhiker's Guide to The Galaxy") written by the late DA (aka Douglas Adams)

    2. Re:Beware of the leopard^W lion^w mavericks by SJHillman · · Score: 1

      If you're going to write out the title and author, why bother abbreviating it in the first place?

      Personally, I read it as XKCD #1031

  44. They do it here, and yes, it's a MITM by Anonymous Coward · · Score: 0

    It's becoming more and more common

  45. Mobile phone hotspot by Anonymous Coward · · Score: 0

    What are you doing using THEIR network thinking you have any privacy? Regardless of VPN or not?

    When on-site with a customer, I always use my own equipment (laptop, tablet, etc) connected to my own phone's wifi hotspot (or tethered) to connect back to my own business systems.

    (Posting as AC because I lost my ~1997 account long ago and can't bear the shame of a new one with a high uid)

    1. Re:Mobile phone hotspot by JohnFen · · Score: 1

      (Posting as AC because I lost my ~1997 account long ago and can't bear the shame of a new one with a high uid)

      Suck it up, buttercup! I lost my old (5 digit UID) account long ago, and had to make a new one. The shame passes with time.

  46. How can I check? by suutar · · Score: 1

    I don't know if my company does this. I wouldn't be surprised if they do; many folks have already mentioned reasons why it might be desirable (for them) that aren't malicious.

    But I want to know whether it's happening so I can decide if I want to change my behavior. How would I go about checking for such things on a Windows 7 Professional laptop?

    1. Re:How can I check? by ImprovOmega · · Score: 1

      Don't use your work laptop for personal things at work. Simple, problem solved. Use your phone, tablet, personal computer+hotspot, whatever, just don't use company resources on company time to deal with personal things. Or if you do accept any possible consequences.

    2. Re:How can I check? by suutar · · Score: 1

      That would simplify matters, but it doesn't really answer my question. Thanks, though :)

    3. Re:How can I check? by Anonymous Coward · · Score: 0

      Great non-answer to the ACTUAL question. Please try again.

    4. Re:How can I check? by Anonymous Coward · · Score: 0

      go to an ssl enabled website and check the certificate chain. In IE click the lock icon in the address bar and view certificates. go to certification path and see if there's a certificate in the path that appears to be assigned to your company.

  47. In the same boat by Anonymous Coward · · Score: 0

    Yep--my company does the same thing and because they are attempting to do it "under the radar" it has caused a whole lot of issues and wasted time for many folks trying to "fix" problems it has caused. In several cases it was blocking automated updates for Microsoft Windows, Wordpress, and several Linux distributions because the update software wanted to see the vendor-issued cert.

  48. The NetGear, NetSecure RTM does this by Anonymous Coward · · Score: 0

    I recently implemented the same thing at my previous company. This is common, useful for the firewall to track things easier; got both sides of the client/server covered. --- genious! Waiting for our ISP's to do the same thing at the ISP level... then we're doomed!

    1. Re:The NetGear, NetSecure RTM does this by ttucker · · Score: 1

      This type of thing mostly requires the client computers to trust a CA that the firewall uses, so the ISP would need administrator style access to the target machines. Unlikely.

  49. It's pretty common. by Anonymous Coward · · Score: 0

    What the proxies "Usually" don't re-encrypt are Banks and other financial institutions that contain your PIAA. It's mostly so see what you're doing, breaking any laws while on company property and posting bad comments about the company via HTTPS. Basically the data is there if you get audited or investigated.
    So as long as you're clean, there should never be a worry.

    1. Re:It's pretty common. by ttucker · · Score: 1

      So as long as you're clean, there should never be a worry.

      Sounds kind of Soviet...

  50. Deep Packet Inspection by The_Systech · · Score: 1

    it's actually fairly common for any fairly new generation firewall that does Deep Packet Inspection for Intrusion Prevention, Content Filtering, etc. The firewall has to be able to view the data unencrypted to scan it for the "normal" stuff. Nothing overtly hostile in the intent there, just the way it works.

    --
    To err is human, but to really foul things up requires a computer
    1. Re:Deep Packet Inspection by Anonymous Coward · · Score: 0

      DPI does not circumvent encryption though.

  51. A Wolf in Sheeps Clothing by Anonymous Coward · · Score: 0

    Just because they set it up to look like a trusted proxy, it defeats the trust of HTTPS. Are they wrong for doing this? That's debatable.

    1. Re:A Wolf in Sheeps Clothing by Anonymous Coward · · Score: 0

      Just because they set it up to look like a trusted proxy, it defeats the trust of HTTPS. Are they wrong for doing this? That's debatable.

      Yep. There is a known security vulnerability for Windows if you MITM HTTPS for Windows update. There is a forged Windows cert floating around out there that is quite old and uses MD5. Even though it is no longer in use, if your proxy blindly accepts this cert, there is no way for the end machine to know the invalid cert was used. It puts the responsibility of validation on the proxy.

  52. Yes by RobinH · · Score: 1

    This is a very common way to solve the problem of "how do we do a virus scan on files coming in through https?" Many organizations run a proxy server for all web requests to be able to filter content, and to do anti-virus checks, but obviously it needs to view the unencrypted content to be able to do a scan. Otherwise any employee could be downloading malicious content straight through your firewall and bypass all the checks you have in place.

    --
    "I have never let my schooling interfere with my education." - Mark Twain
  53. Pass the blame to employees visiting such sites by tepples · · Score: 1

    in many countries regulations prevent snooping of traffic to websites related to health or banking

    Watch for language in your employment agreement to the effect: "Employees outside the group health insurance and financial departments MUST NOT access health or banking sites through the company network."

    1. Re:Pass the blame to employees visiting such sites by cbhacking · · Score: 1

      In that case, it is legal to do the following:
      A) Block access to those sites.
      B) Fire employees who attempt to access those sites (whether or not successful).

      A proxy is perfectly capable of handling either or both of these (well, probably not the actual firing, but raising a ticket about it) *WITHOUT* intercepting the traffic. Such interception would still be illegal.

      --
      There's no place I could be, since I've found Serenity...
    2. Re:Pass the blame to employees visiting such sites by tepples · · Score: 1

      A proxy can block access to those sites only if it has a comprehensive list of those sites. This raises the question of how to make such a list.

  54. pointless political attack by Chirs · · Score: 1

    The message has been, if you want privacy, use your mobile device (and don't vote for Democrats and their spy programs).

    Do you honestly think that a Republican government wouldn't do just as much spying?

    1. Re:pointless political attack by cbhacking · · Score: 1

      Of course not! Snowden blew the whistle during the Obama administration for a reason! Surely you don't think any of those programs go back further than 2009, do you?!? </sarcasm>
      Fuck them both. Idiots like the GP, with their partisan blindness perpetuating the stupidity, are part of the problem.

      --
      There's no place I could be, since I've found Serenity...
  55. Happens in more paranoid outfits by Antony+T+Curtis · · Score: 2

    A previous employer, a game company whose name rhymes with lizard, uses MITM proxy ... All their machines use their custom cert so that their made-up cert shows 'green' on the location box when any user uses a secure web site.

    --
    No sig. Move along - nothing to see here.
    1. Re:Happens in more paranoid outfits by Anonymous Coward · · Score: 0

      Maybe you should report them to the DA for violation of the DMCA which is a criminal offence. Breaking end-to-end encryption on a copyrighted data.

  56. I had the same issue but worse by erroneus · · Score: 1

    I worked for a nuclear technology company and they set up a box which did this on the guest network. I threw up all sorts of warnings why this was a bad idea but our network security guy who cared nothing about the businesses and government entities we came into contact with, insisted that this is the way it should be done. Eventually some form of it disappeared while some other aspects remained. But seriously, how do you think the various large utilities and the NRC would feel about their secure traffic being sniffed while their representatives and executives are in the office?

    Kinda breaks some trust issues doesn't it?

  57. It's not a violation... by Overzeetop · · Score: 1

    It's not a violation if the company isn't bound by HIPAA regulations. I this case, for a generic corp, it's just a terminal and internet access.

    --
    Is it just my observation, or are there way too many stupid people in the world?
  58. Rare +6 comment by Overzeetop · · Score: 0

    Seriously, it's not an "attack"

    --
    Is it just my observation, or are there way too many stupid people in the world?
    1. Re:Rare +6 comment by JohnFen · · Score: 1

      How is it not an attack? I don't understand the argument.

  59. Yes by Greyfox · · Score: 1
    And I expect all employers to do this as a matter of course. That means that if you read your personal E-Mail at work or do online banking there, your employer probably also knows your passwords and the contents of your mail. Keep that in mind before conducting your personal business (or job search) at work.

    I also expect them to be very aware of who you call from the phone at your desk.

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  60. Assume they do. by Anonymous Coward · · Score: 0

    I'd say that any organization over 100 employees it's safe to assume they do perform MITM. If you can, get a copy of PuTTY installed and run an SSH tunnel to a remote server on a random port, or even something like 8080 to appear like you're just accessing your home router's web gui, then proxy all your web traffic through that. Periodically check to see if the certs on your local machine have changed.

  61. not at all what you think by slashmydots · · Score: 1

    The author is an idiot and doesn't get what's going on. By default, Cyberoam products do this. They issue their SSL cert to everyone at the company and then intercept all 3rd party ones to check them. They claim their list of revokes certificates is better than your browser's or whatever. I turned the feature off because it broke Activesync and like 8 other things.

    1. Re:not at all what you think by JohnFen · · Score: 1

      So you give an example of what the OP is talking about, but he's an idiot? Huh?

  62. Very common in larger businesses by s13g3 · · Score: 1

    This is very common in large, enterprise-class businesses with significant numbers of PC's dedicated to end-users, as this methodology is used in various ways to provide security (to the enterprise, while simultaneously robbing the end-user of theirs in favor of the business'). The services provided by companies likeZScaler would be perhaps the most common use of these types of MITM attacks.

    --
    "Inveniemus Viam Aut Faciemus" 'We will find a way... Or we will make one!' --Hannibal of Carthage
  63. You mut not be familiar with HIPAA.... by Anonymous Coward · · Score: 0

    This is fairly common in healthcare - and I suspect in other regulated industries - where the possibility of employees leaking confidential information is more than just a technical irritant.

    Fines and consequences for even inadvertent leakage can be devastating - individually and to the business.

    Reference: http://www.hhs.gov/ocr/privacy/

  64. Oh yes by Anonymous Coward · · Score: 0

    Previous company I worked for did this.

    I really annoyed me as they did not notify anybody that the new proxy was doing a MITM.

  65. As frequently as possible. by Anonymous Coward · · Score: 0

    My employer makes devices that do this MITM interception. My job is to help companies (150-1500 users) implement it in their network. Most of my customers want the benefits of it, many of them don't have the resources to redesign a small network to implement it. (It's hard in a mixed environment with unmanaged IOS/Android devices if you suddenly start globally intercepting their HTTPS traffic.)

    They may not be intercepting passwords, but as far as prevalence goes, it's quite common. The MITM is the most robust way of filtering/reporting/scanning traffic. IP blocking isn't effective anymore (this isn't 1997) and SNI inspection is less intrusive, but has some idiosyncrasies.

    I see a whole range of reasons, from "we don't care what people do, we just don't want anyone surfing for porn or getting viruses" to absolute draconian "give me a weekly report of everyone who is looking at job search sites or using profanity in email".

    As a user, you have no idea what the company is really doing. Make sure you read your employer's IT Acceptable Use Policy, and hold them to it. As a traveler, treat every network as hostile; whether it's a company internal network, guest wireless, hotel, coffee shop, or library.

    Also, try masquerading your VPN as DNS traffic if they're intercepting HTTPS. :-)

  66. My employer does. by Areyoukiddingme · · Score: 1

    My employer does this, using Bluecoat, and doesn't tell anybody about it. Even my colleagues who are programmers aren't necessarily aware of it.

    What's bizarre is the Bluecoat proxy will claim in its boilerplate that it's doing it for network security reasons, but.... they issue everyone in the company a laptop and actively encourage employees to take their laptops home at night. None of the new-hires even have a desktop at all, and veterans only get to keep an old desktop if they can prove the OS licensing is independent of the licensing the IT group administers.

    So... network security? Prevention of funneling company secrets out through the firewall? Ha.

  67. Just don't use the employer's Internet by bobbied · · Score: 2, Informative

    Shesh, Really? Man in the Middle "attack" ? Give me a break.

    If you are using an employer's resources to surf the internet just figure that *everything* you do is monitored. If you don't want to be monitored, GO HOME. If you don't trust your employer, GO HOME to do anything you don't want them to see. GO HOME or use your own internet access.

    Don't try to make this into some "privacy" issue. It's not.

    --
    "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    1. Re:Just don't use the employer's Internet by Anonymous Coward · · Score: 0

      Most workplaces get the internet.
      Just use TOR!

    2. Re:Just don't use the employer's Internet by JohnFen · · Score: 1

      If you are using an employer's resources to surf the internet just figure that *everything* you do is monitored.

      Absolutely correct. And one of the ways they monitor network traffic is by performing MITM attacks. Why do you think it's ridiculous to say so?

    3. Re:Just don't use the employer's Internet by Anonymous Coward · · Score: 0

      It is. Unless you won't object to a camera on you which records everything all day long, even when you're taking a dump, where you are using company equipment. Their network, their crap.

    4. Re:Just don't use the employer's Internet by bobbied · · Score: 2

      Because it's NOT an attack, It's an employer monitoring the use of it's resources by it's employees.

      If they are paying for the internet access, paying to have a proxy installed, paying to have the browsers on their machines set up to trust their certificates, they are doing it to themselves. It's not an attack, or a hack or anything of the sort, it's there to monitor the systems they own which is their right. They can do what they want to the traffic entering/exiting their network, including using proxy servers, firewalls and filters to allow, monitor or deny anything the see fit.

      Some employee claiming this is a Man in the Middle "attack" is inaccurate and misleading. It's a HTTP/HTTPS proxy.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    5. Re:Just don't use the employer's Internet by Anonymous Coward · · Score: 1

      You don't relinquish your Constitutional rights simply by walking onto your employer's property. I know Libertarians have pipe dreams about such a "utopia," but that's not how Constitutional law works.

    6. Re:Just don't use the employer's Internet by Anonymous Coward · · Score: 0

      My employer lets me receive personal physical mail at my work address. If they were steaming my letters open and reading them, I'd be pissed, and they'd be in for a lawsuit. How is this different?

    7. Re:Just don't use the employer's Internet by Anonymous Coward · · Score: 0

      Think of it this way; if you were to put an unsecured wifi access point in a public area and state on a splash page that all traffic may be inspected and start scooping up people's bank account details, that would be considered a crime punishable by jail time. When a corporation does the same thing to the captive audience that is their own employees, they are merely protecting their assets.

    8. Re:Just don't use the employer's Internet by jez9999 · · Score: 1

      If you are using an employer's resources to surf the internet just figure that *everything* you do is monitored. If you don't want to be monitored, GO HOME. If you don't trust your employer, GO HOME to do anything you don't want them to see. GO HOME or use your own internet access.

      I don't buy this argument. What if your home ISP started snooping on HTTPS traffic? "Their network, their rules", right?

      Nobody owns the entire internet; it's a ton of networks connected together. There needs to be a common societal acceptance of a reasonable expectation of privacy when using an internet-enabled computer unless there's a damn good reason not to have it, and "scanning web pages for viruses" is a pathetic excuse for potentially snooping on all SSL traffic.

    9. Re:Just don't use the employer's Internet by bobbied · · Score: 1

      If you are using an employer's resources to surf the internet just figure that *everything* you do is monitored. If you don't want to be monitored, GO HOME. If you don't trust your employer, GO HOME to do anything you don't want them to see. GO HOME or use your own internet access.

      I don't buy this argument. What if your home ISP started snooping on HTTPS traffic? "Their network, their rules", right?

      Nobody owns the entire internet; it's a ton of networks connected together. There needs to be a common societal acceptance of a reasonable expectation of privacy when using an internet-enabled computer unless there's a damn good reason not to have it, and "scanning web pages for viruses" is a pathetic excuse for potentially snooping on all SSL traffic.

      Different thing. If your ISP intercepts your HTTPS traffic, you WILL know because of the certificate errors it would cause. But, you'd never know if they proxy HTTP. In fact, I'd bet your ISP DOES track your usage though DNS snooping if not though transparent HTTP proxies. But you'd never know if they do or not. I'm really sure my ISP (Verizon) does track stuff like this, just based on the kinds of SPAM they choose to deliver to a largely unused E-mail account on their servers. But monitoring by ANYBODY who handles your packet is possible, which likely extends beyond your ISP.

      If you are using your employer's assets to access the internet, just figure on having zero privacy. Common sense or not, it's their equipment, not yours. They can configure it anyway they choose, and if that means they monitor HTTPS traffic, then that's what they do. Common sense says they own the computer, the network equipment and are paying for the internet access, so they can put any policy they choose in place about it's use by their employees. If that means you consent to monitoring of HTTPS traffic, so be it.

      This "social acceptable" argument doesn't wash. At work, what you do online is NOT private and is directly traceable back to them. They can search your desk, your hard drive, and your E-mail, so why do think they somehow have no rights to do this?

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    10. Re:Just don't use the employer's Internet by idontgno · · Score: 1

      Other than the high likelihood that you're either an anonymous troll or an ignorant blowhard (or both), you need to explain why the Constitution has one damn thing to do with this.

      Or did you sleep through the part of Civics class where they discussed the Contitution's protection of rights extends to limiting the actions of government... and absolutely no further. Private action (such as a non-governmental employer) are not in any fashion constrained by the basic protections of the Constitution. Laws, almost certainly. But since you named the Constitution explicitly, you need to be called on it explicitly.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    11. Re:Just don't use the employer's Internet by jez9999 · · Score: 1

      Desk, hard drive, and email are all things that are actually physically located/stored with the employer, or on their equipment. HTTPS traffic, though, is merely going through their equipment and should not be being stored anywhere by them. That's the distinction I see and sure they own their part of the network, which is why I said there needs to be a societal acceptance of what a reasonable expectation of privacy is on any computer network that other people are allowed to access, just like there is with not being able to take camera shots up women's skirts, etc.

    12. Re:Just don't use the employer's Internet by bobbied · · Score: 1

      You are making a very fine distinction here. They can look at your hard drive, but they cannot look in the memory of the machine they own because their employees have an "expectation of privacy"? After all, most network equipment is "store and forward" where each packet is in memory as it flows though so you are claiming that anything in transit (i.e. in memory) is not something they can look at?

      I don't think you can make this distinction. They own the equipment, they can monitor *anything* you do using any means they choose. If they want to install key loggers and screen scraping software to monitor what you do on their equipment, they are free to do so.

      I think what should be socially accepted is that you don't do stuff you'd want to hide from your employer when on their equipment or in their facilities especially when "on the clock". So go home or use your smartphone on your data plan if you don't trust your employer to not scrape your bank account login information or something.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    13. Re:Just don't use the employer's Internet by Anonymous Coward · · Score: 0

      I think your choice of phrase explains this. "My employer lets me...."

      My wife's employer (mom & pop consulting shop) opens all (paper) mail that comes into the office. It's weird, but they pay the rent on the office.

      Needless to say, we get packages delivered to our home now. Also, she does all her personal surfing on her phone. Everyone is (reasonably) happy.

  68. SSL Interception by KingSkippus · · Score: 5, Interesting

    Yes, it's actually extremely common. Google "SSL Interception", as that's the name of the feature that is advertised on hardware/software that performs this function.

    This is why I never browse private web sites on work hardware. You simply do not know how they've mangled the machine, what all it is revealing or to whom. (That's right, most large companies actually outsource security, so all of your private account numbers and passwords are going to third parties that you don't know and never will, third parties who have been indemnified and are completely immune to any kind of action or recourse from you if they screw up.) If I want to browse the web, I use a VPN connection to my house and my own personal laptop. I don't use my work smartphone for Facebook or personal email, I have my own personal phone using my own provider. When I'm working from home and VPNed into the office, I don't use my personal workstation for any work stuff, except as a VirtualBox host for a work VM, which my company has altered through group policy and direct installation of software to be configured how they want.

    It's a shame that in today's work environment we have to worry about such things, but if you think the NSA is bad about spying on you, it's small potatoes compared to what your own company does. Never trust your company to just be innocently looking for malware or other intrusion detection means. Never install any software or services on your personal equipment from your company, no matter how much more convenient it will make your life. (This includes, for example, accepting elevated permissions to connect to your work email on your personal phone.) Always assume that they're watching you, looking for anything that can be used to fire you, cancel your severance, or extort whatever they want from you, whether you're just a paean on the low rung of the corporate ladder or the CEO.

    I've worked very closely with both the network and security people in a large multinational corporation, and I've seen firsthand the kinds of things they do. It ain't pretty. I've seen people leave because they have moral qualms with the kind of monitoring that goes on, and people screwed because something innocent that everyone does was turned into a major issue. I cannot emphasize this enough; never, ever, ever mix your personal life with your work life, especially when it comes to communications and technology.

    1. Re:SSL Interception by Anonymous Coward · · Score: 0

      Agreed!. There are plenty of companies who do this. The most common scenario I have come across is to have a DLP to look for data flowing out of the network. If the employer does not want Credit Card information or SSN's flowing out of the network in email, uploaded to dropbox etc, a "MITM" is the only way to do this (as a technical control). There might be regulatory constraints that companies have to adhere to which necessitates the use of trusted proxies and/or DLP.

    2. Re:SSL Interception by NJRoadfan · · Score: 5, Interesting

      Relevant link: https://www.grc.com/fingerprin... This is one reason why companies are opposed to non-IE web browsers. Firefox has its own cert store for example.

    3. Re:SSL Interception by jez9999 · · Score: 1

      But beware Google Chrome on Windows; it uses IE's cert store.

    4. Re:SSL Interception by Anonymous Coward · · Score: 0

      Easily worked around on a domain computer.

    5. Re:SSL Interception by cbhacking · · Score: 1

      There's also the (experimental, draft, whatever" standard of "HTTP Public Key Pinning". Same idea as HTTP Strict Transport Security (which is becoming more widely supported, though not yet widely implemented server-side), but where HSTS merely requires that future connections to a given site must be over HTTPS (this blocks things like SSL stripping), HPKP requires that for a connection to the site to be trusted (now or in the future), the thumbprint of its public key (or that of the signing cert, perhaps, for agility) must be as specified in the header.

      Of course, like HSTS, it's a trust-on-first-use scenario; if the proxy begins editing the HPKP headers (which it could do easily; just set them to the cert it's using to intercept all your connections), everything will appear fine until/unless you try connecting *without* that proxy in the way. Of course, if HPKP is implemented (in both client and server) before the proxy learns to handle it, you're going to get a whole lot of certificate errors...

      --
      There's no place I could be, since I've found Serenity...
    6. Re:SSL Interception by Anonymous Coward · · Score: 0

      So true!

  69. You would be suprised by Anonymous Coward · · Score: 0

    This is extremely common for any number of reasons. And yes, the information does get logged. You are on the companies time when you are at work and they have the right to monitor what you are doing. You want your banking passwords not to get logged? Don't do online banking from work.

    Here is an example of the software that my company uses, and it literally logs everything:
    http://www.spectorsoft.com/products/SpectorPro_Windows/

    1. Re:You would be suprised by jbmartin6 · · Score: 1

      it is not "extremely common" for employers to log employee's banking passwords or other credentials. By all means produce some evidence if you think I am wrong.

      --
      This posting is provided 'AS IS' without warranty of any kind, implied or otherwise.
  70. FF Extension to notify which sites are MitM'd by Anonymous Coward · · Score: 0

    SSL Bluelight extension for FF is designed specifically for users in these organizations to keep aware of the sites where organizational PKI based SSL inspection is occurring. Many organizations don't MitM all SSL traffic, just some categories, so it's often useful to have conspicuous notification when big brother is watching.

    https://addons.mozilla.org/en-US/firefox/addon/ssl-bluelight/

  71. Hmmm by koan · · Score: 1

    When I worked for a "Large Corporation" I used SSH to my home computer and did my "surfing" over that connection, now I wonder how secure that was =)

    --
    "If any question why we died, Tell them because our fathers lied."
    1. Re:Hmmm by The+RoboNerd · · Score: 1

      Depends, did you ever notice a different key from the server? Did your SSH client warn you that they server key was different from what it had remembered?

    2. Re: Hmmm by Anonymous Coward · · Score: 0

      Nope, and no one from security talked to me about a 9 hour SSH connection either.

  72. common, but... by Anonymous Coward · · Score: 0

    Most enterprises use products that have decent databases with which to categorize the browsable internet, and explicitly choose to not intercept financial and banking sites.

    Pretty much every large enterprise forces everyone to sign something acknowledging that anything they do over the company network may be monitored and recorded. Assuming otherwise is really silly, regardless of the error messages, or lack thereof, displayed by your employer-supplied web browser.

     

  73. My company does this by bradgoodman · · Score: 3, Informative
    They do this with most "big" web sites - but not all (or many little ones). The pre-install their own root CA, so the web browser doesn't complain - but if you bothered to click on the padlock icon - you can tell the cert is signed by our IT department, not by whoever you think you're talking to.

    So we know it's happening - it's not really "hidden" - so I'ts up to me if I want to use Facebook or GMail or whatever - knowing the connection could be snooped. If I don't like it - I can simply not use those services from work.

  74. It is called a proxy by SillyKing · · Score: 1

    It is very common for a company to install a proxy server that decrypts traffic to the outside and inspects with a data loss prevention type tool. Proxy servers act as MITM attacks to be effective at decrypting SSL traffic so it can be inspected.

    It is not as common that you would be allowed to connect to this employers network. Network access control should be in place to prevent vendors or employees from connecting potentially malware laden computers to the internal network. At the least, if you gained access to their network, the same proxy that performs the MITM attack should also be prompting for authentication to access the Internet.

    SillyKing

  75. Not in the EU by Anonymous Coward · · Score: 0

    In most, if not all, EU states this would be highly illegal. Not even a standard form written consent would allow such usually.

    1. Re:Not in the EU by ledow · · Score: 1

      Not really.

      State the law they are breaking by fulfilling their legal obligations to monitor the security and integrity of their OWN computer network.

      There isn't one. It just depends on whether they access that data as a source of personal information or not, and then they are at best subject to the Data Protection legislation - which pretty much is fine so long as you inform people of what you're doing (which all these places will do, with an AUP for the network).

      Don't do crap on company time that you think you have to hide from the company. And that counts what you do at lunchtime, as I bet they don't (and can't reasonably) make an distinction between those actually on a lunch break using the machines for personal purposes and those working through lunch using the machines for company purposes.

    2. Re:Not in the EU by mrbester · · Score: 1

      Taking just interception of banking logon details as an example:
      Misuse of Computers Act.
      Human Rights Act.
      Regulation of Investigative Powers Act.
      Data Protection Act.
      A whole bunch of other laws about obtaining confidential information that is nothing to do with the business.

      --
      "Wait. Something's happening. It's opening up! My God, it's full of apricots!"
    3. Re:Not in the EU by fullmetal55 · · Score: 1

      note: The only example the OP has about this is google maps which is not a banking site.

      most proxies have a built in (often on by default) passthrough for SSL to banking, health, and finance sites. which bypasses the MITM scanning of the financial, health and banking sites.

      Also most proxies don't have a method of actually seeing what was decrypted. it's generally decrypted scanned, and passed through, and discarded. no logging of personal info. other than authenticated username (domain credentials, so information the company already knows) and the site you went to.

    4. Re:Not in the EU by mrbester · · Score: 1

      That means relying on the whitelist to be a) accurate and b) kept up to date. Not particularly reassuring.

      Even intercepting the OP example breaches the laws I listed although most people don't give two hoots if their GMaps traffic is snooped. They do have a problem with financial sessions being intercepted however...

      --
      "Wait. Something's happening. It's opening up! My God, it's full of apricots!"
  76. This is a standard feature on McAfee proxies by Anonymous Coward · · Score: 0

    https://kc.mcafee.com/corporate/index?page=content&id=KB64350&cat=CLEANBOOT&actp=LIST

    My last employer was running McAfee proxies (Linux with a proprietary app), and to my surprise they were *not* using this option.
    It was at a McAfee class that the instructor pointed out this is a textbook MITM attack.

  77. Why is this legal? by Richard_J_N · · Score: 3, Interesting

    As the operator of the webserver, I certainly don't consent, even if the employee had no choice..
    Is there any way to detect this server-side?

    1. Re:Why is this legal? by ledow · · Score: 1

      Nope.

      And your consent doesn't really matter. Your public publishing of information to a public network means that, as much as you might like, you can't really control what the end-user does with it. You could argue about it until the cows come home, but that's the fact of the matter - you can't really stop people doing this and - to you - it's impossible to tell the difference between a request from a proxy server doing this, a request from a proxy server not doing this, and a direct client connection.

      And your disagreement with the methods used by people accessing your website really means nothing. If it did, adblockers, alternate browsers, mobile-data-compressors, etc. would be illegal.

    2. Re:Why is this legal? by Anonymous Coward · · Score: 0

      It can be detected, but afaik not without user interaction.

      You need to ask the visitors to look up the connection properties in their browser and compare or post the fingerprint of the SSL key.

    3. Re:Why is this legal? by maswan · · Score: 1

      DNSSEC. And hoping for client verification at some point in the unknown future. Good luck!

    4. Re:Why is this legal? by Anonymous Coward · · Score: 0

      You can try dropping all HTTP requests with the x-forwarded-for header but most proxies give you the option to disable this setting and most network proxy admins do.

    5. Re:Why is this legal? by Anonymous Coward · · Score: 0

      Is there any way to detect this server-side?

      Not that I'm aware of, and I implement SSL decryption for clients quite regularly. Also, your consent or lack thereof is completely irrelevant.

    6. Re:Why is this legal? by jopet · · Score: 1

      How can secretly accessing the private information of the people accessing the web site NOT be illegal? Where are you living? You need some decent laws over there, if it really is not illegal to do this.

    7. Re:Why is this legal? by Richard_J_N · · Score: 1

      How does DNSSEC help?

      I'd like (ideally) to write a php script that would detect when my users are on "compromised" machines, and warn them.
      What I want is to write some javascript that would send back to the server what the client *thinks* is my certificate fingerprint.

    8. Re:Why is this legal? by cbhacking · · Score: 1

      Well, you could try HTTP Public Key Pinning, but not many clients implement it yet and some proxies might just re-write the headers too. You can tell your users how to check, of course, but good luck getting many to do that. Otherwise, unless you use TLS client certificates, not really. One client's key looks much like another's...

      --
      There's no place I could be, since I've found Serenity...
    9. Re:Why is this legal? by HiThere · · Score: 1

      You don't know his use case. He may have a very good reason.

      FWIW, I don't know how to do it either, but I don't do web programming, so that's not surprising. But I would expect that there would be some client-side javascript, or possibly java, that could acquire and retransmit the information.

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
    10. Re:Why is this legal? by Anonymous Coward · · Score: 0

      Not easily, no. Network address translation (NAT) and Socks/HTTP Proxy Servers both consolidate IP traffic to a smaller number of IP addresses than are on the inside of a company's LAN. So to the website there would be little difference between the HTTPS interception and non-encrypted NAT or Proxy activity going on. Even if there were a protocol where the HTTPS client would some how send back a challenge response based on the public key in the X.509 certificate, that could be intercepted as well, especially if there were a standardized protocol for this post-SSL-Key-Exchange secondary authentication.

      The only way would be for bi-directional X.509 SSL authentication. The web server would issue an X.509 certificate and private key, and sign that certificate (signed by the website's personal CA). The client installs the certificate in his/her browser for bi-directional SSL authentication. If the client's certificate doesn't match the client's identity as confirmed by user name and password, the setup fails.

      But a clever network operator could steal the X.509 certificate, private key, user name and password before sending it off.

      A perfect solution would be to put a password on the private key, and transmit that out-of-band from the network (like in a text message). So that the network operator would have to have access to the machine while the PK was installed, not just capture it while it transitions over the network.

    11. Re:Why is this legal? by bored · · Score: 1

      Is there any way to detect this server-side?

      Yes, and no.. Its detectable client side with javascript on certain browsers. You could then post the information back to your server and blacklist/whatever the resulting IP (likely behind NAT which would then affect the browsers that you cannot detect it on).

      For examples with firefox see:

      https://developer.mozilla.org/...

    12. Re:Why is this legal? by Richard_J_N · · Score: 1

      That would be ideal, but it requires elevated privileges (no idea why that should be). So I'd have to put it in a firefox extension.

      I'm trying to protect normal users who may not be aware that their employer is MITMing them by providing them with a web browser which has been misconfigured into trusting the cert of an SSL proxy appliance.

    13. Re:Why is this legal? by bored · · Score: 1

      Or maybe flash it has a serverCertificaticate method you can call on a socket to retrieve the certificate.

  78. MITM necessary evil? by LordJehovah · · Score: 1

    Long time security worker here...here's my two cents. To answer the original question: How common is it? I don't know the exact stats, but I'd say its common enough that you should just assume the company you work for is doing something like this unless they explicitly say they aren't (which I've read a few posters to this thread have said as much). From my perspective, theres a major reason why a company would choose to implement such a technical control: to prevent loss of intellectual property or sensitive data. Because of encryption in transit techniques like SSL, it makes it very difficult to inspect such traffic for the presence of things the company is concerned about - things like source code, financial data, credit card info, health care info, etc. What's to stop an employee from emailing out the crown jewels thru their Gmail account, assuming there are permissive web filtering policies in place? One answer is to inspect SSL traffic - and the way you do that is MITM. And not only are companies trying to stop disgruntled employees, they're also trying to stop malware - the trend now is for malware authors these days is to no longer exfiltrate data using clear text protocols like http, but to encrypt it via https. Keep in mind that a traditional defense in the distant past (10 or so years ago) for security folks has been wire tapping, and connecting the resultant data feed to some kind of inspection engine like an intrusion detection system. Increased use of encryption, both driven by right-thinking consumers and malware authors, defeats such wiretap efforts, so its no longer effective to simply watch the data fly across the network; now security admins (or intrusive nation states) have to find creative ways to decipher it to see what the data looks like. MITM is fairly cheap to do this. I don't think most companies want to snoop your encrypted traffic outside of the above stated reason. But some companies can/will abuse it and read your emails to see who you're sleeping with, if you have any side businesses going on, if you're looking for another job and sending out your resume, etc.

  79. Nope by Anonymous Coward · · Score: 0

    I work at a f500 in the security department. I can say for sure we don't, I would have raised a fit! That said... we're not in software.

    I will say this though, beware of corporate PKI CA's... they can be loaded into your certificate stores via corporate images... for the suckers that run it...

    Corp CA's can be just as dangerous if they specify a wildcard(again, we don't but... others might).

  80. Very common. by ledow · · Score: 0

    It's not an attack.

    They almost certainly got their employees to sign or otherwise agree to an IT policy that allows this.

    How common? Very common. Anywhere that deploys a decent web filter, most likely. Schools, colleges, universities, I've seen this in an awful lot of them.

    Commercial places do it too. There's no difference. And if you're on work time, using work resources, including paid-for work connections then - guess what - they have a responsibility to monitor what you're doing with it. If they don't it could lead to all sorts of problems with their ISP, for example - you can't just say "Sorry, didn't know our employees were hacking other networks... but you can't cut us off for that", it does not wash.

    If you don't want your employer to find out what you're doing...

    WHY NOT... you're on work time, on work computers, on work resources - what the hell are you doing that they shouldn't know about?

    Outside of that, use a personal device. Personal devices banned? Tough. Go outside and use it out there.

    Your employer owns your computer network. They employ a guy whose responsibility it is to secure it, protect it, and ensure they can follow up on any reports of malicious or illegal behaviour - everything from internal abuse of database privileges to sending their customer database to a rival, to someone accessing child porn or "hacking" a rival company.

    That person will have told you what they are doing and why. You just might not have read it first.

    Don't like it? Don't browse Facebook on company time.

    It's like saying "God, when my friends come into the shop, the guy who owns the shop could listen to us and time how long we're talking". Same thing, different technology.

    There is privacy. There is personal privacy. And then there is the expectation of an employer to provide you with free, untraceable facilities that you could misuse to slack off or cause them damage. One of these does not fit inside a corporate workspace. Guess which one.

    If they were spying in the toilets, fair enough.
    If they were looking up your personal life from work, fair enough.

    But they are monitoring what YOU are doing, in terms of non-work-related activities, while you're on work time and in work premises, on a work-provided resources.

    And, no, unless it specifically says they won't listen at lunch time, you're still on work time. Because that network still needs protecting and auditing even at lunch time because you STILL have access to work data.

    Don't like it, take your phone out with you for lunch and do your personal browsing there.

  81. What if? by Anonymous Coward · · Score: 0

    The arguments: we dont scan bank connections, we dont log your username/pwd because we have these rules in place is generally the argument.

    My argument is:

    Does the legal/HR department know you can look at all their documents/passwords/records, but at the moment choose not too?

    Did you inform all employees we can now see your usernames/passwords/creds for all connections but choose today not to log them.

    Do you truely trust your admins not to mine this information? Seriously?

    Who has your contract to install and maintenance it?

    Who watches the watchers? policy?

    What if the guys that broke into a large retail chain last year understood what the bluecoat server contained or could log?

    in the words from Dwarf Fortress, "Fun!Fun!Fun!"

  82. Niksun by Anonymous Coward · · Score: 0

    any company that uses Niksun appliances 'CAN' do this. A list of companies that use this hard ware includes UPS, DoD, and Verizon.

  83. It's very common. by hpuxguru · · Score: 1

    My employer uses a proxy solution to perform content filtering. It's used to help human resources police personnel (URL filtering) and it's also used for malware inspection and download prevention. User IDs, password, etc. is not captured. This is all agreed upon by each employee as a part of the Internet usage policy they agree to when becoming employed. Each employee is reminded annually of the Internet use requirements. There is a clear understanding that all communications on our network are monitored and there should be no expectation of privacy when using corporate systems or networks. There are some sites (banking, insurance, HR related functions) that are not inspected as a part of the proxy solution. This is in order to allow the user to see the "green bar" when accessing some of their personal data.

  84. SSL and DLP by Anonymous Coward · · Score: 0

    If you're not decrypting SSL and have a DLP solution, your DLP solution is worthless.

    It's entirely within the rights of a company to watch all the data that's leaving their network.

  85. Yes indeed by cyberspittle · · Score: 1

    You should assume that you are being monitored. There is more spying via business than by governments and military. The illusion of privacy is exactly that. I found out when they tracked my post to slashdot during my lunch break.

  86. Yes it is a MiTM attack by Anonymous Coward · · Score: 0

    http://en.wikipedia.org/wiki/Man-in-the-middle_attack

  87. Testing by Anonymous Coward · · Score: 0

    Wondering how a lot of these implementations handle if you go to a site with an invalid cert. Do they attempt to verify it or just replace it with a valid cert and then expose you to two layers of eavesdropping?

  88. It depends on the logging level by Anonymous Coward · · Score: 0

    If the employer is logging everything you do on the computer that they own I would disagree with you. However, if the argument is simply related to the a proxy server doing deep packet inspection and not logging anything I would agree with you. It really boils down to what is getting logged. The Internet Use policy is clearly defined, so as another poster above mentioned if you are doing your banking on a device that you do not own you are already way into the risk category.

  89. Cellular anyone by Giovanp · · Score: 1

    That is a very common occurrence and the reason why many people where I work conduct their personal business on a mobile device via the cellular network. And yes I am posting this from my iPhone over cellular

    1. Re:Cellular anyone by evil_aaronm · · Score: 1

      Yeah, that's how I did personal stuff at work. I had my own Sprint MIFI and laptop. I knew the corporate overlords were watching everything, so anything that wasn't directly related to work, I turned my chair to the left and did it on my laptop.

  90. Yup, but not difficult to work around by Anonymous Coward · · Score: 0

    Yup. My employer does this. I think they decrypt and log everything for analysis if there's ever a data loss. They got burned pretty badly a few years ago, so the paranoia isn't completely unreasonable.

    It's not difficult to work around. You can set up a VPN from home. The normal VPN configuration on the client blocks non-VPN networking, but you can get around that. Once you do that, it's easy to set up a ssh tunnel from a work desktop over the VPN to home and out. Then set up routing to go over the VPN connection for anything you want to keep private, and the company never sees it.

    [posting anonymous for obvious reasons]

  91. Yes by Anonymous Coward · · Score: 0

    They've been doing it with McAfee Web Gateway at my office for years. Those using Firefox notice because of the separate certificate store not having the company CA, but IE and Chrome users are none the wiser.

  92. Completely common at . . . . by sgt_doom · · Score: 1

    . . . all private equity firms (private banks/leveraged buyout firms), hedge funds and most financial services companies. I'm surprised this is news to anyone?

  93. Amazingly, mine doesn't. by Anonymous Coward · · Score: 0

    I thought for sure that mine would, but after checking the GRC Fingerprint website and comparing the results to what I get on my phone and on my home internet connection, I don't think my SSL/TLS is being MITM'ed at work. There is indeed a mandatory proxy in the way between me and the public internet, but it lets encrypted traffic through as-is after filtering (accepting/denying) based on the DNS of the remote box.

  94. BYOD can get complicated by Anonymous+Brave+Guy · · Score: 2

    In the real world, BYOD isn't always that simple. The moment an employer encourages their employee to do something on their own device rather than provide dedicated company equipment, there are issues of who has what access, who is responsible for what, etc. There are entire businesses making tools and consulting in this field right now, because that is how big a minefield it is becoming.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  95. Another YES here by cant_get_a_good_nick · · Score: 1

    We had a source code leakage through email, so first they did for google/yahoo/hotmail. Then they expanded it to any social network site. Now it's on every https site.

    The latter "every" site sucks. Every site gets cert errors, and parts of the site work or fail oddly.

  96. Simple, use your own PC and network by CptJeanLuc · · Score: 1

    Buy your own computer/tablet/phablet, and if you need to do private stuff while at work, use your own 3G/4G or whatever. It is that simple. Don't use the company mail for private mail. Get your own cellphone for your private stuff. It is that simple. You can either have full control of your privacy, or you can save a few bucks by using your company's stuff for free. You cannot have it both ways. If you need more network bandwidth at work than you can transfer over a 3G network, in order to download or watch stuff which you don't want your employer to know about, then well ...

  97. DING DING DING!!! by KingSkippus · · Score: 5, Insightful

    You, sir (or ma'am), are doing it right. This is precisely the thing that gets me so mad at companies today, that they view these issues as an IT problem, not an HR problem. So they spend hundreds of thousands of dollars (sometimes millions) in hardware, software, salaries, support contracts, and lost time when shit breaks, just so that management 1) won't have to do their jobs--you know, managing people, and 2) will have plausible deniability when someone does do something stupid. ("It's not my fault for not making sure my workers were working on what they were supposed to and not violating company policy; IT should have blocked that site!!!")

    It's refreshing to see someone who actually gets where company policies should actually be enforced and where responsibility really ought to lie when there are gaps. Thank you!

    1. Re:DING DING DING!!! by ga53n · · Score: 1

      I have to refer to my sig

      --
      It is not possible to use technology to solve social problems
  98. Legality of wiretapping in two party states? by realxmp · · Score: 1

    Even if you could argue you have the Employee's compelled consent for this, you most definitely do not have the website's consent. If the website in question is based in a two-party consent wiretap state, I'm wondering if employers might in fact be committing a felony by tapping the website's communications back to the client?

  99. Snooping On Personal Life by Anonymous Coward · · Score: 0

    As others have stated, I don’t think using a reverse proxy counts as a MITM attack, so I read your question as asking if it’s common for companies to snoop on the employees’ traffic to/from outside the company’s network.

    To that, I answer yes. Usually it’s a company policy executed by the IT department to ensure employees are not sending company-confidential info out and to make sure they're not doing stuff like surfing porn sites. I’m fine with that.

    But at one of my employers, a small company of ~60 employees, my colleagues snooped on my traffic because management and many of my colleagues wanted to know what was going on in my personal life. They would read my personal emails when I logged into my Yahoo! account (which didn’t offer HTTPS at the time) and then tell other colleagues in the company. Not cool. So I stopped reading my e-mail at work. They weren’t happy about that. That same employer had the line “All employees must divulge what goes on in their personal lives.” in the company’s Core Values document (which I only learned about 6 months into the job), but was immediately removed after I objected to it. They have since denied it ever existed.

  100. I have seen this several times by cs668 · · Score: 1

    One of which was a case where credit card information ended up being in the proxy logs of the company that was doing this :-(

  101. Becoming much more common by MobyDisk · · Score: 1

    I think the increased prevalence of HTTPS in the last 2 years has forced more companies to do it.

    I work for a Fortune 500 and they quietly implemented this around the end of 2013. It breaks various installers that phone home to check licenses, it breaks automatic updates like Firefox, and secure file transfer sites don't work. But even the software engineers didn't notice it for quite a while since corporate IT pushed down certificates to everyone's machine. There are a few sites that they don't intercept, presumably because it would get them in trouble or interfere on too large of a scale. Ex: Some banks are not intercepted, neither is Microsoft.com since I bet that would break Windows Update.

  102. Company goes from the frying pan to the fire by Anonymous Coward · · Score: 0

    This is scissored from http://security.stackexchange.com/questions/40892/what-are-the-risks-associated-with-ssl-interception-in-an-organization

    The risks are about the same as those implied by giving to a designated security guard a key which opens all doors in a building. The guard becomes a valuable target; attackers will want to rob the guard or to bribe the guard, in order to obtain the golden key. Being all-encompassing, the key bypasses all procedures and security layers; you cannot isolate parts of the building from each other, if the potential attacker has a key which opens all doors.

    Knowledge of the mere existence of an open-everything key in the hands of some security guard will make the users quite distrustful. Human users tend to value their privacy, and don't like the idea that someone will be routinely opening their desks and lockers and inspect the contents.

    Beyond the key analogy, using SSL interception (with an organization-specific CA used to build MitM attacks on the fly) has the following specific consequences:

      - On the desktop systems, the interception requires installation of the special CA certificate in the "trusted store". This installation has to be done again whenever a new OS is installed; users may remove it themselves; some Web browsers (in particular Firefox) will disregard the OS trust store and use their own. Thus, there is ample room for breakage here. This can be somewhat fixed by locking down the OS configuration and software installation, but the more you lock things down, the less happy the users become.

      - The OS trust store may be used for other uses than mere SSL; it can be used to verify signatures on software updates and drivers, for instance. An attacker who succeeds in stealing the private key for the organization CA may thus gain extensive power on the whole network, not just the ability to intercept SSL connections (which is already a lot).

      - The private key for the organization CA is thus sensitive, but cannot be protected with high isolation layers, because that special CA, by construction, must be able to issue fake SSL server certificates on the fly. So it must be online, on a server which is "close to the Internet".

      - Such MitM interception breaks certificate-based client authentication. https:// Web sites very rarely use client certificates, but I have seen it done by some banks to authenticate their customers (at least as part of experimental deployments).

      - In many jurisdictions, automatic inspection of user's communications by the employer is lawful, but subject to some conditions, usually an explicit notification right there in the employee's contract. There can be legal risks related to such interception (similarly to reading letters, tapping on the phone and installing video cameras in offices). Some detour through the law department is strongly advised.

    So we can say that while organizational SSL interception allows for inspection of SSL-downloaded contents (thus antivirus and other filters can be applied on the proxy), it also opens new vulnerabilities. Thus, the overall security situation might be worsened by the installation of such system.

  103. Common, to a certain point by Anonymous Coward · · Score: 0

    It is fairly common. However, for the company I work for, it is only for logging which sites the employees visit, rather than collecting the contents of the traffic. In other words, we can detect that you visit, say, Hotmail to look at your personal account, but we do not collect the contents of your emails. While our company policy does not explicitly say we monitor Internet traffic, we do have an entry that says something along the lines of "company resources are to be used for company only."

    If a user starts visiting job sites during company time, we'll know and look out for any nefarious activity for that user.
    If a "user" starts visiting several malicious websites, we'll know and act immediately to contain the infection. I don't know how many times this has helped me detect 0-day malicious programs within the organization.

  104. It is VERY common by dwheeler · · Score: 2

    This is very common in the military and in defense contractors, and it happens elsewhere too. There is a reason for it. Many of these organizations are worried about malicious stuff going in and/or exfiltration of non-public data going out. Employer MITM makes it easy to examine every packet for these kinds of things (to counter them). In the US, at least, it's generally accepted that employer equipment is owned by the employer, and thus they expressly have the authority to examine what goes over their own network... and as a condition of employment or computer use you probably signed something agreeing to this. I'm not a fan of this approach, but it certainly happens.

    Open source software that implements crypto protocols (e.g., SSL or SSH) will (correctly!) report that there's a MITM attack. So if you want to actually *use* the software in such settings, someone has to configure the software to trust the MITM. Some admins will do this automatically. If not, you may need to do it yourself. E.G., on Firefox, install the organization's certificate.

    You configure Linux systems to work in these environments, but since the certs are often files in Windows aka DOS aka CP/M format, you need to convert the files as well as put the into somewhere useful. Here's one way to deal with it.

    On Fedora, given a bunch of .crt files, you can do this:

    dos2unix *.crt ; cat *.crt >> /etc/pki/tls/certs/ca-bundle.crt

    On Ubuntu, you can do this given a bunch of .cer files:

    dos2unix *.cer ; rename 's/.cer$/.crt/' *.cer ; ca=/usr/share/ca-certificates ; mkdir -p $ca/MYORG ; cp *.crt $ca/MYORG ; cd $ca ; ls MYORG/* >> /etc/ca-certificates.conf ; update-ca-certificates

    You could avoid appending to the file if you want to, but I'll leave that as an exercise for the reader.

    --
    - David A. Wheeler (see my Secure Programming HOWTO)
  105. Fairly common by Anonymous Coward · · Score: 0

    And even if it isn't, if you're using their hardware, they could easily have keyloggers, screen grabs, etc. I always heard rumors at MS that they had a division just responsible for looking at random screen captures from employee machines to make sure nothing inappropriate was happening.

    Anyway, this is why I got in the habit of using my own hardware. Most workplaces have at least a guest network you can access, and if it's your hardware they won't have access to alter the CA so they won't be able to MITM you. If you must look at personal stuff at work, bring a netbook or tablet or something, and use that. Otherwise, be prepared to accept that they may see way more private stuff than you expect.

  106. Why does this keep coming up? by Anonymous Coward · · Score: 0

    I've seen this question posted mulitple times... I'm guessing the editors jump at the "outrage" in the post...

    Just about every web filter sold will do this (Cisco Ironport, Blue Coat, M86, Websense. yada yada). The intent is make sure that you're not downloading malware via the ssl connection. Just because a site has SSL doesn't mean its not otherwise compromised.

    I support one of these solutions and we don't give a crap about what's in the stream beyond "is it malware"... otherwise, surf away... (well, and porn... the ownership frowns on porn, so we block that outright...)

  107. Self-Employed by Anonymous Coward · · Score: 0

    As a self-employed person, I totally spy on everything I do. In real time. I feel like such a voyeur / exhibitionist, because I DO know that I'm spying on myself, but it doesn't really alter my behavior. Plus, if I complain, I'll just explain that I own the hardware, so hard cheese.

  108. Probably. by _Shad0w_ · · Score: 1

    Probably. And I honestly don't give a shit if they do. The only thing I browse at work are work related sites. The only thing I care about is when the stupid firewall blocks me from getting to a site which I'm only trying to access for work reasons. Still, that does at least let me send sarcastic e-mails to IT.

    --

    Yeah, I had a sig once; I got bored of it.

    1. Re:Probably. by ichthus · · Score: 1

      The only thing I browse at work are work related sites.

      ...AAaaannddd.... Slashdot?

      --
      sig: sauer
    2. Re:Probably. by _Shad0w_ · · Score: 1

      Not at nine o'clock at night, no.

      --

      Yeah, I had a sig once; I got bored of it.

  109. Cyber Security Analyst here... by shellster_dude · · Score: 1

    My company does it, and it isn't for malicious reasons of spying on their users. It is done so that IDS and IPS can actually detect malware downloads and C2 communication over SSL. I suspect that's the primary reason most other companies do it as well. If they don't the company can't adequately detect or remediation most modern malware.

    Detection of exploit kits via HTTP monitoring is one of our primary indicators of compromise, so this information is vital.

  110. Very Common Practices by Anonymous Coward · · Score: 0

    To add some information to the conversation... As a consultant that implements and integrates https inspection for many different companies, this is a common practice for the benefit of inspecting traffic for security threats (malware, hacks, bot channels, etc), data leakage, legal risks, and productive loss reasons. However, corporations are not interesting in your banking nor health information. Typically, those site categories are typically NOT even inspected by configuration of the equipment. Financials and health bypassing of inspection is the number one most common rule to implement during an inspection project. Businesses are interested in protecting their interests, not your financial or health info.

  111. Doing anything at work by Anonymous Coward · · Score: 0

    other than work is wasting company time. do personal tasks at home. they can do whatever they want if it's their hardware, software, and data connections. you sign a document in the beginning that general states this. as a vendor you do this as well.

  112. This not really new, and extremely common by Anonymous Coward · · Score: 0

    And it's usually (in the UK at least) covered in the Computer Use Policy, and other associated policy documents that employees would be required to read, agree to and sign.

  113. Double SSL by Anonymous Coward · · Score: 0

    I have an ideea: when an invalid certificate is detected, the communication should continue, but a second negotiation should be started imediately. There would be two layers of encryption, only one breached. It would require support in both the server and the client, for example Chrome when loading Gmail. Of course, this requires the browser to controll it's own root certificate database and that the proxy not enforce strict HTTP content in the decrypted stream.

  114. "SSL Inspection" usage is growing daily... by madmatty · · Score: 1

    https://techlib.barracuda.com/... About 2-3 dozen customers a week are setting this up.

  115. Illegal? I doubt it. by Anonymous Coward · · Score: 0

    Really?
    Someone lends you a computer for a certain purpose, and states, in writing, that they are watching what you do with their computer.

    How can that be illegal?

    1. Re:Illegal? I doubt it. by joaommp · · Score: 1

      trust me, it is. a big part of the new law is 50 shades of stupid.

    2. Re:Illegal? I doubt it. by xkpe · · Score: 1

      In Portugal and most of Europe, a contract cannot go against the law. In case it does, that clause or the hole thing would be rendered void.

  116. Only way to accurately tell what user is browsing by Anonymous Coward · · Score: 0

    This is quite common as it's the only way to tell what traffic is passing through in any detail. This is done for content control reasons in work environments ie making sure staff only access required sites or not access inappropriate sites (eg porn) over HTTPS.

  117. detecting MITM by Anonymous Coward · · Score: 0

    https://www.grc.com/fingerprin... posts fingerprints for some common sites so you can compare them with what you get in your Web browser.

  118. No, you're still wrong by Burz · · Score: 1

    The browser is indicating to the user that end-to-end security is in effect, when its actually been subverted. That, more than anything, puts it in the MITM attack category.

  119. By definition a proxy is a MITM by GuanoTO · · Score: 1

    A proxy is am MITM because it terminates your request for a website, makes its own request to that website then once it receives the content from said website, delivers it to you.An SSL proxy does the same thing for HTTPS based content. It should not be a surprise that corporate devices trust the certificates signed by corporate proxy.

    There are many reasons for implementing an SSL Proxy, the primary reason is security. Web-based malware has transitioned almost exclusively to delivery over HTTPS. If the corporation is not inspecting HTTPS traffic for malicious code, then they are ignoring a significant portion of their web traffic, upwards of 40% and growing. This means no URL Filtering, Malware Scanning, Intrusion Prevention or other security measures are applied to almost half of all web traffic.

    Still sticking with the security angle is outbound security, whether it is Data Loss Prevention, Botnet Command and Control or other exiting traffic that the company wishes to prevent, you are still only seeing about half of it without SSL inspection.

    Typically, SSL proxies have the ability to control what sessions are decrypted and which ones aren't. This is usually tied to a URL Filtering package that identifies the category of website being requested based on URL or URI. Then policy is designed so that requests for banking and health care sites don't get decrypted.

    Many security conscious companies do use SSL proxies and unfortunately, many do not. The ones that don't occasionally make the headlines, like Target and Adobe did recently. Sadly for them it wasn't for record breaking profits, it was because of mandatory breach disclosure laws and a security perimeter that is only about 50% effective. While this was bad for Target, it was also bad for the tens of thousands of Target customers who had their private information leaked. And Adobe lost 40Gigs of proprietary source code as well as customer data.

    So, if you work for a company that does use SSL proxies, you can be pretty sure the purpose and intent is not to spy on YOU the employee, but to make sure that the company is doing everything it can to protect itself, its customers and even YOU its employee from the criminals who seek to steal information like credit card data, social security numbers, intellectual property and other private data.

  120. Firefox says every site is Untrusted by Anonymous Coward · · Score: 1

    the client is intercepting all HTTPS traffic on the way out the door and re-issuing an internally generated certificate for the site

    Is this the reason why, when I use Firefox at work, it issues complaints like these?

    You have asked Firefox to connect securely to www.yahoo.com, but we can't confirm that your connection is secure.
    You have asked Firefox to connect securely to www.google.com, but we can't confirm that your connection is secure.

  121. Re:four minutes Pron by fonske · · Score: 1

    Worse than any company rule, my wife intervened: I go locked to work with a "CB". Not sure if she wanted to have as a side effect that all those great looking female students were no-go from there on.

  122. Smartphones by flyingfsck · · Score: 1

    Geez, do your private stuff on your own phone. Why waste your time with the cripple company systems?

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  123. Very common. Most interception based content filte by Anonymous Coward · · Score: 0

    You are on a company network - they are responsible for what gets done on their systems and internet connections - so whats the surprise?

  124. Many hotels do this too by davesag · · Score: 2

    Many of the hotels I've stayed in iver the years, both major chains and smaller boutique hotels, and in several countries, have attested to MiM my secure mail server or http a sessions. Similarly I caught the Qantas lounge in Sydney trying this a few years ago. I never use hotel internets any more or airline lounges' wifi - it's just too creepy.

    --
    I used to have a better sig than this, but I got tired of it
  125. MITM Attack clarification by Anonymous Coward · · Score: 0

    Intrusion protection and web filtering aren't MITM attacks. Neither is snarfing up all the network packets using a proxy or some other method. From my understanding a true MITM is where I intercept your traffic and steal either your client or a servers credentials.

  126. Of course more are doing it by Anonymous Coward · · Score: 0

    But the sad thing is most employees don't pay attention to the IT code of conduct and truly understand that their email, banking, Facebook (etc) passwords, credit card details, and HIPPA data (because of the out sourced payroll and health insurance sign up forms) are now being captured and possibly logged internally by people not being bound to secure or keep private that data.

  127. All the time by stickystyle · · Score: 1
    I do it here, and not for nefarious reasons.

    My use case is our floor workers all have very restricted access to the internet at their non-user specific workstations. Since we use Google apps for our mail here I needed a way to allow access to our corporate gmail, but not their personal ones. Since all accounts are on the google.com domain I can't just block via fqdn, I need something to intercept which account they are accessing and restrict based on that.

    Heck, google even documents how to do it right here https://support.google.com/a/a...

    --
    Pluralitas non est ponenda sine neccesitate
  128. perhaps not mitm. by drizuid · · Score: 1

    You will see this behavior pretty frequently if you SSL offload with an f5 or if you filter ssl websites with bluecoats. Im sure there are a slew of other legit apps that also do this. Eg. we blocked youtube, but everyone knew to bypass this you could goto https://youtube.com/ so we started intercepting ssl certificates to block the traffic. In our case; we only intercepted SOME ssl traffic depending on destination to avoid the issue you're discussing but presumably if we just intercepted all and filtered after the fact, you would have seen the same issue.

    1. Re:perhaps not mitm. by ggpauly · · Score: 1

      Eg. we blocked youtube

      Youtube is a vast collection of information of all kinds. Do you block wikipedia too? Why not the entire web?

      --
      Verbum caro factum est
    2. Re:perhaps not mitm. by The+RoboNerd · · Score: 1

      If your remote sites have bandwidth issues, blocking streaming sites can help along with QoS. It's just another tool in your kit. It doesn't mean the sysadmin is being a douchebag.

  129. slashdot? by schlachter · · Score: 1

    even to read and post rants on slashdot?!

    actually, I check all my various accounts from my work machine. I assume my employer is capturing info but is not mining it.

    --
    My God can beat up your God. Just kidding...don't take offense. I know there's no God.
  130. Not MITM by ggpauly · · Score: 1

    The client computer must be compromised for this to work. This is not MITM. The client is participating in the "attack".

    Using an untrusted computer is always dangerous: keyloggers, scrapers, custom DNS. Laptops are security devices.

    --
    Verbum caro factum est
  131. Yes - part of the acceptable usage rules by homebrandcola · · Score: 1

    Don't do anything on a work machine you wouldn't do if it was being shown on a 50" TV above your head. They actually have a white list of sites that they 'trust' and do not do MITM - banks mainly, but a search on Google defaulting to HTTPS is not secure.

  132. sslstrip/ssldump by v3xt0r · · Score: 1

    Building a transparent linux-based proxy/firewall/gateway with sslstrip/ssldump is sexy.

    --
    the only permanence in existence, is the impermanence of existence.
  133. Yes by another_gopher · · Score: 1

    2000+ employee firm in Boston and London

    mandatory install of iphone profile to enable the MITM to work "transparently"

  134. How is this not illegal? by jopet · · Score: 1

    Well in all the countries I have lived and worked so far (not the US) this would clearly be illegal. How is it not illegal in your country? Did you inform the police?

  135. Exactly Wrong by Anonymous Coward · · Score: 0

    This is exactly why I've removed/revoked the trust of the corporate issued certificates. I get warnings when using internal sites, but I also don't get intercepted.

    Although I'm given to understand that verisign et al. offer turnkey solutions for this where you can plug in any keypair of your own to their device and it will automatically perform these attacks.

    All that is required to use it is a trusted certificate & key, which, by the way, certificate authorities are in a position to sell.

    So it may be that my revocation of the corporate certs don't actually secure me. Assuming IE/Windows issues with policy-installed or auto-downloaded trusted certs can be avoided.. (I'm running Firefox)

    Moxie's solution of distributed trust and certificate pinning would still provide some protection.

  136. Mine does. Somewhat. by Will_Malverson · · Score: 1

    From looking at certification chains, I can see that my employer (a state government) MITMs Google (even though GMail is blocked), and probably other sites that I haven't noticed, but they do not MITM banks, at least not the two I visit occasionally from work. I haven't done much investigation beyond that.

  137. WAN Optimization by The+RoboNerd · · Score: 1

    Riverbed Steelheads can do this to optimize SSL traffic for WAN optimization. While this could be considered a good use of MITM for a company, and I wouldn't exactly fault a company for wanting to optimize their SSL traffic on their own WAN. It's still kind of scary prospect if a company's riverbed setup were ever to be "pwnd" by a "hax0r," particularly if it was set up wrong.

  138. Pretty easily by cbhacking · · Score: 1

    So, if this is a work machine and you're using Windows, I'm going to guess you're on IE. If not, you can find similar steps for other browsers, though.

    1) Connect to an HTTPS site.
    2) Find the "Lock" icon in the address bar (it should be on the right side).
    3) Click on it; the exact result of doing this will vary by version but you should get some info about the security of the connection.
    4) Click on "View Certificates" (on IE10+ this is right in the little box that appears when you click the icon; I don't have an older version available to check).
    5) Check each certificate in the chain of trust. Under the General tab, look at Issued By. Also look up the "chain of trust" to check the signing certificates in the Certification Path tab.

    They should be signed by known certificate authorities (if you aren't sure whether a given company is a known CA, look it up online). If the cert is instead signed by your employer or something like that, you're pwned.

    --
    There's no place I could be, since I've found Serenity...
    1. Re:Pretty easily by suutar · · Score: 1

      Exactly what I needed. Thanks :)

  139. That depends by Anonymous Coward · · Score: 0

    First, we have the empirical evidence: The Democrat Obama administration is doing WAY more than the Republican Bush43 admin did... that's the FACT on the table. Now, admittedly, this may be wholly, or in part, a purely temporal argument; i.e. it's possible the this is just the more-recent guy building on the previous guy. It is, however, empirically WRONG to assert that Democrats care more about your personal privacy than Republicans.

    Second, it depends on the TYPE of Republican. Establishment Republicans (includes so-called RINOs) like the Bush family and the Romney family have always campaigned as conservatices but then operated in office like big-government Democrats (bigger government, more government power, more government control, etc and big government entanglements with big business). Conservatives, Libertarian-leaners, and TEA-Party Republicans, on the other hand are actually in favor of smaller government and less snooping (which is why they freak-out establishment Republicans and Democrats alike). In all likelihood, if you elect a Romney or a Bush you get the same big intrusive government as if you elect an Obama or a Clinton. If you elect a Paul or a Cruz.... not so much. The one CERTAINTY is that ANY Democrat gets you bigger government, more spying on citizens, more rules and laws telling citizens what to do, what to think, etc.

    In politics you can almost never get everything you want... you have to prioritize. If you decide you just cannot STAND some position of a Paul or a Cruz, then you are probably going to vote for an Obama or a Clinton. That's fine.... it means you have decided that one position was more important to you than all the other stuff.... but then shut up about the rest; you made your bed now sleep in it. If you decided that one thing was more important than being spied-on and groped, etc then buck-up and smile while you get spied-on and groped - that's the option you chose.

  140. Yes, I call it... by Anonymous Coward · · Score: 0

    The Man In The Middle Defense.

  141. Better question: Why would an organization employ by Anonymous Coward · · Score: 0

    Organizations following a risk management strategy often employ a myriad of controls to mitigate risks. One risk other commenters have pointed out is the outbound data flow inside encrypted tunnels, in this case, a SSL tunnel. Malicious persons could use a SSL tunnel to defeat Intrusion Detection/Prevention Systems, and to move data in and out of a network (bring trojans in, and exfiltrate data out). If your organization is paying attention, they should do this to manage the risk, or accept the risk, and permit SSL.

    An Information Security professional can help people understand the risk, so they can make an informed decision, eliminate, mitigate, or accept the risks.

    In the United States, people do have an expectation of privacy unless that expectation is removed, often through an employee handbook, an acceptable use agreement, and/or a login banner. IANAL, but my understanding is that monitoring of employees by the corporation is legal providing they also remove the expectation of privacy. Check with your lawyer if you have doubts.

    Clearly you perceive this as malicious in intent, but I assure you from sitting on the other side of the table, that this control can help detect malicious traffic. True, it can be abused, as can any system, so you should be asking management who's watching the watchers. That's fair. But I would not use company resources for personal use, such as banking, facebook, day-trading, etc. I would instead expect a corporate to monitor Internet usage, and plan accordingly.

  142. Yep by Anonymous Coward · · Score: 0

    Yep.

    We do exclude URL catgeories shopping, health-and-medical, government, and financial-services.

    We also do inbound decryption where the firewall does MITM for in bound http, outlook web, etc. inspects it, reencrypts it and passes to the appropriate DMZ server. Same with DMZ to internal.

  143. Comcast does this by Anonymous Coward · · Score: 0

    If you work for Comcast, you're getting MITM inspected routinely.

    For company stuff I use browser A (where the certs are accepted). For everything else, I tether to my phone and use an outside link.

  144. stupid question by flipk · · Score: 1

    I would like to ask a stupid question. If my employer is doing this, and I'm using Chrome to look at, say, https://mail.google.com/, when I click on the little green lock next to the URL to view the Certificate Information, and my company's name is NOT present (the cert path is GeoTrust Global / Google Internet Authority / mail.google.com) can trust that to mean my company is not intercepting that traffic? Or can my company make it appear this way and still be intercepting my traffic? I suspect there are a number of people who would like to know the answer to this. I'm hoping it's not as stupid a question as it sounds.

    --
    --PK (Tech Junkie / Junk Techie)
    1. Re:stupid question by Jeremiah+Cornelius · · Score: 1

      Probably, they are not.

      NSA has been doing hash collisions in MD5 space to get past this niggle. Your company, probably not. Yet. :-)

      --
      "Flyin' in just a sweet place,
      Never been known to fail..."
    2. Re:stupid question by gnasher719 · · Score: 1

      I would like to ask a stupid question.

      Let's say you buy stuff from Amazon. Amazon has a certificate signed by Verisign. Your computer gets the certificate and examines it. What it finds: The certificate claims to be from Amazon, and says you should trust it because it is signed by Verisign. The Verisign certificate is trusted because it shipped as part of the OS. Now you get the man-in-the-middle attack: Your company creates a fake Amazon certificate and signs it. Your computer sees the certificate claims to be from Amazon, and says you should trust it because it is signed by your company. Your company's certificate is trusted because they added it to the OS of your work computer. If you click on the certificate, it will say it is an Amazon certificate, and your company's certificate is the root certificate.

      I very, very much hope that Verisign (as the employer of Verisign employees) would be very careful with this.

  145. Re: four minutes Pron by Anonymous Coward · · Score: 0

    What on earth is a "CB"?

  146. yes by mo0n_sniper · · Score: 1

    Looks like to be very common. My current employer does it, and the one before it did it also. It's very annoying.

  147. Also by Anonymous Coward · · Score: 0

    Sure, any place with a high enough number of assets, yes, it should be expected, though i would be extremely untrusting of people and your bank accounts, since you don't exactly vet these operators. And occasionally they will also, pop up a fake version of the site and ask you to reinput your password. Classic bad guy technique.

    Though i'm uncertain which portion anyone should get affronted at: the fact that you expected privacy on a non owner network, or the meta - the fact that the netops think you expected privacy but you don't, or the more mundane - the inability of netops to distinguish extension services on browsers.

    Information is like technology. It's not how much you have, it's how you use it that is the differentiating factor.

  148. That doesn't apply to all cases by Anonymous Coward · · Score: 0

    Internal company policies still cannot violate the sanctity of the client-attourney confidentiality, as can be observed in the Supreme Court ruling of the 2010 Stengart vs Loving Care Agency case. http://en.m.wikipedia.org/wiki/Stengart_v._Loving_Care_Agency

  149. A question of liability by mzellers · · Score: 1

    This all raises an interesting question: Imagine that I need to purchase something for work. If I don't have a company credit card, and if it is allowed by company policy, I might purchase such an item using a personal credit card using my work computer and ask for reimbursement later. Now imagine that there is a data breach in the IT department with the result that the proxy server log falls into the wrong hands and the black hats have my credit card information. Imagine they use that information to make a much larger purchase. Would my company be liable to the credit card company because their interception of the communication resulted in a tangible loss to the credit card company? Or should they be made to eat the loss. I think Visa would have a very good case against such a company since their negligence in protected the intercepted data exposed Visa to a loss it had seemingly defended against by using https.

  150. HTTPS Proxy Interception : detection by advid.net · · Score: 1

    Shall we focus on how one can detect this situation ?

    Case 1 : One have access to the network
    - Bring you own trusted device: laptop / tablet / ... Start your own browser, see the certificate warning.
    Could the device be also abused ?

    Case 2 : One has a limited access to the system
    - Start your own Portable Firefox on USB key, with standard certificates. See the certificate warning.
    Is there any other tool ?

    Case 3 : One has access to a kiosk or similar looked system
    - Assume everything is logged, don't trust. Poor configurations may be worked around to visit any web site, but don't type any password on it.

  151. Clearly not by Neil+Boekend · · Score: 1

    My employer just blocks all non-work related HTTPS trafic. Some supplier sites use HTTPS and they work, but most other sites don't.

    --
    Well, I might have a way, but it only works on a semi spherical planet in a vacuum.
  152. la by Anonymous Coward · · Score: 0

    in most of eu it is illegal though to do it this way. But bofhs don't care.

    1. Re:la by Anonymous+Brave+Guy · · Score: 1

      Why?

      --
      If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  153. This is normal by halln · · Score: 1

    This is extremely common. A lot of newer firewalls have it built in and it is basically just a checkbox and configuring a CA. Palo Alto prevents issues with banking by allowing a company to perform SSL decryption on all traffic, but exclude decryption on certain categories of sites. Therefore, you can perform decryption, but not decrypt banking sites. And, btw, even those "HTTPS" VPNs will often use IPSEC after the initial authentication. SSL is usually a fallback.

  154. This is what is wrong with big business by Anonymous Coward · · Score: 0

    My feeling is there exists a trust that must be established between a good productive employee and their employer. Personally I feel if I will be fed, and feed my family by the company that I spend alot of my time at then, i should both know what they are up to, how they make money and be proud of it.

    What I cannot understand if you dont trust the company you work for then why would you ever use their facility for anything outside of what they ask you, and honestly you should quit and open your own business or work for someone with whom complete transparency can be had. Vice Versa if a company doesnt trust it's employee why would it not just fire said employee.

    All of us worker bees have personal lives and need to do other things than be a robot, if the company wants robots let them work on making them, if I want to be a robot then i wouldnt be able to write this because I would be working...

    If you choose to be a corporate robot more power to you... just make sure you know what your signing and when they can your butt for checking on your kid in childcare while at one of their PC's then dont complain.

    Peace....

  155. Exposure to liability by phorm · · Score: 1

    Seems this could expose the employer to other liabilities. How about if the employee was looking up something online that exposed he/she had a medical issue the employer wasn't aware of, or was in-the-closet.
    Employee gets fired for other reasons, finds out employer was sniffing his/her email and/or searches, sues for wrongful dismissal and discrimination.

  156. Re: four minutes Pron by fscking_coward_2001 · · Score: 1

    I'm guessing "Chastity Belt".

  157. SOP for the enterprise ...? by OldHawk777 · · Score: 1

    Yep, but I chuckle far to often.

    --
    Unaccountable leaders are masters, and unrepresented people are slaves. How do US and EU fare?
  158. Very uncommon. by Anonymous Coward · · Score: 0

    And a little paranoid, don't you think? With totally legit tools like orvell you don't need to do such nasty things like MITM.

  159. One of my prior employers did this by fluffynuts · · Score: 1

    And it's one of the reasons I left. It was all part of the erosion of the "cool place to work" ethos that was there when I joined them.

    If you can, vote with your feet. I totally appreciate that not everyone can. But if you can, do. And make sure that your employer knows about it. Also, it helps to inform the unaware masses if you know about it -- most of the people at my old work didn't know, and that, in and of itself, is possibly worse than the actual act.

  160. Group policy by Anonymous Coward · · Score: 0

    If your employer has a group policy that can push a CA to your computer, then they don't even need a proxy to sniff you. They could just as easily push a keyboard logger.

    If you don't trust your ad admin, gtfo.

  161. I do this to our employees (and students) by Anonymous Coward · · Score: 0

    Hi, technology guy for K-12 school district. We actively do this, use our firewall to MITM and fake proxy the SSL cert, decrypt and do deep packet inspection. All for network security and to remain compliant with CIPA. "You signed the acceptable use policy which states we do this, so you're welcome for the paycheck", is the general motto.

  162. NIST by Mr10001 · · Score: 1

    NIST 800-53 rev. 4 discusses this topic, so it seems like it's going to become more common. http://nvlpubs.nist.gov/nistpu...

  163. blue coat FTW by Anonymous Coward · · Score: 0

    In my work at a major website we had reports from users that they were seeing account pages for other users. Account pages were SSL, so we assumed problem was at our end since nobody should have been able to intercept them. Great consternation and mystery on our side. Users were also very upset and pointing fingers at us about it.

    After looking across the reports we realized they were all coming from the same company. That company was actually caching our pages and giving out secure account pages to the wrong people from the cache on their end. I figured out it was bluecoat proxy from looking at the request headers.

    Company was a European company, btw. I guess they don't care so much about privacy after all.

  164. Up until... by Anonymous Coward · · Score: 0

    someone's banking info is abused then the company is liable no matter how many stupid rules the company has to attempt to protect itself.

    You watch. If it hasn't happened already.

    The company shouldn't have to worry about this sort of thing *as* much if they hire decent, self-respecting employees. Avoid the derelicts of the unwashed masses and the problem of theft is so remote that it might happen .001% of the time. The problem is that in IT you can have shifty people that do a helluva a job, but may not have other aspects such as common decency or care for certain "old-age etiquette".

  165. sure... by Anonymous Coward · · Score: 0

    On what planet? There is ZERO reason a company should be performing MITM attacks on its employees. UNLESS it is done by some red team that has been hired to check out security. And even those logs of employee information (ie: banking infos, e-mail passwords, etc) should be destroyed. This preserves employee faith in the company and builds trust.

    If someone is stealing or embezzling it would be pretty obvious after a while (they'll spend the money eventually).

    If a company is employing MITM as a "security" measure it'd give me reasons to second guess my trust in such an employer. Not only that, it could potentially give an actual attacker a way in to actually steal such info. But beyond that it would make me start guessing about the motives about such a company not just from an employee perspective, but also a business one. What kinds of other things does such a company employ?

    Also, no where does Sarbanes-Oxley state that a MITM attack is a necessary method to collect financial data for reporting. Whom ever suggested that is blathering on non-sense. The only thing I could think of is some internal policy to keep trade secrets, theft of engineering plans, or some government contracting need to (ie: creating some sort of encryption that is illegal to export) keep projects safe.

    1. Re:sure... by Anonymous Coward · · Score: 0

      Different AC here, and probably a lot more stupid than the parent and GP:

      Nowhere in the regs does it state this has to be done... but it is often the justification for this action.

      What I have heard secondhand is that the logs (SSL transactions) tend to be kept and sprung upon the employee come HR review time. "Oh, you had this much money in your checking account. You must not be a good money manager."

  166. It's about your AUP by Anonymous Coward · · Score: 0

    Our AUP invites employees to not do anything they don't want us to know about using our equipment or on our network.

  167. copyright by Anonymous Coward · · Score: 0

    Either I don't understand your comment or you don't understand copyright law. How does having decrypted copies of your data violate your copyright claims? Re-publishing it as their own, yes - that would violate copyright.
    Second, "laws against unauthorized computer access" - what laws are those? I'm wondering if you are just making this up based on what you presume the laws say.
    More obviously, username Joe accessed your website, which you explicitly authorized. Joe is the one not keeping your information private.

  168. Very common! by DaMattster · · Score: 1

    My old employer did it! Technically, it is a violation of HIPAA if employees do anything related to their benefits on the corporate network.

  169. SSH Tunnels by Anonymous Coward · · Score: 0

    can't beat'em