Re:SSH hacks – a little sanity for remote workers
by packetslave on Friday May 01, 2020 @10:07PM
(#23048477)
Maybe not a firing offense, but if you ran 'ssh -R' at $JOB-1, you'd pretty much immediately have someone from the security ops team messaging you to ask what you're up to.
Re:SSH hacks – a little sanity for remote workers
by kazinator on Thursday April 30, 2020 @09:46AM
(#23030732)
All you would have to do is disallow outbound SSH.
Re:SSH hacks – a little sanity for remote workers
by acdha on Thursday April 30, 2020 @02:37PM
(#23034429)
That's tricky, though, since there are many uses for SSH which are not circumventing security policy — blocking outbound SSH would also mean you couldn't use Git, manage servers in the cloud or other locations, transfer files, etc.
Using this to circumvent policy is exactly the kind of move which would lead to those other uses being banned and making life worse for all of your coworkers.
Re:SSH hacks – a little sanity for remote workers
by kazinator on Thursday April 30, 2020 @04:39PM
(#23035821)
> blocking outbound SSH would also mean you couldn't use Git, manage servers in the cloud or other locations, transfer files, etc.
That's right, and that's how it is with my current employer.
If you need outbound SSH to work with Git, that probaly means you're working on a side project, not work. Fetching public code needed for work from a hosting site can be done over https.
Managing servers in the cloud, ditto. If managing servers in the cloud isn't part of your job description, why would your workplace enable that?
Re:SSH hacks – a little sanity for remote workers
by MaxBarraclough on Thursday April 30, 2020 @12:32PM
(#23032772)
Sure, but if you break your employer's cybersecurity policies, you don't get to blame IT for failing to prevent you from doing it.
Re:SSH hacks – a little sanity for remote workers
by kazinator on Thursday April 30, 2020 @04:34PM
(#23035770)
Using outbound SSH when that is allowed is compliance with cybersecurity policy.
Re:SSH hacks – a little sanity for remote workers
by m463 on Thursday April 30, 2020 @05:47PM
(#23036554)
That would be cat and mouse. You can ssh on any port.
But I agree that it's not a good idea to poke holes in your corporate firewall (which is really what this is doing).
If you have to spend time wrestling the VPN while you're on the clock, that's their own time being wasted.