Re:Twitch is hacked, and its source code leaked
by unethical_ban on Wednesday October 06, 2021 @04:05PM
(#28777728)
No one in IT should have access to business data. That's simply best practice. Worst case would be a database engineer who has access to backups or some prod data for troubleshooting, and even that should be under tight control with good access accounting.
[ Parent
| on HN ]
Re:Twitch is hacked, and its source code leaked
by hamburglar on Wednesday October 06, 2021 @04:20PM
(#28777926)
Welcome to devops. Ask Mike down the hall to add you to the “admin” group. Tell him you’re a new dev so you need everything.
(This is a joke but also, at many companies, it’s not. Twitch was once small and grew. Who knows what ancient all-access switches are still critical to running the systems, marked “tech debt” in someone’s backlog)
Re:Twitch is hacked, and its source code leaked
by unethical_ban on Wednesday October 06, 2021 @05:48PM
(#28778925)
The whole point of devops is to automate everything according to best practices, so fuckups are a thing of the past! The only fuckups, of course, will be Terraform state issues.
Re:Twitch is hacked, and its source code leaked
by syshum on Wednesday October 06, 2021 @08:15PM
(#28780133)
No the whole point of devops is to get rid of those terrible sysadmins always keeping the devs from doing anything...
Once you have "DevOps" the devs are ops, your head count drops, and all that pesky security and other things those dirty sysadmins wanted are gone
kinda /s sometimes I think that is really want managers think about devops
Re:Twitch is hacked, and its source code leaked
by hamburglar on Wednesday October 06, 2021 @08:22PM
(#28780179)
As it turns out, the entire industry doesn't quite agree on "the whole point of devops."
Re:Twitch is hacked, and its source code leaked
by cube00 on Wednesday October 06, 2021 @06:21PM
(#28779218)
Until the business raises a priority one incident that their monthly reports are not looking right and you need to dive into the data to find out why some other API back end decided to present its numbers this month divided by 1000 for ease of display to their own users.
I know, I know, service contacts but my point is sometimes engineers need at least temporary access to provide support at times.