--- title: Defer a Remediation task description: If you determine that the issue associated with a remediation task \(VUL\) is a low priority and can be immediately deferred without further analysis, you can use the Request Exception feature. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/security-management/vulnerability-response/defer-vuln-group.html release: australia product: Vulnerability Response classification: vulnerability-response topic_type: task last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Resolve remediation tasks, Working with unmatched CIs, Vulnerability Response remediation overview, Vulnerability Response, Unified Security Exposure Management, Security Operations] --- # Defer a Remediation task If you determine that the issue associated with a remediation task \(VUL\) is a low priority and can be immediately deferred without further analysis, you can use the **Request Exception** feature. ## Before you begin Role required: sn\_vul.vulnerability\_admin or sn\_vul.admin \(deprecated\) ## About this task You can defer a remediation task from a remediation task record in the Vulnerability Response Workspaces. After you submit the request, it is sent for approval. See [Request an exception in the IT Remediation Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/it-remediation-workspace/vr-ws-request-exception.md). A scheduled job runs every day checking for deferred remediation tasks that have reached their reopen date. On the day the task's deferral is set to expire, the task is reopened. **Note:** You can manually move change requests and remediation tasks through the states of their life cycles on their respective records with state synchronization enabled, but when the system registers that a CHG has changed its state, or you add a CHG or remove it from a remediation task, state synchronization potentially can override your manual intervention. However, change request states do not automatically move remediation tasks from the Closed or Deferred states. ## Procedure 1. Navigate to **All** > **Vulnerability Response** > **Remediation Tasks**. 2. Open a record. 3. Click **Request Exception**. 4. Fill in the fields on the form, as appropriate.
| Field | Description |
|---|---|
| Until | Select the date when the Defer state expires and the remediation task is reactivated. After the record is submitted, if [email notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-response/t_DefineEmailNotifications.md) are defined, members of the Vulnerability Response group receive an email when the expiration date is within one week. When the defer date expires, the remediation task is set back to **Open** and a second email notification is sent out. |
| Reason | Enter the reason for deferring the issue. Choices include: - Awaiting maintenance window - False positive - Fix unavailable - Risk accepted - Mitigating control in place - Other |
| Additional information | Enter any other relevant information. |