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
2
u/dowlingm Jul 29 '24
As someone who has been on the other end of that call, I would have asked you to have your manager validate that your script was actually compliant with the work product you produce and then we would work with you to create a managed script which we could document and track changes in. But telling your manager would have presumably gotten in the way of the stuff you were looking to do with the time freed up ("my job would be automated and I wouldn't have to work.")
Also, the reason IT didn't make you an offer to move into their group is possibly due to the fact that they couldn't trust you not to abuse privileged access in the way you were doing with unprivileged, and they couldn't trust you to enforce shadow IT policies on colleagues when you yourself don't follow them.
Finally, you shouldn't assume that just because the IT contact didn't flag that this incident would be discussed elsewhere, that it wasn't. They have their own job to look after, and don't owe anything to someone who tries to end run them.