Data Redaction via Access Policy Views

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Enterprises implementing Service Oriented Architecture (SOA) face challenges in controlling access to data due to the coarseness of conventional access control methods, which often require users to have access to entire data storage constructs, leading to security and complexity issues.

Innovation Solution

The implementation of a mechanism for data redaction based on access policies associated with requestors, allowing systems to provide only permitted portions of data results, using a Liquid Data framework that maps data to views associated with requestors, enabling granular control over information dissemination.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional access control methods are used to control individual access to data storage constructs, then access security is improved, but the granularity of control is too coarse and users must be cleared for the entire content of the data storage construct

Engineering Contradiction:
Improveaccess securityVSAvoidcontrol granularity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments data storage constructs into hierarchical levels (e.g., database, table, column, row) and implements access control at each level. This allows fine-grained control where users can be granted access to specific portions of data rather than requiring clearance for the entire data storage construct, thereby improving control granularity while maintaining security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different access control policies to different portions of data within the same data storage construct. Each data element can have its own access permissions defined based on local security requirements, allowing users to access only the specific data portions they are authorized for, rather than requiring access to the entire construct.

Inventive Principle:
Principle #3Local quality

2Ease of operation

If users are granted access to the entirety of data storage constructs, then access control implementation is simplified, but security is compromised as users gain access to more data than necessary

Engineering Contradiction:
Improveaccess control implementationVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent extracts the access control logic from the data storage construct itself and implements it as a separate layer. Access control policies are defined independently and applied when data is accessed, allowing simplified implementation without requiring changes to the underlying data storage structure while still providing fine-grained security control.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an intermediary access control layer between the user and the data storage construct. This intermediary evaluates access requests against defined policies and determines which portions of data the user can access, simplifying the implementation while maintaining security by preventing direct access to unauthorized data portions.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If fine-grained access control is implemented at multiple hierarchical levels, then data security is improved, but the complexity of managing access policies increases

Engineering Contradiction:
Improvedata securityVSAvoidpolicy management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges access control policies at different hierarchical levels into a unified policy framework. Access decisions are made by evaluating the combination of policies across levels (database, table, column, row), allowing fine-grained security control while simplifying policy management through consolidated policy definitions and centralized policy evaluation mechanisms.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS8086615B2Security data redaction
Publication Date: 2011.12.27 ORACLE INT CORP
  • US8086615B2 patent drawing
  • US8086615B2 patent drawing
  • US8086615B2 patent drawing

AI summary

In accordance with one embodiment of the present invention, there are provided mechanisms and methods for securing access to data. These mechanisms and methods for securing access to data make it possible for systems to have improved control over accesses to information by redacting responses made by services based upon access policies. Requestors may be users, proxies or automated entities. This ability of a system to redact responses to queries or requests for services in accordance with access policies makes it possible to attain improved security in computing systems over conventional access control mechanisms that control based upon privileges for accessing a file, an account, a storage device or a machine upon which the information is stored.