Current Release - Release Notes Ransomware Defender

What’s New in Superna Eyeglass Ransomware Defender Edition Release 2.5.12 (05/09/2023) 

What’s New in Superna Eyeglass Ransomware Defender Edition Release 2.5.11 (04/03/2023) 

New in 2.5.11-23110  

Zero Trust API  now supports locking out ECS users.

Active Directory Compatibility

What’s New in Superna Eyeglass Ransomware Defender Edition Release 2.5.10 (03/06/2023) 

Fixed in 2.5.10

RWD-207 Files displayed after the hour-long wait

Tree View and All File Activity view will show content only after an hour-long wait.

RWD -192 Kafka topic empty after cluster down/up

kafka topic will reset after cluster down/up

Count and Size will reset to zero

• before cluster down/up
• after cluster down/up

Support Removed in Eyeglass Release 2.5.9.1

Deprecation Notices

No deprecation notices at this time.

What’s New in Superna Eyeglass Ransomware Defender Edition Release 2.5.9.1 (02/14/2023) 

Fixed in 2.5.9.1

RWD-228 Syntax error in on-boot preventing proper startup timing.

Workaround: not necessary; verify startup has finished on other nodes, if applicable, before attempting to use the ECA.

RWD-222 enable zkcleanup.timer by default

As an ECA user, I don’t want to have to run systemctl enable --now zkcleanup.timer to start the service. This should be run by default on install/upgrade. 

RWD-145 [RWD-NFS Event] Major & critical events are locked out with default rule when reach threshold value even if - igls rsw nfsevents set --enabled=snapshotonly

Major & critical events are locked out with default rule when reach threshold value even if -

igls rsw nfsevents set --enabled=snapshotonly

Steps-

1.Set igls rsw nfsevents set --enabled=snapshotonly in eyeglass

2.Raise NFS Event with Major/Critical severity ( Detector Mode -Enforcement)

3. Observe Locked out event with critical severity & Major event locked out after expiry

Expected Result -

It should not lockout nfs event even when we reach threshold value for Major & Critical events

RWD-146 [RWD-NFS Event] Lockout option in Actions is also removed for SMB event when set igls rsw nfsevents set --enabled=snapshotonly

Lockout option in Actions is also removed for SMB event when set igls rsw nfsevents set --enabled=snapshotonly

Workaround: you can set igls rsw nfsevents set --enabled=true/false/snapshotonly

RWD-113 Wrong Ransomware event state when created with POST /v2/ransomware/lockout/{user}

The Ransomware event that is created using POST /v2/ransomware/lockout/{user} API call has TO_LOCKOUT state. This event should be created with LOCKED_OUT state.

Workaround: manually run the lockout job from the actions menu on the event.

1. zkcleanup.timer runs by default on install/upgrade

2. The NFS implementation to be more consistent with SMB processing

Ransomware Defender Snapshot Management Enhancements

The Ransomware Defender window has a new Snapshots menu where the new snapshot related features Snapshot Budget and Critical Path Snapshot will be managed.  In addition, it is now possible to disable user share/export snapshots.

To maintain existing snapshot behaviour to take a snapshot at the base path of all shares that associated account has access to, ensure that the User Share Snapshot Settings “Enable Share Snapshots” checkbox is checked.

T19619 Critical Path Snapshot

Introduced in 2.5.8 one or more paths can be configured to always have a snapshot created for any detection.

T19823 Snapshot Budget

Going forward Ransomware Defender (2.5.8 build 21213 and higher) maximum number of snapshots created will be the configured Snapshot Budget (default is 5000).  Prior to creating snapshots, Ransomware Defender will determine the number of Ransomware Defender specific snapshots (snapshot name starts with igls) and only if less than the snapshot budget will proceed with the snapshot step. If snapshots cannot be created due to snapshot budget a critical severity alarm is sent and the Event Action History is updated as well.

T15666 New Behaviour Detections Enabled

New behaviour detections are available and enabled by default.

IMPORTANT: This may introduce new detections that will need to be evaluated to determine whether additional tuning of Ransomware Defender settings is required. Recommend to enable Learning Mode after upgrade and verify no new events after several days. NOTE: Learning mode offers full file system protection.

