Automated Compliance Exception Approval for Modified System Configurations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern computer systems often deviate from compliance rules due to their complexity and continuous evolution, leading to costly and repetitive manual risk assessments for compliance exception approvals.
Innovation Solution
A method for automated approval of non-compliance in computer systems by using pre-approved modification patterns and compliance exception pre-approvals, which are packaged and digitally signed, allowing for automated comparison and approval of detected non-compliances, reducing the need for manual interventions and repetitive risk assessments.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual compliance exception approval processes are used, then compliance rules are enforced, but the process becomes costly and repetitive
Solution Approach 1:
The patent applies preliminary action by pre-approving modification patterns before they are deployed to systems. Compliance exceptions are anticipated and approved in advance through a formal process, allowing the pre-approved patterns to be automatically applied without triggering repetitive manual approval workflows. This resolves the contradiction by maintaining compliance enforcement while eliminating repetitive approval time losses.
Solution Approach 2:
The patent uses copying by creating reusable pre-approved modification patterns that can be replicated across multiple systems. Once a modification pattern is approved, it can be copied and applied to numerous systems without requiring separate approval processes for each instance. This resolves the contradiction by maintaining compliance enforcement while dramatically reducing approval process time through pattern reuse.
2Adaptability or versatility
If complexity and continuous evolution of computer systems increase, then system functionality improves, but deviations from compliance rules increase
Solution Approach 1:
The patent applies dynamics by making the compliance management system adaptive to system evolution. Modification patterns can be created, approved, and integrated into the system dynamically as needs arise. The system evolves through a structured process where new modification patterns are pre-approved and then automatically applied, allowing the system to adapt to changing functional requirements while maintaining compliance through the pre-approval mechanism.
Solution Approach 2:
The patent applies segmentation by dividing compliance management into separate, manageable components: compliance rules, modification patterns, and approval processes. This segmentation allows each component to be independently managed and updated. Modification patterns are segmented into pre-approved and non-pre-approved categories, enabling systematic handling of compliance deviations while maintaining overall compliance integrity.
3Productivity
If pre-approved modification patterns are used, then manual interventions are reduced, but the need for pre-approval processes increases
Solution Approach 1:
The patent applies preliminary action by establishing a pre-approval process for modification patterns before they are deployed. This upfront approval process creates a library of pre-approved patterns that can be automatically applied without further manual intervention. The pre-approval complexity is paid once, enabling repeated automated deployments without recurring manual intervention, thus resolving the contradiction between productivity improvement and process complexity.
Solution Approach 2:
The patent applies self-service by enabling systems to automatically apply pre-approved modification patterns without requiring manual approval for each deployment. The system serves itself by automatically matching system deviations to pre-approved patterns and applying the appropriate modifications. This eliminates the need for repetitive manual interventions while the pre-approval process manages the complexity of compliance exceptions in advance.
Data Source
AI summary
Automated approval of a non-compliance of a modified configuration of a computer system includes performing a compliance check by a compliance management system. The modified configuration results from deploying a pre-approved modification pattern by a package management system modifying an initial configuration of the computer system. The modification pattern is provided by a software package that specifies at least one modification to be applied to the initial configuration and at least one compliance exception pre-approval specifying pre-approved non-compliances of modifications with compliance rules. Responsive to detecting a non-compliance, the non-compliance is compared with the pre-approved non-compliances. In response to determining that the detected non-compliances are not matching any pre-approved non-compliances, a compliance exception approval is requested. The detected non-compliance is approved in response to receiving the compliance exception approval for the detected non-compliances.