LIBRAESVA ESG V4.9

On the 29th December 2020 we released Libraesva Email Security Gateway 4.9! 

All of our Libraesva Private Cloud customers will have their machines upgraded automatically at a time where the technical team see fits, however if you want to upgrade earlier, or are an on-premise user, visit this link here: https://docs.libraesva.com/download/libraesva-esg-4-8-to-4-9-upgrade/. 

All features and improvements are included as standard with all versions of Libraesva ESG, unless stated otherwise. 

Below is an overview of the changes that comes with the Libraesva Email Security Gateway 4.9 release. 

New Multi-FactorAuthentication with T-OTP 

Till the previous Libraesva ESG release the appliance login was simply related to a username and a password. We have now implemented Multifactor Authentication for Local DB users (Users and Admin). We are using Time-Based OTP (one-time password) which can be used in conjunction with Google Authenticator APP (or any other application which accepts T-OTP) for MFA. 

Allowing us to offer MFA for all our user types not just M365 or G Suite. 

Threat Remediationfor G Suite 

Libraesva ESG Email Threat Remediation is a feature to recall delivered messages to user’s managed mailboxes.  

Thanks to the new connector you can now recall directly from Libraesva ESG interface, the email that you have in your G Suite inbox 

Guide: https://docs.libraesva.com/document/threat-remediation/g-suite-threat-remediation-settings/ 

Custom TLS certificates

These certificates can be used to relay email to internal domains. 

URLs rewritten by URLSand can be logged to syslog 

Addition to the syslog of URLs rewritten by the URLSand Sandbox Libraesva, in order to convey this information into a SIEM and to know which URLs have been rewritten and in which message they are embedded 

Example: Jan  6 07:01:56 mail MailScanner[17998]: Content Checks: Detected and have disarmed web bug, comment, urlrewriter tags in HTML message in 47B5341303.A63C4 from [email protected] 

New configurable sender/recipient address/domain rewriting rules

We have implemented a Domain rewrite for customers who have two domains but wish to manage them as one. Now, Libraesva ESG can transparently replace domains or email addresses, both for the email sender and recipient. 

Example: Libraesva.com and Libraesva.it. We would rewrite the Libraesva.it to .com and treat it everything as Libraesva.com