T21215 New SmartAirgap API

New API is available that allows external applications to determine whether there are any active Ransomware Defender or Easy Auditor active events. More information can be found here.

Fixed in 2.5.8-21306

T22033 Log4j Vulnerability - CVE-2021-44228

Resolution: log4j version updated to 2.15.0 which has patch for the vulnerability.

T11832 Ransomware Security Event which is promoted from Warning to Major does not respect Major Grace Period

If a Ransomware Security Event is promoted from Warning to Major threshold, the associated user is locked out right away instead of starting Grace Period timer and only locking out if Grace Period has expired and no manual action has been taken. Note that a Ransomware Defender Security event which is raised at the Major level will respect the configured Grace Period.

Resolution: Major threshold Grace Period timer is now respected.

T18985  igls rsw restoreaccess cannot restore access for unresolvable user

If the user specified in the igls rsw restoreaccess cannot be resolved by the Access Zone AD provider.  For example, a lockout might occur on shares provisioned with the Everyone permission even when the Access Zone AD provider cannot resolve the AD user.  

Resolution: the igls rsw restoreaccess command can now be used to restore access for unresolvable user. Note that when using CLI to restore access the GUI is not updated with the new state.

Technical Advisories

Technical Advisories for all products are available here.

Known Issues

Threat Detection

T4151 Action Window Event Action History does not show Unreachable Cluster

In the event that a Cluster is unreachable during a Lockout operation, the Active Event state will correctly show ERROR and the Event Action History will show “Partially Locked out” but does not display the cluster that was unreachable or the shares that could not be locked out.

Workaround: Manually inspect the clusters that were locked out.  Any missing cluster under management need to review the shares and determine which the affected user has access to and then manually block access.

T3732 Restored permission may be incorrect for consecutive lockouts

In the event that user share access has been locked and subsequently restored and another lockout occurs before Eyeglass inventory has run, the “restore” permissions associated with shares may be the lockout settings from the previous lockout.

Workaround: Permissions should be restored manually by removing the deny permission for the affected user.  Use the Event Action History to determine the affected shares.

T4081 Time Zone Mismatch between Ransomware Defender Security Guard Job History and Event History dates

The Ransomware Defender Job History “Run Date” is based on the Eyeglass appliance time zone whereas the Event History “Detected” date is translated to the client browser locale.

Workaround: Translate date for 1 of the dates to the time zone of the other date to correlate Security Guard Jobs to events in the Event History.

T4151 Action Window Event Action History does not show Unreachable Cluster

In the event that a Cluster is unreachable during a Lockout operation, the Active Event state will correctly show ERROR and the Event Action History will show “Partially Locked out” but does not display the cluster that was unreachable or the shares that could not be locked out.

Workaround: Manually inspect the clusters that were locked out.  Any missing cluster under management need to review the shares and determine which the affected user has access to and then manually block access.

T22321 Escalation from major to critical will not change GUI status and lockout delay is blocked

multi event escalation will block delayed lockout even if the UI shows delayed lockout.

Workaround: Change the multi event threshold to a higher value or make sure you do not leave many active events collect to avoid escalated response settings on the settings tab. These values should be increased if you plan to leave many active warning events without resolving them.

T4777 Snapshots not created for any Events that are Active when the Snapshot feature is enabled

If there are any Active Events when the Create Snapshot option is enabled, no Snapshots will be created for these already Active Events.

Workaround: Enable the Create Snapshot option when there are no Active Events.  Events raised after the Create Snapshot option was enabled will have associated Snapshots created for affected shares.

T4819 Empty Event History List

There may be conditions where having other windows open such as the Event Action History may result in the Event History list being displayed with no entries.

Workaround: Close all Ransomware Defender related windows and then re-open the Ransomware Defender -> Event History tab.

T4950 Alarm text for failed Snapshot delete references Snapshot create

The alarm that is raised when a Snapshot delete fails contains the text “Failed to create snapshots” instead of “Failed to delete snapshots”.

Workaround: Check the Action Log for the event to determine whether a snapshot create or delete has failed.

T4955 Subsequent Create Snapshot action will delete reference to previously created snapshots if an error occurs during the create

