Prerequisites
Before you begin, ensure you have completed the following prerequisites.
Jira
Before you create tickets within Jira via Tenable products, you must have the following:
-
A Jira user with the following permissions:
Jira Permission
Purpose in Exposure Response Custom Context Atlassian Documentation "ASSIGNABLE_USER" User Validation Ensures the dedicated integration user is a valid assignee within the project, which is often a prerequisite for using "ASSIGN_ISSUES". Assignable User Permissions "ASSIGN_ISSUES" Work Assignment Allows the integration to assign the newly created ticket to the designated user or group specified in the Initiative configuration. Assign Issues Permissions "BROWSE_PROJECTS" Visibility Allows the integration to read and confirm the existence of the configured Jira project and its Issue Types. Browse Projects Permissions "CREATE_ISSUES" Ticket Creation Required to automatically generate new tickets for findings that match the Initiative's criteria (the "combination").
Create Issues Permissions "EDIT_ISSUES" Status Synchronization Enables Tenable to update key fields, push risk data (like VPR), and change the ticket status (e.g., from Resolved to Resurfaced). Edit Issues Permissions "LINK_ISSUES" Audit Trail Creates the essential link between the Tenable finding and the corresponding Jira ticket, enabling the Ticket Log functionality. Link Issues Permissions -
A Jira project with the following fields enabled for issues:
Important: You must have at least one Jira project for the configuration to function as expected.-
"priority",
-
"assignee",
-
"labels",
-
"summary",
-
"description",
-
"issuetype",
-
"parent",
-
"project",
-
"reporter" — To use this field, the user must also have the "MODIFY REPORTER" permission enabled.
Tip: In Jira, navigate to Settings > System > Admin Helper > Permission Helper to confirm or provision the permission for the user.
-
For more information about Jira configuration, see the Tenable for Jira Cloud Integration Guide.