Comodo Client Security (CCS) keeps detailed records of all antivirus, HIPS, containment, VirusScope and firewall events.
These logs are invaluable for monitoring and troubleshooting on managed endpoints.
The 'Logging' interface lets you specify the location to store logs, the maximum size of log files, and how CCS should react if the maximum file size is exceeded.
Process in brief
Login to ITairian.
Click ‘Applications’ > 'Endpoint Manager’
Click ‘Configuration Templates’ > ‘Profiles'
Click the profile you want to modify
Click the 'Logging Settings' tab
Or click 'Add Profile Section' > 'Logging Settings' if you haven't yet added this section
Click the 'Comodo Client Security' tab > 'Edit'
Click 'Save' to apply settings.
Process in more detail
Open 'Endpoint Manager'
Click ‘Configuration Templates’ > ‘Profiles'
Click the 'Profiles' tab to show all available profiles
Open the profile you wish to work on by clicking its name. This will open the profile's details page.
OR
'Comodo Client Security' settings:
Write to Local Log Database
The log is saved in native Comodo format on the local endpoint.
You can enable extended logging for the following additional items:
Process creation events
CCS components are enabled/disabled by Communication Client .
Changes to CCS configuration made by Communication Client
Submitting files to CAMAS or Valkyrie
Extended logging means that more information is collected about each event. This is most useful if you are working with support to identify and resolve issues. Be aware that extended logging increases the size of log files so takes more disk space.
Write to Syslog Server
Log events are written to a remote syslog server. If enabled, specify the hostname/IP address and port number settings for the server.
Write to Log File (CEF Format)
Logs are saved locally on the endpoint in Common Event Format (CEF) file format.
Write to remote server (JSON format) - Logs are saved in JavaScript Object Notation (JSON) format on a remote server. If enabled, specify the hostname/IP address of the server, its connection port and the security token.
Action when file log size reaches the limit
Behaviour when the log file reaches a certain size:
'Communication Client ' settings:
Crash dump collection - Endpoint Manager creates a dump file if Communication Client crashes on the endpoint. This is useful for analysis and troubleshooting.
Log type – Determines the level of detail included in the log. 'Full' logs are larger so take more space.
Mini - The file only contains enough data to identify the conditions of the crash.
Full - A detailed log of all information related to the crash. Full logs let you analyze the crash in greater detail, but may take longer to generate than mini reports.