1. Introduction
The Jira integration with Hyver keeps your remediation efforts in sync across both platforms. Findings in Hyver can automatically generate Jira tickets, and updates made in Jira are reflected back in Hyver.
Automatic synchronization – When the status of a Jira ticket changes (for example, marked as Resolved), the corresponding finding in Hyver is updated to match (for example, status set to Fixed).
Ticket creation – Jira tickets can be created automatically when new findings are generated in Hyver, or manually for existing findings.
Seamless workflow – You can manage and track remediation work directly in Jira. Once the work is completed and the ticket is resolved, Hyver automatically reflects the updated status of the related finding.
Integrating Jira with Hyver
Before jumping into the technical setup, it helps to know the basic requirements and the main steps you’ll be following. This will give you a clear frame of reference as you work through the integration process.
2. Prerequisites
Make sure you have the following in place before you begin:
A Hyver Access Token (used for Jira to authenticate with Hyver).
The Hyver URL for authentication.
For Jira Data Center: a personal access token from Jira.
Access to your Jira instance.
Administrator access to Hyver.
Workflow Overview
Setting up the integration involves these main steps:
Authenticate with Jira.
Create an access token for Jira to authenticate with Hyver.
Create a webhook in Jira and provide the access token and Hyver URL.
This establishes the connection and allows status updates to sync between Jira and Hyver.
Map Jira fields to Hyver fields to ensure information flows correctly.
Configure notification rules in Hyver to control which findings create tickets in Jira.
Required IP Addresses
For the integration to work smoothly, you may need to allow traffic from Hyver’s servers in your firewall or network configuration. This ensures that Hyver can securely connect to your environment and perform scans without being blocked.
Depending on your region and the type of scan, add the following IP addresses:
General IPs:
Europe →
18.198.79.197America →
52.1.10.176,35.171.70.87
IPs for Azure and AWS Scans:
Europe →
18.158.77.90America →
34.206.252.13
In most cases, you only need to add the IPs relevant to your region and use case.
Multi-Company Dashboard and Integrations
This section explains how Hyver’s Multi-Company Dashboard works in general, and how integrations behave when used in a Multi-Company setup.
What is the Multi-Company Dashboard?
Hyver’s Multi-Company Dashboard is designed for large enterprises with multiple subsidiaries. It gives you:
A centralized view of cybersecurity risk across the entire organization
Key metrics like exposure, cost of breach, and maturity scores
The ability to switch between subsidiaries and view their individual data
Parent admins and power users can view aggregated and subsidiary-level risk, while detailed findings remain visible only to members of the specific subsidiary
Data that updates in real time
To enable Multi-Company, contact your CYE Technical Account Manager.
How Integrations Work in Multi-Company
Here’s the important part:
Integrations are created only at the subsidiary level
Findings from an integration appear only in that subsidiary’s dashboards and reports
Parent companies cannot create integrations — they can only view the aggregated results
Best Practices for Combining Integrations with Multi-Company
To get the most out of Multi-Company with integrations, we recommend:
Each subsidiary should create its own integration, using credentials that only grant access to data relevant to that subsidiary
In some cases, it’s useful to also have a dedicated “General” company, which holds findings that apply to the entire enterprise and cannot be tied to a single subsidiary
The parent company then combines these insights and metrics from all subsidiaries and the General company — but remember, integrations cannot be connected directly to the parent company.
3. Configuring on the Jira Side
Step 1: Authenticate with Jira
The first step in setting up the integration is authentication.
In Hyver, go to Integrations + Workflows.
Scroll down to the Jira card and click Add:
A setup screen opens. The first step is Authentication (the next step will be field mapping, which we’ll cover later):
Authentication Types
The method you use depends on your Jira installation: Cloud or Data Center (on-premises):
Jira Cloud – Authenticate by providing a cloud access token. This method is straightforward and quick.
Jira Data Center – You’ll need two details:
A personal access token generated by someone with the right permissions in your Jira Data Center.
The Jira URL of your Data Center environment.
Tip: If you’re unsure which method applies, click the small ? icon in the authentication screen for a short explanation.
Once authentication is complete, you can configure notification rules in Hyver to determine when Jira tickets are created (automatically for new findings, or manually for existing ones).
Authentication Methods
Authenticate with Jira Cloud
Use this option if your Jira installation is cloud-based (SaaS).
Click Authenticate and enter your Jira Cloud credentials. The Jira authentication page will open:
Create a dedicated integration user in Jira for this connection. (This user does not need to be linked to a specific person.)
Once authentication is successful, the integration status will be shown in Hyver:
Authenticate with Jira Data Center
Use this option if your Jira installation is on-premises (Data Center).
Enter your Personal Access Token.
Provide your Base Jira URL.
Save the details to establish the connection.
Jira Type | How to Authenticate | What You’ll Need | Notes |
Jira Cloud | Click Authenticate and log in with Jira Cloud credentials. | Jira Cloud account + dedicated integration user. | Integration user should be created in Jira but does not need to be linked to a specific person. |
Jira Data Center | Enter Personal Access Token and Base Jira URL. | Token generated in Jira Data Center + URL of your Jira instance. | Requires setup by someone with access to your on-prem Jira environment. |
Next step: We will immediately proceed to the Create an access token section.
Step 2: Personal Access Token (for Jira Data Center)
If you are connecting Hyver to a Jira Data Center (on-premises) installation, you’ll need to generate a Personal Access Token in Jira and then provide it in Hyver.
Create a Personal Access Token in Jira
Open your Jira Data Center application:
Go to Profile > Personal Access Tokens:
Click Create token.
In the Token Name field, type:
Hyver:
Click Create. A new token key is generated:
Important: The token key is displayed only once. Make sure to copy and save it securely before closing the window. If needed, a user can later revoke or generate a new token.
4. Configuring in Hyver
Add the Token in Hyver
Copy the token key and paste it into the Personal Access Token field in Hyver:
In the Base Jira URL field, enter your Jira server’s URL (for example:
https://jiraserver.hyver-dev.com).
Notes
After configuring either Cloud or Data Center authentication, a Change authentication settings button appears in Hyver. You can use this if you need to update or modify the existing connection:
Next step: We will now proceed to the Create a webhook section.
Create a webhook in Jira
To keep Jira and Hyver findings in sync, you’ll need to create a webhook in Jira. This ensures that when the status of a Jira issue changes, Hyver updates the corresponding finding automatically.
Full Guide (Recommended)
For a complete walkthrough with detailed explanations and screenshots, follow this guide:
Create a webhook in Jira for status sync with Hyver
Once you’ve finished, return here to continue with Step 4.
Quick Instructions (Abbreviated Version)
If you prefer, here’s a short version of the steps:
Generate or copy your Hyver access token
In Hyver, go to Settings > Access Token.
Create a new token, or copy an existing one.
Keep the token value and the following URL handy:
https://customer.hyver-labs.com/api/v1/finding/jira/status
Set up a Jira automation rule
In Jira, go to Project Settings > Automation.
Create a new rule with the following:
Trigger: Field value changed → Status (any change).
Action: Send web request →
URL:
https://customer.hyver-labs.com/api/v1/finding/jira/statusMethod:
POSTBody: Issue data (Jira format)
Header:
Authorization: Token <your-token-here>Enable: Delay execution until response received
(Optional) Add an audit log action to log the webhook response:
{{webResponse.status}}
Limitations
This webhook only updates issues that were originally created by Hyver.
If the Jira issue was not created by Hyver, status changes will not be processed.
Next step: Once the webhook is set up, continue to Step 4: Map Jira fields to Hyver fields.
Map Jira fields to Hyver fields
The goal of this step is to align Jira workflow elements with Hyver so that both systems “speak the same language.”
For example:
Jira status → Hyver status: Open ↔ Open, In Progress ↔ In Progress, Done/Closed ↔ Mitigated/Validated.
Source of truth: You’ll decide which platform governs each field (e.g., remediation status follows Jira, while risk metrics remain Hyver-only).
You’ll need to map the following four main areas:
1. Project Key
The Project Key identifies the Jira project you’re integrating:
It usually appears in the project URL or at the start of an issue key (e.g., in
projects/MCP/boards/8, the project key isMCP):
Copy this key and add it to Hyver’s configuration.
2. Issue Type ID
Jira includes several issue types (e.g., Story, Task, Bug, Epic). Choose the one you’ll use for Hyver findings.
To find the Issue Type ID:
Open the project in Jira.
Go to Manage:
Then:
Hover over the issue type (e.g., Task).
Look at the URL displayed at the bottom of your screen — the ID number in the URL is the value you need (here in the example the value is "10027"):
Copy that ID into the Issue Type field in Hyver:
3. Priority
Priorities in Jira are global categories (Critical, High, Medium, Low, Informative):
To find their IDs:
In Jira, go to Settings > Work Items > Priorities:
The schema lists them in order (1–5 by default). Hyver maps to this default order automatically:
If you create a new priority in Jira, copy its numeric ID from the URL and add it to Hyver:
4. Status
You’ll need to map three statuses: Open, In Progress, and Fixed:
To find the Status IDs:
Use the following Jira API endpoint (replace with your domain):
https://<your-domain>.atlassian.net/rest/api/3/project/<PROJECT-KEY>/statusesSearch the list for the names (“Open,” “In Progress,” “Done/Closed”) using Command-F / Ctrl-F.
Copy the numeric ID shown under each status (not the text label). The numeric value is usually listed beneath the literal “untranslated” name, which makes it easier to identify, as shown in the example image:
If you’ve completed the mapping step, it’s time to make sure everything is working as expected.
Support
If you encounter any issues after completing the mappings, our support team is here to help:
Email: [email protected]
Our team will assist with troubleshooting and technical questions.In-app chat: Click the chat icon on the side of your screen.
You’ll start a live conversation with our smart support bot, which can also connect you to a human agent if needed.
Saving and Refreshing
If the mapping was successful, click Save.
In Hyver, go to the Findings page and refresh the page so it recognizes the new Jira integration.
Synchronization in Action
From here, Jira becomes your main workspace for remediation. Any status updates you make in Jira are reflected in Hyver:
When a Jira ticket is marked as Done, the corresponding Hyver finding is automatically updated to Fixed.
5. Viewing Results
Jira Tickets in Hyver After Mapping
Once the integration is active, Jira tickets are visible and synchronized inside Hyver.
Viewing Ticket IDs
The Integration Ticket ID appears on the project tab in the right pane:
Click the ticket ID link to open the Jira ticket directly.
You can also add a column to the Findings page to display the Integration Ticket ID for each finding.
Viewing and Filtering Jira Tickets in Hyver
On the Findings page, a link to the Jira Ticket ID appears in the right pane.
Use filters on the Findings page to manage tickets:
Without a ticket – shows findings without Jira or ServiceNow tickets.
With a ticket – shows findings that already have Jira or ServiceNow tickets.
Once manual ticket creation is complete, Hyver and Jira remain linked, ensuring smooth synchronization.
Jira Status Changes in Hyver
Any status change in Jira is automatically reflected in Hyver, based on your mapped statuses.
Each change is also recorded in the History tab of the finding:
Status Change Example
When a Jira ticket is marked Done, the linked Hyver finding is automatically updated to Fixed.
The Modification field is updated both on the main Findings screen and in the right pane.
6. Auto-Fix Statuses
Findings Set to Fixed Automatically
Hyver handles updates consistently when Jira status changes trigger a “Fixed” state:
Findings without remediation assets: The finding is marked as Fixed automatically.
Findings with remediation assets: Both the finding and its remediation assets are marked as Fixed.
Mandatory fields are updated automatically.
A comment is added to the finding, for example:
“The status was changed to fixed automatically through the integrated ticketing system.”:
Additional automatic updates include:
User name recorded as Hyver integration.
Date and time of the change.
Maturity level of the finding set to 3.
Sources field updated to indicate Jira integration:
All changes triggered by Jira are recorded in the finding’s History tab for full traceability.
Next step: Once the field mapping is complete, continue to Configure notification rules in Hyver.
7. Types of Fetched Entities
Configure notification rules in Hyver
Hyver’s notification system lets you automatically (or manually) create Jira tickets from findings. This ensures new issues are tracked in Jira without extra manual work.
Automatic Jira Ticket Creation
When a new finding is created in Hyver, you can use Notifications to automatically generate a corresponding Jira ticket.
Important to note: automatic tickets are only created for new findings. Existing findings must be handled through manual ticket creation.
To define a new notification for Jira integration:
In Hyver, go to Settings > Notifications.
Click + New notification to open the setup wizard:
Complete the following fields:
Notification Name – Enter a descriptive name.
Entity – Choose Finding or Remediation assets.
Event – Select the trigger, e.g., Finding created, Remediation asset created, or Remediation asset status change.
Note: Automatic ticket creation is based on a single event only.
Define Conditions (optional refinements):
Status – Trigger only for a selected status (e.g., Open).
Severity – Trigger only for selected severity levels.
Security Domain – Limit the scope (e.g., finance department).
On the Actions page, select Jira.
This option is only available once the Jira integration has been authenticated:
Important: Updates made to a finding in Hyver (such as new versions or field changes) are not reflected in Jira after the ticket is created. The Jira ticket captures the snapshot of the finding at creation time.
Manual Jira Ticket Creation
For existing findings — or if you prefer more control — you can create Jira tickets manually.
When you create a manual ticket:
A new ticket is added to your Jira backlog with data pulled directly from Hyver, including:
Finding description
Remediation asset file (if available), attached as an Excel file
In Hyver, a link to the Jira Ticket ID also appears. To track this easily, add the Ticket ID column to your Findings table.
Option 1: From the Findings Page
Go to the Findings page.
Select one or more findings (up to 450).
Findings must be shared with Anyone with permission.
Findings that already have a Jira ticket will be skipped.
Click the Create icon, or open the finding menu (⋮) and select Create ticket > Jira:
A progress indicator shows the status of ticket creation:
Option 2: From the Right Pane
Select a finding and open the right pane.
Click the Jira ticket creation icon at the top, or open the menu (⋮) and select Create ticket > Jira:
Permissions and Rules
Findings must be shared with Anyone with permission (status can be any).
Findings already linked to a Jira ticket will be skipped.
If a finding doesn’t meet the requirements (status or sharing), update its settings before creating the ticket.
Jira Ticket Description Fields
When Hyver creates a Jira ticket, the Description field is automatically populated with details from the related finding. This ensures that anyone working in Jira has the full context without switching back to Hyver.
The Jira Description field includes:
Finding name – The name of the finding, plus the Hyver Finding ID and a link to the finding in Hyver.
Severity – The severity level of the finding.
Priority – The mapped priority value.
Security domain – The domain associated with the finding.
NIST subcategory – Any linked NIST subcategories.
Engagement name – The engagement that includes the finding.
Finding description – A full description of the finding.
Mitigation recommendations – Suggested actions to remediate the finding.
Attachments – Any attachments included with the finding.
Supporting evidence – Evidence associated with the finding.
CSV list of remediation assets – A downloadable file (Excel-ready) listing remediation assets linked to the finding:
8. Deleting the Integration
Deleting the Integration
To remove the connection, click Delete Integration and confirm.
Once deleted:
The connection is immediately terminated.
No new data from Jira will be ingested or processed.
Any data that already exists in Hyver is retained.
Editing the Integration
After setup, you can adjust the configuration at any time.
Click Edit Integration, make your changes, and then click Save.
Wrap-up
In this guide, we walked through setting up the Jira–Hyver integration from start to finish. You learned how to authenticate, create tokens and webhooks, map fields, configure notifications, and manage tickets. With the integration in place, Jira and Hyver now stay synchronized, ensuring findings and remediation work remain aligned across both platforms.