Gateway Server JavaScript Injection for Mobile Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Organizations face challenges in ensuring secure access to corporate data and applications on mobile devices, as existing solutions fail to effectively manage user authentication, authorization, data storage, cookie handling, and external link access while allowing users to access applications in a familiar environment without compromising security.
Innovation Solution
A gateway server is introduced to buffer communication between mobile devices and organization servers, applying security policies by identifying and addressing security vulnerabilities in JavaScript code, intercepting and encrypting files, and controlling cookie handling, ensuring that only authorized actions are performed on mobile devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If security policies are enforced to protect corporate data on mobile devices, then data security is improved, but user convenience and ease of operation deteriorate
Solution Approach 1:
A gateway server is introduced as an intermediary between mobile devices and corporate application servers. The gateway server analyzes JavaScript code, injects security policies, and monitors data storage operations without requiring changes to user devices or applications. This mediator handles security enforcement transparently, maintaining data security while preserving user convenience.
Solution Approach 2:
Security policies are embedded into JavaScript code through code injection before the code executes on mobile devices. The gateway server performs preliminary analysis and modification of JavaScript code to include security constraints, such as preventing unauthorized data storage in local storage or cookies. This preliminary action ensures security is built-in rather than imposed during user operation.
2Reliability
If JavaScript code is analyzed and modified to enforce security policies, then security vulnerability coverage is improved, but system complexity increases
Solution Approach 1:
The gateway server serves as a centralized intermediary that handles all JavaScript code analysis and security policy injection. Rather than distributing security functionality across multiple components or devices, the gateway consolidates complexity in a single location, simplifying the overall system architecture while maintaining comprehensive security coverage.
Solution Approach 2:
The system replaces traditional mechanical security approaches (such as secure browsers or specialized mobile devices) with a software-based JavaScript injection mechanism. By using web-based JavaScript code modification, the system achieves security without requiring specialized hardware or complex device configurations, reducing overall system complexity.
3Adaptability or versatility
If users are allowed to use their own browsers and devices, then adaptability and user preference satisfaction are improved, but security control deteriorates
Solution Approach 1:
The gateway server provides universal security functionality that works across all browsers and mobile devices through standard JavaScript injection. Rather than requiring specific secure browsers or device types, the security mechanism is embedded in web-based JavaScript code that executes universally in any browser environment, maintaining both adaptability and security control.
Solution Approach 2:
The gateway server acts as a mediator between diverse user devices/browsers and corporate application servers. It standardizes security enforcement by injecting and monitoring JavaScript code regardless of the underlying device or browser, allowing users to maintain their preferred devices while ensuring consistent security control across all access points.
4Productivity
If files are downloaded to mobile devices for offline access, then productivity is improved, but security risk increases
Solution Approach 1:
The system replaces traditional file download and local storage mechanisms with web-based offline storage using JavaScript and browser cache. Files are not downloaded to the device file system but are stored in browser-based storage mechanisms that can be monitored and controlled through JavaScript injection, enabling offline access while maintaining security through code-level control.
Solution Approach 2:
Security constraints are embedded in JavaScript code before files are made available for offline storage. The gateway server performs preliminary security analysis and injects code that controls file storage operations, ensuring that files can be accessed offline while preventing unauthorized access, modification, or distribution through pre-configured security policies.
Data Source
AI summary
A computer-implemented method, apparatus and computer program product for providing secure consumption of applications from mobile devices, The method comprises receiving a security policy associated with usage of an application by a user using a mobile device, the security policy comprising at least one vulnerability indication; receiving at least partial code of the application; identifying at least one JavaScript instruction in the code, the at least one JavaScript instruction associated with the security vulnerability; and adding additional JavaScript instructions to the code for handling the security vulnerability.