Secure Server Content Management Object Handling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for handling content management objects lack robust security, as they are conditionally secure when stored locally on terminal devices and can be compromised in replay attacks where memory images are copied across devices.

Innovation Solution

A method involving the transfer of encrypted content management objects from a secure server to a terminal, where they are decrypted, modified, and then re-encrypted before being returned to the server, utilizing secure channels and secure environments to enhance security, with optional caching and mutual authentication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If content management objects are stored locally on terminal devices in a secure environment, then accessibility and operation speed are improved, but security is worsened due to vulnerability to replay attacks where memory images can be copied across devices

Engineering Contradiction:
Improveaccess speedVSAvoidsecurity
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent introduces a secure server as an intermediary between terminal devices and content management objects. The server acts as a trusted mediator that stores the master copy of content management objects and provides authenticated access to terminals. This resolves the contradiction by maintaining local cached copies for fast access while ensuring that the authoritative copy remains on the secure server, preventing replay attacks.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary authentication and encryption actions before local storage. Content management objects are authenticated and encrypted on the secure server before being cached locally on terminal devices. This preliminary security processing ensures that even if local copies are compromised, the attacker cannot create valid replay attacks without the server's authentication.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If content management objects are stored locally on terminal devices, then operational independence is improved, but security is worsened as objects could be reused without restriction on any number of end devices in the event of an attack

Engineering Contradiction:
Improveoperational independenceVSAvoidsecurity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements dynamic validation where content management objects cached locally on terminal devices must be validated against the secure server before use. This dynamic check ensures that even if multiple terminals have cached copies, each terminal must independently validate its copy with the server, preventing unauthorized reuse across devices while maintaining operational independence.

Inventive Principle:
Principle #15Dynamics

3Ease of operation

If content management objects are transmitted and stored on terminal devices, then functionality is improved, but storage space requirements increase

Engineering Contradiction:
ImprovefunctionalityVSAvoidstorage space
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent implements partial storage where only essential content management objects are cached locally on terminal devices, while the complete set remains on the secure server. Terminals store only the subset of objects needed for current operations, reducing local storage requirements while maintaining full functionality through on-demand retrieval from the server.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentEP2851826B1Method for handling content management objects
Publication Date: 2019.07.10 GIESECKE & DEVRIENT EPAYMENTS GMBH
  • EP2851826B1 patent drawingFigure 1~2

AI summary

The present invention relates to a method for handling content management objects (14). In this method, a content management object (14) is transferred from a server (12) to an end device (10), decrypted there, modified, re-encrypted, and transferred back to the server (12). Thus, content management objects are only briefly present on the end device during the modification process and are subsequently transferred to a secure server. The current data is stored on a secure server at all times and protected against attacks and corruption. Additionally, the method allows and supports the storage of local copies as a technical optimization.