3 ms·
As a faceless member of the IT department, we generally only lock something down because someone has found a way to do something really dumb with it. For copy/
by ocdtrekkie 5y ago
As a faceless member of the IT department, we generally only lock something down because someone has found a way to do something really dumb with it.
For copy/paste, I can already tell you: We blocked installing Grammarly because there's no reasonable guarantee of what happens to the sensitive data we are legally obligated not to share, so people copy/paste sensitive data into Grammarly's website. Now we have to block Grammary's website, but I could see someone giving up and taking away pasting into websites as a next step...
- civilized 5y agoI will admit that this does make sense.
- ocdtrekkie 5y agoMore often than not we have a reason for it. I can say I try really hard not to be HR: We tend to look the other way on any activity that isn't a security risk. Though sometimes one can turn into another: I once ignored someone's attempt to run a game on a PC of ours. Turns out it was a hacked version of a game which had malware injected, and when it got blocked, they tried installing VPNs and Wireshark to try to get around our security methods... If you have any questions about presumed oppressive IT policies, I'd be happy to give you my take on them. Some folks do indeed go nuts with it, but often I think the reasons why just aren't obvious at first glance.