4 ms·
I know. We use emails for some meeting summary. But you can't ignore the fact that many attacks start with phishing, and slack is free from that problem
by itaifrenkel 10y ago
I know. We use emails for some meeting summary. But you can't ignore the fact that many attacks start with phishing, and slack is free from that problem
- the_common_man 10y agoSlack is not free of the problem whatsoever: https://arstechnica.com/security/2016/04/hacking-slack-accounts-as-easy-as-searching-github/ https://arstechnica.com/security/2016/04/hacking-slack-accou... http://www.businessinsider.com/slacks-security-breach-may-be-worse-than-its-letting-on-2015-3 http://www.businessinsider.com/slacks-security-breach-may-be... http://www.networkworld.com/article/3123727/collaboration/the-next-target-for-phishing-and-fraud-chatops.html http://www.networkworld.com/article/3123727/collaboration/th...
- daenney 10y agoThose three links don't really relate to third parties getting unauthorised access through phishing by leveraging Slack. Slack has plenty of security issues, but you're not proving phishing by any of those sources. It can potentially make you more vulnerable to phishing, but that's not the same thing. The links in question relate to: * Searching on GitHub for Slack API tokens * The Slack database hack * How the rise of ChatOps can open you up to many more issues if someone gains access to employee's Slack accounts and the risk of third-party applications which might open up things you do to more entities than you realise