Graph-based deployment tool
A computer implemented method is described for validation of a service. A graph data structure is statically analyzed beginning prior to deployment of the service and continues after deployment. The method uses the static analysis to determine that a build exposing the service deviates from a pre-declared whitelist of dependencies. The method rejects insertion of the build into the graph data structure responsive to the determination in accord with a deny-by-default security posture.
1. A computer-implemented method for validating deployment of a service, the method comprising:
performing a static analysis of a graph data structure to validate an item node with respect to a build that exposes the service, wherein the performance of the static analysis begins before deployment insertion of the item node into the graph data structure and deployment of the service to any device, and wherein the static analysis continues into deployment;
determining, via the static analysis, that the build that exposes the service deviates from a pre-declared listing of allowed of one or more dependencies; and
rejecting, responsive to the determination, the deployment of the service after the deployment is inserted into the graph data structure to enforce, at least in part, a default security policy to deny deviations from pre-declared execution parameters.
2. The computer-implemented method of claim 1 , wherein the pre-declared listing includes an immutable whitelist after declaration of the dependencies.
3. The computer-implemented method of claim 1 , wherein determining that the build that exposes the service deviates from the pre-declared listing includes refencing one or more vending cryptographic service identities.
4. The computer-implemented method of claim 3 , wherein the one or more vending cryptographic service identities include vending cryptographic service identities that are tied back to one or more nodes the graph data structure.
5. The computer-implemented method of claim 1 , wherein deployment of the service includes deploying the service using a sidecar model to deploy the service into a separate process from the static analysis to provide process isolation from security enforcement.
6. The computer-implemented method of claim 1 , wherein the performing of the static analysis is responsive to an auto-provisioning of out-of-processing monitoring for deployment of the service.
7. The computer-implemented method of claim 1 , wherein insertion of the deployment into the graph data structure includes associating the item node to a catalog data structure using a mutual transport layer security compliant component communication.
8. A system for validation of a deployment of a service, the system including:
memory; and
a processor in data communication with the memory, the processor configured to execute:
first logic stored on the memory, the first logic configured to perform a static analysis of a graph data structure to validate an item node with respect to a build that exposes the service, wherein the performance of the static analysis begins before deployment insertion of the item node into the graph data structure and deployment of the service to any device, and wherein the static analysis continues into deployment;
second logic stored on the memory, the second logic configured to determine, via the static analysis, that the build that exposes the service deviates from a pre-declared whitelist of one or more dependencies; and
third logic stored on the memory, the third logic configured to reject, responsive to the determination, the deployment of the service after the deployment is inserted into the graph data structure to enforce, at least in part, a default security policy to deny deviations from pre-declared execution parameters.
9. The system of claim 8 , wherein the pre-declared whitelist includes an immutable whitelist after declaration of the dependencies.
10. The system of claim 8 , wherein the second logic is configured to determine that the build that exposes the service deviates from the pre-declared whitelist by refencing one or more vending cryptographic service identities.
11. The system of claim 10 , wherein the one or more vending cryptographic service identities include vending cryptographic service identities that are tied back to one or more nodes the graph data structure.
12. The system of claim 8 , wherein the deployment of the service includes a deployment the service using a sidecar model to deploy the service into a separate process from the static analysis to provide process isolation from security enforcement.
13. The system of claim 8 , wherein the first logic is configured to perform the static analysis responsive to an auto-provisioning of out-of-processing monitoring for deployment of the service.
14. The system of claim 8 , wherein the insertion of the deployment into the graph data structure includes an association the item node to a catalog data structure using a mutual transport layer security compliant component communication.
15. A product including:
non-transitory machine-readable media; and
instructions stored on the machine-readable media, the instructions configured to, when executed, cause a machine to:
perform a static analysis of a graph data structure to validate an item node with respect to a build that exposes a service, wherein the performance of the static analysis begins before deployment insertion of the item node into the graph data structure and deployment of the service to any device, and wherein the static analysis continues into deployment;
determine, via the static analysis, that the build that exposes the service deviates from a pre-declared whitelist of one or more dependencies; and
reject, responsive to the determination, the deployment of the service after the deployment is inserted into the graph data structure to enforce, at least in part, a default security policy to deny deviations from pre-declared execution parameters.
16. The product of claim 15 , wherein the pre-declared whitelist includes an immutable whitelist after declaration of the dependencies.
17. The product of claim 15 , wherein the instructions are further configured to cause the machine to determine that the build that exposes the service deviates from the pre-declared whitelist by refencing one or more vending cryptographic service identities.
18. The product of claim 17 , wherein the one or more vending cryptographic service identities include vending cryptographic service identities that are tied back to one or more nodes the graph data structure.
19. The product of claim 15 , wherein the deployment of the service includes a deployment the service using a sidecar model to deploy the service into a separate process from the static analysis to provide process isolation from security enforcement.
20. The product of claim 15 , wherein the instructions are further configured to cause the machine to perform the static analysis responsive to an auto-provisioning of out-of-processing monitoring for deployment of the service.