Troubleshooting POCs

Use the following tools for troubleshooting during POCs.

Run Diagnostics Push Operation

To troubleshoot CPU and RAM usage caused by Threat Prevention blades, use a Run Diagnostics Push Operation. The system generates an automated process exclusion list after reviewing the interactive report. For more information see, Show Last Diagnostics Report section in Harmony Endpoint EPMaaS Administration Guide.

A screenshot of a computer

AI-generated content may be incorrect.

Caution - It is not safe to add all the suggested exclusions, example, svchost.exe, powershell.exe. For assistance, involve Check Point TAC, local engineers and Harmony Endpoint architects.

Behavioral Guard Low Memory Mode

To reduce RAM consumption on low-spec machines, enable Behavioral Guard (BG) Low memory mode in the Advanced policy settings. Low memory mode significantly reduces memory utilization by retaining only the most recently matched signatures. While it slightly reduces the catch rate, it remains at an effective level.

Disable Capabilities

For troubleshooting purposes, you can temporarily disable selected client blades (except for Data Protection blades) from the client UI with the following steps:

  1. Go to Client Settings policy > General and select the blades to be disabled and set a password.

  2. On the Endpoint Security client, go to Overview > Edit Capabilities.

  3. Enter the password and choose the blade to disable.

Uninstall Capabilities

For troubleshooting purposes, you can temporarily uninstall selected security blades from the client via Software Deployment policy.

Caution - Do not change client version and capabilities at the same time.

CPinfo

For client issues which require support tickets and TAC investigation, collect Harmony Endpoint security client logs.

To collect Harmony Endpoint client logs:

  1. Do one of these:

    1. Collect CPinfo from the client machine. See sk90445.

    2. Manually collect relevant log files under C:\ProgramData\CheckPoint\Logs\

  1. Open a Service Request with TAC:

    https://help.checkpoint.com/s/create-new-sr

  1. Escalate to local Check Point SE or Harmony Endpoint Architect.

Troubleshooting Browser Extension

For Browser extension issues, check the following:

  1. Force a policy update by terminating all browser processes and restarting the browser.

    Note - Browser processes may still be running in the background by default.

    Alternatively, manually refresh the browser policy.

    chrome://policy/

    edge://policy/

    brave://policy/

  1. Verify that the current policy version has reached the client with the following flow:

    1. On the Harmony Endpoint Administrator Portal, go to Web and Files Protection > versions > Threat Emulation.

    2. On the Endpoint Security client, go to Advanced > View Policies.

  2. On the browser, verify that the te_cloud_api_key is valid and is the expected license key:

    chrome://policy/

    edge://policy/

    brave://policy/

Client Troubleshooting Logs

Use the following log locations to troubleshoot issues.

Issue

Logfile

Comment

Browser Extension errors

To collect the browser extension log file, from the Extension UI, go to Collect Logs.

Once collected, the log file will be available in the Downloads folder:
harmony_web_protection_logs.txt

Harmony Endpoint UI errors, deployment errors

Harmony Endpoint client logs (CPinfo)

Collect logs from Endpoint Security client:

Go to Advanced > Collect.

Crashes / Dump Files

C:\Windows\Internet Logs\CP_EFR Crash*

 

Deployment issues

C:\Program Files (x86)\CheckPoint\Endpoint Security Agent\Endpoint Common\Logs\cpda.log (or %DADIR%\Logs)

 

False Positive / False Negative

Use the following steps:

  1. Collect a CPinfo.

  2. Collect the Forensic Database:

    1. Press the Start key.

    2. Type CMD, right-click the program and choose Run As Administrator.

    3. Run:

      C:\Program Files (x86)\CheckPoint\Endpoint Security\EFR\cpefrcli.exe" -b C:\ProgramData\CheckPoint\DBStore\backup\database.db

      File will be under:

      \ProgramData\CheckPoint\DBStore\backup\

  3. Collect the related Forensics report folder:

    C:\ProgramData\CheckPoint\DBStore\Events\<Event ID>

Wait for 15 minutes after False positive/False Negative and then copy  EFR.db aside. Compress the files and create a zip file.