Role-Based Transaction Security via Component Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Distributed transaction systems face security vulnerabilities due to implicit trust between transaction managers and modules within protected LAN environments, which can lead to malicious control and unauthorized role assumption, especially when transactions involve external communication.

Innovation Solution

Implementing role-based security by authenticating transaction components and referencing transaction control information to determine permitted roles, ensuring that transaction operations are only performed within authorized roles as specified in the transaction control information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If implicit trust is used between transaction managers in protected LAN environments, then transaction processing is simplified and faster, but security vulnerabilities increase allowing malicious control and unauthorized role assumption

Engineering Contradiction:
Improvetransaction processing speedVSAvoidsecurity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by performing authentication and authorization checks before allowing transaction operations to proceed. The system pre-verifies the identity and permitted roles of transaction managers and components before enabling them to participate in transactions, thereby preventing malicious control while maintaining efficient processing.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary security mechanism that mediates between transaction managers. This intermediary layer performs role-based access control and authentication without interfering with the core transaction processing logic, allowing fast transactions while blocking unauthorized role assumptions and malicious operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If role-based security checks are implemented for every transaction operation, then unauthorized role assumption is prevented, but system complexity increases

Engineering Contradiction:
ImprovesecurityVSAvoidsecurity mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies local quality by implementing role-based security checks at specific critical points in the transaction flow rather than uniformly throughout all operations. Security verification is performed locally at the transaction manager level and at component enlistment points, providing targeted security without unnecessary complexity in all transaction processing paths.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent uses parameter changes by dynamically determining permitted roles based on the transaction control information and the current transaction context. The system adjusts security parameters (allowed operations, scope, duration) based on the specific transaction requirements and component identities, providing flexible security without rigid complex rules.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If authentication and authorization checks are performed for all transaction components, then malicious operations are prevented, but transaction processing time increases

Engineering Contradiction:
ImprovesecurityVSAvoidtransaction processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs authentication and authorization checks in advance, before transactions begin. By pre-verifying component identities and permitted roles during system initialization or component registration, the system eliminates the need for repeated security checks during transaction execution, thereby maintaining fast processing while ensuring security.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where transaction managers provide information about their identity and permitted roles to other components. This feedback allows subsequent transaction participants to make informed decisions about authorization without requiring repeated authentication checks, reducing processing time while maintaining security through role-based access control.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS7730095B2Controlling transactions in accordance with role based security
Publication Date: 2010.06.01 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7730095B2 patent drawing
  • US7730095B2 patent drawing
  • US7730095B2 patent drawing

AI summary

The present invention extends to methods, systems, and computer program products for controlling transactions in accordance with role based security. A first transaction related component receives a transaction related message from a second transaction related component. The transaction related message indicates a request by the second transaction related component to perform a transaction related operation that is to involve the first transaction related component. The first transaction related component authenticates the second transaction related component. The first transaction related component refers to transaction control information indicating roles the second transaction component is permitted to assume relative to the first transaction related component. The transaction related operation indicated in the request is compared to the permitted roles for the second transaction related component. The transaction related operation is implemented in accordance with the results of the comparison.