Security Test Tool Transforming Non-Relational Database Messages

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current network security tools face challenges in efficiently verifying the proper functioning of security event logging and detection systems, leading to potential intrusions and resource wastage due to format differences in data comparison across databases.

Innovation Solution

A test tool comprising a connection engine, transformation engine, validation engine, and messaging engine that connects to non-relational databases and a server, transforms messages into JavaScript Object Notation, and compares them with server logs to ensure data consistency, reducing resource consumption and improving security event detection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If messages from non-relational databases are compared directly with server logs, then data consistency can be verified, but format differences cause comparison failures and require additional transformation processing

Engineering Contradiction:

Improvedata consistency verificationVSAvoidmessage format compatibility

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a transformation engine as an intermediary component that converts messages from non-relational databases into JavaScript Object Notation format before comparison with server logs. This mediator resolves the format compatibility issue by standardizing the message structure, enabling reliable comparison without requiring direct format matching between different database systems and log files.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The transformation engine changes the parameter format of messages from various non-relational database formats into a unified JavaScript Object Notation format. By altering the structural parameters of the messages, the system enables consistent comparison with server logs regardless of the original database format, resolving the compatibility problem while maintaining verification reliability.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If multiple non-relational databases with different formats are connected and verified, then comprehensive security event detection is achieved, but processor and memory resources are consumed excessively

Engineering Contradiction:

Improvesecurity event detection accuracyVSAvoidprocessor and memory consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The transformation engine serves multiple functions: it transforms messages from different non-relational database formats into a unified JavaScript Object Notation format, standardizes the message structure, and prepares data for comparison with server logs. This multi-functional approach consolidates processing requirements into a single engine, reducing overall system resource consumption while maintaining comprehensive security event detection across multiple databases.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

By changing the data representation parameters through transformation into JavaScript Object Notation, the system creates a standardized format that reduces the processing overhead of comparing multiple database formats. This parameter standardization enables efficient verification across all databases without requiring separate processing paths for each database type, thereby reducing processor and memory usage.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If detailed comparison of all message fields with server logs is performed, then complete verification of security events is achieved, but network bandwidth and processing time increase

Engineering Contradiction:

Improvesecurity event verification completenessVSAvoidprocessing time and network bandwidth

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The transformation engine extracts only the essential fields and formats messages into JavaScript Object Notation that are necessary for comparison with server logs. By extracting and standardizing only the critical verification fields rather than processing all possible message fields, the system achieves complete verification of security events while minimizing processing time and network bandwidth consumption.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS10164990B2Security test tool

Publication Date: 2018.12.25 BANK OF AMERICA CORP

AI summary

A test tool includes a connection engine, a transformation engine, a validation engine, and a messaging engine. The connection engine connects to a first non-relational database, a second non-relational database, and a server. The transformation engine receives first and second messages from the first and second non-relational databases and transforms the second message into a JavaScript Object Notation message. The validation engine compares the first message with a server log stored on the server to determine whether information in the first message matches information in the server log and compares the JavaScript Object Notation message with the server log to determine whether information in the second message matches information in the server log. The messaging engine communicates a message indicating that information in the first message and the second message match information in the server log.