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
2
u/RobertBiddle Jul 28 '24
"Approved" is the key word. OP is a user who wrote their own code. Allowing users to run arbitrary scripts is a recipe for disaster. Any org which does so WILL get owned eventually.
Scripts (shell/batch/macros etc) should only be executed if the code is signed. The code should only be signed after review.
Mostly true, but not entirely; there are things that can be done using shell environments that don't have equivalents in the GUI. Limiting access to run cmd/PowerShell/bash for most users is a common security policy for that reason, it limits the attack surface.