Skip to main content

Release Notes - 2026-NOV-04

Hyperproof release notes

Note: These features, updates, and addressed issues are released first in Hyperproof US and Hyperproof EU on the date noted in the title. They are released in Hyperproof Gov one week later unless otherwise noted.

Added / Improved

Hierarchical scopes

  • You can now add scopes to controls in a hierarchy, allowing teams to manage controls at multiple levels and assign evidence collection to the appropriate user or group. With the release of hierarchical scopes, we have included the following improvements:

    • Everything rolls up. Information tied to a scope, including tasks and tasks created by repeating tasks, now rolls up so you can see it all on the top-level control.

    • Clear ownership. Tasks, proof, and other information that rolls up include an Origin field, so you can see the object where each item originates.

    • Health rolls up too. Health at the lowest scope level feeds into each higher level, all the way up to the top-level control.

    • Import and export support. You can manage scopes through import and export, including updates to custom fields.

  • New import/export format for scopes - Import and export now use a hierarchical format for scopes: CO.02 > Cloud replaces the legacy CO.02_Cloud.
    ​
    For a limited time, you can still export CSV and XLSX files in the legacy format, so integrations with external systems keep working while you update them. Legacy-format files can’t be used for Hyperproof imports, including bulk updates to controls. To import into Hyperproof, use a CSV file exported in the new hierarchical format.
    ​
    For details, see the hierarchical scopes documentation. Note that to access this documentation, you must be logged in to Hyperproof.

Saved views for controls

  • On the Controls page, a saved view now remembers whether Expand scopes is checked. Selecting the view checks or unchecks it to match. Previously, saved views ignored Expand scopes, and the checkbox stayed as you last left it.

Evidence validation test library

  • Nearly all Hypersyncs now have tests that can be added in just a few clicks; see the full list here.

  • Tests are fully customizable

  • Test definitions use the NIST 800-53 moderate baseline or similar

  • Tests can be added from the Label or Control Automation tab or using Hyperproof AI
    ​

Custom fields configurable layouts

  • On a record’s Details tab, administrators can use Settings (gear icon) in the Custom fields panel to change how custom fields are laid out. They can drag and drop fields to change the order, group them into sections, and hide fields. Previously, custom fields always appeared in alphabetical order.

  • The layout is set once per object type and applies to every record of that type. It can’t be set per record or per Risk Register. “Reset to default” returns the list of custom fields for that object type to alphabetical order.

  • Only organization administrators and system administrators can edit the custom field layout. Everyone else can view it as read-only, so it stays consistent across the organization.

  • Hiding a field keeps its values. Required fields can’t be hidden.

Actions menu

Actions such as Archive, Export, and Freshness settings previously available via the "..." overflow menu at the end of the tab row now have their own menu in the page header:

  • On an object's page, open the vertical ellipsis (⋮) button to the right of the Activity Feed button to find that object's actions. Hovering over it shows Actions.
    ​

  • The menu has the same items in the same order as the old "..." menu, which is now reserved for additional tabs or bulk-edit options that don't fit across the top of the window. Who sees each item and when it's available haven't changed. For example, Archive still needs archive permission on the object.

Proof linked objects

  • The proof window and the proof preview now include links and totals for requirements, risks, and requests.

  • For Requests, selecting Expand proof versions ties the link to the specific version, so you can see which version of the proof was actually provided on that Request, not just that the proof was used.

Slack notifications in private channels

Users can now send comments to private Slack channels. See Connecting objects to Slack for additional details.

  • If you already have a Slack connection, you need to reauthorize to accept the new scopes under Settings > Connected Accounts > Slack > Update credentials.

  • In Slack, add the Hyperproof app to a private channel that you're in. If your organization uses Hyperproof EU or Hyperproof Gov, add the Hyperproof EU or Hyperproof Gov app.

    • Right-click the channel and view channel details

    • Go to the Agents & apps tab and add the Hyperproof app.

  • In Hyperproof, go to any object:

    • Click Actions -> Send comments to Slack
      ​

    • Select the private channel

Notification links

  • Email notifications now include primary action buttons such as View task, View issue, or View in Hyperproof, in addition to the existing text hyperlinks.

SCIM support for Hyperproof role assignment with Okta groups

Hypersyncs and integrations

Hyperproof API

Assessments API

The Assessments API endpoints are now available in v1 across all Hyperproof instances. With this release, you can:

  • Create control and requirement assessments

  • Clone an existing assessment along with its evaluations

  • List and filter assessments by status and type

  • Update and archive assessments

Evaluations API

The Evaluations API endpoints manage evaluations within an assessment. Evaluations are addressed directly by ID rather than nested under their parent assessment. With this release, you can:

  • Add evaluations for up to 100 controls, control scopes, or requirements in a single call

  • List and filter evaluations by assessment, work status, target, or assignee, with sorting and paging

  • Update an evaluation’s assignee, group, due date, priority, work status, and observations

  • Archive and unarchive evaluations

  • Expand an evaluation’s linked proof, labels, issues, and metadata in the same call

Support system updates

  • Our support system will be offline from November 20, 5:00 PM Pacific time until November 23, 12:00 AM Pacific time while we transition our support ticketing system from Salesforce to Intercom. Read more about the transition in this article: Ticketing system change

Addressed issues

  • Fixed an issue in the Hypersync for Jira List of Issues proof type where sync operations failed when a filter contained duplicate custom field columns, preventing proof collection. (Case # 00012886)

  • Fixed an issue in the Approvals module where deleting or archiving a task did not cancel its open approval requests, causing orphaned approvals to remain stuck in the approval queue and display access errors. (Case # 00012582)

  • Fixed an issue with sorting the controls grid by proof or label counts. (Case # 00012683)

  • Fixed an issue across multiple modules, including audits, vendors, and tasks, where the Proof Provided date column in proof tables was too narrow and cut off the year portion of the date. (Case # 00012716)

  • Fixed an issue in the Programs module where configuring a new program with smart content risk links failed to link controls to existing risks in the target risk register, resulting in controls showing zero linked risks. (Case # 00012601)

  • Fixed an issue in Settings where administrators were unable to delete custom field options if those values were associated exclusively with archived or deleted objects, such as deleted repeating task templates. (Case # 00012801)

  • Fixed an issue in the Programs module where filtering controls by sections on the Controls tab failed to apply, causing all controls to remain displayed regardless of the selected sections. (Case # 00012802)

  • Fixed an issue in Jira task integration where performing a full sync inadvertently cleared task due dates in Hyperproof. (Case # 00012794, 00012848, 00012849, 00012850, 00012851, 00012852, 00012853)

  • Fixed an issue in the Approvals module where tasks created and submitted via an API service account failed to initiate their configured approval workflows. (Case # 00012836)

  • Fixed an issue in the Proof module where uploading a new file version to an existing proof sometimes resulted in an upload conflict error. (Case # 00012882)

  • Fixed an issue in the Jira task integration where status transitions failed to sync to linked Jira tickets (Case # 00012794)

  • Fixed an issue in Tasks where closing a task failed to promote and link associated policy documents to the target control, leaving the policy documents linked only to the closed task. (Case # 00012795)

  • Fixed an issue in the Assessments module where proposed risk descriptions containing Markdown fenced code blocks didn't render properly during evaluation. (Case # 00012932)

  • Fixed an issue in the Hypersync for Bitbucket List of Pull Requests proof type where synchronizing merged pull requests across all repositories timed out, preventing proof collection. (Case # 00012907)

  • Fixed an issue in the Controls module where updates to Implementation and Testing status values on a parent control were not saved when its associated scoped controls were archived. (Case # 00012937)

  • Fixed an issue in the ServiceNow task integration where connection health checks and new connection attempts failed when usernames contained an "@" symbol. (Case # 00012951

  • Fixed an issue in the Controls module where selecting See more details on a failed automated control test displayed an unexpected error message, preventing users from viewing detailed test failure information. (Case # 00012937)

  • Fixed an issue in Jira Cloud task integration where a task's project identifier was cleared during synchronization, preventing task status updates from syncing between Jira and Hyperproof. (Case # 00012955, 00012959, 00012960)

  • Fixed an issue in the Hypersync for Azure DevOps Members in Permission Group proof type where automated syncs failed with a descriptor lookup error when a permission group contained a nested Microsoft Entra ID group, preventing proof from being collected. (Case # 00012938)

  • .. plus other fit and finish, performance, stability, and security issues — as always!

Did this answer your question?