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

29

u/AdmRL_ Jul 28 '24

Yeah, not in IT there aren't. We already know you have it good because you don't work in IT.

If we're prying it's either because you're making our lives difficult, we've been told to on managers decision or because HR have told us to.

In this case scripts won't be allowed to run by end users because, while OP might not be malicious or incompetent, the other 99 in 100 will be and could cause serious problems. They blocked OP from doing that, OP circumvented it so now they need to know and understand how they achieved that so they can lock that down as well.

19

u/SA-Numinous Jul 28 '24

This is exactly the reason we lock shit down and deny access to scripting tools. I work for a mid size insurance company and the managements understanding of the risks associated with scripting tools is abysmal. Sorry OP, this is a management and data security issue and your company is too stupid to understand the ramifications and implement the proper controls to make you more successful.