Assign an Issue to a User or Team

Overview

You can assign issues to users or teams straight from the platform to help delegate tasks and keep track of who’s handling what.

Since an issue could affect more than one instance (e.g. a host, web application or TCP/UDP port), the platform allows either an issue to be assigned in its entirety (including all affected instances) or assign specific affected instances of an issue. This is useful if affected instances of an issue are managed by multiple different user or teams.

An email alert will be sent to the user when you assign an issue to them. Users can manage these notifications in the User Management section.

• Issues can be assigned from within a Phase/Scan or via the main Issues view under Results.

• Affected Instances of an Issue can only be assigned from within the Issue in question

Assigning an Issue and all Affected Instances

In this example below, the Apache Log4j issue affects 4 different assets/hosts. If a single Platform user or team is responsible for remediating all affected instances, then the entire issue can be assigned to those users or teams.

Open

Open

Assigning only Affected Instances of an Issue

To assign specific affected instances of an issue, you must first be in the Single Issue View to identify the affected instances. Use the action button to the right of the affected instance in question. In the pop-up window then select or user(s) or team(s).

Displaying User Assignment for Issues

You can see which users have been assigned to issues within the Phase/Scan by clicking on the cog and selecting ‘Assigned User’ under “Issues Overview” tab:

You can also see user assignment information in the Issues interface (select Results from the menu, then Issues), again by clicking on the cog.