Systems and methods for remediation of software configuration

#The present disclosure relates to systems and methods for remediation of software configurations, more particularly for identifying a software compliance error based on trigger data, and remediating the software compliance error by applying an existing configuration policy or generating a new configuration policy based at least in part on an existing configuration policy.

#Cloud computing has improved how businesses can implement complicated software packages that provide services to their customers. However, cloud computing has also made it more complicated for businesses to ensure that software instances being implemented in a cloud computing environment are complying in configuration policies that are required for regulatory compliance, legal compliance, and internal policy compliance. Software instances are initialized on the cloud computing service based on complicated configuration policies stored in configuration files. Currently, it is difficult to quickly and efficiently ensure software instances operating on an existing cloud service software are compliant with all necessary policies due to the difficulty in automating the maintenance of stored configuration files to ensure that cloud computing instances comply with the required policies when initialized based on the stored configuration files.

#Accordingly, there is a need for systems and methods to identify an out of compliance software instance based on trigger data, identify an associated configuration file, and automatically remediate a compliance error based on generating and applying configuration policies to the software configuration file associated with the out of compliance software instance. Embodiments of the present disclosure are directed to this and other considerations.

#Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and which are incorporated into and constitute a portion of this disclosure, illustrate various implementations and aspects of the disclosed technology and, together with the description, serve to explain the principles of the disclosed technology. In the drawings:

#FIG. 1 is a diagram of an example system environment that may be used to implement one or more embodiments of the present disclosure;

#FIG. 2 is a component diagram of a compliance remediation system according to an example embodiment;

#Some implementations of the disclosed technology will be described more fully with reference to the accompanying drawings. This disclosed technology may, however, be embodied in many different forms and should not be construed as limited to the implementations set forth herein. The components described hereinafter as making up various elements of the disclosed technology are intended to be illustrative and not restrictive. Many suitable components that would perform the same or similar functions as components described herein are intended to be embraced within the scope of the disclosed electronic devices and methods. Such other components not described herein may include, but are not limited to, for example, components developed after development of the disclosed technology.

#The systems and methods described herein are necessarily rooted in computer technology as they relate to improving the functioning of computer software configuration systems. For example, the systems and methods may determine whether received trigger data indicates a software compliance error that can be remediated using an existing configuration policy. When the trigger data indicates a software compliance error that can be remediated using an existing software policy, the system can update the software configuration file associated with the out of compliance software instance. However, when the trigger data indicates a software compliance error that cannot be remediated using an existing software policy, the system may generate a new configuration policy, thereby avoiding the use of excess computing processing power and network traffic volume by limiting the generation of new configuration policies to those cases when a pre-existing software configuration policy cannot remediate the software compliance error.

#It is also to be understood that the mention of one or more method steps does not preclude the presence of additional method steps or intervening method steps between those steps expressly identified. Similarly, it is also to be understood that the mention of one or more components in a device or system does not preclude the presence of additional components or intervening components between those components expressly identified.