Multilayered Security for Configuration Items

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional approaches to protecting computing systems from malicious manipulation of configuration files are either reactive, expose the system to providers, or provide only a single level of security, making them inadequate for ensuring robust protection against unauthorized changes or attacks.

Innovation Solution

Implementing a multilayered security system that logically isolates protected systems from configuration item providers using asymmetric keys for source identity and content integrity verification, with just-in-time checking and dual protection logics to shield sensitive information from suppliers, ensuring additional security layers beyond conventional systems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional security approaches (digital signatures, provider restrictions, periodic snapshots) are used to protect configuration files, then some level of security is provided, but the system remains exposed to providers and only achieves a single level of security

Engineering Contradiction:
Improvesecurity protection levelVSAvoidsecurity layer structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the security verification process into multiple independent layers: first-layer verification checks digital signatures and provider authentication, while second-layer verification performs additional integrity checks using different cryptographic keys. This segmentation allows each layer to focus on specific security aspects, achieving comprehensive protection without requiring a single complex security mechanism

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediate verification layer between the configuration file provider and the target system. This intermediary performs dual-verification of configuration files, acting as a security buffer that prevents direct exposure of the target system to untrusted providers while maintaining the configuration delivery chain

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If configuration files are digitally signed and verified to ensure integrity, then source identity and content integrity can be confirmed, but the verification process may delay system operation

Engineering Contradiction:
Improveconfiguration file integrity verificationVSAvoidverification processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs security verification in advance before the configuration files are executed or applied to the system. By conducting dual-layer verification beforehand, the system ensures that only authenticated and intact configuration files proceed to the execution stage, preventing security issues from arising during system operation

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements efficient verification mechanisms that quickly validate configuration files through streamlined cryptographic checks. The verification process is optimized to minimize processing time by using pre-computed hash values and efficient signature verification algorithms, allowing rapid security validation without significant operational delays

Inventive Principle:
Principle #21Skipping (Rushing through)

3Adaptability or versatility

If configuration files are made accessible to providers for editing, then configuration flexibility is improved, but the files become vulnerable to malicious manipulation

Engineering Contradiction:
Improveconfiguration file editabilityVSAvoidmalicious manipulation risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent converts the potential harm of provider accessibility into a benefit by using the same provider-accessible configuration files as the basis for cryptographic signing. The files that providers can edit become the very objects that demonstrate integrity through digital signatures, turning the accessibility vulnerability into a verifiable trust mechanism

Inventive Principle:
Principle #22Blessing in disguise (Convert harm into benefit)

Solution Approach 2:

The patent applies preliminary cryptographic signing and hashing to configuration files before they are distributed to providers or executed by the system. This pre-protection measures ensures that any subsequent malicious manipulation by providers can be detected through verification failures, preventing harmful changes from taking effect

Inventive Principle:
Principle #9Preliminary anti-action

Data Source

PatentUS7958346B2Multilayered security for systems interacting with configuration items
Publication Date: 2011.06.07 ORACLE INT CORP
  • US7958346B2 patent drawing
  • US7958346B2 patent drawing
  • US7958346B2 patent drawing

AI summary

Systems, methodologies, and other embodiments associated with providing multi-layered security for configuration items are described. One exemplary system may include a security logic configured to process the contents of a configuration item based on the source of the configuration item and the integrity of the configuration item. The exemplary system may also include a verification logic configured to further process the contents and to selectively provide the contents. A configuration item may be provided to the security logic by a configuration item provider known to the security logic and related to the security logic by a first set of keys. The security logic may be related to the verification logic by a second set of keys different from the first set of keys.