One of the things we hear all the time from our enterprise customers is that they view Appthority as the ‘brain’ of their mobile security strategy while seeing their MDM system as the ‘brawn’ when it comes to remediation. When put into practice, this means that Appthority is being used to analyze mobile apps for risk as defined by the unique mobile information security policies of each enterprise. But when it comes to enforcement, or taking action on specific devices based on the risk policies Appthority is managing, then the MDM system becomes the tool of choice given its many features for managing fleets of mobile devices. So for IT to have a smooth overall mobile risk management workflow, it is critical that Appthority streamline integration with our supported MDM systems.
We’ve enhanced our integrations with both MobileIron and Airwatch to improve mobile risk management workflows. First, for MobileIron customers, we are now including support for the much requested device Quarantine function as one of the remediation options. This means that IT will now have the ability to set an escalating enforcement chain that can include quarantining a device should the risk policy establish a level of risk that merits this action. For Airwatch customers, we’ve now included support for integrated whitelists and blacklisting features of that system. This means that Appthority can continue to analyze mobile apps for risk levels and to automatically assign apps to either an Airwatch managed whitelist or blacklist.
Finally, Appthority is working closely with both Airwatch and MobileIron to integrate and expose our Smart App Lists (SALs) capabilities to both those systems. What customers will see is that Appthority’s SALs will automatically show up in the MDM admin consoles so that IT can assign device enforcement actions based on the apps that are automatically populated to those lists by Appthority. For example, a SAL that was generated for company executive devices based on mobile risk policies, would be available to MDM admins so that they could then assign specific device and/or notification actions to take should any app violate those policies.