External Device Pairing via Random User Action
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods struggle to effectively differentiate between legitimate and malicious external devices connected to a computer, as malicious devices can misidentify themselves, leading to potential security breaches.
Innovation Solution
Implementing a pairing module that detects external devices, segregates them from computer resources, and requires a random user action specific to the device type for successful pairing, preventing malicious devices from accessing resources if the action is not performed correctly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the computer accepts any external device connection, then device compatibility and ease of use are improved, but security risk increases due to malicious devices
Solution Approach 1:
The system performs preliminary validation by detecting the external device type before allowing full access. A pairing module intercepts device connections and requires verification through device-specific user actions (e.g., pressing specific keys on a keyboard, clicking specific buttons on a mouse) before granting resource access. This preliminary check prevents malicious devices from directly accessing computer resources.
Solution Approach 2:
The pairing module acts as an intermediary between external devices and computer resources. It detects the device type, generates appropriate user actions based on device characteristics, and mediates the authentication process. Only after successful verification does the intermediary allow the device to access resources, thus blocking malicious devices while permitting legitimate ones.
2Reliability
If the computer requires validation actions for device pairing, then security is improved, but user convenience and pairing speed deteriorate
Solution Approach 1:
The system dynamically adapts the pairing process based on device type. Different devices require different verification actions (e.g., keyboard devices require key presses, mouse devices require button clicks). The pairing module detects the device type and automatically adjusts the required user actions, making the process efficient and device-appropriate rather than using a fixed, potentially time-consuming validation sequence for all devices.
Solution Approach 2:
The system uses the external device itself to perform the verification action, rather than requiring separate authentication steps. For example, a keyboard device verifies itself by receiving specific key presses, and a mouse device verifies itself by receiving specific button clicks. This self-service approach streamlines the pairing process while maintaining security.
3Ease of operation
If the system uses device identifiers for authentication, then pairing simplicity is improved, but security deteriorates because malicious devices can misidentify themselves
Solution Approach 1:
The system performs preliminary verification by detecting the actual device type before allowing access based on identifiers. The pairing module intercepts the connection, detects what type of device is connected (keyboard, mouse, etc.), and requires verification through device-specific user actions. This preliminary detection prevents malicious devices from successfully masquerading as legitimate devices, even if they provide correct identifier information.
Solution Approach 2:
The system implements feedback by detecting the device type and using that information to determine appropriate verification actions. The pairing module receives device information, processes it to identify the device type, and then provides feedback in the form of device-specific verification requirements. This feedback mechanism ensures that only devices matching both their identifier and actual functionality can successfully pair.
Data Source
AI summary
Pairing of an external device using a random user action is disclosed herein. An example method includes restricting the external device from accessing a resource. A user input receivable from the external device is identified based on a type of the external device, the user input not included in a list of previously generated user actions. In response to receipt of the user input from the external device within a threshold time period, the external device is authorized to access the resource.