Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Lakewatch is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage workspace-level previews.
Lakewatch provides an API connector to ingest audit log entries, issues, and vulnerability findings from Wiz. This article covers prerequisites, configuration instructions, connector schemas, and security observables.
Prerequisites
The connector requires:
- Serverless Lakeflow pipelines turned on in your workspace.
- Unity Catalog, with privileges to create or use a Unity Catalog connection. See Connection permissions.
- The Lakeflow Connect for Wiz Audit Logs preview turned on in your workspace by a workspace admin. See Turn on the connector preview.
- If your workspace's serverless network policy uses restricted access,
api.<tenant-data-center>.app.wiz.iomust be on the policy's Allowed domains list, where<tenant-data-center>is your Tenant Data Center. See Allow the source API domains in your network policy. - A Wiz tenant with administrator access to create a service account.
- Permission to grant the service account read access to the audit logs, issues, and vulnerability findings you want to ingest.
Known limitations
- SCD type 2 is not supported because Wiz security data is ingested as an append-only feed.
- The connector supports OAuth machine-to-machine (M2M) authentication with a Wiz service account. API token and basic authentication aren't supported.
- Automated schema evolution supports new and deleted columns, but not data type changes or column renames.
- Historical lookback can't exceed 180 days. See Choose how far back to ingest.
- Issue ingestion advances by
createdAtwith an overlap of five minutes. Changes toupdatedAt, status, or resolution do not cause an older issue outside that creation-time window to be ingested again. Theissuestable is an append-only creation feed, not a continuously refreshed inventory of issue state.
Configure Wiz for ingestion
In this step, you create a service account in Wiz and note the credentials that you use to create a connection in Databricks.
- Sign in to your Wiz tenant as an administrator.
- Create a service account for the connector:
- In the Wiz portal, go to Settings > Access Management > Service Accounts, then click Add Service Account.
- Enter a descriptive Name for the service account.
- For Type, select Custom Integration (GraphQL API).
- Grant the service account the API scopes for the data you want to ingest:
read:resources(required for all ingestion)admin:auditto ingest audit log entriesread:issuesto ingest issuesread:vulnerabilitiesto ingest vulnerability findings
- Leave Projects blank. Selecting one or more projects prevents the service account from querying audit logs, because the
admin:auditscope is available only when no project is selected. - Create the service account.
- Note the service account's Client ID and Client Secret. Copy the client secret immediately, because Wiz does not display it again after you close the dialog. You enter these values when you create a connection in Databricks.
- Get your tenant details. Click your profile icon in the top right of the Wiz portal, then click Tenant Info. Note the following values, which you enter when you create a connection in Databricks:
- On the General tab, the Authentication URL. This is the token endpoint that the connector uses to exchange the client credentials for an access token. For example,
https://auth.app.wiz.io/oauth/token. - On the Data Center and Regions tab, your data center. This is your Tenant Data Center.
- On the General tab, the Authentication URL. This is the token endpoint that the connector uses to exchange the client credentials for an access token. For example,
Tip
When you create a connection through the Lakewatch UI, enter the Tenant Data Center, Client ID, Client Secret, and Authentication URL gathered above.
For more information, see Configure authentication to Wiz.
Next steps
After completing the configuration above, create a datasource with the Wiz connector in the Lakewatch UI. See API connectors for instructions.
Connector and Lakewatch schemas
The connector ingests the following source tables from the default source schema:
| Source table | Wiz data | Built-in Lakewatch parser |
|---|---|---|
audit_log_entries |
User actions, service account activity, and configuration changes | wiz_audit |
issues |
Risks detected in the cloud environment, including status and severity | wiz_issues |
vulnerability_findings |
Vulnerabilities, affected assets, severity, and remediation guidance | wiz_vulnerability_finding |
The connector writes each source table directly to the destination configured for its built-in parser. By default, the destination table is named <parser>_<datasource>, where <datasource> is the datasource name. For example, with the default datasource name wiz_audit_logs, the table is wiz_audit_wiz_audit_logs. You can set a different destination during datasource creation. There is no separate raw staging table or later parsing step.
Lakewatch-managed columns
The connector adds the following columns to each output row:
lw_id: A non-null string that Lakewatch uses as the primary key. The connector derives a stable, time-sortable ID fromtimeand the Wizidfield.time: A timestamp used for incremental ingestion. Foraudit_log_entries, the connector derivestimefromtimestamp. Forissues, it derivestimefromcreatedAt. Forvulnerability_findings, it derivestimefromupdatedAt.
For issues, time represents issue creation time from createdAt.
For Lakewatch datasources, the connector also adds:
lw_meta: The datasource and connection identity, parser name and version, and ingestion time.lw_observables: Security observables extracted by the connector.
For more information, see Connector output tables.
Connector output table schemas
The destination includes the source and event columns below, together with the lw_meta and lw_observables columns described above.
The following schemas include the Wiz fields and the Lakewatch-managed lw_id and time columns. For field definitions, see the Wiz connector reference.
audit_log_entries
Schema
| Column | Data type |
|---|---|
lw_id |
STRING |
time |
TIMESTAMP |
id |
STRING |
action |
STRING |
requestId |
STRING |
status |
STRING |
timestamp |
TIMESTAMP |
actionParameters |
STRING |
userAgent |
STRING |
sourceIP |
STRING |
serviceAccount |
STRUCT<id: STRING, name: STRING> |
user |
STRUCT<id: STRING, name: STRING> |
issues
Schema
| Column | Data type |
|---|---|
lw_id |
STRING |
time |
TIMESTAMP |
id |
STRING |
sourceRule |
STRING |
createdAt |
TIMESTAMP |
updatedAt |
TIMESTAMP |
dueAt |
TIMESTAMP |
type |
STRING |
resolvedAt |
TIMESTAMP |
statusChangedAt |
TIMESTAMP |
projects |
ARRAY<STRUCT<id: STRING, name: STRING, slug: STRING, businessUnit: STRING, riskProfile: STRING>> |
status |
STRING |
severity |
STRING |
entitySnapshot |
STRING |
serviceTickets |
STRING |
notes |
STRING |
vulnerability_findings
Schema
| Column | Data type |
|---|---|
lw_id |
STRING |
time |
TIMESTAMP |
id |
STRING |
portalUrl |
STRING |
name |
STRING |
CVEDescription |
STRING |
CVSSSeverity |
STRING |
score |
DOUBLE |
exploitabilityScore |
DOUBLE |
impactScore |
DOUBLE |
dataSourceName |
STRING |
hasExploit |
BOOLEAN |
hasCisaKevExploit |
BOOLEAN |
status |
STRING |
vendorSeverity |
STRING |
firstDetectedAt |
TIMESTAMP |
lastDetectedAt |
TIMESTAMP |
updatedAt |
TIMESTAMP |
resolvedAt |
TIMESTAMP |
description |
STRING |
remediation |
STRING |
detailedName |
STRING |
version |
STRING |
fixedVersion |
STRING |
detectionMethod |
STRING |
link |
STRING |
locationPath |
STRING |
resolutionReason |
STRING |
epssSeverity |
STRING |
epssPercentile |
DOUBLE |
epssProbability |
DOUBLE |
validatedInRuntime |
STRING |
layerMetadata |
STRING |
projects |
ARRAY<STRUCT<id: STRING, name: STRING, slug: STRING, businessUnit: STRING>> |
ignoreRules |
ARRAY<STRUCT<id: STRING, name: STRING, enabled: BOOLEAN>> |
vulnerableAsset |
STRING |
Security observables
The connector extracts the following fields into lw_observables.
wiz_audit
Observables
| Field | Observable |
|---|---|
sourceIP |
ip |
serviceAccount.id |
actor_id |
user.id |
actor_id |
user.name |
username |
The issues output has no configured security observable fields.
wiz_vulnerability_finding
Observables
| Field | Observable |
|---|---|
portalUrl |
url |
link |
url |