When Employees Use Software That IT Hasn’t Approved

Re:When Employees Use Software That IT Hasn’t Approved by TheRealDunkirk on Wednesday June 12, 2019 @09:26PM (#20171081)

Outgoing SSH is blocked at my company, even to non-SSH ports. Even to virtual machines I had already setup in Azure before the block.

Sure, guys. Of all things to block, let's block the most secure one. That'll really improve our security posture.

At this point, I'm continually surprised they haven't superglued the USB ports.

[ Parent | on HN ]

Re:When Employees Use Software That IT Hasn’t Approved by mgamache on Thursday June 13, 2019 @12:15AM (#20171754)

You can switch SSH to port 80 or 443, right?

[ Parent | on HN ]

Re:When Employees Use Software That IT Hasn’t Approved by mayniac on Thursday June 13, 2019 @12:53AM (#20171894)

You can switch it to any port you want. Problem is that it's super easy to spot on security monitoring tools. I deal with "SSH not on port 22" alerts at least once a month.

It's possible to get around this by tunneling SSH over other protocols: http://dag.wiee.rs/howto/ssh-http-tunneling/. Bear in mind if you do this in a corporate environment, security will throw the largest book they can find at you.

[ Parent | on HN ]

Re:When Employees Use Software That IT Hasn’t Approved by TheRealDunkirk on Thursday June 13, 2019 @12:59PM (#20176677)

Well, I could if I wasn't trying to host a web site on that particular server. ;-)

[ Parent | on HN ]