Cloudaware offers several key capabilities of integrating with Atlassian JIRA:
Autodiscovery of issues related to CMDB objects and importing them from JIRA to Cloudaware
Creating a JIRA issue whenever any specific criteria is met in Cloudaware (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.)
| Table of Contents |
|---|
Configuring Autodiscovery of JIRA Issues and Importing to CMDB
Adding JIRA Integration to Cloudaware
Cloudaware can discover JIRA issues and automatically add them to the corresponding CMDB objects.
...
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
...
Adding Custom Fields to JIRA
For Cloudaware to associate a JIRA issue with a CMDB object, a JIRA issue should have two custom fields:
...
Add these two fields to JIRA issues using instructions provided by Atlassian here. It's possible to set the values for these fields manually or using internal JIRA processes.
Сonfiguring Automatic 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.
Let's review the following use case. Your company's seсurity team wants a JIRA issue to be created in a specific project every time when a high risk vulnerability is found by Cloudaware. However, in order to avoid lots of manual work with checking and closing JIRA issues, they also need to be notified if a vulnerability has been recognized as fixed. A comment posted to the issue may be a good marker for bulk closing tickets.
Manage Permissions and Create Fields in JIRA
1. Grant Cloudaware with user/project: ADD_COMMENTS permission (see JIRA documentation).
2. Log in to Cloudaware account → Setup → Objects.
3. Select an object you want JIRA issues to 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. In our use case we are using the following fields: Priority, Risk, Severity, CVSS Number, Host, Port, Protocol, Description, Disappearance Time.
| Note |
|---|
Use Cloudaware Field Label names when creating fields in your JIRA as fields names MUST match. |
Setting Up JIRA Notification Integration in Cloudaware
| Anchor | ||||
|---|---|---|---|---|
|
...
Field List - determine the fields you'd like to be displayed in a JIRA issue and Cloudaware comment.
| Note |
|---|
Use API Names of fields. The integration must have all fields you are planning to use in notifications. The sequence you choose for the fields' order will be reflected in a JIRA issue. |
...
4. Click Save.
5. Copy and save the URL as it is required for further configuration in Cloudaware.
...
Configuring Cloudaware Workflows to Create Issues and Post Comments in Jira
| Anchor | ||||
|---|---|---|---|---|
|
Having one JIRA Notifications Integration configured, 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:
...
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.
JIRA issue sample | Cloudaware comment sample |
|---|---|
 |  |
...
JIRA issue sample in Cloudaware CMDB |
|---|
 |
Bulk Closing Issues with Cloudaware Comments in JIRA
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"
...
Populating Custom Fields in JIRA*
| Anchor | ||||
|---|---|---|---|---|
|
...