DRM Security for Untrusted Servers via Client-Side Token Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In client-server architectures, digital rights management (DRM) security is compromised when the server is an untrusted entity, as traditional token passing schemes may not be adequate to protect user data and content from hackers with full access to the server.
Innovation Solution
Implementing a three-layer security system, including public key-private key encryption, application secret cryptographic keys with derivation functions, and authentication processes between the trusted client and untrusted server to ensure data and content security, even if the server is penetrated.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional token passing schemes are used for DRM security in client-server architecture, then security verification activity is shifted to the client, but the server remains vulnerable when it is an untrusted entity with full access to content
Solution Approach 1:
The patent segments the DRM security system into distinct functional components: a head end that generates and manages security tokens, a server that distributes content, and a client that verifies tokens and protects content. This segmentation allows the trusted client to perform security verification independently of the untrusted server, preventing server penetration from compromising DRM protection.
Solution Approach 2:
The patent introduces security tokens as an intermediary mechanism between the head end, server, and client. These tokens carry authorization information that enables the client to verify its rights to receive and use content without relying on the server's trustworthiness. The token acts as a mediator that transfers security credentials securely through the untrusted server environment.
2Reliability
If servers are given greater security controls and centralized data storage, then access and resource control is improved, but security breaches can still occur when hackers gain access to the server
Solution Approach 1:
The patent inverts the traditional DRM security model by placing the security verification function on the client side rather than the server side. Instead of the server controlling access through centralized security checks, the client independently verifies its authorization through token validation. This inversion ensures that even if the server is compromised, the client can still protect its content usage rights.
Solution Approach 2:
The client performs self-service security verification by validating its own authorization tokens locally without requiring trust in the server. The client autonomously determines whether it has the right to receive and use specific content based on the token information, eliminating the need for the server to enforce security controls.
3Loss of information
If DRM protection focuses on encrypting content, then content confidentiality is improved, but the weak link in the overall process remains vulnerable to breaking the protection scheme
Solution Approach 1:
The patent implements preliminary security actions by establishing token-based authorization before content transfer occurs. The head end generates and delivers security tokens to the client in advance, containing all necessary authorization information. This preliminary authentication ensures that the client is properly authorized before receiving encrypted content, strengthening the overall DRM process security.
Solution Approach 2:
The patent adds a new dimension to DRM security by introducing token-based authorization as a separate layer from content encryption. Instead of relying solely on encrypting the content, the system adds an authorization dimension through tokens that verify the client's rights. This multi-dimensional approach (encryption + authorization tokens) creates more robust protection against attacks on the DRM process.
Data Source
AI summary
In the context of a computer client-server architecture, typically used in the Internet for communicating between a server and applications running on user computers (clients), a method is provided for enhancing security in the context of digital rights management (DRM) where the server is an untrusted server that may not be secure, but the client is secure. This method operates to authenticate the server to the client and vice versa to defeat hacking attacks intended to obtain confidential information. Values passed between the server and the client include encrypted random numbers, authentication values and other verification data generated using cryptographic techniques including double encryption.