Requesting Wiz Ignore Rules for Cloud Security Findings

Body

Wiz is a cloud security platform that connects to Northwestern's cloud environments through provider APIs, without agents, to continuously scan for misconfigurations, vulnerabilities, exposed secrets, and excessive permissions, and prioritizes the risks most likely to be exploited

Overview

To ensure consistent governance and risk management across Northwestern University's cloud environments, requests to implement Ignore Rules within Wiz must now follow a formal review and approval process.

An Ignore Rule may be appropriate when a security finding represents an accepted risk, is not applicable to the environment, or cannot reasonably be remediated without significantly affecting University operations or mission. Requests must follow Northwestern's established Risk Exception process, including appropriate justification and compensating controls, and receive Information Security Office approval before implementation.

Policy

Implementation of an Ignore Rule in Wiz requires:

  1. Submission of an Ignore Rule request in Wiz.
  2. Submission and approval of a Risk Exception Request through TeamDynamix (TDX).
  3. Review and approval by the Information Security Office (ISO).
  4. Final validation and implementation by Cloud Operations.

Northwestern IT Cloud Operations will not review or approve Ignore Rule requests until the corresponding Risk Exception Request has been approved by ISO.

Important: Approval of an Ignore Rule does not remediate or eliminate the underlying security risk. Rather, it formally documents the accepted risk and suppresses applicable findings in Wiz based on the approved exception.

Request Process

Step 1: Submit an Ignore Rule Request in Wiz

Initiate the process by creating an Ignore Rule request within Wiz:

  • Provide an appropriate title and brief description of the request
  • Scope the request to your Wiz project
  • Consider the Rule and Ignored Finding Types
  • What resources this rule targets

Step 2: Submit a Risk Exception Request

The Risk Exception Request should include:

  • Business or operational justification
  • Description of the affected resource
  • Compensating controls or mitigating factors
  • Duration of the exception, if applicable
  • Link to the associated Wiz Ignore Rule request

The Risk Exception Request serves as the authoritative record for review and approval.

Step 3: Information Security Office (ISO) Review

The Information Security Office (ISO) will review the Risk Exception Request through the established risk exception process.

ISO may approve the request, deny the request, or request additional information before reaching a determination.

Step 4: Cloud Operations Review and Implementation

Following ISO approval, the ticket will be reassigned to Northwestern IT Cloud Operations for validation and implementation. Only after this review is completed will the Ignore Rule be activated.

 

Process Flow

 

Frequently Asked Questions

Is submission of an Ignore Rule request in Wiz sufficient for approval?

No. A corresponding Risk Exception Request must be submitted and approved through the Information Security Office review process before Cloud Operations can implement the Ignore Rule.

Why is a Risk Exception required?

Risk Exceptions provide a formal mechanism for documenting, evaluating, and approving accepted risks. This ensures appropriate oversight, accountability, and alignment with Northwestern's security governance practices.

What happens if the Risk Exception Request is denied?

If ISO denies the Risk Exception Request, the Ignore Rule will not be implemented.

Will Cloud Operations review my Ignore Rule request before ISO approval?

No. Cloud Operations will defer review until the Risk Exception Request has completed the ISO review process and been approved.
 

 

References and Useful Resources

 


 

Details

Details

Article ID: 2993
Created
Thu 11/12/26 2:02 PM
Modified
Tue 11/17/26 2:21 PM