![]() When this service is not running, the Anti-Malware engine does not work according to the policy. Check Point Anti-Malware Protection service - performs malware protection.Check Point Client UI service and Client UI process - perform user actions handling and show blades status and messages.When this service is not running, the blades do not get the latest policies and do not update the UI and server about their status. Check Point Device Auxiliary Framework service - performs all communications with the installed Endpoint Security Blades and UI. ![]() When this service is not running, the client is disconnected from the server. Check Point Endpoint Agent service - performs all communications with the Endpoint Security Server, including Policies download, log upload, etc.On the client-side, there are several important components which communicate one with another, as described in the figure above. Policy Servers provide the same functionality to Clients however, they cannot be used to manage policies with SmartConsole. To reduce load to the Endpoint Security Server, additional servers can be deployed. The Endpoint Security Client sends the following Anti-Malware-related information to the Endpoint Security Server: Signatures can also be downloaded from different Internet Sources according to the policy. Product architecture Client-Server architectureįrom the Anti-Malware perspective, Endpoint Security Client gets the following information from the Endpoint Security Server: This document describes several aspects of the Anti-Malware blade - its principal architecture, functionality, working with the blade within Endpoint Security Client and configuring its policies with SmartConsole, and troubleshooting recommendations. The Endpoint Anti-Malware blade's purpose is to protect PCs from viruses, spyware, and other malicious software. Introduction to End Point Anti-Malware blade
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |