Call-Intercept Authentication for Transaction-Aware Web Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing web applications lack dynamic transaction-aware authentication mechanisms, treating all transactions equally post-authentication, failing to detect session hijacking, and integrating advanced security features like facial recognition and MFA is cumbersome, especially with legacy applications.
Innovation Solution
Implement dynamic transaction-aware web application authentication using call intercepts to enhance authentication based on transaction sensitivity and user behavior, applying intelligent policies without altering source code, and intercepting transactions in real-time to invoke per-transaction authentication challenges.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional username and password authentication is used for all transactions, then implementation is simple and legacy applications work without modification, but security is insufficient against session hijacking and all transactions are treated equally without dynamic authentication
Solution Approach 1:
The patent implements dynamic authentication that adapts based on transaction sensitivity and user behavior. The system transitions from static authentication to dynamic authentication by monitoring transaction characteristics and automatically adjusting authentication requirements. High-sensitivity transactions trigger enhanced authentication challenges, while low-sensitivity transactions proceed with standard authentication, creating a flexible security model that responds to real-time conditions.
Solution Approach 2:
The patent introduces an intermediary authentication challenge mechanism that sits between the user and the application. When a high-sensitivity transaction is detected, the system inserts an additional authentication challenge (such as MFA or biometric verification) into the transaction flow. This intermediary layer provides enhanced security without requiring modification of the underlying application code, effectively mediating between security requirements and application functionality.
2Reliability
If advanced security features like MFA and facial recognition are integrated, then authentication security is enhanced, but integration effort is daunting and impossible for legacy applications without source code access
Solution Approach 1:
The system introduces an intermediary authentication layer that can be deployed without modifying application source code. This intermediary mechanism intercepts transactions and applies appropriate authentication challenges based on transaction sensitivity, making advanced security features accessible to legacy applications through non-intrusive integration methods.
Solution Approach 2:
The patent segments the authentication process into separate, independent components that can be applied selectively. Instead of requiring full integration of advanced security features throughout the application, the system divides authentication into standard and enhanced layers, applying enhanced authentication only to specific high-sensitivity transactions. This segmentation allows legacy applications to benefit from advanced security without requiring comprehensive integration.
3Reliability
If all transactions are treated the same after authentication, then implementation is simple, but security is insufficient as high-sensitivity transactions require additional verification
Solution Approach 1:
The patent applies local quality by differentiating authentication requirements based on transaction characteristics. Instead of applying uniform authentication to all transactions, the system analyzes each transaction's sensitivity and applies appropriate authentication levels locally. High-sensitivity transactions receive enhanced authentication challenges, while low-sensitivity transactions proceed with standard authentication, optimizing both security and user experience.
Solution Approach 2:
The system implements dynamic transaction processing that automatically adjusts authentication requirements based on real-time transaction analysis. The authentication level is not static but dynamically determined by transaction sensitivity, user behavior patterns, and risk assessment, creating a responsive security model that adapts to each transaction's specific requirements.
4Reliability
If MFA is only checked at login, then implementation is simple, but session hijacking attacks are not detected or mitigated
Solution Approach 1:
The system performs preliminary analysis of transaction sensitivity before executing the transaction. By pre-identifying high-sensitivity transactions and preparing appropriate authentication challenges in advance, the system can quickly respond to potential security risks without adding significant time overhead. The authentication challenge is triggered proactively based on pre-established security policies and transaction characteristics.
Solution Approach 2:
The patent implements continuous feedback loops that monitor user behavior and transaction patterns throughout the session. The system collects data on user actions, transaction types, and behavioral anomalies, then uses this feedback to dynamically adjust authentication requirements. This ongoing feedback mechanism enables the system to detect potential session hijacking attempts and trigger additional authentication challenges in real-time, rather than relying solely on initial login verification.
Data Source
AI summary
According to one or more embodiments of the disclosure, the techniques herein are directed toward a dynamic transaction-aware web application authentication using call intercepts. In one embodiment, a method comprises: intercepting, by a monitoring process, calls made for transactions within an executing application; determining, by the monitoring process, whether a particular intercepted call triggers an enhanced user authentication requirement for a particular transaction; initiating, by the monitoring process in response to the particular intercepted call triggering the enhanced user authentication requirement, a corresponding challenge to adequately authenticate a user for the particular transaction; and allowing, by the monitoring process, the particular intercepted call to proceed for the particular transaction in response to an adequately authenticated user for the particular transaction.