Set filtering for the Wiz Issues Integration
Set the filtering values to import Wiz Issues that identify assets involved in toxic combinations of vulnerabilities and misconfigurations.
Before you begin
|
Supporting core application |
Benefit |
Wiz Integration |
Users |
|---|---|---|---|
|
Configuration Compliance |
Import Wiz Issues that identify assets involved in toxic combinations of vulnerabilities and misconfigurations.These findings are mapped to CTRs and labeled with |
Wiz Issues Integration. |
Vulnerability managers, analysts, and Cloud security teams |
Procedure
-
Navigate to All > Wiz Vulnerability Integration > Administration > Configuration.
-
Select the Issues Configuration tab.
-
Fill in the fields.
For some fields, you can specify multiple values.
--None--is the (default). If--None--remains selected for a field, no data is imported for this field.If displayed select the lock icons ([Omitted image "dlp-lock-icon.png"] Alt text: An closed padlock icon that indicates the field is locked and not editable.) and ([Omitted image "dlp-unlock-icon.png"] Alt text: An opened padlock icon that indicates the field is unlocked and editable.) to edit and lock your edits.
|
Field |
Description |
|---|---|
|
Severity |
Filter by finding severity.- --None--
|
|
Project ID |
Import only findings for the given projects (strings). |
|
Issue type |
Issues by the rule type they are generated by.- CLOUD_CONFIGURATION
|
|
Subscription ID |
Specify findings by entering a subscription ID. You can specify multiple values in an array. |
|
Cloud platform |
Configuration findings by Cloud platform. You can specify multiple values, for example, AWS, GitHub, Terraform, OpenAI, GKE, OKE, EKS, AKS. |
|
Framework Category |
Enter security frameworks, security subcategories, or security categories. You can specify multiple values. |
|
Native type |
Issues based on the native type of the cloud resource, for example, |
|
First |
Pagination. Enter a value. You might prefer to start with 1000. |
|
Status |
Filter by status:- --None--
|
|
Fetch rejected findings |
Select this check box if you want to import Cloud test results in a failed state (rejected) from Wiz. Note: These findings are mapped to CTRs and labeled with If not selected, failed test results reported by Wiz are not imported.If imported, these test results remain in a failed state but are not rolled up to Configuration Compliance findings. |
|
Close rejected findings |
Select this check box if you want to import failed Cloud test results reported by Wiz and automatically close them after import. If not selected, these test results remain in a failed state but are neither closed nor rolled up to Configuration Compliance findings. |
If the credentials have been saved and validated successfully a message is displayed. You can select filtering for another integration import.
---
title: Set filtering for the Wiz Issues Integration
description: Set the filtering values to import Wiz Issues that identify assets involved in toxic combinations of vulnerabilities and misconfigurations.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/security-management/vulnerability-response/wiz-issues-tab-filters.html
release: brazil
product: Vulnerability Response
classification: vulnerability-response
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 2
breadcrumb: [Configure, Vulnerability Response Integration with Wiz, Vulnerability Response integrations, Vulnerability Response, Unified Security Exposure Management, Security Operations]
---
# Set filtering for the Wiz Issues Integration
Set the filtering values to import Wiz Issues that identify assets involved in toxic combinations of vulnerabilities and misconfigurations.
## Before you begin
<table id="table_wdy_rvl_hkc"><thead><tr><th>
Supporting core application
</th><th>
Benefit
</th><th>
Wiz Integration
</th><th>
Users
</th></tr></thead><tbody><tr><td>
Configuration Compliance
</td><td>
Import Wiz Issues that identify assets involved in toxic combinations of vulnerabilities and misconfigurations.These findings are mapped to CTRs and labeled with `Wiz Issues` as the source to help you track and remediate assets that might pose complex, multi-vector risks.
</td><td>
Wiz Issues Integration.
</td><td>
Vulnerability managers, analysts, and Cloud security teams
</td></tr></tbody>
</table>Role required: sn\_vul\_wiz.configure\_integration
## Procedure
1. Navigate to **All** > **Wiz Vulnerability Integration** > **Administration** > **Configuration**.
2. Select the **Issues Configuration** tab.
3. Fill in the fields.
For some fields, you can specify multiple values. `--None--` is the \(default\). If `--None--` remains selected for a field, no data is imported for this field.
If displayed select the lock icons \(\[Omitted image "dlp-lock-icon.png"\] Alt text: An closed padlock icon that indicates the field is locked and not editable.\) and \(\[Omitted image "dlp-unlock-icon.png"\] Alt text: An opened padlock icon that indicates the field is unlocked and editable.\) to edit and lock your edits.
<table id="table_wdj_klr_qfc"><thead><tr><th>
Field
</th><th>
Description
</th></tr></thead><tbody><tr><td>
Severity
</td><td>
Filter by finding severity.- --None--
- LOW
- MEDIUM
- HIGH
- CRITICAL
- INFORMATIONAL
</td></tr><tr><td>
Project ID
</td><td>
Import only findings for the given projects \(strings\).
</td></tr><tr><td>
Issue type
</td><td>
Issues by the rule type they are generated by.- CLOUD\_CONFIGURATION
- THREAT\_DETECTION
- TOXIC\_COMBINATION
</td></tr><tr><td>
Subscription ID
</td><td>
Specify findings by entering a subscription ID. You can specify multiple values in an array.
</td></tr><tr><td>
Cloud platform
</td><td>
Configuration findings by Cloud platform. You can specify multiple values, for example, AWS, GitHub, Terraform, OpenAI, GKE, OKE, EKS, AKS.
</td></tr><tr><td>
Framework Category
</td><td>
Enter security frameworks, security subcategories, or security categories. You can specify multiple values.
</td></tr><tr><td>
Native type
</td><td>
Issues based on the native type of the cloud resource, for example, `bucket`.
</td></tr><tr><td>
First
</td><td>
Pagination. Enter a value. You might prefer to start with 1000.
</td></tr><tr><td>
Status
</td><td>
Filter by status:- --None--
- OPEN
- IN PROGRESS
- RESOLVED
</td></tr><tr><td>
Fetch rejected findings
</td><td>
Select this check box if you want to import Cloud test results in a failed state \(rejected\) from Wiz.
**Note:** These findings are mapped to CTRs and labeled with `Wiz Issues` as the source to help you track them.
If not selected, failed test results reported by Wiz are not imported.If imported, these test results remain in a failed state but are not rolled up to Configuration Compliance findings.
</td></tr><tr><td>
Close rejected findings
</td><td>
Select this check box if you want to import failed Cloud test results reported by Wiz and automatically close them after import. If not selected, these test results remain in a failed state but are neither closed nor rolled up to Configuration Compliance findings.
</td></tr></tbody>
</table>4. **Select Save and test**.
If the credentials have been saved and validated successfully a message is displayed. You can select filtering for another integration import.
| title | Set filtering for the Wiz Issues Integration |
| description | Set the filtering values to import Wiz Issues that identify assets involved in toxic combinations of vulnerabilities and misconfigurations. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/security-management/vulnerability-response/wiz-issues-tab-filters.html |
| release | brazil |
| product | Vulnerability Response |
| classification | vulnerability-response |
| topic_type | task |
| last_updated | 2026-09-10 |
| reading_time_minutes | 2 |
| breadcrumb | ConfigureVulnerability Response Integration with WizVulnerability Response integrationsVulnerability ResponseUnified Security Exposure ManagementSecurity Operations |