Hypersyncs and integrations
New and updated proof types
New! Hypersync for KnowBe4 - List of Acknowledgments: Collects policy-acknowledgment data, showing which employees have and have not acknowledged each assigned policy.
New! Hypersync for AWS - Security Hub: Cross-Region Aggregation: Provides the mapping for Home Region and Linked Region.
Updated! Hypersync for AWS - Backup: Backup Plan Details: Added the Cross-Region Replication and Replicated Region fields.
Updated! Hypersync for Azure: Resource group filter settings now support the ability to select All resource groups for the following proof types:
Key Vault: Access Configuration
Key Vault: Deletions
Key Vault: Private Endpoint Connections
Storage Account: Minimum TLS Version
Storage Account: Networking Configuration
Storage Account: Peerings
Storage Account: Primary and Secondary Endpoints
Hypersync SDK Version 6.0.0 Required Update
In January, we released a required update to the Hypersync SDK (version 6.0.0). This update included several improvements, including upgrading to Node.js 22.
As of the May 6th, 2026 release:
Any Hypersyncs compiled with a version of the Hypersync SDK earlier than version 6.0.0 will fail to run.
The system will prevent deploying Hypersyncs developed with earlier versions of the Hypersync SDK; a minimum version 6.0.0 will be required.
Update instructions
You must rebuild your custom apps and redeploy each of them. Detailed instructions are provided here: V6 Hypersync SDK migration guide
Addressed issues
Fixed an issue where the LiveSync toggle failed to remain enabled when selecting the same file as a new proof version from an external cloud storage source. (Case # 00011503)
Fixed an issue where attempting to create a risk intake register with the same name as a risk register resulted in an unexpected error instead of preventing the user from using the duplicate name. (Case # 00011635)
Fixed an issue where the External link for editing field was intermittently missing for Policy documents uploaded via LiveSync. (Case # 00011649)
Fixed an issue where the Members column was missing or empty when exporting control lists to CSV or XLSX formats. (Case # 00011758)
Fixed an issue where survey sections and questions were displayed out of order when viewing completed risk intake survey results. (Case # 00011759)
Fixed an issue where sorting audit requests by the Reference column did not function correctly when using a mix of single, double, and triple-digit numbers. (Case # 00011807)
Fixed an issue where users experienced significant delays when opening tasks associated with control scopes. (Case # 00011539)
Fixed an issue with task integrations where tasks sometimes failed to sync automatically. (Case # 00011809)
Fixed an issue in control assessments where parent controls were incorrectly included in filtered results when the Expand scopes option was used. (Case # 00011855)
Fixed an issue where approval workflows were not properly generated for repeating tasks triggered by changes in label freshness. (Case # 00011861)
Fixed an issue where users couldn't assign a contact to an issue during the initial issue creation process. (Case # 00011865)
Fixed an issue where users attempting to log in via Azure SSO before accepting their initial invitation were unable to complete the invitation process. (Case # 00011869)
Fixed an issue in the Issues module where the "Closed on" date was not cleared when an issue was moved from a closed state back to an active state. (Case # 00011909)
Fixed an issue where proof preview generation caused system performance degradation and service interruptions. (Case # 00011914, 00011915, 00011916, 00011917, 00011918, 00011921, 00011923, 00011924)
Fixed an issue where the required OAuth scope for the Role Assignments API was incorrectly restricted, preventing users from accessing the published endpoint. (Case # 00011922)
Fixed an issue with the LiveSync for Confluence where proof uploads would stall, and new content would fail to synchronize. (Case # 00011937)
Fixed an issue in task approval workflows where sequential approvals were not automatically triggered when a task was moved to the Submitted status, preventing the approval process from advancing as expected. (Case # 00011931)
.. plus other fit and finish, performance, stability, and security issues β as always!
