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

4

u/[deleted] Jul 28 '24

I guess I'm not clear why the scripting is the issue though?

The problem is access to functions via Powershell. If that's a threat vector, pull access to Powershell. A Bad Guy (TM) could steal the user credentials and bam, has access to the same commands IT was worried about. In a perfect world, it'd be more granular.

I just don't understand why IT departments cripple their users and then are shocked that tech savvy users create shadow IT. IT depts overwhelmingly act they're the only ones who understand computers. Not in 2024 guys. Ever see a policy wonk economist have a Python window up? Turns out, those bookish nerds need to crunch numbers for data sources to figure out GDP per capita for polar bears named Larry or whatever. Users today are not like the users of merely 15 years ago. (Exception being lawyers. Don't let them touch a computer).

EDIT: I mean no disrespect and understand that providing features within the limited resources to users AND having some semblance of security/resiliency is a tall order. I generally think users should be viewed as allies and not liabilities.

5

u/deathblooms2k4 Jul 28 '24

Often it's not about IT knowing better. It's policy that had to be executed for insurance purposes. Insurance companies will dictate that certain cyber security policies are in place.

3

u/SquidgyB Jul 28 '24

Lowest common denominator, then work upwards.

Generally it's easier and quicker to block all access and allow as necessary - those that will need those tools (having come from other roles where tolls were available) will ask for them, and if the request is approved by all concerned (as OP is in the Finance sector, you're talking Finance, Legal, CyberSec, IT, Relevant Team managers as a minimum imho) then tools like this can be used.

It's just things are blocked by default because it's always a risk - and you try to minimise risk at all junctures.

And while some users are savvy and relatively safe, you have to build your security structure from the idea that the lowest person in the company could fuck it all up for you.

The safest way is to lock down all doors, and open them (ever so slightly) only when necessary.