Cryptographic Document Versioning with Segmented Access Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing model for granting access to user data is insecure, particularly when multiple entities are involved, as it allows unauthorized access and malicious changes or corruption if the security of any entity is compromised.
Innovation Solution
Documents are encrypted and updated with a private key, allowing authorized entities to create new versions and validate their authenticity using public keys, while also enabling changes to security principals for subsequent versions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple entities are granted access to user data, then data accessibility and collaboration are improved, but security and risk of unauthorized access deteriorate
Solution Approach 1:
The patent segments access control by creating individual cryptographic signatures for each entity and each document version. Each entity receives a unique private key for signing, and the system maintains separate security data records for each entity-document pair, isolating security risks to individual segments rather than affecting the entire system.
Solution Approach 2:
The patent introduces cryptographic signatures and security data as intermediaries between entities and user data. Instead of direct access, entities must use their private keys to sign document versions, and the system validates these signatures using public keys stored in security data, creating a secure intermediary layer that prevents unauthorized access.
2Reliability
If cryptographic validation is implemented for each document version, then security and authorization verification are improved, but system complexity and computational overhead increase
Solution Approach 1:
The patent performs preliminary cryptographic setup by generating key pairs and storing public keys in security data before document operations. The system pre-configures which entities are authorized to sign which documents, so that during document versioning, only simple signature validation is needed rather than complex authorization checks.
Solution Approach 2:
The patent uses cryptographic public keys as copyable validation tokens. Instead of complex runtime authorization logic, the system copies public keys from security data to validate signatures, replacing complex verification procedures with simple cryptographic comparison operations.
Data Source
AI summary
Aspects of the subject matter described herein relate to updating and validating documents secured cryptographically. In aspects, documents are encrypted to protect them from unauthorized access. An entity having write access to a document may create a new version of the document and sign the new version with a private key. Other entities may validate that the new version of the document was created by an authorized entity by using a public key available in security data associated with the version. The entities that are authorized to create a new version may change which security principals are allowed to create subsequent versions.