I/O Interception for Real-Time Threat Detection Under Link Errors

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional malware detection methods in computing systems are time-consuming and disruptive, often requiring significant disk access and processing time, and may not detect threats in real-time, allowing potential damage to occur before countermeasures can be deployed.

Innovation Solution

A detection engine with an interceptor and detector system that intercepts Input/Output operations in the data path, allowing for real-time malware detection by analyzing metadata and data streams, with error handling mechanisms to ensure continuous threat detection during communication disruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional disk scanning methods are used for malware detection, then detection capability is provided, but detection time increases and normal disk operations are disrupted

Engineering Contradiction:
Improvemalware detection capabilityVSAvoiddetection time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by establishing a baseline of normal disk I/O patterns and maintaining a queue of intercepted I/O operations before actual malware detection is needed. This allows the system to be ready for immediate detection without requiring time-consuming full disk scans when threats arise.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system introduces an intermediary mechanism (the I/O queue and interception layer) between normal disk operations and the detection process. This intermediary captures and buffers I/O operations, allowing detection to occur without directly interfering with ongoing disk scanning operations, thus reducing detection time and operational disruption.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If disk scanning is performed to detect malware, then threat detection is achieved, but normal disk operations are interfered with and delayed

Engineering Contradiction:
Improvethreat detectionVSAvoidnormal disk operation continuity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system segments disk I/O operations into separate queues (e.g., read queues, write queues) and processes them independently from normal operations. This segmentation allows the detection system to monitor specific I/O patterns without blocking or interfering with the overall disk operation flow, maintaining ease of operation while achieving threat detection.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

An intermediary I/O queue layer is introduced between the disk driver and the detection engine. This intermediary captures I/O operations for analysis without directly interfering with normal disk access, allowing continuous operation while maintaining detection capability through the queued and processed operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of time

If delta scanning is used to optimize detection, then scanning time is reduced, but significant damage may occur before detection

Engineering Contradiction:
Improvescanning timeVSAvoidreal-time threat detection
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system maintains continuous monitoring of disk I/O operations through an always-active interception mechanism that continuously queues operations for analysis. This continuous action eliminates the gaps between scans, ensuring that threats are detected in real-time as they occur rather than after periodic scanning intervals, thus preventing significant damage while maintaining efficient processing.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The system performs preliminary interception and queuing of I/O operations continuously, preparing detection data in advance before actual malware activity is fully manifest. This preliminary action allows the detection system to identify threats immediately when patterns match, preventing damage while avoiding the need for time-consuming full scans.

Inventive Principle:
Principle #10Preliminary action

4Speed

If real-time detection is implemented through I/O interception, then detection speed improves, but system complexity increases

Engineering Contradiction:
Improvedetection speedVSAvoiddetection engine structure
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The system creates a copy of the I/O queue structure that can be processed independently from the main disk operation flow. This copying mechanism allows the detection engine to analyze queued operations without adding significant complexity to the core disk I/O path, achieving real-time detection speed while managing structural complexity through the use of data copies rather than complex interception logic.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250377960A1Continuous data content integrity compromise detection with error handling
Publication Date: 2025.12.11 DELL PROD LP
  • US20250377960A1 patent drawing
  • US20250377960A1 patent drawing
  • US20250377960A1 patent drawing

AI summary

A detection engine for handling communication errors while performing threat detection in a computing system is disclosed. The detection engine includes an interceptor that is positioned in a data path and configured to intercept IOs. The interceptor transmits a data stream, which may include data and/or metadata or the intercepted IOs, to a detector. The detector perform a detection analysis. When a threat is detected, a response may be initiated. When a communication error is present with respect to the detection engine, the interceptor may perform error handling operations. The error handling operations may store tracking data that allow the detector to catch-up with respect to the detection analysis when the communication error is resolved.