Third-Party Integrations
Setting up third-party integrations allows your team to receive updates in your Slack workspace and connect to your preferred GRC tool to streamline information across multiple teams.
1. Slack Integration
To integrate Portal and Slack:
Click the user menu icon in the top right corner of your Portal Dashboard.
Go to “Settings”
Scroll down to the "Integrations" section.
Click on the "Connect Slack Account" button and follow the steps provided by Slack.
You will be redirected back to Portal and will now see settings for Slack notifications under the "Notifications" section within Settings. You can toggle these on/off depending on which ones you want to receive.
You will see the name of your Slack workspace and Slack channel that you have permitted Portal to post messages to under the "Integrations" section.
2. GRC Tools (Vanta and Drata)
To integrate Vanta or Drata to Portal:
Open the user menu icon in the top right corner of your Portal Dashboard.
Go to “Settings” and scroll down to the "Integrations" section.
Click on the "Add Vanta Account" button or "Add Drata Account" and follow the steps provided by your GRC tool.
3. Jira
The Jira Integration is a Premium feature. Please contact sales for more information.
The Jira integration allows you to connect your most important Jira boards directly to Portal, streamlining project management. Automatically create new Jira records from your vulnerabilities, or link your existing records straight to Portal.
To Integrate Jira and Portal:
Open the user menu icon in the top right corner of your Portal Dashboard.
Go to “Settings” and scroll down to the "Integrations" section.
Find the Jira integration and click "Add Jira Account +".
Setup
Step 1: Generate a Jira API key
Login to your Jira account
Click your profile icon in the top right corner, and click "Manage Account" from the dropdown.
In the new window, click on the "Security" tab
Click on "Create and manage API tokens"
Create a new API token with a relevant name, such as "Portal Integration Token". Make sure to set a long expiry, but not too long. We recommend 1 year.
Copy the token for the next step in setup
Step 2: Connect Portal to Jira

In the server URL, enter the domain of your Jira tenant. It usually looks like
<your-company>.atlassian.comEnter your Jira username, and the API Key from the previous step. Click "Next"
Step 3: Select Projects & Board

Select the Jira Project & Board that you would like to connect. Jira records from this board will be used to track vulnerabilities in portal.
Select the Portal project you would like to connect them to.
Step 4: Configure Field Mapping

This is one of the most important parts of the integration configuration. This step allows you to map which fields in portal will be used to populate fields in Jira when creating records. If you already have fields in Jira that match the name of the fields in Portal, they will be automatically mapped. The initial mapping can still be customized by selecting different fields from the dropdown.
Select the record type you would like the integration to use. You can select any record type from your board.
Customize the field mapping if necessary.
Step 5: Review & Enable
Review your integration config on this page, and click on "Finish" to enable the integration.
Jira Integration Usage

1. Create Jira Issues Button
This will use the configured field mapping to create new records in Jira for each of the vulnerabilities you select. These records will be created in your configured Jira board with the default status. Use the multiselect to choose which issues you would like to use.
2. Link Jira Issues Button
This is used to link multiple Jira records to Portal vulnerabilities if you have already created records to track your vulnerabilities. By using a custom UID field to indicate which Jira record maps to which Vulnerability, you can connects all of your records in one click.
Select which vulnerabilities you would like to link using the multiselect.
In the modal, select which field in your Jira records contains the issue UID (Ex. FZBZ001). This can be any field that contains the UID, it doesn't have to be a field that has only the UID. For example, if your record titles already contain the UID you can use the title.
Click "Next"
Review the valid mappings that portal identified. If there are mapping issues, make sure to resolve any UID mismatches in your Jira records. If the valid mappings are correct, click finish to link all of your vulnerabilities.
3. Single Vulnerability Link

Each vulnerability in portal can be linked to a Jira record. If the Jira section of a vulnerability shows that it is not connected, click on the "Not Connected +" text to link the vulnerability. Simply select the Jira record you would like to link from the dropdown.
Last updated
Was this helpful?

