Starting with Vulnerability Response v15.0, use the flow designer to approve exception requests for exception management, exception rules, and false positive management. If you are deploying Vulnerability Response (VR) for the first time, the flow designer is enabled by default.

Before you begin

Role required: sn_vul.vulnerability_admin

About this task

If you are an existing VR user, the default option is workflow.

If you have deployed Vulnerability Response v15.0 or later, the value of the system property sn_vul.flow_designer_activation is set to true. This means that the flow designer is enabled by default.

If you are already using Vulnerability Response prior to v15.0, the value of this system property is set to false. You can activate the flow designer by changing the value to true.
Note: You cannot revert to using the workflow after activating the flow designer. For a detailed comparison between the workflow and flow designer, see Exception management workflow versus flow designer.

To use the flow designer, create rules using the Approval Rules module. Using this module, you can configure approval rules for each of the following exception management workflows.

  • Exception request for remediation tasks
  • Exception request for vulnerable items
  • Exception rule
  • False positive for remediation tasks
  • False positive for vulnerable items
Note: You can also define conditions containing multiple levels of approval within a rule. The flow designer automatically inherits the rules created in this module and processes the matching approval workflow. For information on configuring approval levels, see Create approval levels for Exception Management.

Procedure

  1. Navigate to All > Vulnerability Response > Administration > Approval Rules.
  2. On the Approval Rules page, select the group for which you want to set the approval rule.
  3. On the form, fill in the fields.
  4. Select Update.
    In the Approval Configurations tab, there are two levels of approvers set up by default. You can select a rule to define the conditions based on different use cases within a rule. For more information, see Create configurations for an approval rule.
    Note: In each configuration page, you can create multiple approval levels. For more information, see Create approval levels for Exception Management.

Example

Based on different use cases, you can define different approval processes for the same vulnerabilities found on different configuration items.