Stub File Data Protection via Virtual Storage Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional data protection methods, such as transparent file encryption and decryption, do not adequately prevent data leaks from client devices, especially for classified files, as they do not ensure that files in memory remain secure.

Innovation Solution

Storing classified data files in a designated virtual storage area, such as a cloud server, and generating a stub file on the client device that records viewing permissions and storage location but not the actual data, thereby isolating operations within a virtual environment to prevent unauthorized access and leaks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If transparent file encryption and decryption methods are used, then data files are protected during storage and transmission, but data files in memory remain vulnerable to leaks

Engineering Contradiction:
Improvedata securityVSAvoidmemory leaks
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts the actual data content from the client device by storing it remotely on a server, while keeping only a stub file (containing metadata and encryption keys) locally. This separation removes the vulnerable element (actual data in memory) from the local environment, preventing memory leaks while maintaining accessibility through the stub file.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a stub file as an intermediary between the user and the actual data. The stub file contains encrypted data references and permissions but not the actual data content. Users interact with the stub file locally, which mediates access to the remote data, thereby preventing direct exposure of sensitive data in local memory.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Speed

If data files are stored locally on the client device, then access speed is fast, but data leaks cannot be prevented

Engineering Contradiction:
Improveaccess speedVSAvoiddata leaks
Core Design Contradiction:
SpeedVSObject-affected harmful factors

Solution Approach 1:

The patent segments the data storage system into two parts: a lightweight stub file stored locally on the client device and the actual data stored remotely on the server. The stub file contains only essential metadata and encrypted references, enabling fast local operations while the actual data remains secure on the server, thus resolving the contradiction between access speed and data security.

Inventive Principle:
Principle #1Segmentation

3Reliability

If encrypted data is written into magnetic disk, then data leaks are prevented during storage, but data in memory remains unprotected

Engineering Contradiction:
Improvestorage securityVSAvoidmemory exposure
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent creates a stub file copy that references the actual data without containing the full data content. The stub file is stored locally and can be freely copied or transmitted, while the actual data remains on the server. This copying approach allows local operations on a safe representation while keeping the real data secure, preventing memory exposure risks.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP3304275B1Protecting data files
Publication Date: 2020.07.22 ALIBABA GROUP HOLDING LTD
  • EP3304275B1 patent drawingFigure 1
  • EP3304275B1 patent drawingFigure 2
  • EP3304275B1 patent drawingFigure 3

AI summary

Protecting data files is disclosed, including: in response to an indication that a data file has been generated by a client device, determining a security classification associated with the data file; determining that the security classification associated with the data file comprises a classified file; storing the data file in a designated virtual storage area; and generating a stub file at an original storage location of the data file, wherein the stub file includes a viewing permission associated with the data file and a storage location of the data file in the designated virtual storage area.