Marcos

It's up to you - if you want to keep current settings, install v15 over, otherwise uninstall v14 and install v15 from scratch. You can also export the configuration and import it into v15 if you want.

Please try downloading and installing v15 over v14 or uninstall v14 and install v15 from scratch.

Then re-configure Apache http proxy as follows:
1, Either disable the module reqtimeout_module
2, Or disable limits, ie. by creating a new file reqtimeout.conf in /etc/httpd/conf.d/ and setting "RequestReadTimeout header=0 body=0". Include the file in the configuration, ie. add "IncludeOptional conf.d/reqtimeout.conf" to /etc/httpd/conf/httpd.conf.

Then re-configure Apache http proxy as follows:
1, Either disable the module reqtimeout_module
2, Or disable limits, ie. by creating a new file reqtimeout.conf in /etc/httpd/conf.d/ and setting "RequestReadTimeout header=0 body=0". Include the file in the configuration, ie. add "IncludeOptional conf.d/reqtimeout.conf" to /etc/httpd/conf/httpd.conf.

There is also a write-up on this vulnerability available at https://www.welivesecurity.com/2021/12/13/log4shell-vulnerability-what-we-know-so-far/.

More information here:
https://support.eset.com/en/alert8188

We don't use Log4J in our products so they are not affected by the vulnerability.

This has been already fixed and the modules should start updating soon.

To sum it up, the issue may be caused by 2 things:
1, If you use Apache http proxy on Linux - the configuration of the http proxy is incorrect. Please refer to the post above how to fix it. Apache HTTP proxy for Windows is not affected.
2, If you don't use Apache http proxy - the issue is caused by a bug in Endpoint v9 which checks for EPNS connectivity even if checking for license changes via EPNS is disabled, ie. when the interval check is set to "Limited". Solution: change it to Automatic. If you need to have it set to Limited for whatever reason, there will be a fix via an automatic module update within a couple of days. Please use "Automatic" at least temporarily until the new Direct cloud communication module is available.

Currently there's nothing you could do to prevent this, however, there should be a module update probably this month which will temporarily quit deleting these policies. Later you will be able to create cleaner exceptions yourself, this option is not available in the Endpoint setup yet.

Currently there's nothing you could do to prevent this, however, there should be a module update probably this month which will temporarily quit deleting these policies. Later you will be able to create cleaner exceptions yourself, this option is not available in the Endpoint setup yet.

To sum it up, the issue may be caused by 2 things:
1, If you use Apache http proxy on Linux - the configuration of the http proxy is incorrect. Please refer to the post above how to fix it. Apache HTTP proxy for Windows is not affected.
2, If you don't use Apache http proxy - the issue is caused by a bug in Endpoint v9 which checks for EPNS connectivity even if checking for license changes via EPNS is disabled, ie. when the interval check is set to "Limited". Solution: change it to Automatic. If you need to have it set to Limited for whatever reason, there will be a fix via an automatic module update within a couple of days. Please use "Automatic" at least temporarily until the new Direct cloud communication module is available.

If you have a license for ESET CyberSecurity for Mac, you can install ESET NOD32 Antivirus on Windows provided that you have a free license seat.

The firewall is not a part of ESET Endpoint Antivirus. You must install ESET Endpoint Security if you have a license for it.

The issue was resolved on Friday with the release of the Advanced antispam module 7909.1.

Since this is a quite specific question that we won't be probably able to answer in a timely manner here, I'd recommend raising a support ticket.

I was able to find only an expired trial license registered with your forum email address. Please provide your public license ID in the form of XXX-XXX-XXX.

The feature will be included in ESET Server Security v9 next year.

If you send a Run command task from the ESET PROTECT console, the command is run in the system account so you should leave out psexec and replace it with "powershell" command followed by the script name. Haven't tried running a PS script remotely this way but I guess it could work.

Hello ESET consumer security products users,
We are pleased to announce the availability of ESET NOD32 Antivirus, ESET Internet Security  and Smart Security Premium version 2022 for ARM64 devices
The new generation of ESET products for Windows ARM brings new features and improvements, let us briefly describe the most visible ones.
What’s new
LiveGuard – A new service that is personalized to you, designed to discover and stop never-before-seen types of threats. Handles a wide range of file types, including documents, scripts, installers and executable files. Suspicious files are run in a safe, sandboxed environment ESET HOME - is a web portal and mobile app for Android and iOS that provides comprehensive oversight of ESET products, licenses and services on your devices. It’s designed to be accessible whenever you need it, wherever you go Improved Exploit Blocker, Host-Based Intrusion Prevention System (HIPS), Password Manager, Network Inspector  
Official ARM64 support : Note, that following features are not available due to incompatibility. Banking and Payment Protection (EIS, ESSP), Advanced Machine Learning (EAV,EIS,ESSP), Deep behavioral inspection (EAV,EIS,ESSP) and Secure Data (ESSP) features are not available for ARM64 platform in this version.
To install product go to :
ESET Internet Security : link  

ESET Smart Security Premium is the highest product with most features for home users.

Unfortunately it seems you fell a victim to scam. To prevent this, we recommend purchasing a license from authorized partners.

Yes, Smart mode honors all created rules.

Since this topic has gone astray and turned out into features requests and comparisons, we'll draw it to a close. The purpose of the topic was to determine how many users have come across a false positive with aggressive detection set.
Regarding behavior monitoring, I have checked with developers and confirm that the system is continually being improved and we plan to continually work on it.