Content Management System Integrity Hash Injection for CDN Assets
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current techniques for securing content from compromised content delivery networks (CDNs) require multiple steps and custom code, making it difficult for content authors using content management systems like Adobe Experience Manager to implement integrity checks for content assets hosted on third-party servers, especially in WYSIWYG interfaces where altering HTML is not feasible.
Innovation Solution
A system and method that automatically detects content assets hosted on third-party servers within a content management system, generates an integrity check hash value, and injects this verification into the HTML, allowing for secure content delivery without manual hash regeneration or complex custom code.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If current techniques for securing CDN content are used, then content integrity can be verified, but the implementation requires multiple steps and custom code making it difficult for content authors
Solution Approach 1:
The system automatically detects third-party content assets, generates integrity hash values, and injects verification code into HTML without requiring manual intervention from content authors. The content management system performs these security functions autonomously, transforming a complex manual process into an automated self-service operation.
Solution Approach 2:
The integrity hash value is generated and embedded in the HTML code during the content authoring process, before the content is published or served. This preliminary generation of security verification data eliminates the need for subsequent manual steps and ensures integrity checks are already in place when content is delivered.
2Reliability
If manual hash generation and HTML modification is required, then integrity checks can be implemented, but it is not feasible in WYSIWYG interfaces where altering HTML is not allowed
Solution Approach 1:
The content management system acts as an intermediary between the content author and the final HTML output. It allows authors to work in the familiar WYSIWYG interface without directly modifying HTML, while automatically inserting the necessary integrity verification code into the generated HTML in the background.
Solution Approach 2:
The manual mechanical process of editing HTML code is replaced with an automated system that generates and injects integrity verification code programmatically. This substitution allows integrity checks to be implemented without requiring direct HTML manipulation by the content author.
3Reliability
If custom code is used for integrity verification, then security can be enforced, but the process becomes complex and time-consuming
Solution Approach 1:
The system automatically generates the integrity hash value and injects the verification code into the HTML without requiring content authors to write or manage custom security code. This automation eliminates the time-consuming manual process of creating and maintaining security verification mechanisms.
Solution Approach 2:
The integrity verification code is generated and embedded during the content creation process, before publishing. This preliminary generation eliminates the need for subsequent code implementation steps, reducing overall implementation time while maintaining security enforcement.
Data Source
AI summary
Techniques for automatically generating an integrity check hash value for a content asset served by a third-party server when the content asset is added to a template in a user interface. The techniques include displaying, by the user interface, a visual layout of web content, the UI configured to receive modifications to a component of the web content. The component comprising a template for generating hypertext markup language (HTML) embodying the component. The techniques further include receiving a modification to the component of the web content, wherein the modification includes instructions to include a content asset in the component of the web content and detecting that the content asset is hosted on a third-party server. Additionally, the techniques include generating HTML for the web content, the HTML including an integrity hash value for the content asset based on the template.