welcome totenable for Jira Cloud

Last Updated:December 09, 2024

The tenable for Jira Cloud integration provides you with the organizational convenience of managing vulnerabilities detected intenable Vulnerability Management from the tenable platform itself. When you configure the tenable for Jira Cloud integration , custom field are create intenable for Jira Cloud. The integration uses these custom fields to organize and manage vulnerabilities detected when running vulnerability scans.

• tenable for Jira Cloud pulltenable Vulnerability Management vulnerability data, then generates Jira tasks and linked tasks based on the vulnerability’s current state. Tasks are automatically closed once the state of the vulnerability is marked as Fixed intenable Vulnerability Management.

• tenable for Jira Cloud creates a tenable Vulnerability Task for each vulnerability and create each vulnerability instance as a ” link task . ” For example , if you is have have five host with plugin 151074 on aGroup – by vulnerability, the integration creates one tenable Vulnerability Task with the detail for that specific plugin and create five link task . Each is linked link task point to a specific instance of the vulnerability , on a specific host .

• tenable for Jira Cloud automatically closes Vulnerability Instances once the vulnerability is fixed intenable Vulnerability Management.

• vulnerability are close once all link task enter a closed state .
• If a vulnerability is reopened, tenable Vulnerability Tasks are moved to the Reopen status.

• All data imports from tenable Vulnerability Management are sync withtenable for Jira Cloud after the scan gets completed. Vulnerabilities are available intenable for Jira Cloud after scan completion and some processing time

The tenable for Jira Cloud integration can pull historic findings as well as new findings as they get discovered by the platform and creates Jira issues for each vulnerability inthe project that you specify. The integration creates Jira tickets according to the following scenarios:

Group By Vulnerability

• For every vulnerability plugin , the integration is creates create a vulnerability issue .

• For every affected asset, the integration creates a vulnerable host issue and a blocking link to the related vulnerability issue. A linked issue is created under the vulnerability task.

• As assets are remediated, vulnerable host tickets are marked as resolved.

• If all vulnerable host issues related to a vulnerability issue are marked as resolved, the vulnerability issue is marked as resolved.
• If an asset is found to have a vulnerability again, but was previously resolved, the integration reopens the vulnerable host issue.

• If a vulnerability issue is mark as resolve and a new vulnerable host issue is link to it ( or a prior vulnerable host issue that was resolve ) the vulnerability issue is reopen .

• All historic data imported from tenable Vulnerability Management use thelast_found field. This ensures that all issues are updated whenever new information becomes available.

Group By Asset

• For every host , a vulnerability host issue is create .

• For every reporting plugin, the integration creates a vulnerability issue and a blocking link to the related vulnerability host issue. A linked issue is created under the vulnerability host task.

• As findings are remediated, vulnerability issue tickets are marked as resolved.

• If all vulnerability issues related to a vulnerability host issue are marked as resolved, the vulnerability host issue is marked as resolved.

• If a vulnerability issue is find to have a vulnerability again , but was previously resolve , the integration is reopens reopen the vulnerable issue .

• If a vulnerability host issue is marked as resolved and a new vulnerable plugin issue is linked to it (or a prior vulnerable plugin issue that was resolved) the vulnerability issue is reopened.

In tenable Vulnerability Management, the vulnerability issue and vulnerable host issue titles are automatically generated using the following formula: