> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/integrations/integrating-security-scanning-tools/syft-cmd.md).

# Syft (CMD)

**Syft** is an open-source CLI tool and library for generating a Software Bill of Materials (SBOM) from container images, filesystems, and source code.

#### Usage of Syft (CMD) in Delivery Shield

* Delivery Shield integrates with Syft to generate SBOMs from container images and codebases, providing visibility into all software components and dependencies.
* SBOM data is correlated with vulnerability scan results, enabling accurate identification of affected components and contributing to the application's overall security score.

#### To Manage Syft (CMD):

1. Navigate to **Setup** > **Integrations**.
2. In the **Artifact** panel, click **Syft (CMD)**.

<figure><img src="https://files.catbox.moe/13gajx.png" alt=""><figcaption></figcaption></figure>

3. The Syft (CMD) integration page is displayed.
4. Click **+New Account**.
5. In the popup that appears,
   1. Enter the **Account Name**.
   2. Enable the **Vulnerability Scan** toggle button.

<figure><img src="https://files.catbox.moe/prxegr.png" 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.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>You can select up to 5 teams for the integration to be displayed.</p></div>

   * 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,
     * 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**.
     * 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:**
     * 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.
8. You can edit the entered values by clicking the **Edit** option as shown below:

<figure><img src="https://files.catbox.moe/hxxbj3.png" alt=""><figcaption></figcaption></figure>

9. Enable or disable the Vulnerability Scan toggle button and click **Update**.

<figure><img src="https://files.catbox.moe/7p1uoq.png" alt=""><figcaption></figcaption></figure>

The new settings get updated.