Token-Based Secure Data Management via Mediator
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data security measures often interfere with legitimate access needs, and there is a lack of efficient methods to securely manage and share sensitive data within enterprises while maintaining security.
Innovation Solution
A data storage service generates and uses tokens, such as randomly generated character strings combined with user IDs and data types, to represent sensitive data, allowing secure storage and access while minimizing exposure of the actual data, with access policies determining authorized access levels.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional data security measures are implemented to protect sensitive data, then data security is improved, but access efficiency deteriorates
Solution Approach 1:
The patent introduces tokens as intermediary objects that represent sensitive data without exposing the actual data. These tokens enable authorized access to data functionality while maintaining security boundaries. The token acts as a mediator between the data consumer and the sensitive data, allowing operations to be performed on the data through the token without direct exposure of the underlying sensitive information.
Solution Approach 2:
The patent creates token copies that represent the sensitive data rather than using the actual data directly. These token copies contain sufficient information to perform data operations and validation while not exposing the sensitive data itself. The copying mechanism allows efficient access to data functionality while maintaining security by working with representations rather than the actual sensitive information.
2Reliability
If access safeguards are enforced to limit unauthorized access to sensitive data, then data security is improved, but legitimate access needs deteriorate
Solution Approach 1:
The patent implements dynamic access control where tokens can be configured with different permission levels and validity periods. Access rights are not static but can be adjusted based on the specific operational context, user role, and data sensitivity requirements. This dynamic approach allows legitimate access needs to be met while maintaining security by adjusting permissions appropriately for each access scenario.
Solution Approach 2:
The patent changes the parameters of data access by using tokens with varying attributes such as permission scopes, expiration times, and access conditions. Instead of binary authorized/unauthorized access, the system uses parameterized tokens that define specific access conditions. This allows legitimate users to access data under defined parameters while maintaining security through conditional access control.
3Adaptability or versatility
If sensitive data is exposed for internal service access, then service functionality is improved, but data security deteriorates
Solution Approach 1:
The patent extracts the essential access functionality from the sensitive data itself and places it into tokens. The tokens contain the necessary information to perform data operations, validate access rights, and maintain data integrity without containing the actual sensitive data. This extraction allows services to function with the extracted access capabilities while the sensitive data remains protected and separate.
Solution Approach 2:
The patent introduces tokens as intermediary objects that enable service functionality without exposing sensitive data. The tokens mediate between internal services and sensitive data, providing the necessary access controls and validation mechanisms while keeping the sensitive data protected. This intermediary approach maintains service versatility while preventing direct exposure of sensitive information.
Data Source
AI summary
In some implementations, tokens that are representative of sensitive data may be used in place of the sensitive data to maintain the security of the sensitive data. For example, data may be separated into sensitive data and nonsensitive data, and at least the sensitive data is securely delivered to a data storage service. The data storage service generates a token that is representative of the sensitive data and stores the sensitive data as secure data. The data storage service may deliver the token to an entity that also receives the nonsensitive data, and the entity may use the token in place of the sensitive data. In some implementations, different tokens are generated each time the same piece of sensitive data is submitted for storage as secure data. Further, in some implementations, An expiration time may be assigned to sensitive data, and expired data and associated tokens may be deleted.