Ransomware Mitigation via Virtual File System Checkpoints

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cybersecurity solutions are inadequate in detecting and mitigating advanced ransomware strains, particularly those that are fileless, polymorphic, and employ state-of-the-art anti-analysis and anti-detection methods.

Innovation Solution

The implementation of a device, system, and method that uses artificial intelligence (AI) with anthronoetic capabilities to stealthily detect malicious actions by creating temporary checkpoints during file operations, comparing existing data to determine destructive behavior, and preserving important data before destruction.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If signature-based antivirus and anti-spyware protection measures are used, then traditional malware can be detected, but advanced ransomware strains (fileless, polymorphic, with anti-analysis methods) cannot be effectively detected

Engineering Contradiction:
Improvedetection capabilityVSAvoidability to detect evolving threats
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system changes the detection parameters from static signature matching to dynamic behavioral analysis. It monitors file access patterns, encryption operations, and system behavior changes in real-time, allowing detection of ransomware based on its actions rather than its code signature. This enables detection of polymorphic and fileless ransomware that continuously changes their signatures.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system performs preliminary actions by creating checkpoints and snapshots of file systems before ransomware can execute destructive operations. It proactively monitors and detects malicious behavior patterns early in the ransomware lifecycle, before encryption completes, enabling prevention and recovery actions to be taken in advance.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If visible security agents and processes are deployed to detect malware, then detection capabilities are provided, but ransomware can detect and evade these security measures

Engineering Contradiction:
Improvemalware detectionVSAvoidanti-detection capability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system uses an intermediary approach by implementing a virtual file system layer that sits between the ransomware and the actual file system. This intermediary layer can detect and block malicious operations without the ransomware being aware of its presence, as the security mechanisms are embedded within the file system abstraction rather than appearing as separate visible agents.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system employs self-service detection by having the file system itself perform security checks and validations. The file system automatically monitors its own operations, detects anomalous patterns indicating ransomware activity, and triggers protective actions without requiring external security software intervention, making it invisible to ransomware anti-detection mechanisms.

Inventive Principle:
Principle #25Self-service

3Reliability

If data is preserved after ransomware destruction, then recovery is possible, but data loss occurs before preservation can happen

Engineering Contradiction:
Improvedata recoveryVSAvoidtime to preserve data
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary data preservation by continuously maintaining checkpoints and snapshots of the file system state. These checkpoints are created proactively before ransomware can destroy data, allowing immediate recovery by restoring from the most recent checkpoint without waiting for detection and response after the attack begins.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system ensures continuity of protective action by continuously monitoring file system operations and maintaining up-to-date checkpoints. This continuous protection ensures that data preservation is always current and ready, eliminating the time gap between ransomware infection and data recovery capability.

Inventive Principle:
Principle #20Continuity of useful action

4Measurement precision

If cybersecurity solutions are made more sophisticated to detect advanced threats, then detection accuracy improves, but system complexity and difficulty of use increase

Engineering Contradiction:
Improvethreat detection accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The system employs self-service by implementing automated behavioral analysis and anomaly detection algorithms that continuously learn and adapt to new ransomware patterns without requiring manual configuration or expert intervention. The complex detection logic is embedded within the file system, which automatically performs security analysis and takes protective actions, simplifying the user experience while maintaining high detection accuracy.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12306937B1Devices, systems, and methods for ransomware protection and mitigation
Publication Date: 2025.05.20 OCEANIT LABORATORIES INC
  • US12306937B1 patent drawing
  • US12306937B1 patent drawing
  • US12306937B1 patent drawing

AI summary

Disclosed herein are devices, systems, and methods for detecting, mitigating, and protecting against malicious actions and/or malicious computer software, including malware and ransomware. Specifically, disclosed embodiments mitigate the threat of ransomware across a wide range of devices including, for example, servers, storage systems, computers, and portable storage devices. At least one embodiment stealthily detects malicious actions by interposing when a file is opened for writing, creating a temporary checkpoint, comparing existing data in the file to what will be written to determine if it is destructive, and, if the behavior is malicious and/or destructive, preserving the checkpoint. At least a further embodiment can be implemented on, and/or ported in, a portable storage device (e.g., a USB device).