File System Content-Based Security Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

File synchronization systems face challenges in ensuring data integrity and security, particularly due to the risk of nefarious third parties intercepting and spoofing commands, which can lead to irreversible errors such as unintended deletions.

Innovation Solution

The implementation of Content-Based Security Factors (CSF) generates expressions based on synchronized content, providing an additional authentication factor to validate transactions and automate secure file synchronization operations, including delete commands, by utilizing the very content synchronized across filesystems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional authentication methods are used for file synchronization commands, then security against unauthorized access is provided, but the system remains vulnerable to command interception and spoofing by third parties

Engineering Contradiction:
ImprovesecurityVSAvoidcommand interception and spoofing
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary authentication mechanism that uses synchronized file content itself as a mediator to verify command authenticity. Instead of relying solely on traditional credentials that can be intercepted, the system uses a cryptographic expression generated from the actual file content as an intermediate verification layer, making it difficult for third parties to spoof commands without access to the actual synchronized content.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the authentication parameter from static credentials to dynamic content-based expressions. The authentication factor is derived from the actual file content through cryptographic functions, meaning the authentication parameter changes with each file version and synchronization state, preventing replay attacks and spoofing while maintaining security.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If additional authentication credentials are required for secure file synchronization, then security is enhanced, but system complexity and performance overhead increase

Engineering Contradiction:
ImprovesecurityVSAvoidauthentication credential management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent makes the synchronized file content serve multiple functions simultaneously: it is both the data being synchronized and the source of authentication credentials. The same file content that needs to be kept in sync across systems is used to generate the cryptographic expression for authentication, eliminating the need for separate credential management systems and reducing overall complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system uses its own synchronized content to generate authentication factors, making it self-sufficient. Rather than requiring external authentication servers or separate credential storage, each system generates its own authentication expression from the local copy of the synchronized content, reducing dependency on external infrastructure and simplifying the architecture.

Inventive Principle:
Principle #25Self-service

3Reliability

If manual authentication verification is performed for each file synchronization operation, then security control is maintained, but automation and productivity are reduced

Engineering Contradiction:
Improvesecurity controlVSAvoidfile synchronization automation
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent performs preliminary authentication by generating and verifying cryptographic expressions automatically as part of the synchronization protocol itself. The authentication verification is built into the synchronization workflow, so that when files are synchronized, the authentication happens automatically in the background without requiring manual intervention, thus maintaining security control while enabling full automation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10467424B2File system content based security
Publication Date: 2019.11.05 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10467424B2 patent drawing
  • US10467424B2 patent drawing
  • US10467424B2 patent drawing

AI summary

A filesystem command is sent by a first processor, and for synchronization by a second processor. The filesystem command is directed to a second object of a second filesystem that is synchronized with a first object of a first filesystem. An expression is sent by the first processor to the second filesystem, and for authentication by the second processor. The expression is generated based on a third object of the first filesystems that is synchronized with a fourth object of the second filesystem.