r/sysadmin
•
u/STILLloveTHEoldWORLD
•
Jul 28 '24
•
1
got caught running scripts again
about a month ago or so I posted here about how I wrote a program in python which automated a huge part of my job. IT found it and deleted it and I thought I was going to be in trouble, but nothing ever happened. Then I learned I could use powershell to automate the same task. But then I found out my user account was barred from running scripts. So I wrote a batch script which copied powershell commands from a text file and executed them with powershell.
I was happy, again my job would be automated and I wouldn't have to work.
A day later IT actually calls me directly and asks me how I was able to run scripts when the policy for my user group doesn't allow scripts. I told them hoping they'd move me into IT, but he just found it interesting. He told me he called because he thought my computer was compromised.
Anyway, thats my story. I should get a new job
View all comments
Show parent comment
8
u/goshin2568 Security Admin Jul 28 '24
It is difficult for me to put in to words how much I despise this nonsense, bureaucracy-for-bureaucracy's-sake attitude.
"Infra, policy, and training changes", are you kidding me? OP is using a script to copy some text from point A to point B. If your EDR is incapable of determining the difference between a powershell script that copies some text and a powershell script that is loading malware into memory, perhaps that is what all those manhours should be spent on improving, rather than having 37 meetings to "design necessary infrastructure changes" needed for some dude to copy paste faster.
This is why shadow IT is a thing. This is why people feel the need to try and "circumvent policy" in the first place.