Bluetooth Security Verification via Pairing History and Policy Checks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Bluetooth networks are vulnerable to various security attacks such as PIN cracking, man-in-the-middle attacks, location attacks, and Bluesnarfing due to their wireless nature, which compromises data integrity and privacy in devices like mobile phones and PCs.

Innovation Solution

A method that enhances security by determining if a wireless device is trusted through pairing history and security policy checks, including file transfer controls, scanning engine verification, and context-aware authentication, ensuring secure connections and data exchange.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If Bluetooth devices establish connections easily without strict verification, then ease of operation is improved, but security vulnerability increases

Engineering Contradiction:
ImproveConnection establishment easeVSAvoidSecurity reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary security verification by checking pairing history and security policies before establishing a connection. This preliminary action ensures that only trusted devices can connect, resolving the contradiction by maintaining ease of operation for authorized devices while preventing unauthorized access through pre-established trust relationships.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention introduces an intermediary security verification mechanism that mediates between connection requests and actual connection establishment. This intermediary layer checks pairing history and security policies, allowing easy connection for trusted devices while blocking unauthorized connections, thus resolving the contradiction between ease of operation and security reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If comprehensive security verification is performed for each connection, then security reliability is improved, but device complexity increases

Engineering Contradiction:
ImproveSecurity reliabilityVSAvoidSecurity verification complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Security verification is performed preliminarily during the pairing phase rather than at each connection attempt. The system stores pairing history and security policies in advance, allowing quick verification decisions during actual connections. This reduces device complexity while maintaining high security reliability through pre-computed security assessments.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The invention creates a copy of security verification results by storing pairing history and security policies for future reference. Instead of performing complete verification each time, the system uses stored copies of security assessments, reducing computational complexity while maintaining security reliability through consistent verification based on historical data.

Inventive Principle:
Principle #26Copying

3Reliability

If pairing history is checked for every connection request, then security reliability is improved, but loss of time increases

Engineering Contradiction:
ImproveSecurity reliabilityVSAvoidConnection establishment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Pairing history is checked preliminarily and stored for quick reference during connection requests. The system performs the time-consuming verification work in advance during pairing, then uses stored results for rapid connection decisions. This resolves the contradiction by maintaining security reliability through historical checks while minimizing time loss through cached verification data.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates copies of pairing history and security policy results for rapid retrieval during connection requests. Instead of re-verifying security attributes each time, the system uses pre-computed copies stored in memory, maintaining security reliability while dramatically reducing connection establishment time through efficient data access.

Inventive Principle:
Principle #26Copying

4Reliability

If security policies are strictly enforced for all devices, then security reliability is improved, but adaptability decreases

Engineering Contradiction:
ImproveSecurity reliabilityVSAvoidDevice compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system applies different security verification levels to different devices based on their pairing history and trust relationships. Trusted devices with established pairing history receive streamlined verification, while unknown devices undergo strict security checks. This local quality approach maintains security reliability for all devices while providing adaptability and ease of operation for trusted devices.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

Security policy enforcement is made dynamic rather than static. The system adjusts verification strictness based on real-time assessment of device trustworthiness, pairing history, and security context. This dynamic approach ensures security reliability is maintained for suspicious devices while allowing adaptable, fast connections for trusted devices, resolving the contradiction between security and adaptability.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9596604B2Method and system for enhanced wireless network security
Publication Date: 2017.03.14 MCAFEE LLC
  • US9596604B2 patent drawing
  • US9596604B2 patent drawing
  • US9596604B2 patent drawing

AI summary

A method, system, and computer program product for securing wireless network devices improves the security of wireless networks and devices, such as Bluetooth networks and devices, to prevent security attacks on and hacking of such networks and devices. A method for secure wireless communications, comprises the steps of requesting a connection with a wireless device, determining whether the wireless device is trusted, determining a security policy of the wireless device, and establishing a connection with the wireless device if the wireless device is trusted and if the security policy of the wireless device is as expected.