Send Wiz logs to LogPulse

Wiz issues and the Wiz audit log: misconfigurations, toxic combinations and threat detections in your clouds, with the resource, account and severity.

In short
To send Wiz logs to LogPulse, add Wiz under Configure → Sources → Cloud. LogPulse reads the Wiz GraphQL API itself, without an agent. Events land in the vulnerabilities, audit indexes with source wiz and fill the Vulnerabilities, Change data models.

Overview

How Wiz data reaches LogPulse
Vendor
Wiz GraphQL API
Collect
Integration pollerreads new events, maps the fields
Store
index=vulnerabilities
index=audit
  1. Wiz GraphQL API to Integration poller
  2. Integration poller to index=vulnerabilities
  3. Integration poller to index=audit

LogPulse signs in to Wiz with the credential you give it and fetches new events every five minutes by default. You can set the interval per integration, from one minute to 24 hours.

What you need

  • A Wiz service account with read:issues (and admin:audit for the audit log)
  • In LogPulse: a role that may manage API keys. Cloud integrations fall under that right.

1. Create a credential in Wiz

Field in LogPulseWhere you find it
API endpointIn Wiz: User Settings, Tenant. Copy the API endpoint URL, such as https://api.eu17.app.wiz.io/graphql.
Client IDIn Wiz: Settings, Service Accounts, Add Service Account (type Custom Integration). Scopes read:issues and, for the audit log, admin:audit.
Client secretStored encrypted and never shown again.

2. Add the integration in LogPulse

Go to Configure → Sources → Cloud and choose Wiz. Fill in the fields, tick the data sources you want and save. LogPulse first tests the connection with your credential and tells you what is wrong when it fails.

Tip: Secrets are stored encrypted and never shown again. To change one, paste a new value; the rest stays.

What arrives

Data sourceIndexSourceSourcetypeWhat it holds
Issuesvulnerabilitieswizwiz:issuesNew and changed issues: the rule, severity, status and the cloud resource, account and region.
Audit log (off by default)auditwizwiz:userAuditLogsWho did what in the Wiz portal and API: user or service account, action, source IP and status.

The index is the kind of data and the source is the product, so detection rules for that kind of data find Wiz without changes.

Note: An issue that is resolved arrives again with its new status, so you see when it was fixed.
Note: The audit log needs the scope admin:audit on the service account.
Note: Wiz for Government (app.wiz.us) works too.

Fields and data models

Data modelWhat you get
VulnerabilitiesIssues with rule, severity, status and the resource, account and region.
ChangeAudit entries with user, action and source IP.

Field names follow the CIM field names. These are the fields LogPulse sets on Wiz events; a field is left out when Wiz did not send a value.

  • account
  • account_name
  • action
  • category
  • cloud_platform
  • dest
  • dest_id
  • dest_type
  • http_user_agent
  • id
  • project
  • region
  • request_id
  • severity
  • signature
  • signature_id
  • src_ip
  • status
  • user
  • user_id
  • user_type
  • vendor_action

The original record of Wiz is kept with each event under raw, so nothing the vendor sent is lost.

3. Check the data

The first events arrive within a few minutes. Check what came in:

earliest=-1h index IN (vulnerabilities, audit) source IN (wiz)
| stats count by index, source, sourcetype

The integration page in LogPulse shows when it last read events and the last error, if any.

Troubleshooting

The connection test names what is wrong. These are the answers you are most likely to see.

What you seeWhat to do
Wiz refused the client id and secret.Create a new service account of the type Custom Integration under Settings, Service Accounts, and copy both values.
The service account cannot read issues. Give it the read:issues scope (and admin:audit for the audit log).Edit the service account and add read:issues. Add admin:audit only when you turn on the audit log.
apiEndpoint is the API endpoint of your Wiz tenant, e.g. https://api.eu17.app.wiz.io/graphqlCopy the API endpoint URL from User Settings, Tenant. It differs per tenant region.
The test passes but no events arrive.Run the search above over a longer time. No results: check on the integration page that the data source is switched on and when it last read events. Wiz may also simply have had nothing new.

Frequently asked questions

How do I send Wiz logs to LogPulse?
Add the Wiz cloud integration under Configure, Sources, Cloud in LogPulse and fill in API endpoint, Client ID, Client secret. LogPulse reads the Wiz GraphQL API itself, every five minutes by default; there is nothing to install.
Which permissions does LogPulse need in Wiz?
A Wiz service account with read:issues (and admin:audit for the audit log). Read access is enough for collecting logs.
Which index does Wiz data go to?
The index is the kind of data: vulnerabilities, audit. The source is the product: wiz. Each data source has its own sourcetype, listed on this page.
Which data models does Wiz fill?
Vulnerabilities, Change. Detection rules and dashboards written for a data model work on Wiz without changes.
Why is Audit log off by default?
To keep your daily ingest down until you need it: Audit log is high volume or of use to fewer teams. Tick the data source in the integration to switch it on.
Do I see when a Wiz issue is resolved?
Yes. An issue arrives again when its status changes, with the new status, so a search shows when it was opened and when it was fixed.