Access Control Component Filename Verification for Secure Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing access control methods for secure data storage devices that rely on encryption keys are ineffective when the storage device itself stores keys, and sharing such devices poses risks of unauthorized access, as they do not adequately prevent one user's data from being accessed by another.

Innovation Solution

A method that determines the return address of a software function caller within an access control component, identifies the caller's filename, and allows access only if the filename is included in a safelist of authorized components, using digital signatures for verification and module-specific tags to ensure secure data access and sharing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If key-based access control is used for secure data storage devices, then data security is improved, but the device cannot be securely shared among multiple users as one user's data may be accessible to another

Engineering Contradiction:
Improvedata securityVSAvoiddevice shareability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The access control mechanism is segmented into multiple independent components: return address verification, filename extraction, safelist checking, and digital signature validation. Each component performs a specific function, and all must succeed for access to be granted, creating a multi-layered security architecture that enables both security and shareability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The access control component acts as an intermediary between software components seeking access and the protected resource. It intercepts access requests, verifies caller identity through return address and filename, checks against the safelist, and only permits access when verification succeeds, thereby enabling secure sharing without direct key exposure

Inventive Principle:
Principle #24Intermediary (Mediator)

2Device complexity

If encryption keys are stored on the secure data storage device itself, then access control simplicity is improved, but security is worsened as the device becomes a target for key extraction

Engineering Contradiction:
Improveaccess control simplicityVSAvoidsecurity against key extraction
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The critical security verification functions (return address determination, filename extraction, safelist validation) are extracted from the secure data storage device and placed in a separate access control component. This separation removes the attack surface for key extraction while maintaining the device's ability to enforce access control through the intermediary component

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The access control component serves as an intermediary that handles all security-critical operations outside the secure device boundary. It verifies caller identity and authorization without exposing internal keys or cryptographic materials, thereby simplifying device architecture while enhancing security against extraction attacks

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11907405B2Secure data storage device access control and sharing
Publication Date: 2024.02.20 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11907405B2 patent drawing
  • US11907405B2 patent drawing
  • US11907405B2 patent drawing

AI summary

A return address of a caller of a software function within an access control component is determined, the caller comprising a software component seeking access to a protected resource protected by the access control component. From the return address, a filename of the caller is determined. Responsive to determining that the filename is included in a set of filenames of components allowed to access the protected resource, the caller is allowed to access the protected resource.