Why YSK: It appears several Lemmy Instances are flagged as suspicious and at least 1 instance intentionally using the name of ransomware. A couple of the big enterprise monitoring suites (Fortiguard, ZScaler) will flag your account and may end up with you being pulled into an office for an explanation, or worse.

TL;DR: Keep browsing to your local instance at work for now.

  • terraetos@lemmy.ml
    link
    fedilink
    arrow-up
    15
    ·
    1 year ago

    I’m a systems admin. Last week, I had an employee using a VPN to try and hide their traffic. My monitoring software caught it. I couldn’t see the traffic, but I could see it connected to a known Tor IP. My system saw the fishy connection and sent the alert. Just be careful and don’t assume you’re completely safe with the VPN.

    It’s best to assume your IT department can see everything you do, and keep personal stuff on personal devices.

    • ludwig@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      How could you see it was connected to a known tor IP? Would you not just see the IP of the VPN server and not the final destination?

      And VPN servers are often flagged for all kinds of shit because some use them for tor or spam.

      • Car@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year ago

        Yeah, it doesn’t read very clear. I’m assuming they meant that the destination IP was for the VPN server and that some deep packet analysis determined that the encapsulated traffic was TOR-bound. Or it was a wild assumption that they were using TOR and they use it synonymously with VPN.

        Either one of these events (unauthorized VPN or TOR connections) would be reason enough to look more into the employee’s IT resource usage.

        • terraetos@lemmy.ml
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          You’ve got it. I have an NDR I mirror packets to and it picked up the connection. I think the guy hit a Tor IP before connecting with NordVPN, but I do remember seeing the connection to Tor that sparked the alert, followed by the traffic to Nord. Either one of those things would have triggered an investigation into the user.

          Forwarded that to my security team and washed my hands of it. Wish I knew why users pull stuff like that on company resources. If they just did it at home, I wouldn’t care!