Enterprise Data Security Architecture Using Workflow-Centric Reference Model

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data security approaches in enterprises often result in inefficiencies and high costs due to the need for multiple security components at different levels, each securing all data, rather than targeting specific security requirements across multiple levels based on workflows.

Innovation Solution

A method and system for architecting enterprise data security using a workflow-centric approach, employing a reference model to identify and secure specific data elements across multiple levels by determining vertical components that meet security requirements based on workflows, thereby focusing security on only the necessary data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple security components are deployed at different enterprise levels to secure all data, then data security coverage is improved, but system complexity and implementation costs increase

Engineering Contradiction:
Improvedata security coverageVSAvoidnumber of security components
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal security component that can operate across multiple enterprise levels (presentation, application, data) simultaneously. This single component provides authentication, authorization, and data protection functions throughout the entire enterprise architecture, eliminating the need for separate security components at each level while maintaining comprehensive security coverage.

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

Solution Approach 2:

The patent merges security functions that were previously distributed across multiple components into a single integrated security component. This consolidation combines authentication, authorization, and data protection capabilities into one unified system that operates across all enterprise levels, reducing overall system complexity while maintaining security effectiveness.

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If security is implemented at all enterprise levels for all data, then security comprehensiveness is improved, but implementation efficiency and cost-effectiveness deteriorate

Engineering Contradiction:
Improvesecurity comprehensivenessVSAvoidimplementation efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies local quality by enabling the universal security component to dynamically adjust its security measures based on the specific data sensitivity and enterprise level context. The component provides appropriate security controls locally at each interaction point while maintaining a unified architecture, ensuring comprehensive security without the overhead of multiple separate components.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The universal security component provides multi-functional capabilities that improve implementation efficiency. It handles authentication, authorization, and data protection in a single integrated system that operates across all enterprise levels, eliminating the need to implement and maintain separate security components at each level while maintaining comprehensive security coverage.

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

3Device complexity

If a universal security component is used across all enterprise levels, then system simplicity and cost are reduced, but the ability to provide targeted security for specific data elements may be compromised

Engineering Contradiction:
Improvenumber of security componentsVSAvoidtargeted security capability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The universal security component implements local quality by dynamically adapting its security controls to the specific requirements of each data element and enterprise level. It provides targeted security measures based on data sensitivity classifications and contextual requirements, ensuring that each data element receives appropriate security protection while maintaining a unified component architecture.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The universal security component employs dynamic behavior to adjust its security controls in real-time based on the specific data element being accessed and the enterprise level context. This dynamic adaptation enables the single component to provide targeted security for specific data elements while maintaining overall system simplicity and avoiding the need for multiple specialized components.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS7716716B1Method and system for architecting enterprise data security
Publication Date: 2010.05.11 T MOBILE INNOVATIONS LLC
  • US7716716B1 patent drawing
  • US7716716B1 patent drawing

AI summary

A method for architecting enterprise data security solutions for an enterprise having multiple levels is provided. The method includes analyzing the enterprise levels and a workflow related to the plurality of levels and analyzing a data element having a security requirement. The method includes providing a reference model including the data element. The reference model associates the data element and the security requirement with the workflow. The method includes determining a vertical component of the data element using the reference model. The vertical component identifies the security requirement for the data element based on the workflow for each of the plurality of levels of the enterprise. The method includes identifying a technical component using the reference model and the vertical component. The technical component is operable to provide the security requirement of the data element for the workflow across each of the plurality of levels of the enterprise.