Software Container Identity Detection via Template Metadata Analysis
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Effective software asset management in software container-based cloud systems is challenging due to the sealed nature of software containers, which makes it difficult to determine software presence and usage without disrupting high-workload environments and requires expensive file-system scans that may not be feasible.
Innovation Solution
A method and system that utilize software container engines to create templates for each software container, storing metadata about installed software, allowing for the identification of software content by analyzing template metadata rather than conducting file-system scans, thereby reducing resource usage and avoiding workload disruptions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If file-system scans are conducted to determine software presence in containers, then software identity determination accuracy is improved, but system performance deteriorates and workload disruptions occur
Solution Approach 1:
The patent applies preliminary action by scanning and determining software identities within container images before they are instantiated and deployed to production environments. This allows software asset management information to be captured in advance, avoiding the need for disruptive scans of running containers. The software presence is identified in the static image phase, and this information is stored for later retrieval, thus preventing performance degradation during runtime operations.
2Measurement precision
If file-system scans are conducted to determine software presence in containers, then software identity determination accuracy is improved, but resource consumption increases
Solution Approach 1:
The patent performs software scanning and identity determination during the container image build phase, before the container is deployed. This preliminary action captures all software asset information in advance, eliminating the need for resource-intensive scans during container runtime. The scanning process occurs when the container is not yet consuming production resources, thus avoiding increased energy and computing resource consumption during operational phases.
3Reliability
If software containers are sealed to ensure security, then security is improved, but software asset management becomes difficult
Solution Approach 1:
The patent leverages the sealed nature of container images by performing software asset management operations during the image build phase, before the container is deployed. During this phase, the image is accessible for scanning and analysis. Once the software inventory is captured and stored, the container can be deployed in its sealed, secure state without compromising asset management capabilities. The preliminary capture of asset information bypasses the security constraint imposed by sealed containers during runtime.
Data Source
AI summary
One or more processors scan a first software container template for one or more identities of software present on a first software container associated with the first software container template. One or more processors generate a map of the one or more identities of software present on the first software container. The one or more identities of software present on the first software container are mapped with one or both of: an identifier of the first software container template and an identifier of the first software container associated with the first software container template.


