When we designed our survey looking to quantify the time it takes to manage the email threat, we tacked on a few questions that, at first glance, might seem unrelated. We asked about:
- The level of vulnerabilities present in Slack and Teams
- The type of risks involved with those platforms
- And when protection would be needed to address these concerns
We asked this because, as Slack and Microsoft Teams security providers, we're seeing in real-time the types of attacks inherent in the platform. We wanted to see what the general public thought, as well, of the needs of Slack Security and Teams Security.
The results spoke volumes.
76.1% of respondents strongly agree or agree that vulnerabilities in Slack and Teams present a security risk.
Most respondents felt they would need to adopt mitigation technology in about eight months.
Of the most prevalent concerns about risks, here's where the respondents came out:
The biggest concern was leakage of sensitive data, at 72.6%. Phishing links are second at 60.7%. Messages with malicious files, and the hosting of malicious files, weren't far behind.
Think about your Slack or Teams usage. How often are you quickly sharing files or links? Are you accepting requests from an external partner? In other words, has the email hygiene you've been working on for years transferred to collaboration apps?
Our analysis indicates no. For the State of Microsoft Teams Security report, we analyzed close to 200 enterprise customers and found that most end-users operate as if Teams is internal only and completely safe.
This isn't the case. And as the collaboration apps—Teams in particular—skyrocket in popularity, the issues this could present are huge.
Securing email but not Slack or Teams isn't full security.
Learn about how we secure collaboration apps by RSVPing to our webinar on Thursday, February 25th at 1 PM ET.