The Create Snapshot action can be executed multiple times for a given event.  If it has been run previously and then run again and the subsequent run has an error on creating any snapshot, the Snapshots list only contains the snapshots from the last run. Previously created snapshots are no longer displayed.

Workaround: Check the Event Action History log for complete list of created snapshots.

T5024 Major Events may reappear in the Active Events list after being recovered

An event which crosses the Major threshold and is recovered to Historical Events without being locked out (Stop lockout timer) may appear in the Active Events list again immediately after being recovered (Mark as recovered).

Workaround: Stop the lockout timer and Mark the event as recovered again.  This may have to be repeated several times. Locking the affected user out followed by Restore User Access and then archiving the event as recovered may also resolve this issue.

T5756  Error on restoring permissions does not raise an alarm

If permissions restore action encounters an error there is no associated alarm notification.

Workaround: Review the Action History for the Event to confirm that all restores were successful.

T5954  Events that are promoted to Major due to multiple event “Upgrade to Major” are locked out immediately

For the case where there are multiple Warning events that cross the “Upgrade to Major” limit, when they are promoted to Major they are locked out right away instead of waiting for the configured Grace Period before locking out.

Workaround: The occurrence of this behaviour can be reduced by setting the “Upgrade to Major” threshold to a high number of users.

T6728  Extensions with special characters cannot be removed from the ignore list

Extensions have been added to the extension ignore list using the igls rsw allowedfiles add --extensions command cannot be removed from the ignore list using the igls rsw allowedfiles remove --extensions command.

Workaround: Contact Superna Support at support.superna.net to assist with removing these extensions.

T7062  User may not be locked out in a multi-user security event

It may occur that a user is only partially locked out when a multi-user lockout is occurring due to an error response from the PowerScale cluster during user resolution in Active Directory.  In this case the error is not displayed in the Eyeglass event history.

Workaround: The Event History will contain the shares that were successfully locked out.  Should events continue to be generated against the user for the unlocked share, it may be locked out a a result of subsequent event.  User may also be locked out manually by adding the deny permission manually to share that was not locked out.

T7190  Active Events may show State of Warning instead of Monitor when Monitor Mode is enabled

Instead of the event state being Monitor in Active Events when Monitor Mode is enabled, the event state may incorrectly display as Warning instead.

Workaround: None Required.  This is a display issue only.  Verify that Monitor Mode is enabled on the Ransomware Defender / Settings tab.

T7525  Affected Files also shows Active Auditor Affected Files

When viewing the Affected Files for a Ransomware Defender security event, any files associated wtih an Active Auditor event that has occurred at the same time are also displayed.

Workaround: Download the csv file and use the path associated with the Ransomware Defender event from the GUI to filter the results.

T15639 T18812 Error replicating AD Group or Local User Run as Root SMB permissions affects Lockout and Restore

In some cases an SMB share permission that is configured with an AD groupor Local User that has Run as Root privileges has an error on share updates for Ransomware Defender that blocks Lockout such that it does not take effect or on Restore it does not restore the Run as Root SMB share permission.

Important: If you use run as root on shares you are exposing data to very high security risk since no ockout will be possible. This is because the user SID that is sent when an AD user accesses data with run as root enabled is the root user SID not the actual AD user SID.

We recommend to NOT use run as root on shares for the reason above and it fails all security audits of PowerScale in all industry standards (PCI, HIPPA, FedRAMP, ITSG, etc...). Remove run as root option on all shares.

Please review our documentation for more information: Securing root user on PowerScale.

Workaround: Manually restore or lockout user.

T16229 GUI incorrectly reports error when manually creating a snapshot

If you use the Action menu to manually create a snapshot, the GUI shows an error but the snapshot is actually created. Automatic snapshot creation as part of active event detection is not affected by this issue.

Workaround: None required as snapshot is created. Verify snapshot creation using Powerscale OneFS interface.

T16462 NFS lockout may fail

Under some conditions Ransomware Defender successfully detects security event and notifies regarding the event but the associated NFS lockout action fails.

Workaround: Manual steps to block access to the Powerscale cluster are required in this case.

T18271 Ransomware Event State incorrect shows success when Powerscale is unreachable during restore operation

If a Restore operation is initiated on an Active Event when the Powerscale cluster is unreachable, the restore steps will fail but the state of the Event on the Active Events GUI is ACCESS_RESTORED.

Workaround: None required.  The Event Action History shows that the restore step failed.  Once connectivity to the Powerscale cluster is restored the Restore operation can be retried.

T18643, T19217 State of Active Event shows WARNING when it should be MONITOR for File Filter in Monitor

When Ransomware Defender is configured for Enforcement Mode and Critical on Mode, an Active Event related to a File Filters extension in Monitor will be displayed in Active Events with State of WARNING instead of MONITOR.

No impact on behaviour, no lockout applied.

Impact to Automatic learning - the File Filter extension is not set to disabled.

Workaround: Review events and put File Filter extension into Disabled as required.

T18718 igls rsw allowed files remove option not working

The igls rsw allowed files CLI command executes and reports success but does not actually activate the extension or file entered in the command.

T19040 After upgrade to 2.5.7, Ransomware Events in Event History do not display the Signal Strength correctly

Signal strength not displayed correctly for Ransomware Events in the Event History after upgrade to 2.5.7 for events that were added to Event History in previous release.

Workaround: None required.  These events had already been managed and archived on previous release.

T19106 Acknowledge/Archive options not blocked while lockout in progress

The Acknowledge / Archive options are incorrectly available to be used in the window of time between when the lockout action starts and the active event enters the Locked Out state. Impact: If selected during that window, the event never enters the Locked Out state and even though it is locked out and there for the restore option is not available to restore permissions.

Workaround: The Event Action History correctly documents the shares that were locked out and the account and time of lockout. The account can be restored from the command line following the instructions here for igls rsw restoreaccess command.

T19198 Multiple concurrent Major Events not upgraded to Critical based on "Upgrade to Critical (events)" setting

The setting to promote Active Events from Major to Critical without having to reach the Critical Threshold, "Upgrade to Critical (events) " is not respected. Events are not promoted until their Signal Strength Threshold crosses the Critical setting.

None Required: Events will be promoted if their Signal Strength Threshold crosses into Critical threshold and Lockout will be applied. For events that remain at Major severity if no manual steps taken, Lockout will be applied once grace period expires.

T19236 Honeypot file detector incorrectly crosses Major threshold in Monitor Mode

When Ransomware Defender has Monitor Mode active the Honeypot file detector incorrectly promotes a Honeypot event to Major instead of staying in Monitor state. Once promoted to Major the Grace Period timer begins and if no manual steps taken a lockout of the account will occur once the grace period expires.

Workaround: Upon notification of the Major event, manual steps can be taken from the Active Event Action menu to stop the Lockout timer and resolve the event from the GUI if appropriate. If a lockout occurs access can be restored through the GUI from the Active Event Action menu as well if appropriate.

T19356 Files/Folders with language characters not displayed properly in CSV and email

If the files/folders associated with a detected Ransomware security event contain language specific characters, the path/file names are not displayed correctly in the email sent as well as the CSV.

Workaround: Use the GUI to see the files and folders.

T19409 Well known extension detection not working under some circumstances

Under some circumstances when there have been no customization to the File Filters for well known extension detection, the well known vector for detection of Ransomware security event is skipped.

This does not affect the user behaviour or honeypot detection vectors.

Workaround: User behaviour and honeypot detection vectors still available for monitoring.

T20094 CLI command to restore access does not work when user name contains special characters

The igls rsw restoreaccess command does not execute if the user name contains special characters. Impact: No impact on lockout. Impact on ability to restore access.

Workaround: Use the Ransomware Defender Action Event history to identify all shares that were locked out and manually remove the deny permission using Powerscale native tools.

T23012 Restore access for NFS lockout from Event History does not complete

Using the Restore User Access option in the Event History for an unresolved NFS lockout will restore the permissions as expected but the job gets stuck at the Restore job initiated step and the overall status does not change to Recovered and no alarm is sent.

Workaround: Verify manually using OneFS native tools that client list for NFS export has been restored as expected.

RWD-279 Lockout API returns response code 500 for ECS IAM User

Lockout API returns response code 500 for ECS IAM User

Security Guard

