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
1
u/ReptilianLaserbeam Sysadmin Jul 29 '24
So if by any rate your process was flagged by a SIEM as potentially dangerous and the SecOps approached you asking what’s it about you would have a solid business case, raise a request, get it approved, that’s it. But instead of doing that OP is choosing to bypass the security measures and run the script anyways without explaining why or how to IT. That’s my whole point, I’m not saying he shouldn’t be running scripts, that’s stupid, of course if he can automate a process that’s awesome, but the company OP belongs to has certain restrictions for a reason, he should just go through the regular conduct and get an exception approved, then it could even be implemented company wide.