Persistent NFC Authentication Using Device Drift Checks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing authentication methods require manual reauthentication at each instance, causing user annoyance and friction, especially in scenarios where authentication needs to be frequent or high-risk.
Innovation Solution
Implementing an authentication persistence check that allows previously successful authentication to persist for a predetermined period if the user apparatus remains stable and within a predetermined drift threshold, using device fingerprinting and behavioral biometrics to ensure security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If manual reauthentication is required at each instance, then security is maintained, but user experience deteriorates due to annoyance and friction
Solution Approach 1:
The system performs preliminary authentication and stores authentication results in advance, allowing subsequent operations to reuse these results without requiring repeated authentication. The authentication persistence mechanism pre-Validates user identity and device stability, then caches this information for future use, reducing the need for frequent reauthentication while maintaining security.
Solution Approach 2:
The system continuously monitors device stability metrics (sensor data, configuration changes, app installations) and uses this feedback to dynamically determine whether authentication persistence should be maintained. When device stability changes exceed thresholds, the system automatically invalidates cached authentication results, ensuring security while enabling seamless operation during stable periods.
2Ease of operation
If authentication persistence is allowed, then user experience improves by reducing manual reauthentication, but security risk increases due to potential drift in device characteristics
Solution Approach 1:
The authentication persistence mechanism is dynamic rather than static. It continuously evaluates device stability by comparing current sensor readings, configuration states, and installed applications against baseline values. The system automatically adjusts authentication persistence status based on real-time device conditions, maintaining security by invalidating persistence when drift exceeds acceptable thresholds while enabling convenience when device characteristics remain stable.
Solution Approach 2:
The system monitors multiple device parameters (sensor data, configuration settings, installed applications) and uses changes in these parameters as indicators of device stability. By tracking parameter drift over time and comparing against predefined thresholds, the system can determine whether authentication persistence should be maintained, thereby balancing security requirements with user convenience.
3Reliability
If device fingerprinting and stability checks are performed, then security is enhanced, but system complexity increases
Solution Approach 1:
The device itself generates and provides the authentication evidence through its own sensors and configuration data. The stability check mechanism uses the device's existing hardware (accelerometer, gyroscope, microphone) and software (installed apps, configuration files) to create a fingerprint, eliminating the need for external verification infrastructure and reducing overall system complexity.
Data Source
Figure 1A
Figure 1B
Figure 2
AI summary
An apparatus comprising: a near-field communication (NFC) reader; one or more processors operable to execute stored instructions that, when executed, cause the one or more processors to: authenticate a user via first factor authentication; authenticate the user via second factor authentication different from the first factor authentication, wherein the second factor authentication comprises: a contactless card being tapped to the apparatus such that NFC communication is established, receiving user authentication information from the contactless card via the NFC reader, sending the user authentication information to one or more remote computing devices, and receiving indication from the one or more remote computing devices that the user is authenticated; determine one or more device settings of the apparatus and one or more user behavioral biometrics at a first time of the second factor authentication; cause a stability check on the apparatus to be performed: (i) at a second time after the first time or (ii) when a authentication event occurs after the first time; in response to the apparatus being stable, perform device fingerprinting on the apparatus to determine whether the apparatus is within a predetermined drift threshold; in response to the apparatus being within the predetermined drift threshold, allow the second factor authentication to persist for a predetermined time period; and in response to the apparatus not being within the predetermined drift threshold, reauthenticate the user via the second factor authentication.