Remote Key Management for Revocable Data Encryption

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data security solutions in corporate IT environments fail to adequately restrict access to encrypted data once an employee has possession of the host and mass storage, as they rely on the operating system for encryption and decryption, allowing unauthorized access if the employee retains the password.

Innovation Solution

Implementing a system where a remote authority manages encryption keys, allowing data to be encrypted and decrypted independently of the operating system, with periodic key revocation to prevent unauthorized access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the operating system encrypts data using a key generated by the operating system, then data security is improved, but the ability to revoke access is worsened because the employee still has possession of the host and mass storage

Engineering Contradiction:
Improvedata securityVSAvoidaccess restriction capability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The encryption key is extracted from the operating system and stored in a separate, secure location on the mass storage device. This allows the key to be independent of the OS, enabling revocation of access even when the employee possesses the host and storage device.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

A key management system acts as an intermediary between the operating system and the encryption key. This intermediary controls the distribution and revocation of keys, allowing the system to revoke access without requiring physical control of the storage device.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If the operating system manages encryption keys, then ease of operation is improved, but data security is worsened because the employee can continue to access data after authorization is revoked

Engineering Contradiction:
Improveencryption managementVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The key management function is extracted from the operating system and placed in a dedicated key management system. This separation allows the OS to remain simple for the user while the key management system provides secure, revocable access control.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system is segmented into distinct functional components: the operating system for user interaction, the key management system for key distribution, and the mass storage for data and key storage. This segmentation allows each component to be optimized independently for its specific function.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9135470B2Data security
Publication Date: 2015.09.15 INTEL CORP
  • US9135470B2 patent drawing
  • US9135470B2 patent drawing
  • US9135470B2 patent drawing

AI summary

In one embodiment, a method is provided that may include one or more operations. One of these operations may include, in response, at least in part, to a request to store input data in storage, encrypting, based least in part upon one or more keys, the input data to generate output data to store in the storage. The one or more keys may be authorized by a remote authority. Alternatively or additionally, another of these operations may include, in response, at least in part, to a request to retrieve the input data from the storage, decrypting, based at least in part upon the at least one key, the output data. Many modifications, variations, and alternatives are possible without departing from this embodiment.