Skip to main content
Version: 2.8.2

Release Notes

RWD 2.8.2

Fixed Issues

  • DS-198 New UI - SG history - sorted by time: Security Guard sorting by time is not working correctly. The current Security Guard history is randomly sorted in the new UI.

  • DS-190 Enhancement - Show the platform for Ignored list/Monitor Only list: The platform of Ignored list/Monitor only list is not displayed.

  • DS-201 New UI - Alerts Window - SG filter is not working: The Security Guard events are shown in the Security Guard category on the Alerts active window. When clicking on the Security Guard filter - no events are displayed.

  • DS-203 New UI - Alerts overview details include HTML tags: The HTML tags are displayed in the details for the Alert overviews.

  • DS-204 New UI - SG log cannot be copied: The Security Guard logs were shown to be copied, but they were not.

  • DS-213 New UI - Security Guard - running scan is reported as failed until completed successfully: The status in Last Scan for Security Guard shows as failed even though it is in progress. The scan is counted as failed.

  • DS-214 New UI - Security Guard - information in the toast is not accurate: Starting the Security Guard invokes a toast that suggests the run was completed, not that a run has started.

  • DS-215 New UI - Only successful Security Guard logs are presented: Only successful Security Guard logs are displayed in the new UI.

  • DS-219 New UI - Events - Filter on user format domain\username fails: Filtering for users where the format is domain\first-name.last-name does not work. No values are returned.

  • DS-223 New UI - Recovery Manager - cannot filter by Cluster: There is no option to select for the Cluster filter. The user can filter by path.

  • DS-222 New UI - events in error are not displayed: Security Guard events only render if the user filters for them.

  • DS-224 New UI - Logout returns a 403 Forbidden page: Logout returns a 403 Forbidden page when you try to open 172.25.60.30/login

  • DS-226 New UI - Snapshots expiry/creation time is not correct on the new RWD UI: Snapshot expiry and creation times are displayed incorrectly in the new RWD UI.

  • DS-230 New UI - Alerts - SG events do not render unless you filter for them: Security Guard events are only rendered if the user filters for them.

  • DS-232 Ignored List - NES not saved on Edit if Target NE Type is changed: When a user edits an Ignored Client IP entry, if they change the Target NE Type (e.g., from Vast to Qumulo), the value in the Source field and the Network Element checkbox does not persist. The user can enter a value in the Source field and check the Network Element, but the Network Element remains unchecked on Save. Workaround: Remove the entry and re-add the new one

  • DS-233 New UI - No data available for policies/shares that are locked out: In the new UI, no additional data is available for policies/shares on triggered ransomware events that have been locked out.

  • DS-157 SID is missing for users added in Learned Thresholds: In the Learned Thresholds tab, user Security Identifiers (SIDs) are not shown for Threat Detectors instances flagged as false positives.

  • DS-158 Snapshot creation job is not starting on demand when all snapshot options are disabled: The snapshot creation job is not starting on demand when all snapshot options are disabled.

  • DS-162 List for affected shares should be fixed for NFS RWD events: The affected NFS exports are displayed correctly in the list, but there is a + sign to expand them next to them; there is nothing else to display.

  • DS-159 For NFS events after lockout/restore access, we are continuously adding rules: When a lockout or restore action is performed on an NFS event, a read-only rule is added to the NFS Export.

  • DS-160 Recovery job is marked as failed, but files are recovered on the share: The recovery job is marked as failed, but files are recovered on the share.

  • DS-156 The NFS export with permission All is not locked out: The NFS export with permission “All” is not able to be locked out.

  • DS-371 Manual snapshot fails if all options in Snapshot Settings are disabled: Manual snapshot fails if all options in Snapshot Settings are disabled.

  • DS-367 SG - igls-securityguard view should be created automatically: Security Guard needs a dedicated SMB share to run its simulated attack. Currently, the user must manually create an SMB share for the Security Guard during the setup.

  • DS-376 Easier to modify Vast SG Access IP: The IP for Security Guard cannot be altered directly. Workaround: Choose a different entry, modify the IP, and then switch back to the desired entry.