On This Page

Home / Search/ Get Data In/ Add Sources/Ingest Wiz Security Events into Cribl Search

Ingest Wiz Security Events into Cribl Search

Collect security events and alerts via Wiz webhook notifications to store them in Cribl Search for fast analysis.


Before You Begin

You’ll need:

  • Cribl.Cloud Enterprise. For details, see Pricing.
  • A lakehouse engine. See how to get one at lakehouse engines.
  • Search Admin Permission, or higher. Learn who can do what at Cribl Search Permissions.
  • Wiz webhook integration that can send data to Cribl Search over HTTP(S).

You don’t need Cribl Stream, Edge, or Lake. (Looking for the Wiz Webhook Source in Cribl Stream instead?)

1. Add a Wiz Webhook Source in Cribl Search

On the Cribl.Cloud top bar, select Products > Search > Data > Add Source > Wiz Webhook.

Under General, configure:

SettingDescriptionExample
IDSource ID, unique across your Cribl.Cloud Workspace.

Use letters, numbers, underscores, hyphens.
wiz_webhook_prod
DescriptionDescribe your Source so others know what it’s for.Ingests Wiz webhook security events
AddressHostname (FQDN) that your Wiz webhook connects to.

You’ll need this to set up your webhook client.
search.main.foo-bar-abc123.cribl.cloud
PortNetwork port to listen on.

Keep the default unless it conflicts with another service.
20000 (default)

Set Up Authentication

Use authentication to make sure only authorized clients can send data to your Cribl Search Source.

Under Authentication, select Add Token, and configure:

SettingDescriptionExample
TokenAuthentication string you’ll need to set up your Wiz client.

Enter a token text, or select Generate for a random one.
420
DescriptionDescribe which clients or environments use the token.Prod UF

Set Up Encryption

Use TLS encryption to protect your data in transit between Wiz and your Cribl Search Source.

Under Encrypt, select Enabled, and set the Minimum TLS version you want to accept.

TLS VersionWhen to Use
1.3Recommended. Provides the best security.
1.2Use only when connecting to older systems that don’t support TLS 1.3.
Older than 1.2Avoid if possible. These versions are no longer considered secure.

Select Save to create the Source.

2. Set Datatype Rules

Configure Datatype rules to parse, filter, and normalize your data into structured fields. We call this process Datatyping.

On the Cribl.Cloud top bar, select Products > Search > Data > Datatyping (auto). Here, you can:

See also:

3. Set Dataset Rules

Configure Dataset rules to organize the parsed events into Datasets. This also determines how long the data is kept, as each Dataset has its own retention period.

On the Cribl.Cloud top bar, select Products > Search > Data > Datasets: Organize Your Data, and see Organize Your Data for details.

4. Set Up Your Wiz Webhook

In Wiz, configure a webhook to send security events to Cribl Search.

You’ll need these details from your Source configuration:

Name
Example
Addresssearch.main.foo-bar-abc123.cribl.cloud
Port20000 (default)
Token420

To find these for an existing Source: On the Cribl.Cloud top bar, select Products > Search > Data > Sources, and select your Source.

Example Request (Wiz Webhook > Cribl Search)

Configure the webhook in Wiz to point to your Source endpoint, using the following example.

Replace the example address (search.main.foo-bar-abc123.cribl.cloud), token, and port (if you changed the default 20000) with your Source values.

curl -k "https://search.main.foo-bar-abc123.cribl.cloud:20000" \
-H "Authorization: 420" \
-d '{"event":"Wiz security alert", "host":"wiz", "source":"wiz-webhook", "severity":"high", "findingId":"abc123"}'

Without TLS, use http instead of https.

5. See Live Data Flow

Verify that events are successfully flowing from Wiz into Cribl Search.

On the Cribl.Cloud top bar, select Products > Search > Data > Live Data.

Here, check for your Wiz Webhook Source. For details, see See Live Data Flow.

Next Steps

Now that your data is in Cribl Search, you can start using it. For example: