Overview
This article highlights new features released in August 2024. You'll learn about updates to maturity framework settings, new data export options, improved integrations, and expanded support for maturity scoring inputs. These updates help improve accuracy, transparency, and control in how you manage cyber risk with Hyver.
1. Set your organization's primary maturity framework
Hyver now lets admins define which maturity framework is used across the platform for scoring and reporting — such as NIST CSF 2.0.
To update this setting:
Go to Settings.
Click Maturity.
Choose your preferred framework (e.g., from NIST CSF 1.1 to NIST CSF 2.0).
The selected framework will be reflected throughout Hyver, including in the Risk dashboard and mitigation planning.
2. Register security processes to improve maturity scoring
To improve objectivity in maturity assessments, you can now register implemented security processes directly in the Maturity view.
Each subcategory now includes a section where you can list relevant processes. These are then factored into scoring, helping Hyver rely more on structured inputs than manual interpretation.
3. Export findings to Excel
You can now export findings from Hyver to Excel, whether it’s a single finding or the entire list.
This is useful for sharing data with teams outside the platform or performing offline analysis.
To export:
Go to the Findings view.
Select the findings you want to export (or leave all selected).
Click Export and choose Excel.
4. Use bidirectional integration with ServiceNow
The ServiceNow integration is now bidirectional. This means Hyver can receive ticket status updates from ServiceNow and automatically reflect them in the associated finding status.
This helps keep statuses in sync across both platforms and gives users up-to-date information at a glance.
5. Add custom technologies and processes for maturity scoring
If your organization uses a security technology or process that isn’t predefined in Hyver, you can now add it manually.
Go to Create asset.
From the Type field, select Security technology or Security process.
Complete the fields to define the asset.
These custom entries are included in maturity scoring and allow you to fully represent your security environment.
6. Enforce authentication methods for users
Admins can now enforce specific authentication methods for login.
By default, Hyver supports username/password and Microsoft SSO. You can restrict access to specific methods in the Settings, and login attempts using other methods will be blocked.
This allows organizations to align platform access with internal security policies.
7. Identify unmapped findings and assets
To help you maintain alignment with your primary maturity framework, Hyver now flags findings and assets not mapped to any framework.
In both the Findings and Assets views, use the new Unmapped framework filter to quickly spot these gaps and update their mappings accordingly.
Wrap-up / Next Steps
This update brings more clarity and control to how your organization tracks and improves cybersecurity maturity in Hyver. Whether you're managing frameworks, syncing systems, or strengthening access controls, the new tools are built to support real-world workflows — without extra complexity.