Take Action on Your Findings

Required User Role: Administrator

On the Findings page, you can select any number of findings on which you want to take action by creating a ticket or sending an email. A ticket can be used to track the remediation effort for the finding or findings; an email provides a one-time snapshot of the finding data for recipients who may not use Jira or ServiceNow.

Tickets and emails created from the Findings page are considered "manual," because they do not currently support the automated status updates available through an initiative's ticketing automation.

Take Action on your Findings in Seconds with Tenable Hexa AI

Did you know that you can use Tenable Hexa AI to create a ticket or send an email for you? Simply click the button in the upper-right corner of any page to open the Hexa AI panel.

For example, you can ask Tenable Hexa AI to create a ServiceNow ticket for a specific finding:

For more information about using Tenable Hexa AI, see the following topics:

• Use Tenable Hexa AI via User Interface

• Use Tenable Hexa AI via MCP Server

Create Tickets Manually

To create a manual ticket from the Findings page:

1. Access the Findings page.

2. Manually select up to 200 findings.

   1. In the row for the finding(s) that you want to select, click the check box(es).

   2. In the action bar, click the check box.

      You will see [number][findings_type] selected, based on the current number of items per page displayed.

      Tip: You can modify the number of items displayed in the table on a single page. For more information, see Workbench Tables.

3. In the action bar, click Take Action.

   A drop-down menu appears.

   

4. Select one of the following options:

   • Create Jira Ticket — Create a manual Jira ticket directly from the Findings page. This is useful when you want to track and assign remediation work using your team's existing Jira projects and workflows, or when you want to open a one-off ticket outside of an initiative's regular ticketing automation schedule.

     Important! You must have a Jira Cloud configuration enabled to perform this action. For more information, see Configure Jira.

     1. Configure the following options:

        Option	Description
        Action to Perform	Select how you want Tenable One Vulnerability Management to aggregate tickets for the finding: New ticket for every new finding — Every time a finding appears, a new ticket gets created in Jira. New findings create subtasks on an existing ticket — Every time a finding appears, a subtask gets created on an existing Jira ticket.
        Project	The Jira project in which you want tickets to be created. Important: You must have at least one Jira project for the configuration to function as expected.
        Existing Jira Ticket (optional)	Select the existing Jira ticket from the drop-down list. Note: You see this option only if you choose New findings create subtasks on an existing ticket.
        Work Type	The specific type of issue created, for example, Story, Task, or Bug.
        Summary	The Jira Summary combines the finding name, asset name, and this text to create a descriptive ticket title.
        Description	A detailed explanation of the issue, context, and steps to reproduce (if applicable).
        Priority	The relative importance or severity of the issue. Default value: Default Mapping. Note: Leave this set to Default Mapping to allow the priority to be set by the finding severity based on your Jira instance configuration. For more information about overriding this severity, see Configure Jira.
        Reporter	The user who created the issue and submitted it to the project.
        Assignee	The user to which the ticket or subtask is assigned in Jira.
        Parent	The larger issue (for example, an Epic) under which the current item is nested.
        Labels	Custom tags you want to apply to the ticket for flexible categorization and filtering.

   • Create ServiceNow Ticket — Create a ServiceNow incident directly from the Findings page. This is useful when you want to track and assign remediation work using your team's existing ServiceNow incident management workflows, or when you want to open a one-off incident outside of an initiative's regular ticketing automation schedule."

     Important! You must have a ServiceNow configuration enabled to perform this action. For more information, see Configure ServiceNow.

     1. Configure the following options:

        Option	Description
        Action to Perform	Select one of these two options: New incident for every new finding Every time a finding appears, a new incident gets created in ServiceNow. New findings create subtasks on an existing incident Every time a finding appears, a subtask gets created on an existing ServiceNow incident.
        Existing ServiceNow Incident (optional)	Select the existing ServiceNow incident from the drop-down list. Note: You see this option only if you choose New findings create subtasks on an existing incident.
        Caller	The user who originally reported or requested the issue.
        Assignment Group	The team or group responsible for managing and resolving the ticket.
        Assignee	The individual user currently responsible for resolving the ticket.
        Category	A high-level classification of the issue or request, for example, Hardware, Network, Software.
        Subcategory	A more detailed breakdown within the selected Category, for example, Laptop, Wireless, OS.
        Impact	The measured effect this issue has on the business process or service. Values are Default, High, Medium or Low. Note: Set this to Default to allow the finding severity to set the impact based on your ServiceNow instance configuration. See Configure ServiceNow. You can override it here.
        Urgency	The speed required to resolve the issue, based on business needs. Values are Default, High, Medium or Low. Note: Set this to Default to allow the urgency to be set by the finding severity based on your ServiceNow instance configuration. See Configure ServiceNow. You can override it here.
        Tags	Any tags or labels you want to apply to the incident.
        Short Description	This value is appended to the name of the finding.
        Description	Additional descriptive information for this incident.

   • Send Email — Email findings as a password-protected attachment directly from the Findings page. This is useful when you want to share findings with a team that does not use Jira or ServiceNow, or when you want to send a one-time email outside of an initiative's regular ticketing automation schedule.

     Important! You must configure your email allow list for the users to which you want to send the information.
     Note: You can include up to 5MB of findings in a single email. If you select more than 5MB of findings, Tenable One Vulnerability Management sends multiple emails, each containing up to 5MB of findings.

     1. Configure the following options:

        Option	Description
        To (required)	Select one or more recipients from your organization's Email Allow List.
        CC (optional)	Select one or more additional recipients from your organization's Email Allow List.
        Subject	Tenable One Vulnerability Management generates a default subject line based on the finding data. Optionally, type your own subject.
        Message (optional)	Type a custom message to include above the finding summary in the email body.
        Attachment Format	Select CSV or JSON as the format for the findings data attachment.
        Columns	Select the finding fields you want to include as columns in the attachment.
        Password (required)	Type a password to encrypt the attachment. Tenable One Vulnerability Management zips and password-protects the attachment using this value. Important!Tenable One Vulnerability Management does not send the password to recipients. You must share the password with your recipients separately, outside of Tenable One Vulnerability Management.

5. Click Create or Send Email.

Tenable One Vulnerability Management creates the ticket based on the selected finding data. It can take up to 10 minutes to see the updated ticket information in both Tenable One Vulnerability Management and the selected ticketing system. If you sent an email instead, Tenable One Vulnerability Management creates one record for each finding included in the email. It can take up to 10 minutes for the email to be delivered.