Controlled Corruption for Authentication Data Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing authentication systems are vulnerable to third-party interference during data transfer, allowing unauthorized access as login details can be extrapolated from transmitted data, compromising security.
Innovation Solution
A method involving controlled corruption and multi-layer encryption, where login information is divided into chunks, corrupted with alphanumeric or symbolic characters, and encrypted using AES protocols, with unique portions stored across multiple devices, preventing revelation of login details to the system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional authentication systems transmit login details between user and system, then authentication functionality is achieved, but security is compromised as third parties can intercept and extrapolate login information
Solution Approach 1:
The login information is divided into multiple separate chunks that are stored on different devices. Each chunk alone is insufficient for authentication, but all chunks together reconstruct the complete login information. This segmentation prevents third parties from obtaining usable authentication data through interception of individual transmissions.
Solution Approach 2:
A corruption mechanism is introduced as an intermediary layer between the login information and its transmission/storage. This corruption mechanism deliberately modifies the data by adding, removing, or substituting characters, making intercepted data unreadable and unusable for authentication purposes while allowing authorized reconstruction.
2Reliability
If login information is divided into chunks and stored across multiple devices, then security against third-party interference is improved, but system complexity increases
Solution Approach 1:
The login information is divided into multiple separate chunks that are stored on different devices. Each chunk alone is insufficient for authentication, but all chunks together reconstruct the complete login information. This segmentation prevents third parties from obtaining usable authentication data through interception of individual transmissions.
Solution Approach 2:
A corruption mechanism is introduced as an intermediary layer between the login information and its transmission/storage. This corruption mechanism deliberately modifies the data by adding, removing, or substituting characters, making intercepted data unreadable and unusable for authentication purposes while allowing authorized reconstruction.
3Reliability
If multi-layer encryption and corruption operations are applied to login data, then security against interception is enhanced, but processing time and computational resources increase
Solution Approach 1:
The login information is divided into multiple separate chunks that are stored on different devices. Each chunk alone is insufficient for authentication, but all chunks together reconstruct the complete login information. This segmentation prevents third parties from obtaining usable authentication data through interception of individual transmissions.
Solution Approach 2:
The corruption mechanism applies parameter changes to the login data by systematically adding, removing, or substituting characters at specific positions. This transforms the data into an unusable form for interceptors while maintaining the ability to reconstruct the original information through authorized processing.
Data Source
AI summary
The present disclosure, in some embodiments, relates to a data protection method comprising: determining a file comprising content data on a computing system; generating index information for the file; transmitting the index information to a cloud system; executing a corruption operation on the file comprising: dividing the content data of the file into a plurality of data chunks; executing a first encryption operation based on an encryption protocol, on the first data chunk; executing a second encryption operation based on the encryption protocol, on the second data chunk; generating or assigning a first name for the first data and a second name for the second data chunk; and generating a key associated with an order of the first data chunk and the second data chunk.