Shared Security Value Verification for Mobile App Interactions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile devices are vulnerable to attacks by malicious applications that exploit interactions through fake messages, leading to unauthorized access and fraudulent transactions, posing significant financial risks.
Innovation Solution
Implementing a security mechanism using shared security values generated by a second application and its SDK, which requires matching verification before allowing legitimate interactions, thereby preventing unauthorized access by malicious applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If mobile devices allow free installation and execution of applications, then application versatility and user convenience are improved, but security vulnerability to malicious applications increases
Solution Approach 1:
The system performs preliminary security verification by generating and verifying security values before allowing any application interaction. The verification process checks whether a malicious application has accessed another application's data by comparing security values generated by the operating system with those provided by the application, blocking any unauthorized interactions in advance
Solution Approach 2:
The operating system acts as an intermediary between applications and the user. It intercepts all data access requests, generates security values, and verifies application authenticity before allowing interactions. This intermediary layer prevents direct access between applications and user data, enabling the system to detect and block malicious applications while maintaining legitimate application functionality
2Reliability
If the system verifies security values for all interactions, then security against malicious applications is improved, but system complexity increases
Solution Approach 1:
The operating system automatically generates security values and performs verification without requiring manual intervention or complex configuration from users or developers. The security verification is transparent and autonomous, with the system self-managing the generation, storage, and verification of security values across all applications
Solution Approach 2:
The system changes the parameter of data verification by introducing security values as a new verification dimension. Instead of verifying only application installation or basic functionality, the system adds security value verification as a mandatory parameter for all data access interactions, enabling reliable detection of malicious applications through this additional verification layer
3Object-affected harmful factors
If the system blocks all unverified interactions, then security against fraudulent transactions is improved, but legitimate application functionality may be restricted
Solution Approach 1:
The system provides feedback to both legitimate applications and malicious applications through security value verification. Legitimate applications receive feedback in the form of successful verification and are allowed to function normally, while malicious applications receive feedback in the form of verification failure and are blocked. This feedback mechanism ensures that only verified applications can access user data
Solution Approach 2:
The verification system is segmented into distinct components: security value generation by the operating system, security value collection by applications, and verification by the operating system. This segmentation allows the system to maintain clear separation between trusted system functions and application functions, enabling reliable verification without restricting legitimate application operations
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method is disclosed. The method includes providing, by an SDK and a first application in a mobile device, first and second security values to a security value verification module in the mobile device. If the mobile device confirms that the first and second security values match, then a second application can proceed with interaction processing.