Systems and methods for a governance engine
A governance engine is provided that receives changes identified in dependencies in an enterprise and compares those changes to rule triggers, executing an output of a rule if a trigger is implicated. Related agents may examine the identified changes for new, potentially vulnerable or otherwise disallowed dependencies.
1. A computer-implemented method for enforcing rules governing software in an enterprise, comprising, on a governance asset, executing a governance engine configured to:
receive at least one rule specifying at least one trigger and at least one output;
receive a set of potential vulnerabilities;
receive a set of detected changes in dependencies in an enterprise from a delta agent based on a comparison of subsequent dependency graphs to previous dependency graphs;
examine the set of detected changes for changes that implicate a trigger of a rule;
compare any new dependencies contained in the set of detected changes for nodes identified in the set of potential vulnerabilities, and generate an output identifying any positive results of such comparison; and
if a trigger is implicated by a change, execute the one or more outputs associated with the implicated trigger.
2. The method of claim 1 , wherein the governance engine is further configured to:
receive a set of restricted open source software nodes;
compare any new dependencies contained in the set of detected changes for nodes identified in the set of restricted open source software nodes; and
generate an output identifying any positive results of such comparison.
3. The method of claim 1 , wherein at least one rule includes more than one output and both outputs are executed if a trigger of that rule is implicated.
4. The method of claim 1 , wherein at least one rule specifies more than one trigger and an output of that at least one rule is executed if at least one of said triggers is executed.
5. The method of claim 1 , wherein at least one rule specifies more than one trigger and an output of that at least one rule is executed only if all of said triggers is executed.
6. The method of claim 1 , wherein a trigger of at least one rule identifies a node in a hierarchy with at least one node that is a child of said node, said trigger being configured such that the trigger is implicated if a change is detected in said node or any child of said node.
7. The method of claim 1 , wherein the governance engine is further configured to receive a set of at least one rule from a source outside the enterprise.
8. The method of claim 1 , wherein a trigger of a rule specifies a type of change necessary for an associated output to be executed.
9. A computer-implemented method for enforcing rules governing software in an enterprise, comprising,
executing a delta agent configured to:
receive dependency graphs from a synthesis agent,
compare subsequent dependency graphs to previous dependency graphs to identify any dependency changes in the enterprise, and
output a set of detected changes to a governance engine; and
executing a governance engine configured to:
receive at least one rule specifying at least one trigger and at least one output,
receive a set of potential vulnerabilities,
receive a set of detected changes in dependencies in an enterprise from a delta agent based on an examination of subsequent dependency graphs,
examine the set of detected changes for changes that implicate a trigger of a rule,
compare any new dependencies contained in the set of detected changes for nodes identified in the set of potential vulnerabilities and generate an output identifying any positive results of such comparison; and
if a trigger is implicated by a change, execute the one or more outputs associated with the implicated trigger.
10. A computer-implemented method for enforcing rules governing software in an enterprise, comprising, on a governance asset, executing a governance engine configured to:
receive at least one rule specifying at least one trigger and at least one output;
receive a set of restricted open source software nodes;
receive a set of detected changes in dependencies in an enterprise from a delta agent based on a comparison of subsequent dependency graphs to previous dependency graphs;
examine the set of detected changes for changes that implicate a trigger of a rule;
compare any new dependencies contained in the set of detected changes for nodes identified in the set of restricted open source software nodes, and generate an output identifying any positive results of such comparison; and
if a trigger is implicated by a change, execute the one or more outputs associated with the implicated trigger.
11. The method of claim 10 , wherein at least one rule includes more than one output and both outputs are executed if a trigger of that rule is implicated.
12. The method of claim 10 , wherein at least one rule specifies more than one trigger and an output of that at least one rule is executed if at least one of said triggers is executed.
13. The method of claim 10 , wherein at least one rule specifies more than one trigger and an output of that at least one rule is executed only if all of said triggers is executed.
14. The method of claim 10 , wherein a trigger of at least one rule identifies a node in a hierarchy with at least one node that is a child of said node, said trigger being configured such that the trigger is implicated if a change is detected in said node or any child of said node.
15. The method of claim 10 , wherein the governance engine is further configured to receive a set of at least one rule from a source outside the enterprise.
16. The method of claim 10 , wherein a trigger of a rule specifies a type of change necessary for an associated output to be executed.
17. A computer-implemented method for enforcing rules governing software in an enterprise, comprising,
executing a delta agent configured to:
receive dependency graphs from a synthesis agent,
compare subsequent dependency graphs to previous dependency graphs to identify any dependency changes in the enterprise, and
output a set of detected changes to a governance engine; and
executing a governance engine configured to:
receive at least one rule specifying at least one trigger and at least one output,
receive a set of restricted open source software nodes,
receive a set of detected changes in dependencies in an enterprise from a delta agent based on an examination of subsequent dependency graphs,
examine the set of detected changes for changes that implicate a trigger of a rule,
compare any new dependencies contained in the set of detected changes for nodes identified in the set of restricted open source software nodes, and generate an output identifying any positive results of such comparison, and
if a trigger is implicated by a change, execute the one or more outputs associated with the implicated trigger.