Connect and Configure Tenable for Jira Cloud

Required User Role: Administrator

Before you begin:

  • You must have your Tenable Vulnerability Management API keys.

    Note: For your Tenable Vulnerability Management integration:

    • Generate an API key in Tenable Vulnerability Management to complete the configuration.  See the Tenable Vulnerability Management user guide for instructions on how to generate an API key. (Do not use this API key for any other third party or custom-built application or integration. It must be unique for each installed instance of the integration.)

To configure Tenable Vulnerability Management:

  1. Log in to Tenable Vulnerability Management.
  2. In the upper-left corner, click the Menu button.

    The left navigation plane appears.

  3. In the left navigation plane, click Settings.

    The Settings page appears:

  4. In the Integrations section, click the Jira Cloud tile.

    The Jira Cloud - Vulnerability Management page appears:

  5. Click the Configuration button.

    The Configuration pop-up appears. By default, the Request Connection tab is active:

  6. Use the following table to fill in the appropriate Tenable for Jira Cloud options in the Request Connection tab.

    Option Name Description Required
    Jira Cloud URL

    Your Jira cloud instance URL. (For example, yoursite.atlassian.net)

    Note: The integration only supports Jira cloud URLs with a domain ending in *.atlassian.net.

    yes
    Jira Cloud Access Key The Tenable for Jira Cloud integration requires a Site Admin Access Key to create the project, the custom fields, and link all elements to the correct screens. yes
    Jira User Email Address The Atlassian user email of the user whose key is provided in the Jira Cloud Access Key field. yes
  7. Click the Connect button. If your credentials are valid then you are taken to the Set Up section to configure the integration.

    The Set Up page appears:

  8. Use the following table to fill in the appropriate Tenable for Jira Cloud options in the Set Up tab.

    Option Name Description Required
    Set up

    Multiple fields to configure Tenable for Jira Cloud, based on your requirements.

    yes
    Lowest Severity to Store

    The lowest severity for which tickets are created. (For example, if you select Medium severity, the integration creates a ticket of severity Medium, High, and Critical.

    yes
    Sync Since If provided, the integration pulls historic data from that time. The maximum allowed past date is one month. yes
    Asset Tags (Required if Tags are provided) Tickets are only created for assets which include the provided tag. yes
    Default Assignee If selected, all the tickets are assigned to the selected user. If not selected, the Tenable for Jira Cloud user who configured the integration is used by default. yes
    Select Project

    You can create a project by providing a unique name or by selecting a project already created in Tenable for Jira Cloud, By default, this integration uses the Business project in Tenable for Jira Cloud. For more information about project types, see Product Features and Project Types in the Atlassian documentation.

    Note: This integration supports classic (Company-managed) Jira projects, You must create a Company-managed project and select that project in this field.

    yes
    Default Reporter

    If selected, the selected user is used as the default reporter on all tickets, If not provided, the Tenable for Jira Cloud user who configured the integration is used by default.

    Note: You must have appropriate permissions to assign the default reporter. If not, the Default Reporter is not assigned.

    yes
    Project Lead The lead user for the project. yes
    Group by You can group tickets by either Asset or Vulnerability. yes
  9. Click Save to complete the setup.

What to do next:

Tenable for Jira Cloud creates a "Tenable Vulnerability Workflow" to manage the transition of the Jira tickets. It may take several minutes to setup projects and custom fields in Tenable for Jira Cloud. Details are automatically refreshed on-screen once they are created. As soon as this integration is saved, Tenable for Jira Cloud starts listening to new findings discovered by the scans, providing near real-time vulnerability data into Tenable for Jira Cloud. When Tenable for Jira Cloud starts creating tickets, the "Waiting for ticket creation on Jira instance" notification banner is removed.

Once the integration is saved, the integration starts listening to new findings discovered by the scans, providing near real-time vulnerability data into the Jira cloud. Next, Tenable for Jira Cloud fetches metrics and shows them on the Tenable for Jira Cloud dashboard, as shown in the following image: