Sending Reports to Jira

Jira is a platform that combines issue collection and agile project management capabilities. You can configure CloudGuard to send findings to Jira with an HTTP endpoint.

To send a report to Jira:

  1. In Jira, create an account.

  2. For this account, create a token for the API requests. For more information on API tokens in Jira, see How to create API tokens in Jira.

  3. In CloudGuard, navigate to Settings > Notifications and click Add Notification.

  4. Enter the applicable options as described in Notifications.

  5. In the Immediate Notification section, select Send to HTTP Endpoint. The set of Endpoint parameters opens.


    1. Below the Endpoint URL, enter your Jira domain URL and select the Jira option.

    2. Set Authentication Type to Basic.

    3. Below the Username, enter the Jira account email from step 1.

    4. Below Password, enter the API token from step 2.

    5. Click Json Payload. See JSON Payload below for the guidelines on how to enter the data.

    6. To check the template, click the Verify Syntax button.

    7. Below Endpoint URL, click the Test button to check the integration configuration.

    8. Verify that a Jira ticket is created on the specified board.

  6. Click SAVE.

  7. From the Posture Management menu, navigate to the Continuous Posture and set up a Continuous Posture with the Notification created in the previous steps.

JSON Payload

The Json Payload section contains a JSONClosed JavaScript Object Notation. A lightweight data interchange format. template that represents your ticket template in Jira. On the left side, use the expressions from the list on the right. These expressions are replaced with the alert data after evaluation of the cloud entity.

You can fill the built-in Jira fields with values when you add them to the JSON payload (in the API example, Labels takes an array of values). Custom Jira fields are not accessed with their names directly, but through the format “customfield_#####”. For more information, see REST API example.

Important - You must configure:

  • in the project object, the project name for the key parameter

  • in the issuetype object, the ticket type name for the name parameter

(WJIT and Bug in the example below, respectively).