Fabricated Data Account Orchestration for Leak Source Detection

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Detecting data leaks in a distributed data orchestration apparatus is challenging due to the difficulty in tracking and diagnosing the source of data leaks without experiencing the leak within the network, and existing solutions are inefficient, inaccurate, and resource-intensive.

Innovation Solution

Creating fabricated data accounts within network servers, analyzing transmitted responses through an orchestration apparatus, and using a breach engine to locate the geographic source of the leak, with support from a distributed ledger and machine learning to determine the root cause and update security rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If traditional data leak detection methods are used, then detection capability is limited, but computing resources and time consumption increase significantly

Engineering Contradiction:

Improvedata leak detection accuracyVSAvoiddetection efficiency

Core Design Contradiction:

Measurement precisionVSProductivity

Solution Approach 1:

The system performs preliminary actions by creating fabricated data accounts and exposing them to potential data leaks before actual detection begins. These fabricated accounts serve as traps that proactively wait for data leak attempts, allowing the system to detect leaks as they occur rather than analyzing historical data after the fact.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The orchestration apparatus acts as an intermediary between the fabricated data accounts and the analysis system. It coordinates the creation, exposure, and monitoring of fabricated accounts across multiple network servers, managing the complex interactions and data collection without requiring direct access to each individual account or server.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Measurement precision

If distributed data orchestration with fabricated accounts is implemented, then data leak detection accuracy improves, but system complexity increases

Engineering Contradiction:

Improvedata leak detection accuracyVSAvoidsystem architecture complexity

Core Design Contradiction:

Measurement precisionVSDevice complexity

Solution Approach 1:

The system segments the data leak detection function into multiple independent fabricated data accounts distributed across different network servers. Each account operates independently as a detection node, and the orchestration apparatus coordinates them without requiring tight coupling. This segmentation allows parallel detection efforts while maintaining individual account simplicity.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The fabricated data accounts serve multiple functions: they act as data traps for detection, serve as monitoring points for network traffic analysis, and provide a standardized interface for the orchestration apparatus. This multi-functionality reduces the need for separate specialized components for each detection task.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Loss of information

If fabricated data accounts are exposed within network servers, then data leak source tracking improves, but security risks during the process increase

Engineering Contradiction:

Improvedata leak source trackingVSAvoidsecurity exposure risk

Core Design Contradiction:

Loss of informationVSObject-affected harmful factors

Solution Approach 1:

The system uses fabricated data accounts with disposable, non-sensitive information rather than exposing real user data. These accounts contain dummy data that can be safely exposed without consequence. Once their detection purpose is fulfilled, they can be discarded and replaced, minimizing the duration of any potential security exposure.

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

Solution Approach 2:

The system converts the potential harm of exposed data into a benefit by using the exposure itself as the detection mechanism. The very act of exposing fabricated accounts to potential data leaks allows the system to identify and track leak sources, turning what would normally be a security vulnerability into an active detection capability.

Inventive Principle:

Principle #22Blessing in disguise (Convert harm into benefit)

Data Source

PatentUS12513165B2System and method to detect data leaks via a distributed data orchestration apparatus and transmitted fabricated data responses

Publication Date: 2025.12.30 BANK OF AMERICA CORP

AI summary

Systems, computer program products, and methods are described herein for detecting data leaks via a distributed data orchestration apparatus and transmitted fabricated data responses. The present disclosure is configured to: create a plurality of fabricated data accounts within a set of network servers, where the plurality of fabricated data accounts are connected to an account monitoring engine; collect a set of transmitted fabricated data responses from the plurality of fabricated data accounts; analyze the collected set of transmitted fabricated data responses via an orchestration apparatus; determine the root cause of the data leak associated with the plurality of fabricated data accounts via the orchestration apparatus; and locate a geographic source of the data leak associated with the plurality of fabricated data accounts via a breach engine, where the geographic source of the data leak is located through the root cause of the data leak.