Stateless Sidecar Proxy for Database Access Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional security models are inadequate in protecting data sources as they often require complex and expensive management of secure perimeters, leaving applications vulnerable to unauthorized access and data breaches.

Innovation Solution

A sidecar architecture is implemented as a protective layer around data sources, utilizing a dispatcher and services for authentication, behavioral baselining, tokenization, and federated identity management to validate and secure access, while being data-agnostic to accommodate various data sources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional security models with secure perimeters are used to protect data sources, then data security is improved, but device complexity and management cost increase significantly

Engineering Contradiction:
Improvedata securityVSAvoidmanagement complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces sidecar proxies as intermediary components that sit between applications and data sources. These sidecars handle security validation, authentication, and access control, acting as mediators that protect data sources without requiring complex perimeter security infrastructure. The sidecar architecture distributes security functions to lightweight agents near each data source, eliminating the need for centralized complex security management.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The security function is segmented and distributed to individual sidecar proxies deployed near each data source rather than implementing a monolithic perimeter security system. Each sidecar is a lightweight, independent component that handles security for its local data source, dividing the complex security management task into many simple, manageable units that can be independently configured and maintained.

Inventive Principle:
Principle #1Segmentation

2Reliability

If sidecar architecture with multiple services is deployed to validate access, then unauthorized access prevention is improved, but device complexity increases

Engineering Contradiction:
Improveaccess validationVSAvoidarchitecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The sidecar proxy is designed as a universal, multi-functional component that can perform authentication, authorization, behavioral baselining, tokenization, and federated identity management all in one lightweight agent. This multi-functionality consolidates what would otherwise require multiple separate security services into a single deployable unit, reducing overall system complexity while maintaining comprehensive access validation capabilities.

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

Solution Approach 2:

The sidecar proxies are designed to be self-configuring and self-managing to the extent possible, with automatic enrollment, self-provisioning of security policies, and autonomous operation. This self-service capability reduces the operational complexity of deploying and managing multiple sidecar instances, as they can automatically integrate with existing infrastructure and manage their own security contexts without requiring complex centralized configuration.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11863557B2Sidecar architecture for stateless proxying to databases
Publication Date: 2024.01.02 CYRAL INC
  • US11863557B2 patent drawing
  • US11863557B2 patent drawing
  • US11863557B2 patent drawing

AI summary

A mechanism for providing connection to a database is described. A connection to the database is intercepted. The connection is assigned to an instance of the database. A sidecar is configured to proxy the connection to the database. The sidecar is stateless and passes all communications for the connection to the instance of the database.