Extensible App Wrapping Platform with Customizable Action Points
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
App developers have limited control over the security wrapping process of their apps, as they can only select from pre-defined security policies, lacking granularity and the ability to integrate non-security features, which may not meet the specific needs of employers or users who require more customized administrative functions.
Innovation Solution
Extending the app security program to include customizable action points and managerial features, allowing developers to create target code using defined naming conventions, which can be parsed and linked to the security program to generate a dynamic library for injection into the app, enabling more control over the wrapping process and adding administrative functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If pre-defined security policies are used to wrap apps, then security is improved, but developer control and customization are limited
Solution Approach 1:
The security policy is segmented into multiple independent components: pre-defined security policies, customizable action points, and target code. This allows developers to select specific security features and combine them with custom functionality, rather than accepting a monolithic pre-defined policy. The segmentation enables granular control over which security measures are applied and how they are executed.
Solution Approach 2:
The system transitions from static pre-defined policies to a dynamic architecture where developers can inject custom target code at specified action points. This dynamic injection mechanism allows the security behavior to be adapted and customized without changing the core policy structure, enabling both reliability through pre-defined policies and versatility through dynamic customization.
2Adaptability or versatility
If the security wrapping process is extended to include customizable features, then developer control is improved, but system complexity increases
Solution Approach 1:
Action points serve as intermediaries between the pre-defined security policies and custom developer code. These designated injection points provide a controlled interface that allows custom functionality to be integrated without directly modifying the core policy structure. The intermediary mechanism manages complexity by confining custom code to specific, well-defined locations rather than allowing unrestricted modifications throughout the system.
Solution Approach 2:
The action point mechanism provides a universal interface that can accommodate multiple types of custom functionality while maintaining a consistent integration pattern. Whether the custom code performs security-related tasks or non-security administrative functions, the same action point injection mechanism is used, reducing overall system complexity through standardized multi-functional integration points.
3Measurement precision
If more granular security control is implemented, then security precision is improved, but ease of operation decreases
Solution Approach 1:
The system performs preliminary action by providing pre-defined security policies that already contain common security measures. Developers can achieve granular security control by selectively combining these pre-configured policies with custom target code, rather than having to build granular security controls from scratch. This preliminary preparation maintains ease of operation while enabling precision.
Solution Approach 2:
The action point mechanism allows developers to copy and paste standardized injection points throughout the policy structure. Each action point represents a pre-vetted location for custom code insertion, ensuring security consistency while enabling granular control. This copying approach simplifies the operation of creating granular security configurations by reusing proven patterns.
Data Source
AI summary
An extensible platform gives app developers more control and granularity when developing apps and making them secure. App developers are able to use an app wrapping process to have more control over including non-security related features, such as managerial and administrative features, and more granularity with respect to security features included in the apps they develop. The app wrapping software is extended to be viewed more as a platform for the app developer to customize app security and administrative features without losing the efficiency and simplicity of the original app wrapping process of the present invention.