Configure Jira

The following is not supported in Tenable FedRAMP Moderate environments. For more information, see the Tenable FedRAMP Product Offering.

Required User Role: Administrator

Before you can create Jira tickets within Tenable Vulnerability Management, you must configure your Jira account.

Prerequisites

Before you begin, 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.

Configure the Integration

To configure Jira to support Jira issue creation in Exposure Response:

1. In the left navigation, click Settings.

   The Settings page appears.

2. Click the Jira Cloud tile.

   

   The Jira connector page appears.

3. Configure your Jira Cloud Credentials:



Option	Description
Integration Name	Choose your own Jira integration name.
Jira Cloud URL	The unique web address for your organization's instance of Jira Cloud, typically formatted as https://[your-company-name].atlassian.net.
Jira Cloud User Account	Your individual credentials (email and password) used to authenticate and access your organization's Jira Cloud site.
Jira Cloud API Token	Your API key or token for authenticated access to the Jira Cloud API.

4. To test the connection, click Connect.

   

   Once Tenable validates the integration connectivity, a Connection was Successful notification appears.

   

5. Configure the following default values for each Jira Project:



Set the following options.

Option	Description
Project	The Jira Project name that these options relate to.
Default Assignee	Assign a user as a default assignee from the drop-down list.
Default Reporter	Assign a default reporter value from the drop-down list.
Default Label(s)	Your organization's Cloud URL.
Sync Jira Priorities	Create a mapping of Tenable findings severities (for example, Critical, High, Medium, Low, Info) to Jira Priorities (for example, Highest, High, Lowest).

6. To set default values for additional Jira projects, click Add Another Project.
Note: To delete project configurations click the next to the corresponding project.
7. Click Save.