Business Capability Model for Data Dependency Tracing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods are ineffective in understanding and addressing complex information security incidents that involve multiple applications and systems, making it difficult to trace data lineage and transformation, and identifying unauthorized access risks.

Innovation Solution

A computing platform generates a business capability model to map enterprise technology resources, identify data flow relationships, and display visual representations of data dependencies, allowing users to trace and simulate impacts of incidents or changes on the system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Difficulty of detecting and measuring

If current security monitoring methods are used, then basic security threats can be detected, but complex information security incidents involving multiple applications and systems cannot be effectively traced or understood

Engineering Contradiction:
Improvedifficulty of tracing data lineageVSAvoidunderstanding of data transformation
Core Design Contradiction:
Difficulty of detecting and measuringVSLoss of information

Solution Approach 1:

The patent segments the complex enterprise system into discrete data flow relationships between applications and systems. By breaking down the monolithic view of data movement into individual data flow segments, the system enables granular tracing of data lineage across multiple applications without being overwhelmed by system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary data flow mapping system that sits between the complex enterprise applications and the security monitoring tools. This intermediary layer translates and standardizes data flow information from various applications into a unified representation, enabling effective tracing and analysis of data lineage across heterogeneous systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If detailed data flow relationships across multiple applications are mapped, then complete data lineage can be traced, but system complexity and difficulty of implementation increase

Engineering Contradiction:
Improvecompleteness of data lineage tracingVSAvoidcomplexity of mapping system
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal data flow mapping framework that can handle multiple types of applications and systems through a common interface and methodology. This multi-functional approach allows the same mapping system to trace data flows across diverse applications without requiring application-specific customization, thereby reducing overall system complexity.

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

Solution Approach 2:

The patent performs preliminary data flow mapping and relationship establishment before security incidents occur. By pre-mapping data lineage relationships and storing them in an accessible format, the system enables rapid incident analysis without needing to perform complex real-time tracing, thereby reducing the operational complexity during security events.

Inventive Principle:
Principle #10Preliminary action

3Measurement precision

If comprehensive data dependency mapping is implemented, then impact analysis of security incidents can be performed, but time and resources required for implementation increase

Engineering Contradiction:
Improveprecision of impact analysisVSAvoidtime for incident analysis
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent performs comprehensive data dependency mapping in advance, before security incidents occur. By pre-establishing and storing the complete data flow relationships between applications and systems, the system enables rapid impact analysis during incidents without needing to perform time-consuming real-time tracing, thus reducing analysis time while maintaining precision.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a simplified copy or model of the complex data flow relationships that can be quickly queried and analyzed. This abstracted representation maintains the essential connectivity information needed for impact analysis but is much faster to process than the full detailed system state, enabling rapid incident response.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11704618B2Application mapping and alerting based on data dependencies
Publication Date: 2023.07.18 BANK OF AMERICA CORP
  • US11704618B2 patent drawing
  • US11704618B2 patent drawing
  • US11704618B2 patent drawing

AI summary

Aspects of the disclosure relate to application mapping and alerting based on data dependencies in business and technology logic. In some embodiments, a computing platform may receive a request to map enterprise technology resources. Then, the computing platform may generate a business capability model. Next, the computing platform may cause a user computing device to display a graphical user interface comprising selectable graphical representations of applications associated with the enterprise technology resources. Then, the computing platform may receive a user input identifying an occurrence of a technology incident by selecting one of the graphical representations. In response to the selection, the computing platform may trace, using the generated business capability model, upstream or downstream impacts of the technology incident. Then, the computing platform may cause a visual representation of data dependencies indicating upstream or downstream impacts of the technology incident to be displayed on the user computing device.