GUI Event Authentication via WAF Against Clickjacking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Web applications are vulnerable to malicious actions triggered through graphical user interface (GUI) elements without user knowledge, such as clickjacking and bot-generated clicks, which can compromise security and integrity.

Innovation Solution

A web application firewall (WAF) injects client-side components to monitor and authenticate events associated with selected GUI elements, capturing event metadata before allowing actions, and verifies against predefined authentication criteria to ensure genuine user intent.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a web application provides accessible GUI elements for user interaction, then ease of operation is improved, but vulnerability to malicious actions like clickjacking and bot-generated clicks increases

Engineering Contradiction:
ImproveGUI element accessibilityVSAvoidMalicious action vulnerability
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary authentication mechanism between the GUI element and the action trigger. When a GUI element is activated, the system intercepts the event, verifies authentication metadata (such as user session validity, event source legitimacy, and contextual permissions), and only then allows the action to proceed. This intermediary layer blocks malicious actions like clickjacking and bot-generated clicks while preserving legitimate user interactions.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary authentication checks before allowing GUI element actions to execute. Authentication metadata is validated in advance of the actual action, including verifying user session authenticity, checking event source legitimacy, and confirming contextual permissions. This preliminary verification prevents malicious actions from succeeding while maintaining smooth operation for legitimate users.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If comprehensive event monitoring and authentication is implemented for all GUI elements, then security against malicious actions is improved, but device complexity increases

Engineering Contradiction:
ImproveSecurity against malicious actionsVSAvoidAuthentication system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The authentication mechanism is applied selectively rather than uniformly across all GUI elements. The system identifies critical GUI elements that require authentication protection and applies the authentication metadata verification specifically to those elements. This localized approach maintains security for high-risk operations while avoiding unnecessary complexity for low-risk interactions.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The authentication mechanism serves multiple functions simultaneously: it verifies user session validity, checks event source legitimacy, validates contextual permissions, and logs security events. By consolidating these security functions into a single unified authentication layer, the system achieves comprehensive protection without proportionally increasing complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS12488093B2GUI event authentication methods and systems using a web application firewall
Publication Date: 2025.12.02 SALESFORCE INC
  • US12488093B2 patent drawing
  • US12488093B2 patent drawing
  • US12488093B2 patent drawing

AI summary

Database systems and methods are provided for securing actions associated with graphical user interface (GUI) elements within an instance of a web application using a web application firewall. One method of securing an action associated with a GUI element within a GUI display of an instance of a web application involves monitoring a location associated with the GUI element associated with the action within the GUI display of the instance of the web application, detecting an event associated with the GUI element within the location of the GUI display, capturing event metadata associated with the event within a context of the instance of the web application, authenticating the event when the event metadata corresponds to authentication configuration metadata associated with the GUI element, and providing event data corresponding to the event to the GUI element to initiate the action in response to authenticating the event.