Browser Data Security via Developer Tool Detection and One-Off Encoding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data security in web browser environments is vulnerable to hacking due to the ease of using developer tools to decode encoded data, with existing methods being susceptible to manipulation and unable to effectively prevent unauthorized access.

Innovation Solution

A system and method that monitors the use of developer tools by measuring execution consumption time and window size, creating a one-off encoding/decoding module, and displaying an error page when tools are detected, ensuring secure data transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If developer tools are provided in web browser for debugging, then ease of operation is improved, but data security deteriorates due to easy decoding of encoded data

Engineering Contradiction:
Improvedebugging capabilityVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent applies preliminary action by detecting developer tool activation before data transmission occurs. The system monitors for the presence of developer tools and proactively prevents data transmission when detected, rather than attempting to secure data after transmission. This is implemented through time measurement mechanisms that detect abnormal execution patterns indicative of developer tool usage before sensitive operations complete.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary security mechanism between the web browser and data transmission processes. This intermediary layer monitors execution time and detects developer tool presence, acting as a mediator that can block or alert on attempted data access. The security system interposes itself in the execution flow to prevent direct access to encoded data even when developer tools are present.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If time measurement is used to detect developer tool execution, then reliability of detection is improved, but ease of operation deteriorates as hackers can hook time functions to bypass detection

Engineering Contradiction:
Improvedetection accuracyVSAvoidvulnerability to hacking
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the time measurement function into multiple independent components and verification layers. Rather than relying on a single time function that can be hooked, the system divides detection into multiple time measurement points and cross-validates results. This segmentation makes it harder for hackers to bypass detection by hooking a single function, as they would need to compromise multiple segmented measurement points simultaneously.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by using multiple time measurement points rather than attempting to measure the entire execution flow. It measures specific critical segments of execution time and compares them against expected ranges. This partial measurement approach provides sufficient detection capability without requiring complete control over all execution paths, making it more resilient to hacking attempts.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If encoding/decoding mechanisms are implemented for data security, then data security is improved, but ease of operation deteriorates as encoded keys can be extracted through developer tools

Engineering Contradiction:
Improvedata securityVSAvoiddata accessibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent applies preliminary anti-action by preventing data transmission before encoding/decoding operations can be performed by developer tools. The system detects developer tool presence and blocks the execution flow before sensitive data is transmitted or keys are exposed. This preemptive approach neutralizes the threat before the encoding mechanism can be exploited, making the encoding/decoding process itself unnecessary when threats are detected.

Inventive Principle:
Principle #9Preliminary anti-action

Solution Approach 2:

The patent extracts the security verification function from the data transmission process itself. Rather than relying on encoding mechanisms within the data flow that can be intercepted, the system separates security verification into a distinct preliminary step that checks for developer tools before data transmission is initiated. This extraction removes the vulnerability point from the encoding/decoding mechanism.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS12470581B2Service providing system and method for security of data based on web browser
Publication Date: 2025.11.11 DRM INSIDE
  • US12470581B2 patent drawing
  • US12470581B2 patent drawing
  • US12470581B2 patent drawing

AI summary

The present disclosure relates to a service providing system and method for security of data based on a web browser. In more detail, the present disclosure relates to a service providing system and method for security of data based on a web browser, the system and method preventing unauthorized takeover of data by accurately finding out whether development tools provided from a web browser for hacking data, which is transmitted through a web browser, are being driven, and the system and method securing security for data by using a one-off encoding/decoding module. According to the present disclosure, it is possible to accurately find out whether a developer tool is being driven through a web server and prevent execution of the developer tool by guiding a hacker to an error page, whereby it is possible to safely transmit data and increase security for data.