System and method for detecting and preventing changes in business-critical applications that modify its state to non-secure and/or non-compliant

1. A system comprising:

a processor and a memory configured to store non-transitory instructions, that when executed by the processor:

receive a compliant state of a computer software configuration;

analyze the compliant state to confirm that the compliant state is compliant;

monitor a state of the computer software configuration in real time;

detect, based on the monitoring, a proposed change of the computer software configuration, wherein the proposed change causes a changed state, which is a change to the state of the computer software configuration;

compare the compliant state and the changed state to determine whether the changed state results in a non-compliant state that conflicts with the compliant state;

when the changed state conflicts with the compliant state based on the comparing, stop the proposed change and require further approval in order for the proposed change to be implemented; and

when the changed state does not conflict with the compliant state based on the comparing, apply the proposed change.

2. The system of claim 1 , wherein the processor is further configured to receive a comment describing a reason for the proposed change.

3. The system of claim 1 , wherein the processor is further configured to receive the approval for the proposed change from a user.

4. The system of claim 1 , wherein the processor is further configured to generate an alert or a block to the proposed change if the changed state conflicts with the compliant state.

5. The system of claim 1 , wherein the processor is further configured to receive a configuration policy comprising a configuration scenario.

6. The system of claim 5 , wherein the configuration scenario includes at least one of a password policy configuration, an audit log configuration, a file access definition, a system type definition, an interface security configuration, and a service access control list definition.

7. The system of claim 5 , wherein the configuration scenario has a predetermined value and an action corresponding to the predetermined value.

8. The system of claim 5 , further comprising the step of assigning a priority to the one or more configuration policies.

9. The system of claim 1 , wherein the processor is further configured to detect a change in a configuration scenario based on the monitoring, the change generating a change information analyzed by a policy enforcer, wherein the change information includes the configuration scenario, an old state, and a new state.

10. The system of claim 9 , wherein the processor is further configured to compare the new state with the old state, wherein based on the comparison, the policy enforcer sends at least one of a pass signal, an alert signal, a block signal, an approval signal, a deny signal, and an allow signal to a change detector configured to detect the change.

11. A computer implemented method comprising the steps of:

receiving an old state of a computer software configuration;

determining whether the old state is a compliant state;

monitoring, upon determining that the old state is a compliant state, a state of the computer software configuration in real time;

detecting, based on the monitoring, a proposed change of the computer software configuration, wherein the proposed change causes a new state of the computer software configuration;

comparing the old state when it is determined to be a compliant state with the new state to determine whether the new state is also compliant;

stopping, when the new state conflicts with the old state, the proposed change and require further approval in order for the proposed change to be implemented; and

applying the proposed change when, based on the comparing, the new state does not conflict with the old state.

12. The method of claim 11 , further comprising the step of receiving a comment describing a reason for the proposed change as part of the further approval.

13. The method of claim 11 , further comprising the step of receiving the further approval from a user for the proposed change.

14. The method of claim 11 , further comprising the step of generating an alert or a block to the change if the changed state conflicts with the old state.

15. The method of claim 11 , further comprising the step of receiving a configuration policy comprising a configuration scenario.

16. The method of claim 15 , wherein the configuration scenario includes at least one of the group consisting of a password policy configuration, an audit log configuration, a file access definition, a system type definition, an interface security configuration, and a service access control list definition.

17. The method of claim 15 , wherein each of the configuration scenarios has a predetermined value and an action corresponding to the predetermined value.

18. The method of claim 15 , wherein a user defines a priority to the configuration policy.

19. A computer implemented method comprising the steps of:

determining whether an old state for a computer software configuration scenario is compliant by monitoring the computer software configuration scenario;

detecting a change in the computer software configuration scenario based on the monitoring;

generating a change information comprising the computer software configuration scenario, the old state, and a new state of the computer software configuration scenario;

comparing the new state with the old state;

sending, based on the comparison, a pass signal when the new state is compliant, wherein the change is applied;

sending, based on the comparison, an alert signal when the new state is conflicting with the old state; and

sending, based on the comparison, an approval signal when the new state is conflicting with the old state, wherein the approval signal requires a user approval in order for the change to be applied, further wherein a deny signal is sent when the user does not approve.