72
Attacks abuse Microsoft DHCP to spoof DNS records and steal secrets
(www.theregister.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 09 Dec 2023
72 points (97.4% liked)
Technology
59205 readers
2637 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
I hate to be that guy, but the documentation for AD DHCP goes over this.
It isn't always Microsoft's fault when they fail to save their customers from their own stupidity and lack of concern for security.
It is bad that this is the default behavior, but defaults aren't always defaults because they are the best, they are the defaults that will all work functionally together as long as everything is at default settings.
It is more about making it "work out of the box" with defaults than "making sure it is secure out of the box."
Frankly, the security of their AD DHCP/DNS is the job of the SysAdmin, not Microsoft. A SysAdmin is supposed to be a professional, so why do they want to blame a third party for their own shortcomings and lack of security conscientiousness?
Nobody is blaming Linus for badly secured Linux servers, or saying the defaults should be more secure.
I am going to blame Microsoft, because “works out of the box” shouldn't conflict with “secure out of the box.”
And while I won't blame Linus for insecure-by-default Linux configs, I will blame whoever integrated the distro/dockerfile/etc.