The Difference Between Managed (MAM) and BYOD (EMM/Appdome Security) When Preventing Screenshots and Copy/Paste
Even when communication and data transfer from an app is restricted, screen sharing, screen recording and screenshots may still be used to extract sensitive data. Preventing these functionalities adds additional protection against data leakage. Appdome offers several options for preventing screen sharing and copy/paste in Android and iOS apps. The implementation, however, is different when the device on which the app is installed is a managed or a BYOD device.
This Knowledge Base article describes the functionality difference in Preventing Screen Sharing and Copy/Paste on managed and unmanaged (BYOD) devices.
If an end-user is using a managed device (either corporate issued or managed BYOD), you (the Appdome user) would fuse the relevant EMM-MAM service to the app and use the EMM-MAM to control/block screen captures and enable copy/paste prevention. Of course, you could augment the EMM-MAM protections with Appdome specific features as well as use Appdome DEV-Events to notify you (in the app, to the app server, etc.) if and when screen captures were taken.
If end-user is using a non-managed device (true BYOD), you would fuse Appdome’s Block Screen Capture, Copy/Paste prevention (and additional features such as Blur Screen as required) to the app. These features do not require a management system and can be applied to all apps – without or without a management system. The protection is placed inside the app as if the developer added that protection in the app.
OS Specific Implementations
In Android, the implementation-enforcement is self-contained in the app. Users trying to take a screenshot will only see a “black screen” in any attempt. In iOS, it’s a little different based on the way iOS is designed. In iOS, the default behavior of Appdome’s Block Screen Capture is to “notify” on the event. In iOS, the app will be closed and the user will be notified that screen capture is not allowed. As an Appdome admin, you can enhance this implementation with Appdome’s DEV-Events to send a notification to IT, Compliance, or to the app via Appdome’s API directly to the app server or the authentication service used to authenticate the user to the app, etc. This would allow you to revoke access to the app if/when a screen capture is taken.
Either way, Appdome’s implementations cover all forms of screen capture – screenshots, screen recording and mirroring. So, we offer 360˚ protection with or without an EMM-MAM.
After Adding Prevent App Screen Sharing and Copy/Paste Protection to a Mobile App on Appdome
After you have added Prevent App Screen Sharing and Copy/Paste Protection to your app, there are a few additional steps needed to complete your mobile integration project.
Add Context™ to the App
Appdome is a full featured mobile integration platform. Within Context™, Appdome users can brand the app, including adding a favicon to denote the new service added to the app.
For more information on the range of options available in Context™, please read this knowledge base article.
Sign the App (Required)
In order to deploy an Appdome built app, it must be signed. Signing iOS app and Signing an Android app is easy using Appdome. Alternatively, you can use Private Signing, to download your unsigned app and sign locally using your own signing methods.
Deploy the App to a Mobile Device
Once you have signed your app, you can download to deploy it using your distribution method of choice. For more information on deploying your Appdome-Fused apps, please read this knowledge base.
That is it – Enjoy Appdome with Prevent App Screen Sharing and Copy/Paste prevention in your app!
How Do I Learn More?
If you have any questions, please send them our way at firstname.lastname@example.org or via the chat window on the Appdome platform.
Thanks for visiting Appdome! Our mission is to make mobile integration easy. We hope we’re living up to the mission with your project. If you don’t already have an account, you can sign up for free.