(Originally published May 2022)
90% of Fortune 500 today use Teams. This overwhelming reliance on Microsoft Teams has turned it into a goldmine of sensitive data. For CISOs, that means addressing Teams security issues and following Teams security best practices are a #1 priority.
This article covers:
In any given organization, two categories of devices are typically used to access the Microsoft Teams environment: authorized devices, which are managed and monitored by IT staff, and unauthorized devices, which are not. The latter poses a significant risk for data leaks. Microsoft 365 provides administrators with tools to limit access from unauthorized devices, enabling users to view documents but preventing them from editing or downloading sensitive information.
Best Practices:
Incorporating external vendors, contractors, and guests into Teams for their expertise is common. However, it's crucial to limit their access to prevent the exposure of business-critical information. Teams allows granular control over guest access, but it requires the creation of private channels or careful management of access permissions.
Best Practices:
Available on-demand: Microsoft experts covered how to manage personnel changes and external users in M365 in this 45-minute webinar.
With the shift from email to instant messaging for work communications, controlling access to specific channels in Teams has become more critical. Channel moderators can help manage this by controlling who can start new posts, add or remove members, and oversee bot activity within the channel.
Best Practices:
Screen sharing during video conferencing is a common practice but can lead to unintentional data exposure if notifications are not turned off. Mismanaged screen sharing settings can display private conversations or sensitive information to unauthorized viewers.
Best Practices:
The necessity of sharing documents remotely introduces security concerns, especially since Teams inherits security settings from SharePoint and OneDrive. Microsoft 365's Sensitivity Labels help mitigate this by maintaining specific access rules with documents as they are shared.
Best Practices:
Phishing remains a prevalent threat, adapting to target Teams users with malicious links. Microsoft 365 combats this with Safe Links, which scans URLs before redirecting users, but constant vigilance and education are crucial.
Best Practices:
Organizations must also navigate compliance and data residency regulations, which can vary significantly across jurisdictions. Microsoft 365 Multi-Geo capabilities allow for data storage across different locations, facilitating compliance with various data protection regulations.
Best Practices:
Beyond addressing specific security issues, several overarching best practices can fortify your Teams environment:
By integrating these best practices into your Microsoft Teams strategy, you can significantly enhance the security and compliance posture of your Teams environment. To codify these best practices, use them to create a robust M365 governance framework.
Or, if you aren’t sure how to get started, use the Microsoft 365 Governance Starter Kit complete with an assessment checklist, strategy template, and plan template.
Just interested in Microsoft Teams governance? Establish crucial Teams creation and management policies with the free Microsoft Teams Governance Plan Template.
Securing Teams is not a one-time process but a continuous effort that requires vigilance, adaptation to new threats, and regular review of access controls and policies.
The easiest way to close the door on these M365 security threats? End-to-end Microsoft Teams security, governance, and automation tools from CoreView.
Learn how a Canadian utility company assessed (and remediated) insider threats in minutes with CoreView, finding and fixing key collaboration and identity risks.