588
Disney hack leads to 1.2TB of Slack communications leaked online
(stackdiary.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 14 Jul 2024
588 points (98.5% liked)
Technology
59169 readers
2343 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 think when Disney demands an internally-hosted version of your product, then the sales team tells engineering that they'll provide one, and mark the price up accordingly. That kind of thing doesn't appear on the external listing for everyone else.
Why would Disney demand that?
Why would they choose slack if they want to host, maintain and be responsible for the internal chat themselves?
They choose slack because they do it for them so that they don't have to do it themselves. That is the selling point for them.
Businesses buy cloud services, because they do not want to manage stuff themselves.
They can still have support contracts and SLA etc from slack.
It's just that the servers slack runs on are on-prem and completely controlled by the business buying into the self hosted licence.
The benefits should be tighter security (say, can only be accessed via VPN), and for many many MAU probably lower costs. Chances are, Disney already has datacenter ops and hardware contracts.
And why choose slack? For quite a while, it was extremely common for developers (maybe even industry standard?). It had loads of features in the small market of internal chat programs. And it's easy to build extensions and integrations for.
I'm not saying that Disney is running on-prem slack, but I wouldn't be surprised if they were
Ostensibly better opsec
Your logic isn't making sense.
The code would end up somewhere for others to use...? What?
One-off products or beta offerings are often kept private, sometimes indefinitely.
In this case, Disney is using Slack Cloud-hosted for internal communication, but I can definitely understand people interpreting it differently.
Providing Disney with an internally hostable version of Slack doesn't require giving them the code. They can just ship them compiled binaries