More and more organizations use Microsoft Teams for collaboration, including the sharing of documents.
It is quite common for users to upload files into Microsoft Teams, to share with colleagues and customers, and this introduces some risks. If the user’s device does not have adequate anti-malware protection installed, uploaded documents may contain malware or other undesirable content. Other users opening these files may end up having their devices infected, and naturally this is not wanted.
Teams Protection, part of WithSecure™ Elements Collaboration Protection, can now be used to scan uploaded content, and if it is found to be harmful the content can be deleted, or quarantined.
Taking Teams Protection into use
It is quick and easy for the organization’s Microsoft 365 Administrator to take Teams Protection into use. with just a few clicks.
What does the Microsoft Teams user see?
Whenever a file is uploaded to teams, it is scanned by Teams Protection, and this includes full analysis to see if there is harmful content. Please note: the file used in these screenshots is a harmless test file used for demonstration purposes, but the product works in the same way with real malware.
If an uploaded file is considered harmful, for example containing malware, the user is not able to open the file. When they do try this, they are given a short summary that the file has been quarantined or removed, and they can then inform the person who uploaded the file, or with the Microsoft 365 Administrator if they think the file should have been allowed.
If Teams Protection does not find anything harmful with the uploaded file, it is made available to the other users for downloading or opening.
What does the Microsoft 365 Administrator see when a harmful file is detected?
When harmful content is found, the administrator is able to see the full details, such as file name, file location, and the nature of the harmful content.
With the information presented, the administrator can check further to see if the file should be acted on further.
If you are not yet using WithSecure™ Elements Collaboration Protection, you can find out more on our website.
