> For the complete documentation index, see [llms.txt](https://docs.scanner.dev/scanner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/wiz.md).

# Wiz

This guide walks through how to set up Wiz logs in Scanner Collect. Wiz provides two webhook-based data sources: **Wiz: Defend** (for cloud threat detections and runtime alerts) and **Wiz: Issues** (for cloud misconfiguration and security findings). Both are configured to send events directly to Scanner's HTTP receiver via webhooks.

## Create a Collect Rule

{% stepper %}
{% step %}

### Begin Setup

In the Scanner UI, go to the Collect tab.

* From the Overview page click the '+' icon in the upper right corner
* Select create new **Collect Rule**
* Choose either **Wiz: Defend** or **Wiz: Issues** (you may set up both).

{% hint style="info" %}
If you're collecting data from both **Wiz: Defend** and **Wiz: Issues**, you'll need to create two separate sources in Scanner Collect—one for each data type. The setup process is identical for both.
{% endhint %}
{% endstep %}

{% step %}

### Configuration

* Set a Display Name such as `my-org-wiz-defend` or `my-org-wiz-issues` depending on which source you're configuring.
* Leave the Payload Format as the default: **JSON: Generic**.
  {% endstep %}

{% step %}

### Authentication

* Keep the default Authentication Type: **Bearer Token**.
* Generate a secure Bearer token. You can use a command like: `echo "token_$(uuidgen | tr '[:upper:]' '[:lower:]')"`
* Note this token (we'll refer to it as `BEARER_TOKEN`)—you'll need it when configuring the webhook in Wiz.
  {% endstep %}

{% step %}

### Logs Destination

* Select the S3 bucket where you want raw logs delivered.
* (Optional) Enter a bucket prefix. The default is fine for most setups.
  {% endstep %}

{% step %}

### Review and Create

* Review your configuration.

After creation, Scanner will display a unique Endpoint URL like:

`https://collect.your-org-and-region.scanner.dev/receiver/v1/http/<id>`

**Save this URL** — you'll need it when configuring the webhook in Wiz.
{% endstep %}
{% endstepper %}

## Webhook Configuration in Wiz

{% stepper %}
{% step %}

### Accessing Wiz Settings

* Log in to your Wiz account at `wiz.io`.
* Navigate to **Settings** → **Integrations**.
  {% endstep %}

{% step %}

### Creating the Webhook

* Click **Add Integration** (or **+ Add** if you see it in the interface).
* Under **SIEM & Automation Tools**, select **Webhook**.
* Set a meaningful **Name** such as `Send Wiz Defend to Scanner` or `Send Wiz Issues to Scanner`.
* Set the **Project Scope** to apply the integration to the appropriate projects (or select all if preferred).
  {% endstep %}

{% step %}

### Configuring Webhook Details

* Paste the Endpoint URL (from the Review and Create step above) into the **Webhook URL** field.
  {% endstep %}

{% step %}

### Setting Up Authentication

* Click **Add Header** to add a custom header for authentication.
* Enter the header name: `Authorization`
* Enter the header value: `Bearer ${BEARER_TOKEN}`
  * Replace `${BEARER_TOKEN}` with the actual Bearer token you generated in the Configure Authentication step.
    {% endstep %}

{% step %}

### Configuring Events

* Select which events to send via the webhook:
  * For **Wiz: Defend**: Choose event types relevant to cloud threat detections and runtime alerts.
  * For **Wiz: Issues**: Choose event types relevant to issues, misconfigurations, exposed secrets, and identity risks.
* You may select one or multiple event types depending on your needs.
  {% endstep %}

{% step %}

#### Finalizing the Webhook

* Review all settings.
* Click **Save** or **Create** to finalize the webhook configuration.

Wiz will validate the webhook endpoint and begin sending events immediately.

**Verification**: After setup is complete, you should see events flowing into Scanner:

1. In the Wiz UI, you can monitor webhook delivery status in Settings → Integrations (if available).
2. In Scanner, navigate to the index you selected to view incoming Wiz logs.

{% hint style="info" %}
Multiple webhook sources can be configured to send different Wiz data streams (Defend and Issues) to the same or different Scanner indexes for flexible organization and analysis.
{% endhint %}
{% endstep %}
{% endstepper %}

## Create an Index Rule

Create an Index Rule to have Scanner index them for fast search and detections.

{% content-ref url="/pages/Gem9jwD4aqayN3OiChpN" %}
[Create an Index Rule](/scanner/using-scanner-complete-feature-reference/data-ingestion/create-an-index-rule.md)
{% endcontent-ref %}

### Wiz Defaults

When you create the Index Rule from the Collect Rule, the following defaults are pre-populated:

* **Transformations**: Add Metadata, Parse JSON Columns
* **Timestamp Field**:
  * `.createdAt` for Wiz: Defend
  * `.created` for Wiz: Issues


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.scanner.dev/scanner/using-scanner-complete-feature-reference/data-ingestion/sources/wiz.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.