T4197 Security Guard Error for Unlicensed Cluster

Security Guard fails when PowerScale Cluster selected to run is not licensed.

Since Ransomware Defender dynamically picks priority PowerScale Clusters to license (refer to Eyeglass Ransomware Defender Admin Guide for details on selection of licensed cluster) for the case where Eyeglass is managing more clusters than there are Ransomware Defender Agent Licenses, one cannot be sure the selected Cluster in Security Guard is actually licensed at the run time.

Workaround: Deploy same number of Ransomware Defender Agent Licenses as the number of PowerScale Clusters being managed by Eyeglass.

T8889 Cannot enable Security Guard with default schedule for on a newly deployed 2.5.3 ovf 

The drop down list to schedule security has an invalid default.

Workaround: Click the drop down and set a valid schedule.

T4228  Security Guard Temporary Errors

Security Guard may occasionally error with 0 files written.   

Workaround: This condition typically clears it self on the next Security Guard run. It does not affect workflow for a real security event.

If it does not clear, follow these steps to recover:

1. Archive as Unresolved

2. Run Security Guard manually to ensure that it is operational again.

T4965  Security Guard User Authentication Fails

When provisioning the Security Guard Active Directory User and password, Eyeglass checks that the username name and password entered can be successfully authenticated.  It may occur on initial configuration that you will see the message “user could not be authenticated” even though the username and password are correct.

Workaround: After confirming that the username and password are correct, subsequent provisioning is successful.

T7574  Flag as False Positive Option should not be available for Security Guard Events

Security Guard provides automated end to end validation of Ransomware detection, lockout and restore and therefore should not be flagged as false positive. The Flag as False positive option is currently available to be selected for Security Guard events and should not be.

Workaround: Manual process required to prevent applying Flag as False positive to Security Guard events.

T15175 Existing Security Guard Logs lost formatting after upgrade to 2.5.6

Any existing Security Guard logs viewed from the Eyeglass GUI will have lost the formatting.

Workaround: None required. New logs will have the correct formatting.

Manage Services

T4192 Manage Services status not accurate after ECA Node Down

After an ECA node has been powered off / gone down and subsequently powered back on and rejoined to the ECA cluster it continues to display the Inactive state in the Eyeglass Manage Services window even when it is active again and healthy.

Workaround:  Once the node is back up, remove it from the Manage Services window by selecting the X in the node’s row.  Wait 1 to 2 minutes and the service should be rediscovered with the correct state.

General

T4230 Blank Ransomware Defender Window

After archiving an Event the Ransomware Defender window tabs may appear empty.   

Workaround: Close and reopen the Ransomware Defender window.

T4183  Refresh does not work for Ransomware Defender multi-page lists

Ransomware Defender window with multiple pages is not updated by Refresh except for the first page.   

Workaround: To update the list go back to the first page of the list.

T15457 HTML 5 vmware vcenter bug on OVA deployment

 Some versions of vmware vcenter HTML user interface have a known issue with OVA properties being read correctly post power on, leading to first boot issues.

Workaround: use the Flash client as a work around.

T4336  Eyeglass Restore does not restore Security Guard Job History

Security Guard historical log files are not restored when you restore configuration from backup.   

Workaround: None available.

T4549  Ransomware Defender Settings Submit button enabled when no changes made

When the Ransomware Defender Settings window is opened, the Submit button is enabled even though no changes have been made to any settings. If you navigate to another view and come back to Settings, the Submit button is then correctly disabled until a change is made on the page.  

Workaround: None required.

T6617  PowerScale Directory Selector does not display hidden directories

Directories that start with a dot (.) are not displayed in the PowerScale Directory Selector.   

Workaround: Use the PowerScale Directory Selector to enter \ifs\ and then enter the remainder of the path manually.

T8807  Deleting cluster from Eyeglass does not clear associated Ignore List and Wiretap settings

When an PowerScale cluster is deleted from management in Eyeglass, any associated Ransomware Defender Ignore List or Wiretap settings are not cleared.  

Workaround: Manually delete Ignore List and Wiretap settings for deleted clusters.

T18810 GUI not updated after cancelling an operation to switch modes

