Skip to main content

Release Notes - 2026-JAN-08

Added

Note

The new Risk Intake and Risk Assessment features are available for customers with the Risk module. If you have a Risk register and are not seeing Risk Assessments and Risk Intake, please contact your Customer Success Manager for assistance.

  • Risk Intake -

    Hyperproof’s risk intake feature streamlines the risk workflow end-to-end. It allows teams to gather cross-company feedback, automatically identify duplicates or existing risks, and seamlessly add validated risks to the Risk Register. Once submitted, proposed risks can be added to risk assessments, allowing teams to evaluate likelihood, impact, and control gaps quickly. With Hyperproof’s integrated intake portal, organizations can maintain an accurate, up-to-date risk posture without relying on external tools or manual data transfer.

    • Use our new Intake Register and Intake Surveys to capture proposed risks from anyone in your organization, including people who are not Hyperproof users.

    • Once you've captured proposed risks, easily review, assess, and approve them using our new Risk Assessments.

  • Risk assessments - Use our new risk assessments to propose, review, and approve updates to proposed or existing risks.

  • Freshness activity feed - Updated the activity feed entries for freshness expiration to indicate that Hyperproof has set the object's freshness to expired. (Case # 0001066)

  • UI enhancement - Added tooltips for single-line text that exceeds the display capabilities of the containing field. The tooltip displays the entire contents of the field. (Case # 00010304)

  • Testable proof API - Using the API, you can now upload CSV-based evidence and explicitly define data schemas to ensure type safety for downstream ACT testing.

    • Key Technical Requirements:

      • Authentication: API clients must be configured with the proof.update  scope

      • Date upload (POST): Proof must be submitted as a CSV file

        • The request should include contentType: text/csv

      • Schema Management (PATCH): The schema of the file can only be updated via PATCH, not POST.

        • Explicit typing: Use the PATCH method to define field types. Available types include text, number, boolean, and date.

        • Default behavior: Unlike the application, API-patched schemas do not default to text if a type is not specified. You can only run ACT with the fields you specifically patched.

        • Case sensitivity: Column names in the schema patch are case-sensitive and must exactly match the headers provided in the CSV.

    • Implementation workflow:

      • POST the raw CSV data to the add proof endpoint with the correct text/csv  content type

      • PATCH the resulting proof object to define the schema and assign the appropriate data types to your columns.

Improved

Hypersyncs and integrations

  • Updated! Hypersync for AWS - Added a new service: ECS with a new proof type: List of Containers

Hyperysnc SDK

Hyperproof will release a new Hypersync SDK in mid-February.

Customers currently using the Hypersync SDK for custom-developed Hypersyncs will be required to update to this SDK by May 1. Detailed instructions will be provided.

For further information, please contact your Customer Success Manager.

Addressed issues

  • Fixed an issue where inactive sessions were not gracefully terminated, causing the user to be logged out abruptly. (Case # 00010624)

  • Fixed an issue where session timeout errors occurred inconsistently when users worked in multiple tabs in Hyperproof, leading to user access interruptions. (Case # 00010747, 00010760)

  • Fixed an issue where archiving a Control did not disable its linked repeating task template if any task from the template had already been submitted, causing new tasks to continue generating. (Case # 00010981)

  • Fixed an issue where the Hypersync for Jira List of Users proof type returned no data or was limited to 100 users when using JIra Data Center. For this fix to take effect: (Case # 00010560)

    • If you are using Jira Data Center, you must upgrade to Jira Data Center version 11.

    • To filter the List of Users proof type on a specific group, you must have the ADMINISTER (admin) permission in your Jira Data Center instance.

  • Fixed an issue where editing the description of labels sometimes generated intermittent errors, causing an unexpected error page to appear even though the changes were saved. (Case # 00011074)

  • Fixed an issue in the Hypersync for Coupa List of Users proof type where the sync failed, resulting in a 403 Forbidden error when retrieving user data. (Case # 00011071)

  • Fixed an issue where custom fields configured to be set independently per scope were incorrectly updated across all scope assignments, instead of only updating the one being edited. (Case # 00011070)

  • Fixed an issue where archived program requirements were incorrectly available for linking in the Issues module, allowing users to associate them with active issues. This fix ensures that only requirements from active programs appear in search results. (Case # 00011110)

  • Fixed an issue in the Work Items module where only nine proofs were visible on a task due to a missing scrollbar, preventing users from accessing the full list directly. (Case # 00011125)

  • Fixed an issue where custom field selections were not saved when users created a new label and entered data during the creation process, causing the fields to appear blank after saving. (Case # 00011127)

  • Fixed an issue where attempting to reassign work from a recently deactivated user caused the reassignment window to close unexpectedly, preventing selection of a replacement user. (Case # 00011044)

  • Fixed an issue in the Audit Requests grid view where custom column arrangements were reset after toggling to card view and back, requiring users to reconfigure their layout manually. (Case # 00011164)

In this section: