Contextual Transaction Security Hardening

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current security measures for sensitive transactions are inadequate in protecting user data from various threat surfaces, including endpoint devices, networks, and online services, as they often rely on traditional protections that fail to account for vulnerabilities in the client environment and social engineering attacks.

Innovation Solution

A system that identifies the sensitivity level of online transactions based on contextual factors and provides holistic security by disabling keyloggers, adding authentication layers, autofilling non-mandatory fields, and enabling VPN tunnels, while hardening the browser environment and using cloud-based services to assess trustworthiness and provide end-to-end protection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional security protections are used for sensitive transactions, then basic security coverage is provided, but they fail to account for vulnerabilities in the client environment and social engineering attacks

Engineering Contradiction:
Improvesecurity protection effectivenessVSAvoidability to account for client environment vulnerabilities and social engineering attacks
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system segments security protection into multiple independent modules: browser environment hardening, keylogger detection, authentication layer addition, and autofill functionality. Each module addresses specific vulnerability types independently, allowing comprehensive coverage without requiring a complete security overhaul.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by preemptively hardening the browser environment, detecting keyloggers, and preparing authentication mechanisms before sensitive transactions occur. This proactive approach prevents vulnerabilities from being exploited during the transaction process.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If comprehensive security measures are implemented for all transactions, then security coverage is maximized, but system performance is degraded

Engineering Contradiction:
Improvesecurity coverageVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system applies different security measures to different transactions based on their sensitivity and context. High-security measures like authentication layers and keylogger detection are applied selectively to sensitive transactions, while less critical transactions receive standard protection, optimizing the balance between security and performance.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system implements security measures proportionally - applying full security hardening only when necessary based on transaction analysis, rather than uniformly across all transactions. This partial action approach maintains security effectiveness while minimizing performance impact on non-critical operations.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If security hardening is applied to all browser environments, then protection against client vulnerabilities is improved, but it affects all online transactions uniformly

Engineering Contradiction:
Improveprotection against client vulnerabilitiesVSAvoidability to provide tailored protection for different transactions
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system dynamically adjusts security hardening measures based on real-time analysis of each transaction's sensitivity, the user's context, and the detected threat level. Security measures are applied adaptively rather than statically, allowing the system to provide appropriate protection for each transaction without uniformly affecting all operations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system continuously monitors transaction characteristics and security conditions, using this feedback to adjust the level of hardening applied. Based on feedback from transaction analysis and threat detection, the system modifies security measures in real-time, ensuring optimal protection while maintaining transaction flow efficiency.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20220309197A1Automated hardening of sensitive transactions
Publication Date: 2022.09.29 MCAFEE LLC
  • US20220309197A1 patent drawing
  • US20220309197A1 patent drawing
  • US20220309197A1 patent drawing

AI summary

There is disclosed, by way of example, a computing apparatus having a hardware platform having a processor and a memory; and instructions encoded within the memory to: identify an online transaction involving a user; according to a plurality of contextual factors, determine a sensitivity level for the online transaction; and according to the sensitivity level, contextually increase security for the online transaction without altering at least one other online transaction.