Skip to main content

Release Notes - 2025-FEB-10

Added

Groups

  • Added support for groups as control owners and request assignees.

  • Where applicable, grids now show groups as owners or assignees.

  • Added support for filtering by groups on the Controls grid and the Requests grid.

  • Assigning a group as a control owner or request assignee triggers the same Hyperproof notifications for the group lead as for an individual who has been given that designation. The Activity Feed also documents when a group has been added as an owner or assignee.

  • See the following articles for more information:

Assessments

  • Added support for the creation and import of requests in assessments. Requests can be assigned to team members or to auditors, and comments can be shared back and forth via the Activity Feed.

  • Additionally, when a request is linked to an evaluation, all of the request's proof is linked to the evaluation via the request. At the same time, the evaluation’s target object (e.g. control) is linked to the request via the evaluation. If the request is unlinked from the evaluation, all of the implicit links are also unlinked.

Filtering

  • Added support for filtering by control owner.

Connection health

  • Users can now understand the connection health of a task integration. This feature proactively notifies users when a connection stops working and allows them to fix unhealthy connections.

  • See the following articles for more information:

  • Redesigned Settings > Connected Accounts for Hypersync connections. It's now much easier to see the health of a Hypersync connection and any Hypersyncs that use the connection. Users can check the connection, update credentials, and change connection all from the the new view.

Access Reviews

  • Added support for the Hypersyncs for Orca Security, Bitbucket, and SAP SuccessFactors (via Finch).

Policy

  • Version IDs are now editable.

Improved

Hypersyncs and integrations

  • New! Hypersync for Bitbucket. Proof types include: List of Users, List of Users (Access Reviews), List of Pull Requests, and List of Commits.

  • New! Hypersync for SAP SuccessFactors (via Finch). Proof types include: List of Employees, List of Employees (Access Reviews), and List of Employees with a Change in Status.

  • Updated! Hypersync for Okta. New proof type: List of User Login Events.

  • Updated! Hypersync for Azure. New proof type: List of Application Configurations.

  • Updated! Hypersync for Tenable. New proof type: List of Attestations.

Program frameworks

  • Updated! NIST 800-53 Full Catalog has been updated to version 5.1.1 and now includes SSP fields and reporting.

  • See the idea in the Ideas portal.

Addressed issues

  • Fixed an issue where customers could not log in to Hyperproof via SSO. (Case # 00008786)

  • Fixed an issue that caused a Hypersync to continue to sync proof on an archived control. (Case # 00008843)

  • Fixed an issue with connecting the Hypersync for Snyk in Hyperproof EU. (Case # 00008552)

  • Fixed an issue where a group member with manager permissions could not create a requirement assessment. (Case # 00009115)

  • Fixed an issue with the Hypersync for Jira that caused inaccurate filter data and search results. (Case # 00009247)

  • Fixed an issue that caused an unexpected error to occur while navigating Hyperproof. (Case # 00009297)

  • Fixed an issue where importing to change a control owner was successful, but the new owner was not added to the control's facepile. (Case # 00009171)

  • Fixed an issue with the size of the Audits > More options pop-up window. (Case # 00009440, 00009461)

  • Fixed an issue that caused an error with the Hypersync for Google Workspace Platform proof type 'User Security Report'. (Case # 00009554)

  • Fixed an issue that caused the Hypersync for AWS (set up for us-east-2) to incorrectly display no results. (Case # 00009343)

  • Fixed an issue with the task integration for Jira that caused Hyperproof repeating tasks to display no Jira ticket numbers. (Case # 00009536, 00009394, 00009224)

  • Fixed an issue where changing a requirement's status to 'Not applicable' and then abandoning the process halfway causes all other requirement statuses to display as 'Not applicable'. (Case # 00009407)

  • Fixed an issue where a Partner received an 'Access denied' error when accessing a customer program. (Case # 00009411)

  • Fixed an issue that caused an 'access denied' error when reconnecting to Amazon S3 for LiveSync. (Case # 00009396)

  • Added additional permissions to AWS JSON file. (Case # 00009357)

  • Fixed an issue where, when selecting a task's hyperlink, tasks in the Work items module did not match the number of tasks in the filtered grid view. (Case # 00009369)

  • Fixed an issue that caused an 'Invalid error' when trying to connect the Hypersync for Okta. (Case # 00009468)

  • Fixed an issue that caused task assignees to receive an 'Access denied' error if they were not on the request's facepile. (Case # 00009528, 00009493)

  • Fixed an issue where an existing risk category could not be selected from the Category drop-down menu. (Case # 00009491)

  • Fixed an issue where assignees did not appear on requests. (Case # 00009499, 00009502, 00009504, 00009503, 00009501, 00009500, 00009498)

  • Fixed a latency issue in the Audits module. (Case # 00009515, 00009514)

  • Fixed an issue in the Audits module that caused the 'Export proof' option to be greyed out when selecting individual requests while in Grid view. (Case # 00009530, 00009517, 00009518)

  • Fixed an issue that caused an 'Access denied' error when deleting earlier versions of proof. (Case # 00009520, 00009506)

  • Fixed an issue with archived audits where refreshing caused requests to be hidden. (Case # 00009551)

  • Fixed an issue with facepile membership that caused users who had both individual and group memberships to have limited access to proof. (Case # 00009555)

  • Fixed an issue with the task integration for Jira where changing the status resulted in the status value cycling through each status in the mapped column eventually settling on the bottom status value. (Case # 00009198)

In this section: