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. Sudo /opt/BitDefender/bin/bduitool get ps Verify that the Antimalware module On-access scanning is enabled on the security agent, run the following command: 
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.
On-access scanning is incompatible with certain security policies applied on that endpoint. On-access scanning is disabled from the policy settings regarding the Antimalware module. In some situations, On-access scanning from Bitdefender Endpoint Security Tools may not properly work on the Linux endpoint. This article describes how to troubleshoot On-access scanning in Bitdefender Endpoint Security Tools for Linux.
0 kommentar(er)
