I/O Inspection System for Storage Cybersecurity Threat Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cybersecurity measures for storage systems are inadequate in detecting and defending against malicious software and code threats, relying on basic access control methods that lack advanced intelligence and analysis.

Innovation Solution

Implementing input/output (I/O) inspection methods that intercept and analyze I/O operations, storing segments of data in a write I/O buffer, and injecting protection instructions to detect security threats, with defensive actions such as taking snapshots, breaking replication, throttling, or halting I/O operations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If basic access control lists are used for security, then system simplicity is maintained, but security detection capability is insufficient

Engineering Contradiction:
Improvesecurity detection capabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

An I/O inspector is introduced as an intermediary component between the host and storage system. This inspector intercepts I/O operations, performs security inspections on data segments, and injects protection instructions without requiring fundamental changes to the existing storage system architecture. The intermediary handles the complex security analysis while maintaining the simplicity of the core storage system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Security inspections are performed preliminarily on data segments before they are written to storage. The I/O inspector analyzes data segments in the write I/O buffer, detects potential threats, and injects protection instructions in advance. This preliminary action prevents malicious data from being stored while allowing legitimate data to pass through unchanged.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If advanced security inspection is implemented, then security detection capability is improved, but processing time increases

Engineering Contradiction:
Improvesecurity detection capabilityVSAvoidI/O processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The I/O inspector performs partial inspections on data segments rather than analyzing every byte in detail. It uses multiple inspection levels, applying more rigorous analysis only when suspicious patterns are detected. This selective approach maintains security detection capability while reducing the average processing time for legitimate data.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

Data is divided into segments that are inspected independently in the write I/O buffer. The segmentation allows parallel processing of multiple data segments and enables the system to focus computational resources on specific segments that require security analysis, rather than processing the entire data stream sequentially.

Inventive Principle:
Principle #1Segmentation

3Reliability

If protection instructions are injected into data segments, then security protection is enhanced, but data integrity may be compromised

Engineering Contradiction:
Improvesecurity protectionVSAvoiddata integrity
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

Protection instructions are extracted and injected as separate metadata elements rather than being embedded within the actual data content. The I/O inspector adds these protective markers to data segments in the write I/O buffer, allowing the original data to remain intact while attaching security attributes that enable future protective actions without altering the core data.

Inventive Principle:
Principle #2Taking out (Extraction)

4Speed

If real-time security inspection is performed, then threat detection speed is improved, but system resource consumption increases

Engineering Contradiction:
Improvethreat detection speedVSAvoidsystem resource consumption
Core Design Contradiction:
SpeedVSUse of energy by moving object

Solution Approach 1:

The I/O inspector utilizes resources already allocated for I/O processing to perform security inspections. By integrating the inspection function into the existing I/O path and using the same buffer memory structures, the system achieves real-time security detection without requiring separate dedicated resources for each inspection operation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10586052B1Input/output (I/O) inspection methods and systems to detect and defend against cybersecurity threats
Publication Date: 2020.03.10 EMC IP HLDG CO LLC
  • US10586052B1 patent drawing
  • US10586052B1 patent drawing
  • US10586052B1 patent drawing

AI summary

Input/output (I/O) inspection methods and systems are disclosed to detect and defend against cybersecurity threats. In one example, a method includes intercepting input/output (I/O) operations including I/O write operations for a storage system. Segments of data related to the intercepted write I/O operations are stored in a write I/O buffer. One or more levels of inspection are performed on the segments of data stored in the write I/O buffer to detect a security threat. A protection instruction is injected in any segments of data having a detected security threat. The defensive action can be performed for the injected protection instruction prior to storing segments of data in the write I/O buffer in the storage system. The protection instruction can be injected at the head of the segments of data having a detected security threat.