JIRA

The integration with Jira enables users to create templates defining the layout and creation of Jira issue tickets. The Jira Cloud and Jira Server apps for ThreatConnect Playbooks to manage issues and more actions across Jira Cloud and Jira Server. Each app contains the following actions:

• Create Issue
• Get Issue
• Update Issue
• Add Issue Attachment
• Add Issue Comment

This listing can be found in the ThreatConnect App Catalog under the name Jira Core.

The integration with Jira enables users to automatically get, create, or add attachments/comments to Jira Service Desk Requests. Now you’re able to manage any Jira Issue or Service Desk Request— built-in or custom — as part of a ThreatConnect Playbook. Repeatable and mundane tasks like copy and pasting information from ThreatConnect to Jira or opening a Jira issue can now be completely automated. Each app contains the following actions:

• Get Service Desk Request
• Add Service Desk Request Comment
• Create Jira Service Desk Request
  • This component will allow a user to create a Jira Service Desk Request. This can be useful for tasks such as opening up tickets for asset changes as part of an investigation or remediation.
• Add Service Desk Request Attachment
  • This component will allow a user to create an attachment to be added to an existing Jira Service Desk Request. It also allows the user to define the attachment visibility to either public or private (setting attachment visibility is dependent on the user's permission. For example, Agents can create either public or internal attachments, while Unlicensed users can only create internal attachments, and Customers can only create public attachments). Additionally, a comment may be provided which will be added to the attachment.

This listing can be found in the ThreatConnect App Catalog under the name Jira Service Desk.

The Polarity - Jira integration allows users to get a quick understanding of what is in their Jira ticketing system. The integration will query different indicators (IPs, hashes etc) and even Jira ticket numbers so analysts will quickly know the status of a ticket or how many tickets are related to different indicators.

Examples

Jira Data Overview

• Summary Tags: Quickly understand if there are associated tickets about an indicator. If it is a ticket indicator, quickly know the tickets status, ticket type and who it is assigned to.
• Ticket Information: Get a quick understanding of the tickets details from the status, reporter to labels and description about the ticket. Enabling a quick analysis of the different tickets.