IT guy here, if we gave developers the option to exclude whatever the hell they wanted from AV scanning it would just mean that we would end up with computers where the entire C: drive would be excluded.

No, can't have that.

So what should a decent IT department do to give developers the access they need to do their job while maintaining a decent level of security?

Well, the least bad solution I have worked with was to have a non generic path that was excluded by policy.

Something like C:\Excluded

The directory was excluded from AV scan and allowed in policy, the user could put what they needed there and it would be fine.

[–] wizardbeard@lemmy.dbzer0.com 7 points 8 months ago

Your user base must be better than mine.

Some chucklefuck over a decade ago caved to the "need" for a public shared drive. I can see the argument for things like HR policy documents and such. But they didn't just give all users read access. Oh no, everyone got full read write. No fucking governance model, no process to check that PII wasn't being stored there by people too lazy to follow proper procedure.

Thankfully that horror has been thoroughly killed, and MS Teams makes it so easy for people to spin up collab spaces and file storage that there's no use case anymore.

load more comments (13 replies)