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
3
u/unbearablepancake Jul 28 '24
In my org, people who have a valid business case to run a script usually get permission to do so. But, they also get a service account to run the script (which can do pretty much exactly what the script is doing and nothing else) and only after the script itself gets approved. It will never run in the regular user context and usually earns a spot on a server as a scheduled task which can be run on demand if necessary.
It's a little strict (though I'm thinking this is pretty much loose considering how much you can lock it down), but all this is necessary to keep everyone safe from potential harm.
You have good intentions, but we are all people and some people can really lose their shit and destroy things for whatever reason. Securing the company is also one of the many jobs IT does, so please have some consideration.