Dynamic Security Objects for Immediate Key Availability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional cryptographic key management systems are inefficient in ensuring immediate availability of new keys across all domain controllers due to non-atomic repository replication, leading to potential data unavailability and security vulnerabilities.

Innovation Solution

A method and system for dynamically updating software security objects, such as cryptographic keys, by determining the client's domain of operation and generating keys that conform to current standards and rulesets, ensuring immediate compliance and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a new cryptographic key is stored in a distributed key repository, then key availability to some domain controllers is improved, but key availability to all domain controllers is delayed due to non-atomic replication

Engineering Contradiction:
Improvekey availabilityVSAvoidkey replication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by creating a new cryptographic key and immediately distributing it to all domain controllers before the key is needed for data protection. The system proactively manages key distribution rather than passively waiting for replication, ensuring keys are available when needed without delays from traditional replication processes.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements dynamic key management where keys can be created, distributed, and activated at any point in time rather than following a fixed replication cycle. The system dynamically adjusts key availability based on real-time needs, allowing immediate key distribution to all domain controllers regardless of replication schedules.

Inventive Principle:
Principle #15Dynamics

2Ease of manufacture

If cryptographic keys are managed using traditional key lifecycle management, then key creation and retirement are simplified, but compliance with evolving security standards is compromised

Engineering Contradiction:
Improvekey management simplicityVSAvoidstandard compliance
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements feedback mechanisms that continuously monitor security standards and key usage patterns. The system receives feedback about evolving security requirements and automatically adjusts key management practices to maintain compliance while preserving operational simplicity through automated standard updates.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent applies parameter changes by automatically updating key characteristics such as length, algorithm type, and format based on evolving security standards. The system modifies key parameters dynamically to meet new compliance requirements without manual intervention, maintaining both simplicity and adaptability.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If data is stored in highly available cloud storage independent of the key repository, then data accessibility is improved, but data availability is reduced when new keys are being replicated

Engineering Contradiction:
Improvedata accessibilityVSAvoiddata availability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies preliminary action by creating and distributing new cryptographic keys to all domain controllers before they are needed for accessing data in cloud storage. This ensures that when data needs to be accessed, the necessary keys are already available locally at all domain controllers, eliminating availability issues during key replication.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent ensures continuity of useful action by maintaining continuous key distribution and validation processes. The system continuously manages key lifecycle operations to ensure uninterrupted data accessibility, preventing any downtime or unavailability periods even when cloud storage is involved.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS20260019251A1Dynamic software security objects
Publication Date: 2026.01.15 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US20260019251A1 patent drawing
  • US20260019251A1 patent drawing
  • US20260019251A1 patent drawing

AI summary

A computer-implemented method (CIM), according to one approach, includes determining a first domain of operation associated with a first client, and creating a software security object that satisfies a current standard and/or ruleset associated with the first domain. The method further includes distributing the software security object to the first client, and in response to a determination that the current standard and/or ruleset has been updated, causing the software security object to be updated to conform to the updated standard and/or ruleset. A computer program product (CPP), according to another approach, includes a set of one or more computer-readable storage media, and program instructions, collectively stored in the set of one or more storage media, for causing a processor set to perform any combination of features of the foregoing methodology.