Microservice Data Flow Mapping for Security Policy Ambiguity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing security systems for microservices are limited in their ability to detect and prevent a wide range of security breaches, particularly due to the complexity of microservice-based applications, infrastructure transitions to the cloud, and stringent privacy laws, leading to issues like broken object level authorization and data breaches.

Innovation Solution

A security controller is deployed to analyze relationships between entities in a computing environment, generating a map of data flows, extracting access keys, and detecting inconsistent security policies, with features like side-scanning and API tracing to enforce security policies and prevent breaches.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If existing security systems are deployed to detect security breaches in microservice-based applications, then detection capability for specific problems is improved, but the ability to detect and prevent every security concern remains insufficient

Engineering Contradiction:
Improvedetection capabilityVSAvoidcomprehensive security coverage
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal security controller that performs multiple security functions including policy analysis, data flow mapping, anomaly detection, and breach prevention across diverse microservice architectures. This multi-functional approach enables a single system to address various security concerns comprehensively rather than requiring separate specialized systems for each security problem type.

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

Solution Approach 2:

The security system segments the complex microservice environment into individual data flows and entities, analyzing each component separately through automated mapping. By breaking down the overall security monitoring into discrete data flow segments, the system achieves both precise detection at the component level and comprehensive coverage across the entire distributed system.

Inventive Principle:
Principle #1Segmentation

2Productivity

If microservice-based applications are deployed to increase functionality and scalability, then system adaptability and productivity are improved, but security breaches and vulnerabilities increase

Engineering Contradiction:
Improvesystem scalabilityVSAvoidsecurity breaches
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent implements preliminary security actions by automatically mapping data flows and analyzing security policies before security breaches can occur. The system proactively identifies vulnerabilities and policy inconsistencies in the microservice architecture, enabling preventive security measures to be taken before actual security incidents happen, thus maintaining scalability while preventing breaches.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The security controller continuously monitors data flows between microservices and provides real-time feedback on security policy compliance. This feedback mechanism enables the system to detect and respond to security issues dynamically as they arise in the scalable microservice environment, maintaining both productivity and security.

Inventive Principle:
Principle #23Feedback

3Adaptability or versatility

If frequent changes are made to microservice-based applications to adapt to new requirements, then system adaptability is improved, but security vulnerabilities increase due to complexity

Engineering Contradiction:
Improvesystem flexibilityVSAvoidapplication complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements self-service security through automated data flow mapping and policy analysis that continuously adapts to changes in the microservice architecture without requiring manual reconfiguration. The system automatically discovers new data flows and entities when the application changes, maintaining security coverage despite increasing complexity and frequent modifications.

Inventive Principle:
Principle #25Self-service

4Productivity

If cloud-based systems are transitioned to improve infrastructure scalability, then system productivity is improved, but security breaches increase due to distributed architecture

Engineering Contradiction:
Improveinfrastructure scalabilityVSAvoidsecurity breaches
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces a security controller as an intermediary component that mediates security analysis across the distributed cloud-based microservice architecture. This intermediary system coordinates security policy enforcement and data flow monitoring across multiple cloud services and infrastructure components, enabling scalable cloud deployment while maintaining comprehensive security coverage.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12592973B2System and method for security control over data flows in distributed computing systems
Publication Date: 2026.03.31 CABER SYST INC
  • US12592973B2 patent drawing
  • US12592973B2 patent drawing
  • US12592973B2 patent drawing

AI summary

The present application generally relates to methods, systems, and programming for detecting security issues within a computing environment. In some embodiments, data flows may be analyzed to determine links between data sources and metadata. Using the derived relationships, a determination may be made as to whether the is a security issue, such as a security policy ambiguity, or a potential security issue. If so, one or more actions may be taken to prevent or minimize an impact of the security issue.