File System Content Obfuscation via Encrypted Name Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In high-security environments, existing file systems pose challenges in managing file and directory names securely, as they often require IT administrators to have access to sensitive information, which can compromise security protocols and burden end users with administrative tasks beyond their expertise.

Innovation Solution

Implementing an encrypted database that maps directory names to automatically generated 'code names' or obfuscated names, allowing system administrators to manage file systems without viewing content, while end users can collaborate using different security clearances and maintain operational security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If IT administrators have access to file and directory names in traditional file systems, then they can perform management tasks, but security is compromised and users bear administrative burdens

Engineering Contradiction:
ImproveIT administration task performanceVSAvoidSecurity compromise
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an encrypted database as an intermediary layer between the file system and administrators. This database stores mappings between original filenames and obfuscated code names, allowing administrators to manage files using secure code names without direct access to sensitive original filenames, thus resolving the contradiction between administration capability and security

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If traditional file systems are used in high-security environments, then file management is simple, but administrators must view sensitive information

Engineering Contradiction:
ImproveFile system structureVSAvoidSensitive information exposure
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The patent extracts the sensitive filename information from the visible file system interface by storing it in an encrypted database. Administrators interact with obfuscated code names instead of original filenames, removing sensitive information from the administrative workflow while maintaining full file management capability

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a copy of the file system interface using obfuscated code names that map to original filenames through encrypted storage. This copy allows administrators to perform all necessary file operations without exposing sensitive original filenames, maintaining operational simplicity while preventing information exposure

Inventive Principle:
Principle #26Copying

3Reliability

If end users perform IT administration tasks, then administrators can maintain security clearance, but users face tasks beyond their expertise

Engineering Contradiction:
ImproveSecurity clearance maintenanceVSAvoidUser task capability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The encrypted database acts as a mediator that allows end users to perform administrative tasks using simple code names without needing to understand complex file system structures or security protocols. The system handles the complexity of encrypted mappings automatically, enabling users to maintain security clearance while performing tasks within their expertise

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11947696B2File system content obfuscation in high security environments
Publication Date: 2024.04.02 EMC IP HLDG CO LLC
  • US11947696B2 patent drawing
  • US11947696B2 patent drawing
  • US11947696B2 patent drawing

AI summary

A system can receive, from user input, request data indicative of a request to create a file with a first filename. The system can, based on the request data, determining a second filename for the file. The system can store an association between the first filename and the second filename. The system can create the file in a file system with the second filename.