Secure Electronic Document Storage with Encrypted Search Indexing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems for storing electronic documents are inefficient due to large archive sizes overwhelming computer resources, risks of unauthorized access or modification by third-party storage providers, and difficulties in implementing document retention policies, especially when the third party is not trusted.

Innovation Solution

A system comprising a client and server portion, where the client encrypts documents and identifies terms of interest, which are then transferred to a server for secure storage and indexing, allowing for searchable retrieval without decrypting the entire archive, and includes features for document retention and destruction policies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If documents are stored in a third-party archive, then storage capacity and resource processing are improved, but security and trust are worsened

Engineering Contradiction:
Improvestorage capacityVSAvoidsecurity
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces an intermediary encryption layer between the client and third-party storage. The client encrypts documents before storage, and provides decryption keys only when retrieval is needed, acting as a mediator that enables both third-party storage capability and client security control.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system segments the document storage function into two parts: unencrypted storage at the third-party location and encrypted retrieval at the client location. This segmentation allows the third party to store documents without accessing their contents, while the client maintains security through encryption.

Inventive Principle:
Principle #1Segmentation

2Reliability

If documents are encrypted before storage at third party, then security is improved, but searchability and retrieval efficiency are worsened

Engineering Contradiction:
ImprovesecurityVSAvoidsearchability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The client performs preliminary encryption of documents before they are stored at the third party location. This preliminary action ensures that the third party never sees unencrypted documents, maintaining security while enabling efficient encrypted search and retrieval operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system creates encrypted copies of documents for storage at the third party location, while maintaining the ability to retrieve and decrypt specific copies when needed. This copying approach allows secure storage without permanent loss of access capability.

Inventive Principle:
Principle #26Copying

3Reliability

If entire encrypted archive is returned for search, then security is maintained, but processing time and computational burden are worsened

Engineering Contradiction:
ImprovesecurityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Instead of returning the entire encrypted archive for search, the system extracts and returns only the specific encrypted documents that match the search criteria. This extraction approach reduces the amount of data that needs to be processed while maintaining security through encryption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system performs partial action by retrieving only the necessary encrypted documents for the search query rather than the entire archive. This partial retrieval reduces computational burden and processing time while maintaining security through encryption.

Inventive Principle:
Principle #16Partial or excessive action

4Reliability

If third party provides archive for evidentiary purposes, then provenance can be established, but complexity of verification and decryption is worsened

Engineering Contradiction:
ImproveprovenanceVSAvoidverification complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The client acts as an intermediary that manages the encryption keys and decryption process. When evidentiary purposes require verification, the client provides the necessary decryption keys and performs the decryption locally, simplifying the verification process while maintaining security.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables self-service verification where the client can independently verify the provenance of documents by providing decryption keys and performing local decryption. This eliminates the need for complex third-party verification processes while maintaining evidentiary integrity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7512814B2Secure and searchable storage system and method
Publication Date: 2009.03.31 PROOFPOINT INC
  • US7512814B2 patent drawing
  • US7512814B2 patent drawing
  • US7512814B2 patent drawing

AI summary

A system and method for securely storing electronic documents is provided. The system includes a client portion and a server portion and the client portion is located at a trusted location. The client portion encrypts each electronic document and produces a list of terms of interest relating to the document, which terms are also encrypted. The encrypted document and the encrypted terms are transferred to a server portion which need not be located at a trusted location. The document is stored at the server portion in a manner which allows for locating the document again via the encrypted terms and returning the encrypted document to the trusted client portion, where it can be decrypted. Attachments to documents can also be encrypted and stored at the server, as can copies of dynamic documents, such as web pages. The server portion can also have a retention manager and encryptor which is used to implement document retention and destruction policies defined by the user of the system.