# Support Matrix

The support matrix lists the different tool combinations that Delivery Shield supports in various stages of software development, such as source code storage, build, artifact storage, deployment tool, and deployment targets. It also specifies whether the deployment firewall can be enabled for each combination of tools.

{% hint style="info" %}
Apart from the given tools, other security scanning tools are also supported by Delivery Shield. To view the list of tools, refer [Integrating other DevOps tool in Delivery Shield](https://docs.opsmx.com/opsmx-secure-software-delivery-ssd-platform/getting-started/integrating-other-devops-tools-in-ssd). <br>
{% endhint %}

For example, if the deployment tool is spinnaker and source code is in Github, Jenkins is used for build, Docker Hub is used for artifact storage, and Kubernetes is the Deployment Target; then the deployment firewall is enabled.&#x20;

The following table lists the various tools and their combinations with which the firewall can be enabled or disabled.&#x20;

<table data-header-hidden data-full-width="true"><thead><tr><th width="140"></th><th width="129"></th><th></th><th></th><th></th><th width="127"></th><th></th></tr></thead><tbody><tr><td><strong>Deployment Tool</strong></td><td><strong>Deployment Type</strong></td><td><strong>Source Code</strong></td><td><strong>Build</strong></td><td><strong>Artifact Storage</strong></td><td><strong>Deployment Target</strong></td><td><strong>Deployment Firewall</strong></td></tr><tr><td>Spinnaker</td><td><p></p><p>Deployment manifest file-based deployment, with no support for helm </p></td><td>Github</td><td>Jenkins</td><td>Dockerhub</td><td>Kubernetes</td><td>Enabled</td></tr><tr><td>Spinnaker</td><td></td><td>Github</td><td>Jenkins</td><td>Quay</td><td>Kubernetes</td><td>Enabled</td></tr><tr><td>Spinnaker</td><td></td><td>Github </td><td>Jenkins</td><td>JFrog</td><td>Kubernetes</td><td>Enabled</td></tr><tr><td>Spinnaker</td><td></td><td>Github </td><td>Jenkins</td><td>Dockerhub </td><td>ECS</td><td>Disabled</td></tr><tr><td>Spinnaker</td><td></td><td>Github </td><td>Jenkins</td><td>Quay</td><td>ECS</td><td>Disabled</td></tr><tr><td>Spinnaker</td><td></td><td>Github </td><td>Jenkins</td><td>JFrog</td><td>ECS</td><td>Disabled</td></tr><tr><td>Spinnaker</td><td></td><td>Github </td><td>Jenkins</td><td>Dockerhub</td><td>Kubernetes</td><td>Enabled</td></tr><tr><td>Spinnaker</td><td></td><td>Github </td><td>Jenkins</td><td>Quay</td><td>Kubernetes</td><td>Enabled</td></tr><tr><td>Spinnaker</td><td></td><td>Github </td><td>Jenkins</td><td>JFrog</td><td>Kubernetes</td><td>Enabled</td></tr><tr><td>Spinnaker</td><td></td><td>Github </td><td>Jenkins</td><td>Dockerhub</td><td>ECS</td><td>Disabled</td></tr><tr><td>Spinnaker</td><td></td><td>Github </td><td>Jenkins</td><td>Quay</td><td>ECS</td><td>Disabled</td></tr><tr><td>Spinnaker</td><td></td><td>Github </td><td>Jenkins</td><td>JFrog</td><td>ECS</td><td>Disabled</td></tr><tr><td>Argo</td><td><p>Supports manifest file-based deployment, helm and kustomize deployments</p><p><br><br><br><br><br></p></td><td>Github</td><td>Jenkins</td><td>Dockerhub</td><td>Kubernetes</td><td>Enabled</td></tr><tr><td>Argo</td><td></td><td>Github</td><td>Jenkins</td><td>Quay</td><td>Kubernetes</td><td>Enabled</td></tr><tr><td>Argo</td><td></td><td>Github</td><td>Jenkins</td><td>JFrog</td><td>Kubernetes</td><td>Enabled</td></tr></tbody></table>

{% hint style="info" %}
Delivery Shield can run independently without connecting to any source or build tools also.&#x20;
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.opsmx.com/ssd/security-risk-and-prioritization/getting-started/support-matrix.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.