In this article you will find:
- Pre-requisites - Permissions
- How to define Jira connector in Vulcan
1. Pre-requisites - Permissions
To Integrate into JIRA, the user can choose between 2 optional sets of permissions on the JIRA:
- Admin permissions - highest permission covers all the needed functionalities.
- Project Labels (Optional) - Vulcan uses labels in order to mark the related tickets to a specific web-hook, so if you need 2 way updates for your tickets, your projects must support labels.
- Configure a set of permissions based on the following details:
Ability to browse projects and the issues within them.
Users with this permission may be assigned to issues.
Ability to assign issues to other people.
Ability to create issues.
Ability to edit issues.
Ability to resolve and reopen issues. This includes the ability to set a fix version.
Ability to comment on issues.
Users with this permission may create attachments.
Detailed API calls used
Use in Vulcan
Check Current User permissions
Permission to access Jira
List Project available to open tickets in
Projects are returned only where the user has Browse Projects or Administer projects
List users available as assignees in the different projects
List the different fields available to create an issue
Create and update issues
rowse projects and Create issue
Create a webhook to get notified on updated tickets
Only Connect apps can use this operation
Get the current server version
add comments on existing tickets
* Browse projects and Add comments project permission for the project that the issue containing the comment is in. * If issue-level security is configured, issue-level security permission to view the issue
2. Defining a connector
On the Connectors page. click on Add a Connector
Click on Jira Connector
Click on Create
Vulcan Cyber supports both Jira on cloud and On-Premise.
Fill in all the relevant fields, based on your Jira account type.
- Jira Server URL - URL of your organization's Jira account. Relevant for cloud account.
- Username - User with required permissions to access Jira account.
- Password / API Token - Depends on account type, insert Password match to Username, or insert API Token match to Jira Server URL.
- Two Way Jira Integration - Enabling will create webhook in Jira: If a ticket was closed in JIRA, it will be marked as "Done" in the Vulcan campaign.
- Mark Issue as Done - Enabling will allow you to change Jira issue status to closed when a vulnerability is marked as fixed in Vulcan. This applies to both closed a campaign manually or by vulcan detecting the vulnerability is no longer discovered by the scanner thus marking its as fixed.