Secure Online Transactions via Dynamic Device Restrictions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing secure online transaction systems, even when using HTTPS, are vulnerable to side-channel attacks and lack control over user devices, leading to potential security breaches and resource depletion due to application, bandwidth, and traffic attacks.
Innovation Solution
Implementing a system with multiple communication tunnels, dynamic IP addresses, and device access limitations, managed by client and server security modules, which negotiate and enforce restrictions on device properties such as open applications and ports, and generate unique identifiers for secure transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If HTTPS is used for securing communications, then authentication and protection from man-in-the-middle attacks is improved, but vulnerability to side-channel attacks and lack of control over user devices persists
Solution Approach 1:
The patent segments the communication process into distinct phases (setup phase and transaction phase) with different security measures. During the setup phase, device properties are assessed and restrictions are configured. During the transaction phase, those restrictions are enforced while HTTPS provides encryption. This segmentation allows HTTPS to handle authentication while additional controls address side-channel vulnerabilities.
Solution Approach 2:
The system performs preliminary actions by assessing device properties and configuring security restrictions before the actual transaction occurs. The server evaluates client device characteristics during the setup phase and pre-configures appropriate security restrictions, which are then enforced during the transaction. This preliminary configuration ensures that security controls are in place before sensitive operations begin.
2Reliability
If device control measures are implemented to prevent attacks, then security against application and bandwidth attacks is improved, but device complexity and user convenience deteriorate
Solution Approach 1:
The security restrictions are dynamic rather than static. The system adjusts the level of restrictions based on the assessed device properties and the specific transaction context. Different clients receive different restriction profiles tailored to their device characteristics and risk profiles. This dynamic approach provides strong security where needed while maintaining flexibility and user convenience where appropriate.
Solution Approach 2:
The system changes security parameters (such as which applications are restricted, port configurations, and resource limits) based on device properties and transaction requirements. Rather than applying a one-size-fits-all approach, the server modifies security parameters dynamically according to the specific client device characteristics and the nature of the transaction being performed.
3Reliability
If transaction data is retained for auditing purposes, then accountability and security monitoring are improved, but risk of data breach and resource depletion increases
Solution Approach 1:
The system implements a policy of discarding transaction data after it has served its auditing and monitoring purpose. Rather than indefinitely retaining sensitive transaction data, the system maintains it only for the necessary duration to fulfill security monitoring and accountability requirements, then securely discards it. This reduces the attack surface and potential impact of data breaches while maintaining necessary security oversight.
Data Source
AI summary
A user device and a server conduct a secure online transaction. The user device transmits received user login and credentials to the server, as well as one or more properties of the user device, such as a list of applications stored on the user device. The server transmits one or more restrictions back to the user device, such as which ports to close, which applications to close, and what features of applications and the operating system should be limited during the transaction. After implementing the restrictions, the user device and the server conduct the online transaction. A unique ID may be transmitted throughout the transaction and the unique ID may be a hash. After the transaction, the user device purges transaction data, restores normal operation, and notifies the server. The transaction may be conducted in a second tunnel and the other communication via a first tunnel.