Skip to main content

Release Notes - 2026-JAN-29

Added

  • Hierarchical Scopes

    We're excited to announce that Hierarchical Scopes is now available! This feature allows you to organize your compliance program with nested scope structures that reflect your organizational hierarchy—by business unit, geography, product line, or any combination that fits your needs.

    Hierarchical Scopes let you create multi-level scope structures with automatic health roll-ups from child to parent scopes. Scope owners only see information relevant to their scope and any levels below it, and can easily navigate the hierarchy using a tree view with flexible grouping by custom fields.

    Important

    The Hierarchical scopes feature is only available to customers whose organizations do not have the Scopes feature enabled.

    For organizations with configured Scopes, we're working to bring this feature to you as well. This will require some back-end updates to ensure a smooth data transition without disrupting your current setup. We're currently working on these updates and will make them available as soon as possible. We'll keep you updated on our progress.

  • Support for one-time passcodes for contacts

    In this update, we have added one-time passcodes for contacts to Hyperproof US and Hyperproof EU. One-time passcodes are already in place for Hyperproof Gov.

    Contacts and external contacts assigned a task, vendor questionnaire, or risk assessment survey must now complete a one-time passcode authentication. They’ll receive an email with a link to the assigned item, verify their email address, and enter the 8-digit code they receive via email. After verification, they can access, complete, or edit the assigned task, questionnaire, or survey.

    Note

    Users will no longer be able to forward the questionnaire and task assignment emails to others to share or delegate access to complete them.

  • Unassigned option for tasks, task integrations, and repeating tasks

    Tasks, integrated tasks, and repeating tasks allow you to select Unassigned as the assignee. This works well if you have a triage process where tasks are assigned to specific individuals at a later time.

    Note

    When importing tasks or repeating tasks, leaving the Assignee field blank now sets the assignee to Unassigned. Previously, if the Assignee field was left blank during import, the task or repeating task was automatically assigned to the record’s creator (the importer).

  • Proof preview

    Added support for the .webp image type to the proof viewer.

Improved

  • Risk API Updates

    • Added the following new columns related to proposed risks for the risk intake register

      • RiskReporterId - an external contact ID or Hyperproof user ID for the person who submitted the proposed risk

      • RiskReporterType - the type of person who submitted the proposed risk (External Contact or User)

      • RiskStage - the current stage of the risk - Proposed, Evaluating, Operating

        Note

        The Operating stage is for actual risks. The Proposed and Evaluating stages are for proposed risks.

    • PUT /filter - when getting risks, you can now filter on RiskStage

    • POST  /risks - updated the description to indicate that if you post a risk to the intake risk register, it will be a proposed risk

  • Updated Hyperproof developer portal

    We’ve launched a major update to our developer documentation (https://developer.hyperproof.app/) to make it easier to find, understand, and work with Hyperproof’s APIs and SDK.

    All SDK and API documentation is consolidated on a modernized site with clearer, more complete API references. Search has been significantly improved and spans both documentation and API references, with the option to use either traditional or AI-powered search.

    Our interactive Try it experience includes a mock server for viewing sample results without connecting to Hyperproof and supports all three Hyperproof environments: US, EU, and GOV. To further support developers, sample code is available in nine languages along with many other improvements.

  • Performance improvements

    Improved performance when displaying Hyperproof data in a grid format.

Hypersyncs and integrations

  • Updated! Hypersync for Cloudflare: Added the List of WAF Managed Rules proof type.

  • Updated! Hypersync for AWS: Proof types can now be filtered by tags.

    Note

    For the Backup proof types, you must add the backup:ListTags permission to be able to filter the contents of those proof types by tags.

  • Updated! Hypersync for Google Sheets: Improved the Hypersync to support higher data volumes up to the maximum sheet size of 10M cells supported by Google Sheets.

    Note

    • The maximum sheet size of 10M can cause the Hypersync to time out sometimes. The timeout issue will be addressed in a future release.

    • To manage large volumes of data, Hyperproof has added paging to the Hypersync. Hyperproof identifies the last record in the data set by locating the first blank row in the Google Sheet. If a blank row is included in the middle of the data set, the data set is truncated at that blank row, and the remaining data is excluded. Be sure to remove any blank rows that are mixed in with the completed rows.

  • Updated Hypersync SDK - Action Required

    This release includes an updated version of the Hypersync SDK, now running on Node.js 22.

    Customers using the Hypersync SDK for custom-built Hypersyncs must upgrade to version 6.0.0 by May 1. The upgrade requires rebuilding and redeploying each custom app to ensure compatibility.

    For step-by-step guidance, see the migration instructions: https://developer.hyperproof.app/hypersync-sdk/sdk-019-migration-v3-to-v6

Video tutorials

Video tutorials are now available through our AI support agent in Hyperproof. You can access training videos directly from the chatbot window by selecting Help Center → Training → Video Tutorials for quicker, in-context guidance, or click here to go directly to the Video Tutorials page.

Addressed issues

  • Fixed an issue where users deploying custom Hypersyncs with the SDK experienced failures when updating or redeploying code that had previously functioned correctly. (Case # 00011020, 00011234)

  • Improved performance on the Linked Objects window for organizations with a large number of objects. (Case # 00010963)

  • Fixed an issue where selecting a scope in the Overview module’s “Explore by” filter caused the orphaned controls count to be incorrect, and the link redirected to an unfiltered list of all orphaned controls in the organization. (Case # 00011140, 00011173)

  • Fixed an issue in the Hypersync for JupiterOne List of Assets proof type, where duplicate Cloud Account Types displayed in the Cloud Account Type dropdown menu when configuring the Hypersync. (Case # 00011168)

  • Fixed an issue where Controls with freshness set to "On a recurring schedule" did not populate the freshness column in CSV exports, even when the feature was correctly configured. (Case # 00011172)

  • Fixed an issue where sorting labels by the freshness column caused custom field values to disappear until the window was refreshed. (Case # 00011205)

  • Fixed an issue where if an issue’s primary source was an assessment, clicking the source link redirected users back to the issue instead of to the assessment. (Case # 00011220)

  • Fixed an issue in the Hypersync for AWS where the Hypersync was marked as unhealthy and failed to complete collecting proof even when fetching a minimal dataset, stopping after partial collection with a timeout error. (Case # 00011232)

  • Fixed an issue where task integrations failed to sync automatically in Hyperproof US and Hyperproof EU environments. Users were had to trigger manual syncs, and task statuses did not reflect updates from external systems. (Case # 00011277)

  • Fixed an issue in the Hypersync for GitHub that prevented users from connecting or updating credentials due to a misconfigured authentication flow. (Case # 00011199)

In this section: