Skip to main content

Release Notes - 2025-DEC-11

Added

Policy

  • Effective policy documents created/edited in the policy editor or file type DOCX and supporting proof files now sync automatically to all linked controls. See Linking and unlinking controls for a policy.

  • When a policy version is promoted to effective, if the policy document is a DOCX file, it is converted to PDF and added to the Proof section of the policy Document tab.

Multi-step approvals

Multi-step approvals for tasks, repeating tasks, and policies are generally available to all Hyperproof customers, and this capability is turned on by default for all organizations with this release. See Creating a task with an approval and Policy approvals.

SCIM provisioning with Microsoft Entra ID

Use SCIM provisioning with your Microsoft Entra ID SSO directory to bring users and groups into Hyperproof without having to invite each user individually. SSO must be configured in your organization for this functionality to work. See Provisioning Hyperproof users and groups with SCIM .

Improved

Hypersyncs and integrations

  • Updated Hypersync for AWS:

    • New proof - EC2: List of Instance IPs

    • Added a Days Open field to the Security Hub Findings proof.

    • Added an Account filter to the List of SSO Users proof.

    • Added Schedule and Frequency fields to the List of Backups proof.

    • Added an AMI field to the List of Running Instances proof.

    • Added a Last Runtime field to the Backup proof.

  • Updated Hypersync for JupiterOne: Added a region field to the Hypersync configuration window, allowing you to select either the EU region or the US region.

  • Updated Hypersync for Orca: Modified the Orca API used to collect the List of Alerts and List of Assets proof types as required by Orca.

    Note

    If you have either the List of Alerts or List of Assets proof types configured, you must go to the Hypersync configuration for each of these proof types and open the Settings, click Save, and then from the ... (More) menu click Sync now.

Addressed issues

  • Fixed an issue where modifying certain Jira integration fields in repeating tasks caused validation errors. (Case # 00010752)

  • Fixed an issue where the Hypersync for Rapid7 Vulnerabilities by Site proof type was timing out before collecting updated vulnerability data. (Case # 00010852)

  • Fixed an issue that triggered duplicate notifications for task due dates when the recipient was both the creator and the assignee. (Case # 00010574)

  • Fixed an issue where attempting to archive a risk that was linked to a vendor resulted in errors when the user had manager access to the risk but only contributor access to the vendor. (Case # 0010968)

  • Fixed an issue where proof couldn't be exported from selected Audit requests if a Contact uploaded the proof via a task. (Case # 0010980)

  • Fixed an issue in the Hypersync for Jira where filters failed to load when configuring the Hypersync. (Case # 00011013)

  • Fixed an issue in the Risk Register where the Issues pop-up failed to show additional details if more than one issue was attached to the risk. (Case # 00011029)

  • Fixed an issue where making proof linked to archived objects private sometimes failed to remove users with inherited access from its membership list. (Case # 00011048)

  • Fixed an issue in the labels module where the controls column showed “0” even when scoped controls were linked to labels. (Case # 00011060)

  • Fixed an issue with the Links tab where the number of objects linked for most objects had incorrect totals when viewing them in the dropdown list. (Case # 00011065)

  • Fixed an issue where users could not save changes to a repeating task template unless they toggled the “Edit approvals” setting, even when no changes were made to approval settings. (Case # 00011068)

  • Fixed an issue where users couldn't link scoped controls to risks. (Case # 00011078)

In this section: