Skip to content

Commit 532b7ea

Browse files
authored
update Wiz doc (#1998)
1 parent 9bb5cdc commit 532b7ea

File tree

4 files changed

+26
-16
lines changed

4 files changed

+26
-16
lines changed

docs/kb/integrations/wiz.md

+26-16
Original file line numberDiff line numberDiff line change
@@ -12,45 +12,55 @@ tags:
1212

1313
# View Semgrep findings in Wiz's Security Graph
1414

15-
Semgrep integrates with Wiz by calling Wiz’s GraphQL API endpoints and uploading your static analysis (SAST) vulnerability findings to a dedicated Amazon S3 bucket. Your Semgrep SAST vulnerability findings are mapped to the same correlated repository scanned by Wiz and enriched by any available inventory and runtime-related data, such as clusters, pods, containers, cloud configurations, and more. Semgrep's goal is to give you a holistic view of your code and infrastructure security so that you can focus on what matters most.
15+
Semgrep integrates with Wiz by establishing a secure connection with Wiz's API endpoints. If your Wiz instance has a security graph enrichment integration, you can view SAST vulnerabilities that Semgrep identifies in the repositories it scans and are also present in your cloud-native application protection platform (CNAPP). Semgrep's goal is to give you a holistic view of your code and infrastructure security so that you can focus on what matters most.
16+
17+
![A list of Semgrep findings in Wiz](/img/semgrep-findings-in-wiz.png#md-width)
18+
_**Figure**. A list of Semgrep findings in Wiz._
19+
20+
![Detailed information for a finding sent by Semgrep to Wiz](/img/wiz-finding-details-2.png#md-width)
21+
_**Figure**. Detailed information for a finding sent by Semgrep to Wiz._
1622

1723
## Prerequisites and requirements
1824

19-
This integration is available for users with both a [Semgrep Code license](https://semgrep.dev/products/semgrep-code/) and a [Wiz Code Security license](https://www.wiz.io/platform/wiz-code).
25+
This integration is available for users with both a [Semgrep Code license](https://semgrep.dev/products/semgrep-code/) and a [Wiz Code Security license](https://www.wiz.io/platform/wiz-code).
2026

2127
To send Semgrep Code findings to Wiz:
2228

23-
- You must have a Wiz service account with sufficient permissions to create a service account, if needed, and integrations. The service account must be able to provide Semgrep with the following scopes: `create:external_data_ingestion`, `read:system_activities`, and `read:resources`. If you don't have a service account:
24-
1. Create a [Wiz service account](https://docs.wiz.io/wiz-docs/docs/service-accounts-settings?lng=en). When prompted to select the **Type** of the service account, select **Custom Integration (GraphQL API)**.
25-
2. Copy the Wiz **Client ID** and **Client Secret** provided. You must provide this information to Semgrep at a later stage.
29+
- You must [connect your source code manager to Semgrep](https://semgrep.dev/docs/deployment/connect-scm). At this time, Wiz [supports the use of the following](https://win.wiz.io/docs/sast-app-vuln-findings-schema#schema-fields):
30+
- GitHub Cloud
31+
- GitHub Enterprise Server
32+
- GitLab Cloud
33+
- GitLab Self-managed
34+
- You must have a Wiz service account with sufficient permissions to create a service account, if needed, and integrations. The service account must be able to provide Semgrep with the following scopes: `create:external_data_ingestion`, `read:system_activities`, and `read:resources`. You must also have [the client ID and the client secret that accompanies the service account](https://docs.wiz.io/wiz-docs/docs/semgrep-integration).
2635
- You must add the [Semgrep integration](https://app.wiz.io/settings/automation/integrations) from the Wiz Integration Network. During this process, save the following values shown to you:
2736
1. API Endpoint URL
2837
2. Authentication URL
38+
39+
You can find both values at a later date under [tenant info](https://app.wiz.io/tenant-info/general).
40+
41+
:::note
42+
For Wiz users with a [Code Security](https://www.wiz.io/platform/wiz-code) license: this integration takes effect automatically when you create a Wiz Cloud Insights account.
43+
:::
2944

3045
## Limitations
3146

3247
Semgrep sends data to Wiz after every successful full scan; Semgrep does not send data from diff-aware scans. Wiz batches and syncs your data once every 24 hours.
3348

3449
By default, the Code findings that Semgrep sends are:
3550

36-
- High severity
51+
- Critical or high severity
3752
- From full scans
3853
- From the default branch of each repository
3954

4055
Semgrep sends findings from all repositories in your organization. Findings previously sent but not included in submissions are marked as fixed in Wiz.
4156

42-
## Add the Semgrep integration from the Wiz Integration Network
57+
:::caution
58+
Due to [a limitation of how Wiz handles external enrichment data](https://win.wiz.io/docs/limitations#external-enrichment-limitations), you must run a new SAST scan on your Semgrep project once a week to maintain the data displayed in Wiz.
59+
:::
4360

44-
To add the Semgrep integration from the Wiz Integration Network:
61+
## Add the Semgrep integration from the Wiz Integration Network
4562

46-
1. Sign in to [Wiz](https://app.wiz.io/login).
47-
2. Ensure that the account you're using has been assigned the `create:integrations` access scope.
48-
3. Using the navigation bar, go to **Settings > Integrations**.
49-
4. lick **Add Integration**.
50-
5. Find the **Semgrep** integration card and click **Add**.
51-
6. Follow the on-screen steps provided by Wiz to complete the setup of the Semgrep integration. Ensure that you save the following information when provided by Wiz:
52-
1. API Endpoint URL
53-
2. Authentication URL
63+
To learn how to add the Semgrep integration from the Wiz Integration Network, review [Wiz Docs' Semgrep Integration](https://docs.wiz.io/wiz-docs/docs/semgrep-integration).
5464

5565
## Configure the integration in Semgrep
5666

592 KB
Loading

static/img/wiz-finding-details-2.png

610 KB
Loading

static/img/wiz-finding-details.png

411 KB
Loading

0 commit comments

Comments
 (0)