Cloudaware offers several key capabilities of integrating with Atlassian JIRA:
...
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
...
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
...
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 |
|---|---|
 |  |
...
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*
...
Follow these steps to configure automatic update of fields Object Type and Object Identifier.
Object Type
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).
Create a custom text field 'Object Type'.
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.
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'
The automation summary will look the following:
Object IdentifierTo populate this field, ensure that fields indicating the resource ID are created (e.g. AWS EC2 Instance ID, AWS IAM User ARN).
Create a custom text field 'Object Identifier'.
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.
Specify:
7.1. WHEN: Issue created
7.2. THEN: Edit issue fields. Paste the following condition as the value of the field 'Object Identifier':Code Block {{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)
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.