Data Compliance Filters and Observability for Multi-Cloud Geofencing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data compliance strategies are inadequate for applications deployed across multi-cloud and edge infrastructures, lacking integration in application program code and failing to provide automated geofencing and observability of data subject to varying regulatory requirements, leading to increased compliance violations and penalties.

Innovation Solution

An observability and assurance service configures data compliance filters for application services in a data mesh, monitoring traffic to enforce compliance policies and adapt to regulatory changes, using a data compliance as code (DCaC) model to decouple compliance from business logic and ensure data sovereignty across geographies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data compliance is enforced non-specifically and in a programmatic blind-spot, then application deployment flexibility is maintained, but compliance violations increase leading to fines and penalties

Engineering Contradiction:
Improveapplication deployment flexibilityVSAvoidcompliance adherence
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a data compliance filter as an intermediary component between application services and data flows. This filter acts as a mediator that automatically enforces compliance policies without requiring changes to application code or deployment processes, thus maintaining deployment flexibility while ensuring compliance adherence through automated filtering of sensitive data based on geolocation and policy rules

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements preliminary action by configuring data compliance filters with compliance policies before data processing occurs. The system pre-establishes rules for identifying and handling sensitive data based on geolocation, and these rules are automatically applied to incoming data flows, preventing compliance violations before they happen rather than detecting them after the fact

Inventive Principle:
Principle #10Preliminary action

2Reliability

If automated data compliance filtering is implemented, then compliance enforcement reliability improves, but system complexity increases

Engineering Contradiction:
Improvecompliance enforcementVSAvoidsystem architecture complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the compliance enforcement function into a separate, modular data compliance filter that operates independently from application services. This segmentation allows compliance logic to be configured and updated without affecting application code, reducing system complexity while maintaining reliable compliance enforcement through dedicated filtering components that handle only data compliance concerns

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The data compliance filter serves as an intermediary layer that simplifies system architecture by centralizing compliance logic. Rather than embedding compliance checks throughout the application codebase, the filter acts as a single point of enforcement that automatically applies compliance rules to data flows, reducing overall system complexity while improving compliance enforcement reliability

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If data compliance filters are configured according to data compliance policy, then data sovereignty compliance improves, but processing time increases

Engineering Contradiction:
Improvedata sovereignty complianceVSAvoiddata processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-configuring data compliance filters with compliance policies and geolocation rules before data processing begins. The system pre-establishes which data types require filtering and what geolocation-based rules apply, enabling rapid automated enforcement during data processing without requiring real-time compliance analysis, thus maintaining data sovereignty compliance while minimizing processing time delays

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12367294B2Automated data compliance and observability
Publication Date: 2025.07.22 CISCO TECHNOLOGY INC
  • US12367294B2 patent drawing
  • US12367294B2 patent drawing
  • US12367294B2 patent drawing

AI summary

In one embodiment, an observability and assurance service, associated with various clusters of application services for an application that are executed in a data mesh, may configure a data compliance filter for a particular application service in one of the clusters of application services according to a data compliance policy. The observability and assurance service may monitor the data and traffic associated with the particular application service, wherein the data compliance filter is applied to the traffic to restrict sensitive data in the traffic from being processed by the particular application service. The observability and assurance service may make a determination that the data compliance policy has been violated by the particular application service. The observability and assurance service may modify, based on the determination, the data compliance filter for the particular application service.