Selective Screen Capture Protection via Custom UI Class Extension
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data loss prevention solutions for enterprise managed devices lack the ability to selectively control screenshot capture, leading to either global restriction on all applications or no control at all, failing to protect sensitive information while allowing non-critical content to be captured.
Innovation Solution
Implementing a dynamic system that extends operating system classes to selectively hide sensitive content during screen capture by using a custom UI class with protected fields, allowing configuration-based control of what content is protected or exposed, enabling administrators to define protection levels for users and devices without requiring application updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If screenshot prevention is implemented at the device level for all applications, then data security is improved, but user experience deteriorates because every application is blocked from screen capture
Solution Approach 1:
The patent segments the screen capture protection mechanism from a global device-level restriction to an application-specific and content-specific control. By implementing protection at the application level rather than device level, only specific applications can enforce screenshot prevention, allowing other applications to function normally. This segmentation resolves the contradiction by maintaining data security for critical applications while preserving user experience across the entire device.
Solution Approach 2:
The patent applies local quality by enabling screenshot prevention selectively for specific applications and even specific content within applications, rather than uniformly across all applications. The UEM solution allows administrators to configure protection policies for individual applications, creating localized security zones where screenshot prevention is enforced only where necessary, thus maintaining both security and user experience.
2Reliability
If screenshot prevention is applied to all applications, then confidential information is protected, but non-critical content cannot be captured which reduces productivity
Solution Approach 1:
The patent segments screenshot prevention into application-specific and content-specific controls, allowing different protection levels for different applications and even different content within applications. This enables confidential information in UEM-managed applications to be protected while allowing screenshot capture in non-critical applications, thereby maintaining productivity without compromising security.
Solution Approach 2:
The patent implements local quality by applying screenshot prevention selectively to specific applications and content areas rather than globally. Administrators can configure which applications enforce screenshot prevention based on their sensitivity, allowing non-critical applications to permit screenshots for productivity purposes while maintaining security for confidential applications.
3Reliability
If the entire GUI is hidden during screen capture, then all content is protected, but selective protection of sensitive portions while allowing other portions to remain visible is not possible
Solution Approach 1:
The patent segments the GUI into protected and non-protected regions through application-specific implementation. By controlling screenshot prevention at the application level rather than the entire GUI level, the system allows selective protection where only specific applications or content areas enforce screenshot prevention, enabling administrators to protect sensitive portions while allowing other portions to remain accessible.
4Device complexity
If screenshot prevention is implemented without API or SDK access, then implementation is simplified, but fine-grained control over which content to protect is not possible
Solution Approach 1:
The patent introduces an intermediary layer (the UEM solution) that sits between the operating system's native screenshot capabilities and the applications. This intermediary provides API/SDK access to screenshot prevention features, enabling fine-grained control over which applications and content are protected. The UEM solution acts as a mediator that simplifies implementation for administrators while providing detailed control capabilities through configuration interfaces.
Data Source
AI summary
Examples herein include methods for dynamically protecting selective content during screen capture on a user device that is running an iOS operating system. The method includes extending a UI class that includes a protected field of an iOS class. The custom class can receive configuration data and determine which elements to protect. The protected elements can be placed within the protected field whereas the non-protected elements can be kept outside of the protected field. The operating system can hide the protected field and its contents during screen capture, while allowing additional content outside the protected field to remain displayed.