Forum Discussion
StefanKi
Feb 20, 2017Iron Contributor
security guidelines, tools or services to safe and protect in Office365 + Azure for krypto trojaner
Hi,
has Microsoft any security guidelines, tools or services to safe the and protect the user in Office365 and Azure for krypto-trojaner like Locky?
Regards
Stefan
3 Replies
Sort By
- Cian AllnerSilver Contributor
There are lots of material and resources for securing Office 365 (for Azure look at this post from yesterday - Azure Security Center Guide and Demo).
I would start with Office 365 Secure Score, which is now GA, it's not specifically about ransomware but it will check the state of your tenant and how well it's doing with making use of the available security features to mitigate risk. Secure Score will make recommendations on how you can further improve security in your tenant. There is a demo below and more information here - Introducing the Office 365 Secure Score.
New Office 365 capabilities help you proactively manage security and compliance risk
There are plenty of recorded presentations, you can find in the Events section, which goes into great depth about securing Office 365, here is a couple of them:
Get the most out of the Office 365 security solutions
Secure Office 365 like a cybersecurity pro—assessing risk and implementing controls
Fresh from MS Ignite Australia 2017 (hosted on Channel 9)
Security and Compliance Update for Office 365
Hope that helps a bit.
Well, this blog post was just published yesterday: https://blogs.technet.microsoft.com/enterprisemobility/2017/02/20/ransomware-lateral-movement-and-how-microsoft-advanced-threat-analytics-can-help/
Advanced Threat Protection for EOP is another thing you should consider if your company/users are being targetted.
- Cian AllnerSilver Contributor
VasilMichev wrote:Advanced Threat Protection for EOP is another thing you should consider if your company/users are being targetted.
Agreed, we found Advanced Threat Protection for EOP a must for protecting against threats, though after a lengthy trial we went with Proofpoint in the end.