qosaassets.blogg.se

To learn how to configure Fanotify in Debian 8, refer to this KB article. The security agent is using a newer kernel than 2.6.37 and the Fanotify feature is active in the kernel.In this case, the output will look like this: Product version: 6.2.20.87 For example, run the following command: sudo /opt/BitDefender/bin/bduitool get ps In case the remote scan is used, no fallback engine is configured, and the endpoint cannot communicate with Security Server, then the Antimalware module will not work at all. This information is displayed by running the bduitool get ps command. The endpoint can successfully connect to its allocated Security Server through ports 70, if the Scan Type is set to Remote.Go to the Network page, in GravityZone Control Center, and make sure that the endpoint does not have Pending or Expired status under Protection Layers section. The endpoint is correctly communicating with the GravityZone console or with the assigned relay endpoint.Also, check in the GravityZone console that On-access scanning for Linux option is enabled in the policy and has target paths defined in the list. The endpoint has a security policy active that does not disable On-access scanning.To make sure that the Antimalware module is working properly, check the following conditions: Conditions required by Bitdefender Endpoint Security Tools for Linux The On-demand scanning feature of the Antimalware module is always enabled. This is only referring to the On-access scanning feature of the Antimalware module. In this example, the Antimalware module status is Off. Verify that the Antimalware module On-access scanning is enabled on the security agent, run the following command: sudo /opt/BitDefender/bin/bduitool get ps

The conditions required by Bitdefender Endpoint Security Tools for Linux.

To find out why On-Access scanning is not working, you have to verify: This usually happens because of missing dependecies on the endpoint operating system.