Dual File System Architecture for Automatic Sensitive Data Deletion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional device data protection techniques, relying on user authentication and encryption, are not foolproof and fail to protect sensitive data when the device is stolen or compromised, as they require user intervention which may not be feasible in all scenarios.

Innovation Solution

A computing device utilizing two file systems to automatically, quickly, and discretely hide or delete sensitive data when it detects a risky environment or unauthorized access, ensuring continuous protection without user interaction.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If user authentication and encryption mechanisms are used to protect sensitive data, then data security is improved, but the system fails when user intervention is not possible (device theft or loss)

Engineering Contradiction:
Improvedata protection reliabilityVSAvoiduser intervention requirement
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary actions by establishing two separate file systems (secure and non-secure) before any theft scenario occurs. The secure file system is pre-configured with encryption and access controls, while the non-secure file system handles regular operations. This preliminary setup enables automatic data protection without requiring user intervention during the actual theft event.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service through automatic detection of theft scenarios using sensors (accelerometer, GPS, network status) and autonomous execution of protection protocols. When theft is detected, the system automatically switches between file systems, encrypts data, and notifies authorities without requiring any user action, thereby resolving the contradiction between reliability and ease of operation.

Inventive Principle:
Principle #25Self-service

2Reliability

If automatic data deletion is implemented to protect sensitive data during theft, then data security is improved, but user access to legitimate data is restricted

Engineering Contradiction:
Improvedata protection effectivenessVSAvoiddata access flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system segments the file system into two distinct parts: a secure file system for sensitive data with automatic protection and deletion capabilities, and a non-secure file system for regular data access. This segmentation allows the system to delete or protect only the necessary sensitive data while leaving non-sensitive data accessible, thereby maintaining both data protection effectiveness and data access flexibility.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different quality levels of protection are applied to different data locations. The secure file system implements strong encryption and automatic deletion, while the non-secure file system provides open access. This local differentiation of protection quality enables the system to protect sensitive data automatically without restricting access to legitimate non-sensitive data, resolving the contradiction between protection effectiveness and access flexibility.

Inventive Principle:
Principle #3Local quality

3Speed

If data is hidden or deleted quickly upon detecting risky environment, then response time is improved, but system complexity increases due to dual file systems

Engineering Contradiction:
Improvedata protection response speedVSAvoiddual file system architecture
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The dual file system architecture is established as a preliminary structure before any protection event occurs. All data is pre-categorized and stored in appropriate file systems, with pre-configured encryption keys and access controls. When theft is detected, the system only needs to execute pre-planned switching and deletion operations, achieving fast response speed without requiring complex real-time decision-making algorithms.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If user authentication is required before data access, then data security is improved, but protection fails when password is compromised or device is taken during operation

Engineering Contradiction:
Improveauthentication-based protectionVSAvoidpassword compromise vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system extracts the authentication requirement from the data protection mechanism by implementing automatic protection at the file system level. Instead of relying on user authentication to protect data, the secure file system independently enforces protection through encryption and automatic deletion capabilities. This extraction removes the vulnerability to password compromise while maintaining strong data security.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP3161645B1Fast data protection using dual file systems
Publication Date: 2019.11.27 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP3161645B1 patent drawingFigure 1
  • EP3161645B1 patent drawingFigure 2~3
  • EP3161645B1 patent drawingFigure 4~5

AI summary

A computing device (102) is described that utilizes two file systems to enable sensitive data stored thereon to be deleted automatically, quickly, and discretely when the computing device is in a risky environment or context or when data protection has otherwise been activated. A first system (124) on the computing device manages a first memory area (128) that stores non-sensitive data while a second file system (126) on the computing device manages a second memory area (130) that stores sensitive data. Only the first file system operates to receive data requests from other processes executing on the computing device. In a first operating mode, the first file system interacts with the second file system to ensure that both non-sensitive and sensitive data is returned in response to data requests. In a second operating mode, communication between the two file systems is disabled and the second file system deletes the sensitive data.