| Table of Contents |
|---|
...
You can connect the Prism Platform with a Jira instance, enabling you to raise tickets within your Jira environment straight from the Prism Platform. This ensures that issue data in the Prism Platform and your Jira environment remain synchronised.
Once a Jira ticket is moved to ‘Done’, the status for the corresponding issue in the Prism Platform will be automatically marked as Remediated. This process eliminates the need to update the status of an issue in two places.
Integration Overview
The Prism Platform’s integration with Jira utilises Jira’s public API to create and track the status of exported issues in Jira.
| Note |
|---|
Warning! Prism The platform supports the Jira Cloud API v3 only. Any clients with locally installed versions currently only support v2 of this API. This is due to end by 2024 (https://developer.atlassian.com/developer-guide/moving-from-server-to-cloud-for-developers/ ) and will therefore not be supported by Prism the platform for support, compatibility, and security reasons. |
Operation
The Prism Platform & Jira integration is based on a push/pull operation whereby the Prism Platform initiates a connection to Jira to either send data (push) or to retrieve data (pull).
An example of sending (pushing) data is when Prism the platform exports an issue to Jira.
An example of retrieving (pulling) data is when Prism the platform queries Jira for the status of an already-exported issue
| Note |
|---|
Important! Jira does not initiate any communications to the Prism Platform. Any communication between the Prism Platform and Jira is only ever initiated by the Prism Platform |
During the export of an issue from the Prism Platform to Jira, the Prism Platform will retrieve the unique Issue ID and Issue URL that is assigned by Jira (once the issue has been created)
The Prism Platform will associate the Jira Issue ID and URL with the corresponding issue stored in the Prism Platform. This allows the Prism Platform to ‘track’ the corresponding Jira Issue by periodically querying Jira for any status change(s),
When the status of Jira Issue changes to a completed state, such as “DONE” or “RESOLVED”, this change will be detected by the Prism Platform during the next periodic status check.
Once a tracked Jira Issue has changed to a completed state, and the Prism Platform has detected this change, the status of the corresponding issue in the Prism Platform will be changed to Remediated.
| Info |
|---|
Please Note: When a Jira Issue is changed to a completed state, this status change is not immediately updated in the Prism Platform - the Prism Platform queries Jira every 15 minutes to check for status changes across all tracked issues. |
| Note |
|---|
Warning! Once an issue has been exported from the Prism Platform to Jira, if the the corresponding Jira Issue is then copied to a new Jira Issue, the Prism Platform will not be able to locate nor track/update the status of the new Jira Issue in the Prism Platform. |
Set Up
Step 1: Navigate to Connected Accounts on the Menu.
Step 2: Click on ‘Configuration’ under Jira.
Step 3: Prism The platform will ask you for the host URL to your JirasubscriptionJira subscription, e.g. https://company.atlassian.net/
...
Once the connection is confirmed, Prism the platform will ask you to correlate Prism’s the platform’s threat levels with your current priority settings within Jira. This will enable Prism the platform and Jira to apply the appropriate priority and urgency to the reporting of issues.
...
You can export issues from Prism the platform to your JIRA project board from the following interfaces of the platform:
...
You will see the following information within Jirafor Jira for the exported issue:
Link to Prism the platform issue
Finding Title
Summary
Technical Details
Recommendation
Priority levels (assigned at setup by the user)
Prism Platform labels for ease of tracking (example: prism_High, prism_import)
Reporter details
Export Issues in Bulk
...
You can then see which issues have been exported to Jira:
Jira Issue Status
Prism The platform provides you with near real-time updates of the progress of each issue that has been exported to Jira. You can find a Jira Ticket dialog to the top right-hand corner of the corresponding Issue interface in Prismthe platform, which displays the current status of the Jira ticket.
Prism The platform will track your Jira tickets progress and automatically mark an issue as remediated when the Resolution date and status of the ticket id set to Done.
| Note |
|---|
We are aware of a discrepancy when using business projects within Jira. Currently, at the time of writing, Jira is not setting the Resolution Date of tickets marked as done within these project types. there are some workarounds detailed here (https://community.atlassian.com/t5/Jira-Software-questions/How-to-set-Resolution-time-for-Business-Project/qaq-p/2013257 ) to assist in setting this in order for Prism the platform to update. |
Regress Issues
You can regress items via Jira if the vulnerability status is ‘unverified remediation’.
This means, if issues have been marked as ‘done/resolved’ within Jira by accident, they can be moved back to ‘in progress’, and Prism the platform will be updated.
When a ticked is closed or reopened in Jira, a comment is added to Prism’s the platform’s respective vulnerability, so you are able to track for auditing and remediation purposes. For example, the comment will refer to the issue being set as remediated via Jira.
Export a Host to Jira
You can export an affected host to Jira.
Step 1: Navigate to Results on the Menu, and then Issues.
Step 2: Select an Issue.
Step 3: Under ‘Affected Hosts’, select the three-dots button next to the host you would like to export.
Step 4: Select ‘Export Jira…’.