Immutable Log Storage via Cryptographic Hashing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for making log files immutable are either expensive, scalable, or not suitable for large datacenters and cloud computing environments, and there is a need for cost-effective and reliable immutability to prevent attacker modifications and ensure authenticity, especially in compliance with regulations like those in the European Union.

Innovation Solution

The approach involves hashing log files to produce a hash value, storing this value along with metadata, and communicating it to a trusted entity or a secure cryptoprocessor for immutability, allowing for later integrity validation by comparing the stored and re-determined tuples, which can be a third-party service or a TPM, ensuring that any modifications are detectable.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If special dedicated hardware is used to store log files to make them immutable, then reliability and security are improved, but cost and device complexity increase

Engineering Contradiction:
Improveimmutability of log filesVSAvoidspecial dedicated hardware
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a cryptographic copy of the log file (hash value) and stores it separately with metadata. This copy serves as an immutable record without requiring special dedicated hardware for the entire log storage system. The hash value acts as a digital fingerprint that can be verified later without modifying the original log files.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent extracts the essential immutability function from complex dedicated hardware by using cryptographic hashing. Only the critical hash value and metadata need to be stored securely, rather than requiring special hardware to monitor and control all log file operations. This extraction simplifies the system while maintaining immutability.

Inventive Principle:
Principle #2Taking out (Extraction)

2Device complexity

If traditional storage methods (CD, DVD, magnetic tape) are used for immutability, then cost is reduced, but scalability and speed deteriorate

Engineering Contradiction:
Improvetraditional storage methodsVSAvoidscalability and speed
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent replaces mechanical storage systems (CD, DVD, magnetic tape) with electronic cryptographic hashing and storage. The hash values are computed and stored as digital data that can be rapidly processed and scaled across networked systems, eliminating the physical limitations of traditional media while maintaining cost-effectiveness.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent makes the immutability mechanism universal by using cryptographic hashes that can be applied to any log file format or storage location. The same hashing approach works across different systems, networks, and platforms, providing scalable immutability without requiring system-specific hardware solutions.

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

3Device complexity

If hashing and storing tuple with metadata is implemented, then cost-effectiveness and scalability are improved, but measurement precision requirements increase

Engineering Contradiction:
Improvehashing and storage approachVSAvoidintegrity validation accuracy
Core Design Contradiction:
Device complexityVSMeasurement precision

Solution Approach 1:

The patent performs the hashing action preliminarily when the log file is created or modified. The hash value is computed in advance and stored with metadata before any potential tampering can occur. This preliminary action ensures that when integrity validation is needed later, the reference hash is already available for comparison, eliminating the need for complex real-time measurement.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10474554B2Immutable file storage
Publication Date: 2019.11.12 VMWARE INC
  • US10474554B2 patent drawing
  • US10474554B2 patent drawing
  • US10474554B2 patent drawing

AI summary

The present disclosure is related to devices and systems for immutable file storage. An example device can include instructions to hash a log file received from a log source to produce a hash value, store the hash value and information describing the log file, communicate the hash value and the information to a third party service, wherein the third party service maintains the communicated hash value and the communicated information such that the communicated hash value and the communicated information are immutable, access the communicated hash value and the communicated information, and compare the stored hash value and the stored information with the communicated hash value and the communicated information to determine whether the log file is unmodified.