Systems and methods for a governance engine
AssigneeCodeLogic, Inc.
InventorSoumik Sarkar
Life of this patent
Estimating the term…
Abstract
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.
Claims17
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.
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.
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.
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.
Dependencies are inferred from the claim text.