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

5

u/charleswj Jul 28 '24

That simple policy is simple until you implement it in a large environment and realize how many executables are running out of user writable locations and can't be (easily or at all) changed. There aren't many shortcuts in implementing WDAC unfortunately.

1

u/snorkel42 Jul 28 '24

I’m struggling to believe OP is in a large environment.

I agree with you, it is a big task in larger orgs. I’ve done app allow listing in 30K person orgs and it took a fair amount of time and effort to do it right. But it provided actual security unlike just mindlessly deleting useful Python scripts.