Jump to content

user209

Members
  • Content Count

    6
  • Joined

  • Last visited

Profile Information

  • Location
    Syria
  1. When creating a Dynamic group under ESET protect, there is an option to use IP Subnetwork as a category to group hosts. This is the "Network IP addresses . IP subnetwork" expression field. The issue is it appears to be a proprietary subnet format. CIDR notation doesnt work, and standard IP ranges dont work (192.168.0.0/23 or 192.168.0.0 - 192.168.1.255). After looking at some forum posts which suggest trying wildcards or some other formats, those also fail. Please update the software to use a standard IP subnet format that the rest of the industry uses. There is no reason that this d
  2. I receive the following errors when attempting to install the newest version of ESET for linux on a fully updated Debian 10 system: chown: invalid user: ‘eset-eea-logd’ chown: invalid user: ‘eset-eea-scand’ chown: invalid user: ‘eset-eea-updated:eset-eea-daemons’ ESET Endpoint Antivirus Error: Cannot connect to Confd: No such device or address
  3. Is there any way I can securely transfer ESET the zip output of ESET log collector, to avoid leaking information on a public forum?
  4. Yes, as stated in the post, we have ran "scan with cleaning" on multiple occasions and the detection is not removed.
  5. We have had a multitude of detections that are listed as "Unresolved" and shown as "retained". Our understanding is that running a "Scan with cleaning" should delete the files or quarantine them. However, after the scan, the files are still present and repeatedly detected. How can we get ESET to delete all detections, instead of "retaining" over 50% of detections (including trickbot malware embedded doc files)? The organization is using ESET security management center as the interface to control endpoints.
×
×
  • Create New...