In the Ransomware Defender Thresholds window, if you are switching between Advanced and Monitor or Advanced and Enforcement mode and upon being prompted you select No to cancel the operation, the GUI does not refresh and return to the original Advanced mode. Impact: Display issue only, the mode change is cancelled.

Workaround: Switch between tabs in the Ransomware Defender window or use the Eyeglass desktop Refresh Now button.

T18660 Cannot use cloudapps URL to access Well Known Ransomware File Extension list

The cloudapps URL documented here for accessing the Well Know Ransomware File Extension list does not resolve and returns a 404 response code.

Workaround: Following URL does resolve and can be used to manage the Well Known Ransomware File Extension list: https://storage.googleapis.com/rwdefender.superna.net 

T22450 Easy Auditor Event Rate alarm for Ransomware Defender Only deployments

RWD-114 Creating Critical Path Snapshots is blocked

RWD-301 Error getting events - for NFS exports in Recovery Manager

Cyber Recovery manager will show error when trying to display the all activity files affected by NFS export events.

RWD-319 RSW events affected files are not presented in email

RSW events affected files are not presented in email

RWD-362  Support ECS on RWD when turboaudit REST api is configured

Support ECS on RWD when turboaudit REST api is configured

RWD-380 TD11 is not triggered as described in the documentation when using ECS

TD11 is not triggered as described in the documentation when using ECS

Features

RWD-217 Event fails to upgrade with multiple user (ECS events only)

Workaround:

RWD-74 zookeeper cleanup cron is not running as scheduled

Workaround:

apply this command to all eca nodes

1systemctl enable --now zkcleanup.timer

RWD-246 Files with non-ASCII characters fail to recover

2.5.9-22231

Files which will have the extension modified to a known extension like .crypto will trigger TD7 events.

The original files are not recovered even if the Recovery Job finishes successfully.

Known Limitations

Threat Detection

T6914  Some extensions still result in lockout when added to the ignore list

For the following well-known extensions, a lockout will still occur even if these extensions have been added to the extension ignore list using the igls rsw allowedfiles add --extensions command:

*.[teroda@bigmir.net].masterteroda@bigmir.net

*.[mich78@usa.com]

*.symbiom_ransomware_locked

*.[resque@plague.desi].scarab

Workaround: Alternate Ignore capabilities for User, Path or IP address documented here may be used to workaround this issue.

T7191 SMB service not enabled when access restored when lockroot is true

If you have Ransomware Defender configured to disable SMB service is a root user event is detected (see Ransomware Admin guide here, section Securing Root User on PowerScale ), when you restore user access the SMB service is not automatically enabled.

Workaround: Manually enable SMB service on PowerScale once access is restored and you are ready to resume file access for SMB users.

T7670 Restoring user access via CLI does not update status of Security Event in the GUI

If you have restored user access after a lockout using the CLI command "igls rsw restoreaccess set --user=DOMAIN\\user ", the associated Security Event in the GUI will not be updated and remain in active state.

Workaround: Open the Actions window for the active event, enter a comment that access has been manually restored and then archive the event.

T8744 No event processing once Signal Strength passes 2 times Critical Threshold

For the case where both Ransomware Defender and Easy Auditor are licensed, reaching Signals processed count of 2 times Ransomware Critical threshold for a particular user limit is applied independently for Ransomware Defender and Easy Auditor.

Workaround: None Available.

T8986 NFS export lockout cannot be restored

Workaround: On lockout NFS clients are moved to "Always Read-Only Clients". They will need to be manually moved to the correct access type using Isilion GUI or CLI to modify the export.

T15705 After upgrade to 2.5.6 cannot download CSV for Ransomware Event Files from events detected in prior releases

After upgrading to Release 2.5.6, csv download of files related to Ransomware events generated on the previous release is not available.

Workaound: GUI can still be used to view the files or files may be found on the Eyeglass appliance in the /srv/www/htdocs/rsw_event_all_files directory.

T16723 Error on Lockout of Shares on DR cluster

Under some conditions where a Ransomware Defender Lockout job overlaps with a Configuration Replication job you may see an error locking out some shares on DR cluster with error message code 409 AEC_CONFLICT. No impact to protection from Ransomware as the shares on the DR cluster are providing access to read-only data.

