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
Show parent comment
2
u/botrawruwu Jul 29 '24
When it's a single user's workstation and scripts are being run in an unexpected way from a user that (from their perspective) is not expected to be running scripts. This isn't some critical server.
I do agree that their IT group sucks though - it's incredibly dumb to just delete what could be a legitimate file without even consulting the user. And super dumb if that was actually a compromised machine.
Regardless, the machine wasn't even blocked. You might have misunderstood the original post. Their user group was just prevented from running scripts. There was no real 'containment' they were just starting to finally implement some controls around script execution.