ROH 6.32.0.4 Release

Release Overview

Release Name: ROH Beta Hotfix Release

Release Type: Hotfix

Release Number: 6.32.0.4

Purpose

RegScale Orchestration Hub (ROH) enables organizations to automate the import and export of data between RegScale and external systems through configurable integrations and commands.

This beta release is intended for early adopters and validation of core orchestration capabilities. Functionality, supported integrations, and performance characteristics may change before General Availability (GA). This minor release delivers reliability, usability, and maintenance improvements for early adopters, summarized below.

What's Fixed

• Duplicate software inventory on repeated asset syncs: Asset syncs no longer add a second copy of an asset's software inventory each time they run. Previously every run appended the full list again, so a package that should appear once was listed twice after the second sync and gained another entry with each run after that. Software inventory is now reconciled against the records RegScale already holds, and packages reported more than once within a single scan are collapsed into one entry. This affects every integration that synchronizes assets in batches. Note that this fix prevents new duplicates from being recorded; it does not remove entries already written, so any duplicates accumulated before upgrading need to be cleared separately.
• Tanium Cloud vulnerability and compliance synchronization on large data sets: Tanium Cloud jobs that collect vulnerability and compliance findings no longer stop before ingesting any records when a request exceeds the Tanium gateway's data limit. ROH now reduces the amount of data requested per page and retries automatically, so these synchronizations complete. Previously an affected run could finish and report success while ingesting nothing.
• Consistent Qualys asset identifiers: Qualys assets are now recorded with the same identifier whether the asset is created for the first time or updated by a later synchronization. Previously the two paths wrote different values, which could leave an asset's vulnerabilities and issues unlinked from the asset itself. Existing Qualys assets are updated in place to the corrected identifier, so they keep their RegScale IDs and their existing links.

Maintenance and Updates

• Routine dependency and security updates across backend components.