memes

10226 readers

1909 users here now

Community rules

1. Be civil

No trolling, bigotry or other insulting / annoying behaviour

2. No politics

This is non-politics community. For political memes please go to [email protected]

3. No recent reposts

Check for reposts when posting a meme, you can only repost after 1 month

4. No bots

No bots without the express approval of the mods or the admins

5. No Spam/Ads

No advertisements or spam. This is an instance rule and the only way to live.

Sister communities

[email protected] : Star Trek memes, chat and shitposts
[email protected] : Lemmy Shitposts, anything and everything goes.
[email protected] : Linux themed memes
[email protected] : for those who love comic stories.

founded 1 year ago

MODERATORS

Tenthrow

The_Picard_Maneuver

[email protected]

771

So what's changed Microsoft? (lemmy.world)

submitted 6 months ago by androidisking to c/memes

76 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] Boozilla 49 points 6 months ago (1 children)

The old paradox of Microsoft security updates. The more frequent they are, the more they look like they're staying on top of things. While at the same time showing the world there are a lot of frikkin' security holes in Windows all the time.

[–] mlg 31 points 6 months ago (1 children)

Update kbmorbillionnumbersandletters:

Fixes issue in update kbevenmorenumbersandletters

[–] [email protected] 7 points 6 months ago (1 children)

Part of my job used to involve explaining patch supersedence to leadership so that they had a clear idea of why a totally different patch needs to be loaded to address a vulnerability reporting a different patch number in the scanner.

[–] [email protected] 1 points 6 months ago (1 children)

Tenable (or how our security folks have our scans configured) doesn't seem to get that.

[–] [email protected] 2 points 6 months ago (1 children)

I used to have to explain it to them too, but could usually get them to understand by referencing the CVE and the breakdown from the MS security updates guide.

[–] [email protected] 2 points 6 months ago

My favourite is:

Them: We want less red in the pie chart. Fix that remote vulnerability.

Me: We don't even have that component enabled. It's reporting on a DLL file version, not the vulnerability itself.

Them: Just lower our vulnerability score.

(Me wondering if I deploying dozens of fully-patched systems would have the same proportional effect)