You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm trying to write a more defined approval process for new Add-Ons in our Jira Data Center environment. Assume you're managing an enterprise Jira (Or Confluence) environment, and there is a lot of sensitive IP contained in that Jira or Confluence. When your users request Add-Ons, how do you evaluate you those Add-Ons from a security perspective? What kind of criteria would you want the Add-Ons to follow, and then how would you ensure that new Add-Ons follow that criteria?
At a high level this basically means not wanting Add-Ons to be sending the actual content of our Jira issues or Confluence pages to some outside server somewhere, but I want something a little more concrete and defined than that. What criteria do you all use in your organizations, and how do you enforce it?