In a significant data breach, hacktivist group NullBulge has infiltrated Disney’s internal Slack infrastructure, leaking 1.2TB of sensitive data. This breach, posted on the cybercrime platform Breach Forums on July 12, 2024, exposes many of Disney’s internal communications, compromising messages, files, code, and other proprietary information.
An export like this does not include private slack channels from what I know of Slack design and export mechanisms
https://slack.com/intl/en-gb/help/articles/201658943-Export-your-workspace-data
It absolutely does
Right, org owner
I think it would depend on the level of the account. They have that feature for compliance reasons in heavily regulated industries.
Kinda, but not even admin accounts can view/export private channels they are not a member of.
I don’t think that’s even a feature
https://slack.com/intl/en-gb/help/articles/201658943-Export-your-workspace-data
It absolutely is.
Slack must have this for compliance issues, or they would be locked out of many industries (like banking and insurance)
I had to manage a Slack migration to another org we were merging with. As the owner, normally I couldn’t even see the names of private channels, but when it came down to the migration, upgrading the account to Business+ tier, the full export included everything (private channels and DMs), which we imported into the new org.
Slack sends notifications to all Admins that the export was happening, and i’ve only seen that notification once after using Slack for 10 years.
😮I bet there is some spicy stuff in the DMs of companies with 1000+ people
IIRC Admins can not, but Org owners can in certain situations.
Definitely is a feature… Have personally used it.