Ransomware Infection Rule (BETA)

Egnyte Protect can now detect evidence of ransomware infections within your content repositories. This allows you to interrupt and contain active ransomware by disabling the affected user account. Ransomware is detected by the presence of “ransom note” files and known bad file extensions.

To enable this rule, open the settings for a given content source and turn on the switch for the Ransomware Infection rule.

Sensitive Content Whitelist Setting

A new source setting allows you to directly specify which folders are allowed to contain sensitive content of a particular type. Changes made in this setting are reflected in the permitted content list shown in the Sensitive Content view and vice-versa. You can permit whole parts of your folder hierarchy to contain certain types of sensitive content. For instance, you could specify that all HR folders are allowed to contain PII. Also, you can now proactively permit folders for certain kinds of content, even if no files with such content exist in that folder yet.

New Custom Policy Editor

We have revamped the interface for creating custom content classification policies. The new interface is better organized and more spacious.

Privacy Mode setting

A new “Change Display Options” option is shown within the account dropdown menu in the UI. Choosing this option opens a dialog where you can enable Privacy Mode. While Privacy Mode is active, sensitive content matches are shown with the actual sensitive content text (e.g. the Social Security Number) redacted. Privacy Mode is useful when reviewing sensitive content matches with people you may not want to disclose actual sensitive content with.

Privacy Mode is specific to your login session and remains enabled for the duration of the your session - it’s automatically disabled on next login.

Fair Credit Reporting Act policy

We have added a new regulatory compliance policy that looks for consumer credit reports from the three major US credit reporting agencies: Equifax, Experian and TransUnion.

Support for non-ASCII characters in custom keywords

Non-ASCII (aka multi-byte or Unicode) characters are now supported in custom keywords. This allows matching in foreign languages that have accents or different character sets.