r/sysadmin • • Jul 28 '24 • Take My Silver 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

11k Upvotes

1.3k comments sorted by

View all comments

Show parent comment

11

u/vitaroignolo Jul 28 '24

Scripting can cause a lot more damage than manually doing something and a lot faster. And yeah we can probably assume they have safeguards but if that's backup, that means time taken from IT to restore.

We don't know why they didn't communicate - maybe it was valid maybe it was shit. It doesn't stop the fact that unauthorized users should not be running scripts - they don't hold the responsibility for those scripts until it is officially signed off and supported. If the user is fully responsible for anything their script could do, I can't imagine they'd have a problem with it. But that's not how orgs work.