Versions Compared

Version Old Version 80 New Version Current
Changes made by

Daria Lebedeva

Daria Lebedeva

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

This guide explains how to add a Jira account to Cloudaware and configure actions for Cloudaware to automatically discover Jira issues in the CMDB and/or create issues in Jira based on specified criteria.

...

Cloudaware offers several key capabilities of for integrating with Atlassian Jira:

  • Auto-discovery of Jira issues related to specific CMDB objects and importing them from Jira to CloudawareCreating a Jira issue whenever any specific criteria are met (e.g. new incident, policy violation, vulnerability scan, etc.) and posting a comment to the existing Jira issue, CIs

  • Creation and updating of Jira issues when specific criteria are met (e.g., new vulnerability has been detected as fixedincident, policy violation, vulnerability scan, etc. is found)

Configure auto-discovery

...

of Jira issues

...

in Cloudaware CMDB

Cloudaware can discover Jira issues and automatically associate them with corresponding CMDB objects.

Add Jira account to Cloudaware

...

  1. Log in to Cloudaware account → Admin.

    Image Removed

    Image Added

  2. Find Jira Accounts & Actions in the list of Cloud Integrations. Click +Add.

  3. Fill out the form:

    Image Removed

    WHERE
    *

    Image Added

    WHERE
    Name - a meaningful name for Jira integration, e.g. Prod Jira
    URL - Jira URL in the format https://jira.companyname.com
    **Password - Jira password (for cloud version of Jira, use a token)

Ensure that the user whose credentials are used in the form has the appropriate level of access. All Jira projects that are visible for this user will be collected by Cloudaware.

...

Retrieve issues for the last - select a time period from the drop-down list
Trust Certificate - check this check box only if your Jira runs on a private network and TunHub gateway has been set up by Cloudaware (in this case, the URL will be in the format https://tunhub.cloudaware.com:12345)

Click Save.

  1. The green light in 'Status' means your that Jira account has been successfully added. If there is a red light, please contact support@cloudaware.com.

    Image Added

...

Create custom fields

...

in Jira

For Cloudaware will to automatically associate discovered Jira issues with corresponding CMDB objects using custom fields. Add CMDB CIs, add the following custom fields* in Jira:

  • Object Type

  • Object Identifier

...

Set the values for custom fields manually or using internal Jira processes.

Configure auto-creation of Jira issues from Cloudaware

Cloudaware can send sends an outbound message to Jira whenever a specific criteria is are met, which will automatically create a Jira issue in the appropriate Jira project. Cloudaware can also post a comment to your Jira issue once the conditions that have triggered the ticket creation change.

Use case: A security team needs a Jira issue created for a specific project whenever Cloudaware detects a high-risk vulnerability. The team also requires notifications when a vulnerability is marked as fixed to minimize manual work in checking and closing Jira issues. Posting a comment on the issue could serve as an effective trigger for bulk-closing tickets.

...

Manage permissions and create fields in Jira

  1. Grant Cloudaware the user/project: ADD_COMMENTS permission.

  2. Log to the Cloudaware account and navigate to Setup → Objects.

  3. Select the object for which Jira issues should be created for (in this for example, CloudAware Vulnerability Scan).

  4. Review the section 'Custom Fields & Relationships' to define fields that should be displayed in an issue's description. For our use case, the following fields are used: Priority, Risk, Severity, CVSS Number, Host, Port, Protocol, Description, Disappearance Time.

Note

When creating fields in Jira, use Field Label names from Cloudaware, as fields names must match.

...

  1. Select the tab 'Jira Actions'. Click +ADD JIRA ACTION.

  2. Fill out the form:

    WHERE
    Name - a meaningful name for your Jira action, e.g. New Vulnerability Detected
    Jira Account - select the pre-configured Jira account
    Project - select your the Jira project where issues will be created in
    Issue Type - select the issue type (issue types are managed in your Jira)
    Summary - add a summary for your of Jira issues . In (in this example, we use sObject.Name to display the full name of CloudAware Vulnerability Scan name)
    Description - add a description that will to be added into to the Jira issue body
    Comment - add a text that will to be displayed as a Cloudaware comment

    For our use case, we use sObject.CA10disappearanceTime__c, where CA10disappearanceTime__c is the API Name of the field showing the date and time when the vulnerability was deleted from the scanner.

...

Expression

Output

test

test

sObject.Name

'the name of this field in your org'

'sObject.Name'

sObject.Name

'Hey, ' + sObject.Name

Hey, 'the name of this field in your org'

Field List - determine list the fields you'd like to be displayed in a Jira issue and Cloudaware comment.

Note

Use API names for fields. The integration must include all the fields you plan to use in notifications. The order you choose for the fields will be reflected in a Jira issue.

...

Set up Cloudaware workflows to create issues and post comments in Jira
Anchor
workflow-to-create-jira-ticket
workflow-to-create-jira-ticket

Once you have configured Jira Action, set up two different workflow rules － for creating a Jira issue (1) and adding a comment (2).

1. Workflow Rule for Jira issue creation:

...

  • Click Save&Next.

  • Add Workflow Action → New Outbound Message:

Object: CloudAware Vulnerability Scan
Name: Jira Notification: New Vulnerability Detected
Endpoint URL: paste the URL copied from the integration's details

  • Select the fields to be displayed as set up in the Integration details:

...

Note that Name is a mandatory field.

  • Click Done. Click Activate to activate your workflow.

2. Workflow Rule for posting a comment in Jira issue:

...

Object: CloudAware Vulnerability Scan
Name: Jira Notification: Vulnerability Fixed
Endpoint URL: paste the URL copied from the integration's details

  • Select the fields to be displayed as set up in the Integration details:

...

  • Click Done. Click Activate to activate your workflow.

Jira issue sampleexample

Cloudaware comment sampleexample

Jira issue in Cloudaware CMDB (sample)

Bulk close Jira issues with Cloudaware comments

Based on our use case, we can consider all issues with a comment as not requiring further actions since a vulnerability the Jira issue informs of has been fixed.

Follow these steps to configure automatic change of issue status to 'Resolved':

  1. In your Service Desk project select Project settings → Automation.

  2. Select Add rule.

  3. Select Custom rule from the list, then select Next.

  4. Give your custom rule a name and a description.

  5. Configure your rule by defining the WHEN, IF, and THEN fields:
    5.1. When comment added
    5.2. If comment contains This vulnerability is fixed and deleted on
    5.3. Then transition issue to status "Resolved"

...

Populate custom fields in Jira
Anchor
Populating-Custom-Fields-In-JIRA
Populating-Custom-Fields-In-JIRA

This option requires having custom fields Object Type, Object Identifier and fields that were created for Jira actions.

Based on our use case, we can consider having all custom field values populated automatically. This will also provide a great visibility in Cloudaware CMDB as each Jira issue will be linked to a CMDB record.

...