Steve DeJarnett

@Chipper Just checking in to make sure you got the answers you needed. If there's anything else we can do to help, please let us know.

Cross-linking for visibility. I just shared an update in the Mobile Threat Defense area, but this report is relevant to everyone. Steve

Our partners at Lookout just released their Q1 2025 Mobile Threat Landscape report. This summarizes and highlights the latest threats affecting mobile devices and provides a broader view of the security threats impacting companies around the world. Q1 2025 Mobile Threat Landscape Report Also, as a reminder for everyone using Workspace ONE Mobile Threat Defense, you can find a monthly update on the latest emerging mobile threats in the "Intelligence" tab on your Workspace ONE Mobile Threat Defense console. Stay safe out there! Steve

As noted, should be fine, but please note that IP addresses for UEM instances are regional. If you have the chance to use domain names instead of IP addresses for traffic rules, it's better as these should change very infrequently. Just a best practice, not suggesting you've done anything wrong here, and I realize that network infrastructure typically prefers IP addresses for rules matching.

@Daniel.Stefanovic It is available now. Documentation for setting it up is found here: https://docs.omnissa.com/bundle/WorkspaceONE-MobileThreatDefenseVSaaS/page/MTD-IntegrateWithUEM-SG.html If you have tried this and run into problems, please let us know or open a support ticket. Sorry for not catching your comment earlier.

While Omnissa is not exhibiting at the RSA Security Conference, a few of us will be there throughout the week. If you or any of your colleagues are interested in meeting up to discuss ways that Omnissa products can help you or your organization improve both your security and end-user experience, reply below. I'd be happy to connect there.

With the recent launch of DeepSeek, and more generally with multiple AI/LLM apps available, we've heard from customers who want to block access until they can assess the risks. Workspace ONE UEM provides a number of controls that can block applications from installing or running, but one place where that doesn't apply is on the Personal side of an Android COPE device. Normally personal side content isn't a concern, but since the Messaging apps live in the Personal profile, it's possible that work content could be exposed. With Workspace ONE Mobile Threat Defense (MTD) and the Dual Enrollment feature, companies can now better-protect the organization from threats or issues in the Personal profile as well. Read the blog post from @Andreano Lanusse below to learn more about ways to manage and control access to applications. https://techzone.omnissa.com/blog/ai-world-shaken-deepseek-protecting-managed-mobile-devices-workspace-one-uem

Very practical advice to help you manage any kind of application, with specific examples of how to manage access to DeepSeek. Bookmark this.

This gives great flexibility to customers and allows simplified rollouts. Great to see this feature launch!

Hello everyone, I want to share some information to help the recovery process for devices impacted by today’s event related to CrowdStrike sensor updates that cause Windows blue screens. Customers using BitLocker will be locked out after applying the CrowdStrike workaround and access to the recovery key will be required to recover the devices. If your organization manages the Windows devices with Workspace ONE UEM we can help to reduce the recovery time for those devices. Workspace ONE UEM provides self-service access to the BitLocker recovery key through the Self-Service Portal and also in the Intelligent Hub on iOS and Android, which will help to speed up the recovering of all impacted endpoints. Accessing the recovery key on Intelligent Hub enables the end-user to quickly recover the device themselves without the need to contact your company’s Help Desk. To enable users to access the recovery key on their mobile device, make sure the access to the Encryption Recovery Key is enabled in the Hub Services Console. Once you have enabled Encryption Recovery Key, users can open the Intelligent Hub on their mobile device, locate their Windows device under the My Devices List, and finally under Encryption access the recovery key for their respective device as shown on the following screens. Workspace ONE UEM provides other methods to recovery the BitLocker Key, to learn more check the Tech Zone tutorial Enabling BitLocker Encryption to Remote Windows Devices. We hope this helps you and your users recover your systems. If anyone has run across another way that you've resolved this, please let us know so we can add it to our list of resolutions here. Special thanks to @Andreano Lanusse and Josh Burris for their contributions to this post. You can also find this information in our Knowledge Base.