this post was submitted on 03 Dec 2023
41 points (100.0% liked)
Cybersecurity
5410 readers
117 users here now
c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.
THE RULES
Instance Rules
- Be respectful. Everyone should feel welcome here.
- No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia.
- No Ads / Spamming.
- No pornography.
Community Rules
- Idk, keep it semi-professional?
- Nothing illegal. We're all ethical here.
- Rules will be added/redefined as necessary.
If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.
Learn about hacking
Other security-related communities [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
Notable mention to [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What does that mean?
It’s a term used for when IT operations teams want to keep the status quo design of their environments when upgrading or modernizing their infrastructure, instead of fixing and securing things while they’re at it. The common excuse is that they will fix issues once migration/upgrade is complete, either because they’re on a tight timeline to do it, they’re afraid of breaking things, or just plain lazy. They will say it’s temporary until things have settled down. And we all know there’s nothing more permanent than a temporary implementation. The result is the same issues and problems exist, just on new infrastructure.