WithSecure Elements Connector change log
This thread is a changelog for the WithSecure Elements Connector product.
📝 Click here to see the most recent change log and bookmark the discussion to be notified of any updates.
F-Secure Elements Connector is a product that serves two needs:
- Offers an easily adaptable solution for partners who use SIEM products to monitor managed environments.
- Allows you to connect the traffic between managed endpoints in your environment and F-Secure cloud services.
Installation and upgrade:
- Elements Connector installation and configuration are all self-service steps. Elements Connector subscription is free of charge but it is needed for registration. Subscription can be created by PSB portal users for any company directly from the Downloads view. See Elements Connector Getting Started Guide to get the Connector up and running: https://help.f-secure.com/data/pdf/elements_connector_eng.pdf
- Once installed Elements Connector is automatically upgraded from the channel.
- Elements Connector replaces F-Secure Endpoint Proxy keeping all proxy capabilities. F-Secure Endpoint Proxy is still around until Elements Connector for Linux is available.
- Elements Connector is fully managed from PSB portal being visible in the Devices view and configurable via profiles.
- With Elements Connector, you can stream all security events from the F-Secure Elements portal to your SIEM. Elements Connector supports Syslog, Common Event Format (CEF), and Log Event Extended Format (LEEF) message formats to stream data, which makes it a generic solution to integrate seamlessly with almost any SIEM. You can configure the use of the forwarding feature for the whole partner scope or limit it to a certain company.
- Elements Connector keeps all proxy capabilities as were supported by F-Secure Endpoint Proxy. Now it serves malware definitions (GUTS2 traffic) and software updates (SWUP).
- Only Windows version is supported. Linux support is coming soon.
- TLS over TCP is not supported when forwarding security events to SIEM.
- Elements Connector self-generated CA has to be exported and manually added to endpoints trust store in order software updates traffic to be served. Alternatively, Elements Connector self-generated server certificate can be replaced with a certificate that is trusted by the endpoints.
A new release 21.37 is rolled out with the following changes:
- Connector is now able to forward data to SIEM over an encrypted channel (TLS for TCP).
- Forwarded events are extended with complementary properties that are starting with the 'details_' prefix, e.g. details_sha256, details_infectionName, details_targetPath.
- To improve readability some event messages are rephrased and their parameterization is adjusted.
- Elements portal now properly shows Windows 10 version for Connector devices.
- When encountering any unrecognized event or receiving large responses, the Connector could stop forwarding further events.
- Connector could generate extra API requests in case SIEM address or port was misconfigured.
I am happy to announce that Elements Connector for Linux is now available for downloading from all production portals as DEB and RPM installation packages.
Check the updated Elements Connector Admin Guide for the list of the supported platforms and installation instructions: https://help.f-secure.com/product.html#business/connector/latest/en/concept_BA55FDB13ABA44A8B16E9421713F4913-latest-en
Please be aware that current installations of Elements Connector are affected by the Log4J Vulnerability (CVE-2021-44228).
We urge you to apply a hotfix as described in this post:
I am happy to announce that Elements Connector update with the Log4J Vulnerability fixed has been now released. The existing installations will be updated automatically.
The other changes included in this update:
- Security events payload larger than 1KB is no longer truncated when forwarding to SIEM.
- User defined HTTP and HTTPS ports are now kept on the upgrade (applicable for Windows version).
- To simplify event forwarding configuration on Linux, the post installation script is improved.
Please be aware that current installations of Elements Connector are affected by the Spring4shell Vulnerability (CVE-2022-22965).
This hotfix provides an updated Spring Framework (5.2.20), which fixes recently reported vulnerability CVE-2022-22965.
PS. We will provide updated version of Elements Connector via the channel upgrade, but it will still take few weeks.
A new release 22.18 (Windows) / 22.19 (Linux) is rolled out with the following changes:
- Support EDR BCD incidents in Security Events forwarding to SIEM systems. This feature is planned to be released into production back-end later this week.
- Includes latest spring4shell updated binaries, so after new installation you don't need to apply any hotfixes anymore.
First time installers are now released and you can manually upgrade to latest version or wait for the channel upgrade that is planned to happen on Tuesday 14th of June.
channel upgrade for both Windows 22.18 and Linux 22.19 Elements Connector was release just.
A new release 22.35 (Windows) / 22.34 (Linux) is rolled out with the following changes:
- Memory leak that might happen in certain conditions is now fixed
First time installers are now released, and you can manually upgrade to latest version or wait for the channel upgrade that is planned to happen on Tuesday 4th of October.
AleksandrG Posts: 3 WithSecure Product Manager
A new release 23.05 is rolled out with the following changes:
- The Elements Connector Ultimate proxy is introduced with this release. This feature allows Connector to act as a proxy for all traffic between WithSecure endpoints and cloud services simplifying firewall configurations and allowing the use of WithSecure products in semi-closed environments. It extends GUTS2 and SWUP caching only mode and is enabled for all Connectors by default.
- It is now possible to chain Elements Connectors so that it uses another one to reach the backends. For that, you need to specify the upstream connector in the profile as an HTTP proxy. You can specify multiple Connectors using a semicolon.
- With this release, Elements Connector starts using the new Elements API to forward security events. If Connector was already configured to use Event Forwarding, it continues using current credentials after the upgrade, follow API configuration instructions to reconfigure and start using the new Elements API.
- With this release, we introduce support for multiple HTTP proxies so that Elements Connector remains connected in case of proxy failure. You can specify multiple HTTP proxies using a semicolon. If the connection becomes unstable, Elements Connector starts using the next proxy from the list:
- Elements Connector integration for Microsoft Sentinel is now available in the Azure Marketplace.
- This release introduces WithSecure brand.
- Forwarded events now have WithSecure vendor name, if your SIEM is configured to filter based on the vendor name, this filter has to be adjusted.
First-time installers are now released and you can manually upgrade to the latest version or wait for the channel upgrade that is planned to happen on Tuesday 28th of February.