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
If you're a grey-hat/chaotic-good hacker intent on exposing corporate greed or whatever, with a cache like that, you've got a couple options....either release inmediately, or review the data to minimize collateral damage and release.
If the intent was to help people, and there was no driving force to release immediately, then they should've waited and reviewed the data.
I really worry if this is going to lead to my overly-ambitious infosec group putting the kibash on our unofficial/shadow-IT (fully internal) MatterMost.
Review the data cost your time (which is work time, could be transfer into money).
So, better release it all.