Encrypted Token Debugging for Web Rule Sets

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing debugging services for client webpages lack security, allowing customers to inadvertently or deliberately access and view the rule sets and business logic of their competitors, leading to potential data breaches and security concerns.

Innovation Solution

Implementing an encrypted security token system that generates a sharable Internet cookie, ensuring customers can debug their own rules without exposing their business logic, by encapsulating the token with JavaScript and checking its validity across webpages to prevent access to other entities' content.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If existing debugging services are used to allow customers to debug their rules, then debugging functionality is provided, but security is compromised allowing access to competitors' rule sets and business logic

Engineering Contradiction:
Improvedebugging functionalityVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments the debugging access by creating customer-specific isolated environments where each customer's rule sets and business logic are separated into individual debug sessions. This segmentation prevents cross-contamination and unauthorized access between different customers while maintaining full debugging functionality within each isolated space.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism (the debugging service with encrypted tokens and isolated environments) that mediates between the customer's debugging needs and the security requirements. This intermediary layer allows debugging to proceed while enforcing security boundaries that prevent access to competitors' data.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If a shared debugging service is used to support multiple customers, then resource efficiency is improved, but data security deteriorates as competitors' rule sets become accessible

Engineering Contradiction:
Improveresource efficiencyVSAvoiddata security
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The shared debugging service is segmented into multiple isolated customer environments. Each customer receives the same efficient debugging infrastructure and resources, but these resources are logically partitioned and isolated so that data from one customer cannot be accessed by another, preventing information leakage while maintaining resource efficiency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by providing each customer with a customized, isolated debugging environment tailored to their specific needs and data requirements. While the overall system remains shared and efficient, each local debugging space has enhanced security properties specific to that customer's data protection needs.

Inventive Principle:
Principle #3Local quality

3Difficulty of detecting and measuring

If debugging services allow access to rule sets for troubleshooting, then error detection is improved, but security risks increase allowing potential data breaches

Engineering Contradiction:
Improveerror detectionVSAvoidsecurity risks
Core Design Contradiction:
Difficulty of detecting and measuringVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary debugging service that sits between the customer's rule sets and the debugging interface. This intermediary provides full error detection and troubleshooting capabilities while enforcing security boundaries that prevent direct access to the underlying data, thus eliminating security risks associated with traditional debugging approaches.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements beforehand cushioning by pre-establishing security boundaries, encrypted tokens, and isolated environments before any debugging session begins. These protective measures are in place beforehand to cushion against potential security breaches, allowing thorough error detection to proceed without exposing the system to security risks.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS10268536B2Secure debugging with an encrypted token
Publication Date: 2019.04.23 ORACLE INT CORP
  • US10268536B2 patent drawing
  • US10268536B2 patent drawing
  • US10268536B2 patent drawing

AI summary

Systems and methods for debugging dynamically rendered content are described herein. A plurality of rules are defined and stored, wherein each rule includes a condition and an action, and wherein each action includes an instruction to render content within a webpage. A rule object is generated based on the plurality of rules, wherein the rule object includes executable code. The rule object is stored within an in-memory device disposed between a rules server and a transformation server. An error is detected during the execution of the rule object. In response to a user request, an encrypted security token is generated to access one or more rule debugging modules of the rules server.