Short-Lived Program Compliance Scanning Before Deletion
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing compliance scanning systems fail to detect short-lived programs that execute non-compliant operations and are deleted before a scheduled scan, leading to potential non-compliance issues.
Innovation Solution
Implement a compliance operator that tracks short-lived programs and performs a partial compliance scan using a tailored subset of assessment rules relevant to their behavioral attributes before deletion, ensuring some level of compliance testing is conducted.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a scheduled compliance scan is performed, then compliance assessment is maintained, but short-lived programs that execute and delete before the scan are not detected
Solution Approach 1:
The compliance operator performs preliminary actions by monitoring program modules before they are deleted. When a program module is detected to be short-lived (executing for less than a threshold time), the operator initiates a compliance scan on that specific program before it terminates, ensuring no compliance issues are missed due to the program's short lifespan.
2Reliability
If a full compliance scan is performed on all programs, then comprehensive compliance assessment is achieved, but system performance is impacted
Solution Approach 1:
The compliance operator applies local quality by tailoring the compliance scan to the specific characteristics of each program module. Instead of uniformly scanning all programs, the operator identifies short-lived programs (those executing for less than a threshold time) and applies a focused compliance assessment only to those, rather than scanning all programs regardless of their lifespan.
Solution Approach 2:
The compliance operator performs partial action by conducting compliance scans only on a subset of programs - specifically those identified as short-lived. This partial scanning approach ensures that compliance assessment is performed on the most critical programs while avoiding the performance impact of scanning all programs, including long-lived ones that may not require immediate attention.
3Reliability
If compliance scanning is performed on all programs, then all compliance issues are detected, but the time required for scanning increases
Solution Approach 1:
The compliance operator applies local quality by focusing the compliance scan on specific program modules with short lifetimes. The operator monitors program execution times and identifies those that complete before a threshold duration, then performs compliance assessment only on those short-lived programs, rather than scanning all programs regardless of their execution duration.
Solution Approach 2:
The compliance operator performs partial action by scanning only a subset of programs - specifically those identified as short-lived through monitoring. This reduces the overall scan execution time compared to scanning all programs, while still maintaining compliance detection coverage for the most critical short-lived programs that could execute non-compliant operations.
Data Source
AI summary
Provided are a computer program product, system, and method for detecting potentially non-compliant short-lived assets in a computing platform. In response to a command to delete a program module, a determination is made as to whether the program module has a life less than a predetermined time. A determination is made of a subset of assessment rules from at least one compliance profile to execute in response to determining that the life of the program module is less than the predetermined time. The subset of assessment rules is executed in the computational platform to determine the program module compliance with the subset of assessment rules. Compliance results of the program module compliance with the subset of assessment rules are saved.