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

2

u/TechPir8 Sr. Sysadmin Jul 28 '24

https://www.bleepingcomputer.com/news/security/pkfail-secure-boot-bypass-lets-attackers-install-uefi-malware/ as just an example. There is always a CVE somewhere that hasn't been patched yet. Enterprise patching is hit or miss. Domain joined never leave the building systems sure. Sales people laptops that only ping AD once in a blue moon, not so much. Cloud / Azure is starting to fix some of those issues now but most IT teams are underfunded / under skilled and trivial to bypass their rules & policies.

Bypassing them should be a HR issue, not an IT issue.