Storage Drive Controller Hash Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current storage drives lack the ability to authenticate data that is in transit or in motion, such as firmware and operational code, which can be compromised by malware or system failures during power cycles or low-power states, leading to potential data corruption and system instability.

Innovation Solution

Implementing a system that computes and compares hashes of data using a cryptographic hash function at trigger events like power changes or scheduled intervals, ensuring data integrity by marking data as authentic or invalid based on hash matches, and storing these hashes securely.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Use of energy by moving object

If the storage drive enters low power mode or loses power, then energy consumption is reduced, but data integrity cannot be maintained

Engineering Contradiction:
Improveenergy consumptionVSAvoiddata integrity
Core Design Contradiction:
Use of energy by moving objectVSReliability

Solution Approach 1:

The system computes and stores hash values of critical data (firmware, mapping tables, operational code) before entering low power mode or experiencing power loss. These pre-computed hashes are saved in non-volatile memory, enabling rapid authentication upon power restoration without requiring continuous monitoring during the power-off state.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Upon power restoration or exit from low power mode, the system recomputes hashes of the same data and compares them against the stored reference hashes. This feedback mechanism provides immediate verification of data integrity, allowing the system to detect and respond to potential corruption or tampering that may have occurred during the power interruption.

Inventive Principle:
Principle #23Feedback

2Reliability

If the storage drive continuously monitors and authenticates data, then data integrity is maintained, but processing time and computational resources increase

Engineering Contradiction:
Improvedata integrityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Instead of continuous authentication, the system performs hash computation and comparison at specific periodic intervals or trigger events (power state changes, scheduled times, process execution milestones). This periodic approach maintains data integrity while significantly reducing computational overhead and processing time compared to continuous monitoring.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The storage drive autonomously performs hash computation, storage, and comparison operations without requiring external intervention or host system involvement. The controller automatically manages the authentication process, computing hashes of critical data structures and comparing them against stored references, thereby eliminating the need for time-consuming external verification procedures.

Inventive Principle:
Principle #25Self-service

3Measurement precision

If the storage drive stores all data hashes for authentication, then authentication accuracy is improved, but storage space requirements increase

Engineering Contradiction:
Improveauthentication accuracyVSAvoidstorage space
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The system applies hash authentication selectively to specific critical data structures (firmware, mapping tables, operational code) rather than all stored data. By focusing computational and storage resources on the most important data elements that require authentication, the system achieves high authentication accuracy for protected data while minimizing overall storage space consumption.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system extracts only the essential hash values needed for authentication and stores them separately from the original data. By storing only the hash digests rather than the complete data structures, and by extracting authentication functionality into a dedicated controller module, the system reduces storage requirements while maintaining authentication capability.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS10211976B2Hash authenticated data
Publication Date: 2019.02.19 SEAGATE TECH LLC
  • US10211976B2 patent drawing
  • US10211976B2 patent drawing
  • US10211976B2 patent drawing

AI summary

Systems and methods for hash authenticated data are described. In one embodiment, the storage device includes a storage drive and/or a controller. In some embodiments, the controller is configured to identify data to be authenticated, compute a first hash of the data using a hash function, detect a trigger event associated with the storage drive, and authenticate, after the trigger event, the data based at least in part on the first hash of the data.