Adaptive Authorization Token for Dynamic Data Access Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database security systems face inefficiencies in controlling access to files with varying security requirements, leading to resource wastage and vulnerability to unauthorized access, as they often provide generic access and apply uniform encryption, failing to account for user behavior and data sensitivity.

Innovation Solution

Implementing an adaptive authorization token that stores user attributes and usage history to dynamically adjust access permissions and encryption levels based on user activity, applying different encryption algorithms to different data blocks and users, and generating self-decryption modules for secure data transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If generic access control is provided to all files in the data store, then ease of operation is improved, but security reliability deteriorates

Engineering Contradiction:
Improveaccess controlVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent segments access control into multiple levels: data store level, file level, and block level. Each level has its own access control list (ACL) with specific permissions. This allows fine-grained security control while maintaining ease of operation through hierarchical management. Users can access entire data stores, specific files, or even specific blocks within files based on their credentials.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by applying different security measures to different portions of data. Each file and each block within a file can have distinct access control permissions. This means that sensitive blocks can be restricted to specific users while less sensitive blocks remain accessible to broader user groups, optimizing both security and operational ease.

Inventive Principle:
Principle #3Local quality

2Reliability

If uniform encryption is applied to all data blocks, then security reliability is improved, but productivity deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidprocessing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies different encryption algorithms and key lengths to different data blocks based on their sensitivity level. Critical blocks containing sensitive information use stronger encryption (e.g., AES-256), while less sensitive blocks use weaker encryption (e.g., AES-128). This selective approach maintains high security for important data while improving overall processing efficiency.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent changes encryption parameters dynamically based on data characteristics. The system analyzes each data block to determine its sensitivity and adjusts encryption strength accordingly. This parameter adaptation allows the system to optimize the balance between security and processing performance for each individual block.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If strong encryption algorithms are used for all data, then security reliability is improved, but use of energy deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidprocessing energy
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements energy-efficient security by applying strong encryption only where necessary. Data blocks are classified by sensitivity, and encryption strength is matched to the required security level. High-sensitivity blocks receive strong encryption while low-sensitivity blocks use lighter encryption, reducing overall energy consumption while maintaining adequate security.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent applies the principle of partial action by using strong encryption for only the critical portions of data that require it, rather than uniformly applying strong encryption to all data. This partial application of strong security measures optimizes the energy-security tradeoff.

Inventive Principle:
Principle #16Partial or excessive action

4Reliability

If all data is encrypted before transmission, then security reliability is improved, but productivity deteriorates

Engineering Contradiction:
Improvedata protectionVSAvoidtransmission efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent encrypts data blocks selectively based on their sensitivity level and the trust level of the receiving system. Only sensitive blocks are encrypted with strong algorithms, while less sensitive blocks may use lighter encryption or none at all. This selective encryption maintains data protection for critical information while improving transmission efficiency.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent applies encryption partially rather than uniformly to all data. By encrypting only the necessary portions of data based on sensitivity analysis, the system achieves adequate security protection while minimizing the overhead associated with full-data encryption.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11425143B2Sleeper keys
Publication Date: 2022.08.23 BANK OF AMERICA CORP
  • US11425143B2 patent drawing
  • US11425143B2 patent drawing
  • US11425143B2 patent drawing

AI summary

A system includes an authorization token with a memory configured to store user attributes including a record of previous usage of the data store by the user, pre-authorization data for the user, and an access signature for accessing contents of a data store. The authorization token receives an authorization request. Session attributes are collected associated with a file path used by the user to request access to a file. A consistency measure is determined associated with whether the file path used by the user to request access to the file is consistent with a previous file path stored in a record of previous usage of the data store by the user. In response to determining that the consistency measure is greater than a threshold value, the access signature is provided to the data store, thereby granting the user access to the file.