Workaround: You can re-attempt the Lockout from the Ransomware Defender window Action menu for the Active Event. Deny permission can also manually from Powerscale interface as required.

T17287 Many Access Zones slows down creation of snapshots and lockout

In the case where there are many Access Zones configured, analysis of user accessible shares must be done for all Access Zones before snapshot processing or lockout is started.

Workaround: None available

T7574  Option to set learned threshold for Security Guard in RESTORED_USER_ACCESS state

The menu to add Security Guard to the Learned Threshold is incorrectly provided when the event is in the RESTORED_USER_ACCESS state.  The option can be selected and indicates that the flag as false positive was applied but it is not actually applied and it does not appear in the Learned Threshold list.

Workaround: None required

T18733 Ransomware Defender Affected Files Download Menu Naming 

The Ransomware Defender Affected Files Download Menu is incorrectly named Affected Files - All.  As described in the Ransomware Defender documentation here it is possible to have more files associated with the event than displayed in the file.

General

T16137 Anyrelease restore does not restore all Ransomware Defender and Easy Auditor settings

There is no restore of settings from release 2.5.4 and earlier. For release 2.5.4 and earlier continue to capture all Ransomware settings (False Positive, Ignore List, Allowed Extensions, Security Guard) and Easy Auditor settings (Active Auditor Trigger settings, RoboAudit). Post restore verify settings and update where required before cluster up on ECA.

In all cases, restoring an Eyeglass backup using the --anyrelease option will not restore following Ransomware Defender and Easy Auditor settings:

Ransomware Defender: Event History, Threats Detected

Easy Auditor: Finished Reports, Scheduled Reports, Saved Queries

T16821 anyrelease restore restrictions for restore to 2.5.7

Ransomware Defender, Easy Auditor and Performance Auditor deployments cannot use the anyrelease restore option to upgrade to a new appliance running 2.5.7.  For case where a backup & restore is required due to 42.3 OS on original deployment, a backup & restore to 2.5.6 will have to be done first followed by an upgrade to 2.5.7 or inplace OS upgrade prior to 2.5.7 upgrade.

T20370 Monitor Only Settings Client IP applies to all PowerScale clusters

If multiple Powerscale clusters are licensed for Ransomware Defender a setting in the Client IP list for Monitor Only Settings is applied to all clusters. There is no option to associate the setting to a specific cluster. Also if you convert Ignore List to Monitor list any Client IP setting from Ignore list will also be applied to all cluster.

T21852 RSW - Cannot configure and run SG after anyrelease backup and restore from an earlier build

After a backup and restore from the earlier release to Eyeglass 2.5.8, the Ransomware Defender window may no longer allow you to edit or run the Security Guard.

Workaround: After the restore, execute the 2.5.8 run file (same release as you restored to) to resolve the issue.

T21208 Snapshots taken using Action Menu for Ransomware Defender Event follow Ransomware / Snapshots settings

If the Enable Share Snapshots option in Ransomware / Snapshots is unchecked, selecting the Create Snapshot option from the Action Menu will also not create snapshots.

T21110 Ransomware Defender / Snapshots User Share Snapshot Settings also applies for NFS detections

The option to disable/enable Ransomware Defender snapshot functionality is called User Share Snapshot Settings and Enable Share Snapshots but applies to any Ransomware Defender detection for SMB or NFS.

Well Known Ransomware File Extension Whitelist management is not available when a proxy used

If a proxy has been configured to access the internet, the well-known ransomware file extension management does not account for the proxy and will not be able to resolve the configured URLs.

T17624 Ransomware Defender NFS detection creates snapshot on SMB shares with Everyone permission

A Ransomware Defender detection for operations over NFS protocol also creates snapshots for SMB shares that have the Everyone permission.

RWD-75 Page-1 gets hide when navigate to Page-2 & archive all events from this page

RWD-236 [RWD-NFS Event] User is displayed as "Root" or Sid ID instead of EXP:<client_ip>_<user_id>

When using nfs 4 version - it cannot show the EXP:<client_ip>_<user_id>

Workaround: use this command to mount the NFS export.

mount -o nfsvers=3 <isilon-ip>:<export-path> <mount-path>