File
Libraesva ESG v5.5.gpg
Version5.5
File Size12 KiB
File MD5e753c06d0c4b955b8dc2f4638e0c8c7d
File SHA256ad25fe2957169cb093a99e682500a28ed336c304c81eb87abd1b79b5b35f4d35
Create DateMay 12, 2025
Last UpdatedMay 16, 2025

Libraesva ESG 5.5

These are the major features of this release.

New "AI Classifier" engine for email semantical classification

The Libraesva AI engine leverages a multilingual tensor-based model that builds upon core generative AI technology. Specifically designed for classification tasks, it provides tailored intelligence for distributed architectures, delivering high accuracy and performance.

The Libraesva AI Engine runs directly on our Email Security appliance, no data is exfiltrated. The AI engine focuses on analyzing emails from unusual correspondents or those exhibiting suspicious characteristics.

NOTE: A 20% average increase in CPU consumption can be anticipated.

Improved message scan indicators

The message scan result indicators, which provide a tag-based summary of complex analysis, have been enhanced to include both positive and negative signals and are now integrated with the new "AI classifier engine", enabling more accurate and insightful threat assessments.

Each indicator can also be used as a filter in saved searches and included in custom reports, allowing for more precise tracking and analysis.

API for domain administrator: domain based configuration can now be managed via API too

Domain administrators can now configure their domain-based settings through the API. This enhancement allows for programmatic management of domain configurations, supporting automation and integration with third-party systems.

Full release notes

See the full release notes

Minor upgrades for this release, which includes all 5.5.x versions, are automatically updated as soon as they are publicly available. These updates include all security fixes and bug fixes that can be installed without service downtime, and the expected behavior of the appliance remains unchanged.

NOTE: This upgrade takes up to 15 minutes to complete. The appliance will reboot after the upgrade, there is no expected MTA downtime for clusters, and an expected MTA downtime is approximately 1 minute for single nodes. A Snapshot is always recommended as a best practice!
Enter your Email to download