JSON Message Encryption Syntax for Data Confidentiality
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
JSON messages lack confidentiality protection, relying solely on transport security which can be compromised by malicious or accidental alterations during transmission.
Innovation Solution
Implementing a JSON encryption syntax with processing rules to encrypt data items in JSON messages, using a machine-implemented method that generates a cipher value and constructs a data object with encryption method, key, and encrypted key information, allowing for platform-independent encryption of JSON objects, arrays, or strings.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If transport security (SSL) is used to secure JSON messages, then point-to-point message security is provided, but data confidentiality protection is insufficient and data can be compromised through malicious or accidental alterations
Solution Approach 1:
The patent applies segmentation by dividing the security protection into two distinct layers: transport layer security (SSL/TLS) for point-to-point communication protection, and application layer JSON encryption for data confidentiality protection. This segmentation allows each layer to address specific security concerns independently, with JSON encryption providing additional data-level protection against malicious or accidental alterations that transport security alone cannot prevent.
Solution Approach 2:
The patent implements nesting by embedding encrypted JSON data objects within the existing JSON message structure. The encryption syntax is nested within the JSON format itself, with encrypted data represented as specialized JSON objects containing ciphertext and decryption information. This nested approach integrates security functionality into the data structure without requiring complete structural redesign.
2Reliability
If JSON encryption syntax and processing rules are implemented, then end-to-end data confidentiality protection is achieved, but device complexity increases
Solution Approach 1:
The patent applies universality by designing a JSON encryption syntax that can encrypt various JSON data types (objects, arrays, strings) and handle different encryption scenarios (field-level, record-level, message-level). The same encryption framework provides consistent protection across different data structures, reducing the need for multiple specialized solutions and simplifying implementation despite the enhanced security capabilities.
Solution Approach 2:
The patent utilizes parameter changes by allowing flexible configuration of encryption parameters within the JSON structure, including encryption algorithms, keys, modes, and data types. The system can adapt encryption parameters based on the specific data being encrypted and the security requirements, enabling end-to-end confidentiality protection while managing complexity through parameterized rather than fixed approaches.
Data Source
AI summary
The confidentiality of JavaScript Object Notation (JSON) message data is secured using an encryption scheme. The encryption scheme implements a JSON encryption syntax, together with a set of processing rules for creating encrypting arbitrary data in JSON messages in a platform/language independent manner. A method for encrypting a data item in a JSON message begins by applying an encryption method and a key to the data item to generate a cipher value. A data object is then constructed that represents an encryption of the data item. The data item in the JSON message is then replaced with the data object, and the resulting modified JSON message is then output from a sending entity. At a receiving entity, information in the data object is used to re-generate the data item, which is then placed back in the original message.