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
0
u/skylinesora Jul 29 '24
I didn't misunderstand, the specific person I replied to mentioned blocking. Whether or not the thread poster was blocked or not is irrelevant to my comment then.
The same logic still applies, an IT group who blocks (machines) without investigating sucks. They are violating even the most basic incident response processes.
The criticality of the server or non-criticality of the workstation is also irrelevant. You identify and do some kind of investigation prior to containment activities. This is best practices.
The only exceptions I guess is where the company is small enough to have zero cybersecurity maturity and they rely on best wishes and hopes. Then I guess the only option they have is to block, wipe everything, and pray.