Jira Accounts & Actions

To see how Cloudaware seamlessly integrates with Jira in action, request a demo.

Introduction

Cloudaware offers several key capabilities of integrating with Atlassian Jira:

• Auto-discovery of Jira issues related to specific CMDB objects and importing them from Jira to Cloudaware

• Creating 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, e.g. new vulnerability has been detected as fixed, etc.

Configure auto-discovery and import of Jira issues to 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.
   
   

   Open

   

    

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

   Open

   

    

3. Fill out the form:
   
   

   WHERE
   *URL - Jira URL in the format https://jira.companyname.com
   **Password - Jira password (for cloud version of Jira, use a token)

***Trust Certificate - check this 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 format https://tunhub.cloudaware.com:12345)

Click Save.

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

Add custom fields to Jira

Cloudaware will automatically associate discovered Jira issues with corresponding CMDB objects using custom fields. 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 an outbound message to Jira whenever a specific criteria is 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 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.

Set up Jira Actions integration in Cloudaware

1. Log in to Cloudaware account → Admin.
   
   

    

2. Find Jira Accounts & Actions in the list of Cloud Integrations, click N CONFIGURED*.
   
   

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

    

4. Fill out the form:
   
   

   WHERE
   Name - name for your Jira action
   Jira Account - select the pre-configured Jira account
   Project - select your Jira project issues will be created in
   Issue Type - select the issue type (managed in your Jira)
   Summary - add summary for your Jira issues. In this example, we use sObject.Name to display full CloudAware Vulnerability Scan name
   Description - add a description that will be added into Jira issue body
   Comment - add a text that will 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.

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

Click Save.

5. Copy and save the URL as it is required for further configuration in Cloudaware.
   
   

Set up Cloudaware workflows to create issues and post comments in Jira

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:

• From Cloudaware Admin go to Setup → Create → Workflows & Approvals → Workflow Rules → New Rule:

• Select the object. In our use case we are using CloudAware Vulnerability Scan. Click Next.

• Add Rule Name, set Evaluation Criteria and Rule Criteria as shown below:

• 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:

• Click Done. Click Activate to activate your workflow.

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

• Go back to Workflow Rules → New Rule.

• Select the object. In our use case we are using CloudAware Vulnerability Scan. Click Next.

• Add Rule Name, set Evaluation Criteria and Rule Criteria as shown below:

• Click Save&Next.

• Add Workflow Action → New Outbound Message:

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.

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

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.

Follow these steps to configure automatic update of fields Object Type and Object Identifier.

Object Type

1. To populate this field, ensure that fields indicating the resource name or ID are created (e.g. AWS EC2 Instance ID, Physical Server, AWS IAM User).

2. Create a custom text field 'Object Type'.

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

4. Select Add rule.

5. Select 'Custom rule' from the list, then select Next. 

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

7. Specify:
   7.1. WHEN: Issue created
   7.2. Choose If/Else block
   7.3. Add the condition, e.g.: 
   
   IF 'AWS EC2 Instance ID' field is not empty then edit 'Object Type' field with 'AWS EC2 Instance'
   IF 'AWS EC2 Instance Name' field is not empty then edit 'Object Type' field with 'AWS EC2 Instance'
   
   

   
   7.4. Add the second condition:
   
   ELSE - IF 'AWS IAM User ARN' field is not empty then edit 'Object Type' field with 'AWS IAM User'
   
   

8. The automation summary will look the following:
   
   

   
   
   Object Identifier

9. To populate this field, ensure that fields indicating the resource ID are created (e.g. AWS EC2 Instance ID, AWS IAM User ARN).

10. Create a custom text field 'Object Identifier'.

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

12. Select Add rule.

13. Select 'Custom rule' from the list, then select Next. 

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

15. Specify:
    7.1. WHEN: Issue created
    7.2. THEN: Edit issue fields. Paste the following condition as the value of the field 'Object Identifier':
    
    

    {{Issue.fields.Custom_Field_name}}

    where Custom_Field_ is the name of the field under question (e.g. AWS EC2 Instance ID, AWS IAM User ARN)
    
    

16. The automation summary will look the following:
    
    
    

     

Once you set the automation for both Object Type and Object Identifier, make sure to add these fields to the Jira issue.