Associate a remediation task to an existing change request
As a Appsec Manager or Security Champion, avoid creating duplicate change requests (CHG) as you work to resolve your remediation tasks by associating a remediation task (APP-VUL) to a change request that is already available in your instance.
Before you begin
Roles required:
From Vulnerability Manager Manager Workspace: sn_vul.app_sec_manager.
From ITRem Owner workspace: sn_vul.app_sec_champion or sn_vul.app_developer, and itil role.
About this task
As a remediation owner, you can associate remediation tasks that are assigned to you or your assignment group to existing change requests directly from the remediation task records. The following image illustrates the basic flow for associating a change request to an existing APP-VUL (VG).
Before you begin, to avoid creating duplicate change requests, you might prefer to view any existing change requests already associated with a APP-VUL. To easily track the number of change requests that are related to a specific APP-VUL, refer to the CR count column on the Remediation Tasks list. If not displayed, click the settings icon () in the upper right. Move the CR count column from Available to Selected and click OK.
To automatically populate the new column, for customers with existing data in this table, run the scheduled job: Populate new CR Count Column.
Procedure
What to do next
Review the APP-VUL record. In the Change Request column on the Change Requests related list, click link for the new CHG to view CR record. On the open CHG record, you can monitor the state of the change request. The affected configuration items (CI)s and the remediation tasks are displayed on the Affected CIs and remediation tasks related lists.