Secure Transaction Service Agents Using Encrypted Record Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for secure transactions between services are vulnerable to security risks due to unauthorized access to keys or certificates, which can go undetected for an extended period, exposing the system to threats.

Innovation Solution

The implementation of a method where agents from each service generate and store records of transactions in a storage accessible by both services, using credentials to validate requests and ensure secure transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If keys or certificates are used to authorize transactions between services, then transaction security is maintained, but the system becomes vulnerable to undetected unauthorized access when keys or certificates are compromised

Engineering Contradiction:
Improvetransaction securityVSAvoidundetected unauthorized access
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system creates transaction records in advance that serve as proof of authorized transactions. These records are stored with encrypted values that can be verified later without exposing the original keys or certificates. When a transaction occurs, the system preliminarily establishes a record that can be used to detect and verify the transaction's authenticity without requiring continuous access to the compromised credentials.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces transaction records as an intermediary mechanism between services. Instead of services directly trusting each other's keys or certificates, they use the stored transaction records with encrypted values as a mediator to verify transaction authenticity. This intermediary layer allows verification without exposing the underlying credentials that might be compromised.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If administrators monitor for key or certificate leaks, then security breaches can be detected, but the monitoring process increases system complexity and resource consumption

Engineering Contradiction:
Improvesecurity breach detectionVSAvoidmonitoring system complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The transaction record system enables self-service security verification. The encrypted values within transaction records automatically provide verification capability without requiring external monitoring systems. The system itself generates and maintains the verification mechanism through the creation and storage of transaction records with encrypted values, eliminating the need for separate complex monitoring infrastructure.

Inventive Principle:
Principle #25Self-service

3Reliability

If transaction records are stored with encrypted values, then verification security is improved, but the storage and retrieval process becomes more complex

Engineering Contradiction:
Improveverification securityVSAvoidstorage and retrieval complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent transforms the verification parameter from requiring access to original keys or certificates to using encrypted values within transaction records. This parameter change allows verification to be performed on stored data without exposing sensitive credentials. The encrypted values are designed to be searchable and verifiable while maintaining security, changing the verification approach from credential-based to record-based.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12293364B2Systems and methods for performing secure transactions
Publication Date: 2025.05.06 CITRIX SYSTEMS INC
  • US12293364B2 patent drawing
  • US12293364B2 patent drawing
  • US12293364B2 patent drawing

AI summary

Described embodiments provide systems and methods for performing secure transactions. A first service executing on at least one server may receive a request from a second service for the first service to perform a transaction. The request may include an identifier of a record. An agent of the first service may determine, according to the identifier, whether the record is present in a storage. The storage may be accessible using credentials of the agent of the first service and an agent of the second service. The first service may send a response to the request if the record is present in the storage.