# Grype

Grype is a vulnerability scanning tool specifically designed for container images. It helps identify vulnerabilities within Docker containers and other container formats.  

### Usage of Grype in Delivery Shield

* Delivery Shield mandates security scans on images using Grype. It connects with Grype to see if the required version of the image has been scanned by and if not done, SSD generates a security issue.
* Once the Grype scan is done, Delivery Shield pulls container security scan results from Grype, and this data is used to calculate the overall security status of the images and application, to generate alerts and remediation. 
* The scan results fetched by Delivery Shield will be displayed in the [Vulnerability Management](https://docs.opsmx.com/opsmx-secure-software-delivery-ssd-platform/user-guide/vulnerability-management) page, Artifact section of the [DBOM](https://docs.opsmx.com/opsmx-secure-software-delivery-ssd-platform/user-guide/delivery-bill-of-materials-dbom) and [View Open Security Issues](https://docs.opsmx.com/opsmx-secure-software-delivery-ssd-platform/user-guide/view-security-posture/view-open-security-issues) page. 

{% hint style="info" %}
Grype is integrated as part of Delivery Shield. You need to just enable or disable it when required. 
{% endhint %}

### To Manage Grype:

1. Navigate to **Setup** > **Integrations**.
2. In the **Artifact** panel, click **Grype**.

<figure><img src="/files/xKVqwu5qQXmInQwSN577" alt=""><figcaption></figcaption></figure>

3. The Grype integration page is displayed.
4. Click **+New Account**.&#x20;
5. In the popup that appears,&#x20;
   1. Enter the account name.&#x20;
   2. Enable the **Vulnerability Scan** toggle button. &#x20;

<figure><img src="/files/tJn5Ucckz92B77zbIkAB" alt=""><figcaption></figcaption></figure>

6. Select the **Teams** and the corresponding **Environments** from the dropdown for which you want the integration to be available. The integration will be available for the selected teams and environment only.&#x20;

{% hint style="info" %}
You can select up to 5 teams for the integration to be displayed.&#x20;
{% endhint %}

* An example is given below for reference:

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeuMZQzZsZQuulVdW9B9OuffNPoEXqbcpcAkYtKVyb7YiTQxbVIt1L4Gh-zshqX2J9MFKIat8x4oWFIGxdg3j1XVagyUNhUAlD_52soyMyd1cy53p6XiYi0LsTjIBfHcybRWl61?key=D9EXoOdGF7oYOBvYaW2GnRWJ" alt=""><figcaption></figcaption></figure>

* In the example above,&#x20;
  * if **Team 1**, **Team 2**, and **Team 3** are selected, only applications associated with these teams can access the integration. Any applications belonging to other teams, such as **Team 4**, will not have access to this account.
  * Even if the user who created this account is also an admin for **Team 4**, the integration account remains restricted and is not available for **Team 4**.&#x20;
  * Access to the account is strictly limited to the specified **Teams** and **Environments** selected during account creation.
* **For Organization Admins:**
  * When an **Organization Admin** creates an account without selecting specific **Teams** and **Environments**, the account will be universally applicable, granting access to **all teams** and **all environments** by default.
* **For Team Admins with Multiple Teams:**<br>
  * If a **Team Admin** who manages multiple teams creates an account without specifying particular **Teams** and **Environments**, the account will only be accessible to the teams for which the logged-in user holds admin privileges.

7. Click **Save**. The tool is connected.&#x20;
8. You can edit the entered values by clicking the **Edit** option as shown below:
9. Enable or disable the Vulnerability Scan toggle button and click **Update**.&#x20;

The new setting gets updated.&#x20;

<br>


---

# 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/opsmx-1/opsmx-delivery-shield-platform/getting-started/integrating-security-scanning-tools-in-delivery-shield/grype.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.