Approve or reject requests in the Security Exposure Management Workspace
- UpdatedJul 31, 2025
- 3 minutes to read
- Xanadu
- Unified Security Exposure Management (USEM)
Approve or reject requests that are submitted by remediation owners.
Before you begin
Roles required:
| Approval type | Approval levels required | Approver roles | Additional information |
|---|---|---|---|
| False positive approvals | One |
Or Approvers are required to be in the False Positive Approver user group. |
- |
| Exception approvals (deferrals) | Two |
|
An exception request for a record or remediation task is approved by using a default, two-level approval workflow. The exception request requires two levels of approvers. After the request is approved by the level 1 approver, it’s sent on to the second-level approver and is then visible in approver 2's queue. |
| Unassign approvals | One approver is required in the Approver – Level 1 group |
|
Note: By default, an approval configuration is provided and an unassign approval group is created. Users (Unassign Approver - Level 1) of this group can approve the request. This group contains an unassign
approver role, sn_vul.unassign_approver, by default. You can modify or create a new group and update the approval configuration. To configure approval rules, navigate to the respective Approval Rules module,
select any of the following approval rules, and navigate to the approval configuration in the Approval Configurations tab:
|
| Risk reduction approvals | Two |
|
The approval flow for risk reduction is same as the exception approvals (deferrals). |
See Vulnerability Response personas and granular roles and Assign the Vulnerability Response persona roles using Setup Assistant for more information about assigning persona roles to users and users to groups.
Note: Add users to the approval groups before you submit approval requests. If you create requests before you add users to the approval groups, the requests might not be visible to those users that have the approval
permission.
Procedure