Secrets Engine Pseudo-Filesystem Secure Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Computing systems with multi-tier architectures are vulnerable to intrusion due to the storage of secrets in filesystem objects, which can remain accessible indefinitely, and modifying these systems to store and access secrets from external locations requires cumbersome custom programming.

Innovation Solution

A secrets engine that abstracts secret management by obtaining secrets from a secrets store, presenting them as data content of a pseudo-filesystem object, and deleting them after use, mimicking filesystem operations to replace and secure secret storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If secrets are stored in filesystem objects on discrete system components, then secrets are readily accessible for authentication, but the system becomes vulnerable to intrusion as secrets remain accessible indefinitely

Engineering Contradiction:
Improveaccessibility of secretsVSAvoidvulnerability to intrusion
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

A secrets engine is introduced as an intermediary component between the filesystem and client programs. The engine intercepts read requests for secrets, retrieves them from a secrets store, and delivers them to clients without persisting them locally. This mediator architecture maintains accessibility while eliminating the security vulnerability of indefinite local storage.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The secret data is extracted from the local filesystem environment and relocated to a dedicated secrets store managed by the secrets engine. By removing secrets from the traditional filesystem storage location, the system eliminates the security risk associated with persistent local storage while maintaining the ability to retrieve secrets when needed.

Inventive Principle:
Principle #2Taking out (Extraction)

2Object-affected harmful factors

If systems are modified to store and access secrets from external locations, then security is improved, but custom programming becomes cumbersome and complex

Engineering Contradiction:
Improvesecurity vulnerabilityVSAvoidcustom programming requirements
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The secrets engine provides a universal interface that handles multiple secret management operations through a standardized mechanism. By creating a general-purpose secrets retrieval system that works across different client programs and secret types, the solution avoids the need for custom programming in each specific case, reducing overall system complexity.

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

Solution Approach 2:

The secrets engine creates a pseudo-filesystem object that mimics the interface of traditional filesystem objects. This copying approach allows existing client programs to interact with secrets through familiar filesystem-like operations without requiring custom programming, while the actual secret management is handled securely by the engine.

Inventive Principle:
Principle #26Copying

3Duration of action of moving object

If secrets are kept in persistent storage, then they are available when needed, but they expose the system to intrusion risks over extended periods

Engineering Contradiction:
Improveavailability duration of secretsVSAvoidexposure time to intrusion
Core Design Contradiction:
Duration of action of moving objectVSObject-affected harmful factors

Solution Approach 1:

Instead of continuous availability through persistent storage, the system implements periodic retrieval of secrets from the secrets store. Secrets are fetched on-demand when read requests occur and are not maintained in persistent local storage. This periodic action pattern reduces exposure time while maintaining availability when needed.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system discards secrets from local storage after retrieval and recovers them from the secrets store only when needed. By continuously discarding local copies and recovering from the secure secrets store on-demand, the system maintains availability duration while minimizing the time secrets are exposed in vulnerable locations.

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS11841961B2Management of computing secrets
Publication Date: 2023.12.12 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11841961B2 patent drawing
  • US11841961B2 patent drawing
  • US11841961B2 patent drawing

AI summary

A method can include receiving a read request from a client program. The method can further include obtaining, in response to receiving the read request, one or more secrets from a secrets store. The obtaining can include storing the one or more secrets in a storage location. The method can further include initiating, in response to the read request, a transmission of the one or more secrets to the client program. The method can further include deleting the one or more secrets from the storage location.