Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

When will support be available for (Cloud) integration with Jira Cloud

Currently Tenable Nessus integrates only with the On Prem version of Jira. When will this support be available for Jira Cloud?

6 answers

There is a solution, here is the link to it

anything new about this  ?

Hello, has there been any movement on this since last year. we have Jira cloud and and would really benefit from being able to track in Jira. 

This has been an issue for over a year now. Luckily 2U Inc just open sourced their integration. It allows you to use AWS Lambda or Jenkins to integrate between Tenable cloud and Jira Cloud. Not as ideal as a tenable plugin for jira cloud, but better than no integration at all.

It's been going on like this for 8 month, there is a Tenable-Cloud plugin for On-Prem Jira, but no integration for Jira-Cloud. Unless I am very much off here this looks like a Jira Cloud issue in one way or the other. Tenable seems to have the technology ready, it could be they use ways not supported on Jira Cloud - but this is a product feature issue of Jira unless Tenable is really screwing things up here. I assume it is the sync that blocks because Atlassian will not want to host the sync process on their servers, but Tenable might have only implemented a sync and push feature. I'd be glad to offer our services (professional cloud service operations) for hosting the sync component as add-service in between the two companies if that helps.

We are considering this a blocker to not move our security management processes to Jira and this reduces budget for Cloud Jira since the security department spends their budget elsewhere. 

Did you ask Tenable? It their task to connect to Jira Cloud...



Tenable said it was Atlassian holding them up. Finger pointing?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events