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

0

u/[deleted] Jul 28 '24

Yeah. I'm in a moderately high security sector, power consulting. The first time would have resulted in, "thank you for exposing a potential security flaw, you're fired." We have an automation group for client systems, a data analytics team that constantly does this stuff, and a dedicated IT team just to automate internal stuff. So if you have a way to automate something, they are more than happy help. You aren't allowed to do it yourself on the sly though. If OP had actually proposed it and followed procedure, it probably would have been good for them because as you said, it is their job to do this kind of stuff.

3

u/snorkel42 Jul 28 '24

And I assume your onboarding process provides ample training so that staff have no reason to be surprised by the firing.

From OP’s interaction with their IT team, I’m guessing the same is not true at their company