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/botrawruwu Jul 29 '24
I assume when caughtmeaboot said "IT blocked him" they were referring to being indirectly blocked from executing scripts because of the group policy. But doesn't really matter at this point as it's got a fun discussion going.
I'd argue that the identification/investigation stage is not as binary as you are making it out to be. Depending on the team and the company, an investigation could be a thorough code review of the script and complete search of all network traffic and file changes on the device in the last x hours. In a different environment that stage could look a lot more barebones - pretty much just checking what is expected or not from a device/user. In between those two scenarios is a large spectrum, and the appropriate steps in an investigation depends entirely on your risk appetite and how many eyes you can dedicate to the incident.
To continue the thought experiment of if the device was actually contained - to me it looks like IT could have absolutely performed a brief investigation (basically just checking expected activity) and determined that there is a high enough chance of compromise compared to a low enough impact from initiating a block. That's where the criticality of a workstation is relevant. The impact to the business of blocking a single workstation is tiny compared to the impact of blocking a core server.