Egnyte Protect 9.1 (August 2, 2019)

We’ve made some exciting changes based on your feedback and can’t wait for you to check them out.

  • Archiving: Retention policies can now specify that files are automatically archived when retention expires. Archived files will be moved to the configured archive domain and will be deleted from the source domain. They will be purged according to the trash purge interval configured for the source domain.

    Standalone archive policies can also be created that specify that certain file versions be automatically archived after a specified amount of time following version creation. Archiving based on last access date is not currently supported, but will be in the future (Q4 2019).

    Only Egnyte Connect domains are supported as archive destinations.

  • Sensitive Content False Positive Whitelisting: Now you can mark false positive matches within a file that will result in all identical matches within the file being whitelisted. Such matches are hidden and do not contribute to sensitive content scoring.

  • Malicious IP detection in Compromised Account rule: Logins from known malicious IPs (based on MaxMind database) will be flagged as Compromised Account issues.

  • India jurisdiction: An India jurisdiction is now available in the Content Classification settings. This jurisdiction includes India PII patterns and a built-in policy corresponding to the Indian privacy law.

Experience the difference. Learn more about Protect today. Don't forget to comment about these changes in the Community.   

Egnyte Community

Egnyte Community

Want to connect with other Egnyte users and our Egnyte team? Share ideas and ask questions in our Community .