Standardized Object Model for Message-Oriented Middleware Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current queue-based message-oriented middleware (MoM) systems lack standardization, making it difficult to monitor and ensure security, understand end-to-end application dependencies, and integrate with existing network monitoring tools, leading to inconsistent and complex operational management, especially in enterprise environments with private data centers and cloud computing.

Innovation Solution

A system comprising a cloud connector, graphical unit, and policy compute engine that converts MoM system information into a standardized object model, generates a graph of producer and consumer relationships, and creates policies to detect deviations, issuing alerts and setting permissions to secure access to message queues.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple different MoM systems are deployed in enterprise solutions, then functionality and versatility are improved, but standardization and ease of monitoring deteriorate

Engineering Contradiction:
ImproveMoM system functionalityVSAvoidsystem standardization
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a standardized object model as an intermediary layer between diverse MoM systems and security monitoring tools. This object model acts as a mediator that translates various MoM system-specific interfaces into a unified standardized representation, enabling consistent monitoring and security control across different MoM systems without requiring changes to the underlying systems themselves.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The standardized object model provides universal functionality that can represent multiple MoM systems through a single unified interface. This universal model allows the same monitoring and security tools to work across different MoM systems (such as IBM MQ, TIBCO, Apache Kafka, etc.) by mapping their specific characteristics to the standardized model, thereby eliminating the need for system-specific monitoring solutions.

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

2Ease of operation

If MoM systems operate above the networking layer, then application-level control is improved, but integration with network monitoring tools deteriorates

Engineering Contradiction:
Improveapplication-level controlVSAvoidtool integration
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The standardized object model serves as an intermediary that bridges the gap between application-level MoM systems and network-level monitoring tools. It translates application-level MoM operations into standardized representations that can be understood and processed by network monitoring tools, enabling integration without sacrificing application-level control or requiring changes to the MoM systems themselves.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If open MoM systems are used by default, then ease of connection is improved, but security control deteriorates

Engineering Contradiction:
Improveconnection easeVSAvoidsecurity control
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements feedback mechanisms through the standardized object model that enable continuous monitoring and analysis of MoM traffic. The system can detect anomalies, unauthorized access attempts, and policy violations by analyzing the standardized representations of MoM operations, allowing for real-time security control while maintaining easy connection through the standardized interface.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The standardized object model acts as an intermediary security layer that sits between the open MoM system interfaces and the security control mechanisms. It translates open connections into standardized representations that can be securely monitored and controlled, allowing easy connection while maintaining robust security through standardized policy enforcement and anomaly detection.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Device complexity

If manual data generation is used for security reviews, then simplicity is maintained, but time consumption and labor requirements increase

Engineering Contradiction:
Improveprocess simplicityVSAvoidreview time
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The standardized object model enables MoM systems to self-monitor and self-report their own operations in a standardized format. The systems automatically generate security review data through the standardized interfaces, eliminating the need for manual data collection and processing. This self-service capability provides continuous automated security reviews while maintaining simplicity through the unified standardized approach.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements automated feedback loops where MoM operations are continuously monitored, represented in the standardized object model, and analyzed for security compliance. This automated feedback mechanism provides continuous security reviews without manual intervention, significantly reducing review time and labor requirements while maintaining simplicity through the standardized automated process.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11876817B2Modeling queue-based message-oriented middleware relationships in a security system
Publication Date: 2024.01.16 GRYPHO5 LLC
  • US11876817B2 patent drawing
  • US11876817B2 patent drawing
  • US11876817B2 patent drawing

AI summary

A system and a method for modeling queue-based message-oriented middleware (MoM) are provided. The method commences with connecting with a MoM system and converting information associated with the MoM system into a standardized object model. The standardized object model may include a queue-based node, at least one producer application, and at least one consumer application. The at least one producer application provides a message to the queue-based node. The at least one consumer application receives the message from the queue-based node. The message persists in the queue until consumed by the at least one consumer application. The method continues with generating a standardized graph of relationships between a producer and a consumer over a period of time. The method further includes creating a policy, periodically analyzing the standardized graph for at least one deviation from the policy, and issuing an alert in response to detecting the at least one deviation.