Re:Security 101 for SaaS startups
by itaifrenkel on Sunday March 05, 2017 @05:17PM
(#13799122)
And... Apparently after enough time, people come to expect slack to be asynchronous too.
> And the two teams I worked on that use slack killed productivity by chatting all day and sending animated gifs.
That sounds much more like a people problem than a technology problem, if that's how they chose to spend the majority of their time on the job.
Re:Security 101 for SaaS startups
by itaifrenkel on Sunday March 05, 2017 @05:13PM
(#13799100)
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
Re:Security 101 for SaaS startups
by the_common_man on Sunday March 05, 2017 @05:46PM
(#13799304)
Those 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
Email gives me a reminder to keep me organized.
And the two teams I worked on that use slack killed productivity by chatting all day and sending animated gifs.
Plus, people expect email to be asynchronous. With slack, I get a mixture of immediate and asynchronous requests. So every message breaks my flow while I determine the priority level.