| 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. |
...
Auto-discovery of Jira issues related to specific CMDB CIs
Creation and updating of Jira issues when specific criteria are met (e.g., new incident, policy violation, vulnerability scan, etc.)
Configure auto-discovery of Jira issues in Cloudaware CMDB
Add Jira account to Cloudaware
Log in to Cloudaware account → Admin.
Find Jira Accounts & Actions in the list of Cloud Integrations. Click +Add.
Fill out the form:
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)
...
Retrieve issues for the last - select a time period from the drop-down list
Trust Certificate - check this check box only if 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.
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
...
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
Grant Cloudaware the
user/project: ADD_COMMENTSpermission.Log to the Cloudaware account and navigate to Setup → Objects.
Select the object for which Jira issues should be created for (in this example, CloudAware Vulnerability Scan).
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. |
...
Set up Cloudaware workflows to create issues and post comments in Jira
| Anchor | ||||
|---|---|---|---|---|
|
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 sample | Cloudaware comment 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':
In your Service Desk project select Project settings → Automation.
Select Add rule.
Select Custom rule from the list, then select Next.
Give your custom rule a name and a description.
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 | ||||
|---|---|---|---|---|
|
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.
...