Request an extension for a deferred remediation task (VUL) before it reaches its deferred until due date. As a remediation owner, you’re no longer required to wait until the deferred due date to make this request.
Before you begin
Role required: sn_vul.vulnerability_admin or sn_vul.admin (deprecated)
About this task
You can also request an extension from the Vulnerability Response Workspaces. For more information, see Request an extension for a deferred vulnerable item in the Vulnerability Manager workspace.
Procedure
-
Navigate to .
-
Open a deferred remediation task.
-
Select Request Extension.
-
Fill in the fields on the form, as appropriate.
| Field |
Description |
| Extend Until |
Select the date when the Defer state expires and the remediation task is reactivated. |
| Reason |
Enter the reason for deferring the issue. Choices include:
- Awaiting maintenance window
- Fix unavailable
- Risk accepted
- Mitigating control in place
- Other
|
| Additional information |
Enter any other relevant information. |
-
Select Request Approval.
On approval of the request, the changes on the remediation task are rolled down to the application vulnerable items as well, which are part of the remediation task. However, the application vulnerable items should be
in the deferred state and their current until data precedes the updated until date. An email is also triggered on submission of the request and subsequent action by the approver.
Note:
- The request goes through two levels of approval.
- The Request Extension button is unavailable for remediation tasks that are created as part of an exception rule.
- If a deferred remediation task is extended again, the extend deferral count increases in the backend.