This means that IT only need to concern itself with the in-app security. In a BYOD environment whereby IT can’t restrict the functionality of the device then sandboxing can make sense.
Although, it must be said that Android Enterprise (formally known as Android for Work) and iOS have matured and provided built-in, out-of-the-box separation of private and corporate data. Sandboxed applications are designed to mitigate these threats.
In addition, mobile devices do not provide an audit trail for potentially where the data has leaked. This is called Shadow IT.Īll the above threats mean that valuable corporate data can leak outside the control of IT. Once this has happened the data is outside the remit of IT’s control. Shadow IT: If IT doesn’t provide the tools to do business then users may default to using applications that synchronise corporate data.
Not having an MDM to provide device management means that corporate data on the device is at risk. Malware: Both iOS and Android have suffered their fair share of exploited vulnerabilities and malware. The three main vectors are:ĭata Leakage: A Q1 2016 Report by AppThority found that 48.2% of applications on iOS and 86.7% of applications on Android leak data.
This is because data using native apps and mail clients can potentially be exposed. It is only with the advent of corporate information residing on mobile devices that the need for sandboxing arose. The wrapping process enables the app to only communicate to other wrapped applications, push configurations, encrypt the app and its communications and push MDM policies to restrict in-app behaviour. The sandboxed applications are either available by vendors or the MDM vendors provide SDKs or URLs to upload and wrap the applications.
0 kommentar(er)
