CP Harmony Endpoint AdminGuide
CP Harmony Endpoint AdminGuide
HARMONY ENDPOINT
EPMAAS
Administration Guide
Check Point Copyright Notice
© 2020 - 2024 Check Point Software Technologies Ltd.
All rights reserved. This product and related documentation are protected by copyright and
distributed under licensing restricting their use, copying, distribution, and decompilation. No
part of this product or related documentation may be reproduced in any form or by any means
without prior written authorization of Check Point. While every precaution has been taken in
the preparation of this book, Check Point assumes no responsibility for errors or omissions.
This publication and features described herein are subject to change without notice.
TRADEMARKS:
Refer to the Copyright page for a list of our trademarks.
Refer to the Third Party copyright notices for a list of relevant copyrights and third-party
licenses.
Important Information
Latest Software
We recommend that you install the most recent software release to stay up-to-
date with the latest functional improvements, stability fixes, security
enhancements and protection against new and evolving attacks.
Certifications
For third party independent certification of Check Point products, see the Check
Point Certifications page.
Feedback
Check Point is engaged in a continuous effort to improve its documentation.
Please help us by sending your comments.
Related Documents
Endpoint Security Client for Windows User Guide Provides the end-user instructions on
how to use the Endpoint Security
Client installed on Windows
endpoints.
Endpoint Security Clients for macOS User Guide Provides the end-user instructions on
how to use the Endpoint Security
Client installed on macOS endpoints.
Harmony Endpoint Security for Windows MDM Describes how to deploy the Endpoint
Deployment Guide Security Client on Windows endpoints
using a device management system.
Harmony Endpoint Security for macOS MDM Describes how to deploy the Endpoint
Deployment Guide Security Client on macOS endpoints
using a device management system.
Revision History
Date Description
2 May 2024 Added Client Language for Default Client User Interface.
See "User Interface" on page 390
26 April 2024 Added video tutorial for automatic patch updates. See
"Detecting Common Vulnerabilities and Exposures" on
page 384.
16 April Added:
2024
n Using Reconnect tool without uninstall password.
See "Without Client Uninstall Password
(Recommended) " on page 56
n Helpdesk Level 3. See "Specific Service Roles" on
page 48
n "Software Deployment Policy Template" on page 596
for MSSP.
13 March Added:
2024
n Enable patch updates (Automatic Patch Updates).
See Detecting Common Vulnerabilities and
Exposures.
n Admin Comment column. See "Viewing Computer
Information" on page 149.
Date Description
22 January Added:
2023
n "Managing Microsoft Entra ID Scanners" on
page 459.
n "Viewing Device Hardware Information" on page 158
n Chained exclusions in "Smart Exclusions" on
page 265
7 December Added:
2023
n Video tutorial for Run Diagnostics. See "Performing
Push Operations" on page 491.
n "Appendix B - Uninstalling the Harmony Endpoint
Security Client (For macOS and Windows)" on
page 605
3 October Added:
2023
n "MSSP Essentials" on page 566.
n "MSSP Custom Dashboard" on page 571.
11 Added:
September
2023
n "Patches By Status" on page 189.
n Posture Last Scan Status. See Table Filters and
Column Description in"Viewing Computer
Information" on page 149.
n New columns to "Vulnerability Assessment Table" on
page 190.
7 September Added:
2023
n Browser Status
n Anti-Bot Last Update
See Table Filters and Column Description in "Viewing
Computer Information" on page 149.
4 September Added "Smart App Control" on page 601 for Windows 11.
2023
28 July 2023 Added deploying the Endpoint Security Client "Using the
Vanilla Client" on page 73.
28 June 2023 Added Browser Status to the Table Filters and Column
Description. See "Asset Management View" on page 149.
31 May 2023 Added Scan Targets and Scan Target Exclusions. See
"Scan" on page 240.
.23 May 2023 Reconnect Tool is now supported for macOS with client
version E87.50 or higher. See "Reconnect Tool" on
page 55.
Date Description
19 April 2023 Added information about moving a device or user from one
virtual group to another. See "Managing Virtual Groups" on
page 452.
18 April 2023 Updated the Policy Mode settings. See "Configuring the
Threat Prevention Policy" on page 213.
26 July 2022 Added support for sending forensics data to third-party data
analytics tool. See "Sending Forensics Data to Third-Party
Analytics Tool" on page 522.
18 July 2022 Updated Adding Exclusions to Rules for the new method to
add and edit an exclusion.
13 July 2022 n Added information about the new "Web & Files
Protection" on page 224.
n Added three new options for "Web & Files Protection"
on page 224.
n Added information about the new Easy Unlock
feature. It allows you to Accept or Reject a Network
One-Time Logon request or a Network Password
Change request from a user who has forgotten the
login credentials of the endpoint or the endpoint is
locked due to invalid login attempts using incorrect
credentials.
Note - This feature is available only to customers in
the Early Availability program.
13 October Updated:
2021 Introduction
10 October Added:
2021 "Recent Tasks" on page 602
Date Description
07 October Updated:
2021 "Known Limitations" on page 603
"Connected, Disconnected and Restricted Rules" on
page 402
01 October Updated:
2021
n Adding Exclusions to Rules
n "Automatic Deployment of Endpoint Clients" on
page 68
n "Remotely Installing the Initial Client" on page 97
26 Updated:
September
2021
n "Configuring Client Settings " on page 389
13 Updated:
September
2021
n "BitLocker Encryption for Windows Clients" on
page 299
02 Added:
September
2021
n "User Authentication to Endpoint Security Clients
(OneCheck)" on page 302
n "Configuring Client Settings " on page 389
31 August Added:
2021
n "Connected, Disconnected and Restricted Rules" on
page 402
Updated:
n "Web & Files Protection" on page 224
05 August Added:
2021
n "Installation Token" on page 67
Updated:
n "Manual Deployment" on page 80
29 March Added:
2021
n "Application Control" on page 356
22 March Updated:
2021
n "Configuring Client Settings " on page 389
n "Harmony Endpoint for Linux" on page 525
11 March Added:
2021
n "Configuring Media Encryption & Port Protection" on
page 310
Updated:
n "Viewing Computer Information" on page 149
n "Exporting Logs" on page 487
25 February Updated:
2021
n Registering to the Infinity Portal
n "Creating a New Endpoint Management Service" on
page 43
n "Managing Firewall Objects and Groups" on
page 346
n "Configuring Alerts" on page 104
22 February Added:
2021
n "Harmony Endpoint for Linux" on page 525
Date Description
08 February Updated:
2021
n Managing Licenses
n "BitLocker Encryption for Windows Clients" on
page 299
n "Configuring Alerts" on page 104
n "Performing Push Operations" on page 491
07 January Added
2021
n "Firewall" on page 352
11 November Added:
2020
n "Remote Installation of Initial Client" on page 92
n "Threat Hunting" on page 514
Updated:
n "Exporting Logs" on page 487
Table of Contents
Introduction to Harmony Endpoint EPMaaS 39
Getting Started 40
Creating an Account in the Infinity Portal 40
MSSP Account 40
Accessing the Harmony Endpoint Administrator Portal 41
Creating a New Endpoint Management Service 43
Managing Licenses 43
User Center 43
Amazon Web Services Marketplace 46
Activating the License 46
License Violation 47
Getting Started Walkthrough Wizard 48
Specific Service Roles 48
Reconnect Tool 55
Windows 55
macOS 56
Without Client Uninstall Password (Recommended) 56
With Client Uninstall Password 57
Supported Operating Systems for the Endpoint Client 59
Microsoft Windows 59
macOS 61
Linux 61
Supported Browsers for the Browser Extension 63
Migrating an On-premises Security Management Server to Harmony Endpoint 64
Use Case 64
Prerequisites 64
Known Limitations 64
Overview 140
Chrome on Windows 140
Firefox on Windows 140
Microsoft Edge on Windows 141
Brave on Windows 141
Chrome on macOS 142
Firefox on macOS 142
Microsoft Edge on macOS 142
Enabling the Browser Extension on a Browser with Incognito or InPrivate Mode 143
Ending the Browser Process Running in the Background 143
Browser Extension Pinning 144
Managing Endpoint Components in SmartEndpoint Management Console 145
Managing Accounts in the Infinity Portal 147
Managing Harmony Browse 148
Overview 148
Limitations 148
Viewing Computer Information 149
Asset Management View 149
Select a View 149
Creating a Custom View 150
Status Icon 150
Filters 151
Working with the Computers Table 157
Viewing Device Hardware Information 158
Managing Computers 158
General Actions 158
Push Operations 161
Diagnostics 185
Full Disk Encryption 186
Remote Help and Recovery 187
Result 437
Specific Event 437
Result 437
Specific Event 437
Result 438
Specific Event 438
Result 438
Specific Event 439
Result 439
Specific Event 439
Result 439
Import or Export Policies 440
Overview 440
Limitations 440
Prerequisites 440
Exporting Policies 441
Importing Policies 441
Capabilities of Offline Endpoint Security Client 442
Performing Data Recovery 444
Check Point Full Disk Encryption Recovery 445
BitLocker Recovery 448
FileVault Recovery 449
Managing Virtual Groups 452
Managing Active Directory Scanners 457
Supported Directory 457
Prerequisite 457
Managing Microsoft Active Directory Scanner 457
Organization Distributed Scan 457
Full Active Directory Sync 458
Managing Microsoft Entra ID Scanners 459
Limitations 459
Configuring the Settings in the Microsoft Entra ID Portal 459
Importing Objects from Microsoft Entra ID 465
Giving Remote Help to Full Disk Encryption Users 471
Active Directory Authentication 472
Endpoint Security Active Directory Authentication 472
Configuring Active Directory Authentication 473
UPN Suffixes and Domain Names 476
Configuring Alternative Domain Names 476
Troubleshooting Authentication in Client Logs 478
Harmony Endpoint Logs 479
Query Language Overview 481
Criteria Values 481
NOT Values 483
Wildcards 483
Field Keywords 484
Boolean Operators 486
Exporting Logs 487
Creating Security Certificates for TLS Mutual Authentication 487
Sending Security Reports 490
Performing Push Operations 491
Certificate Management 513
Forensics Data 514
Threat Hunting 514
Supported Regions 515
Supported Versions 515
Enabling Threat Hunting 515
Using Threat Hunting 516
Saving a Query as a Bookmark 520
Use Case - Maze Ransomware Threat Hunting 521
Contracts 583
Accounts Info 583
Accounts Contracts Distribution 584
Contracts by Accounts 584
Contract Details Table 584
Contract Status Report 585
Sending an Email to Account on Contract Status 586
Reports for MSSP 587
Global Exclusions 588
Adding Global Exclusions using Legacy Exclusion 588
Adding Global Exclusions using Smart Exclusion 589
Syncing Exclusions with Child Accounts 590
Templates for Child Accounts 590
Use Case 590
Benefits 591
Threat Prevention Policy Template 591
Creating a Threat Prevention Policy Template 591
Attaching the Threat Prevention Policy Template to a Child Account 592
Viewing the Accounts Attached to a Template 594
Software Deployment Policy Template 596
Creating a Software Deployment Policy Template 596
Attaching the Software Deployment Policy Template to a Child Account 597
Viewing the Accounts Attached to a Template 598
Smart App Control 601
Recent Tasks 602
Known Limitations 603
Appendix 604
Appendix A - Deploying Harmony Endpoint Security Client using SCCM 604
Step 1: Create the Harmony Endpoint Windows Application in SCCM 604
Step 2: Deploy the Harmony Endpoint Windows Application in SCCM 605
Appendix B - Uninstalling the Harmony Endpoint Security Client (For macOS and
Windows) 605
Note - Google Chrome is the recommended browser for the Harmony Endpoint
Administrator Portal.
Getting Started
To get started with Harmony Endpoint:
1. Create an account in Infinity Portal
2. Assign Specific Service Roles to Users
3. Access the Harmony Endpoint Administrator Portal
4. License the product
5. Create a New Endpoint Management Service
MSSP Account
Harmony Endpoint supports an interface for Managed Security Service Providers (MSSP) to:
n Create and manage (pause, stop, start and restart) the service of their child accounts
n View general statistics about their child accounts
n View operational statistics about their child accounts
n View contract details of their child accounts
To convert an existing account to MSSP account, refer to Infinity Portal Administration Guide.
To create a new MSSP account and to add child accounts, refer to Infinity Portal
Administration Guide.
To manage your MSSP and its child accounts, see "Managed Security Service Providers
(MSSP)" on page 563.
4. If you are accessing the portal for the first time, do one of these:
n If you already have a Check Point contract, click Already have a contract? to
attach the contract to the product. For more information, see Associated Accounts
in the Infinity Portal Administration Guide.
n If you want to trial the product, click Start free trail.
If you have already attached the contract with the product, the Harmony Endpoint Getting
Started appears.
Managing Licenses
User Center
When you create an account in the Infinity Portal and access the service, you get a free 30-day
trial. After the 30-day trial period, you must purchase a software license to use the product. To
purchase a license, you must create a Check Point User Center account.
Once you create a User Center account, contact your Check Point sales representative to
purchase a license.
7. Click Next
8. In the Provide Evaluation Info section that opens, fill in these details:
a. User Center Account
b. Email Address
c. Evaluation Product will be used by
d. Purpose of Evaluation
9. Click Get Evaluation.
A confirmation notice is received that the product was successfully added to your User
Center account.
Click the link in the confirmation notice to view the license in the Product Center.
10. In the Product Center, go to Selected Account and select the account to which the
license was added.
11. Select the license and click the License button above the list of the licenses.
12. Under License Information, select the License for Cloud Management checkbox.
13. If you have not subscribed to the VPN feature (Check Point Security Gateways are not
used for client VPN), then click License.
14. If you have subscribed to the VPN feature that uses Check Point Security Gateways
for client VPN, then in the IP Address field for CPSB-SB-EP-VPN, replace
164.100.1.8 with the IP address of the Gateway Security Management System and
then click License.
Note- If you already have an associated account and wish to add another
license, go to Global Settings > Service and Contracts. At the upper-right of
the screen, click Manage Accounts and use the sync option to refresh the
license.
License Violation
Harmony Endpoint notifies you about the license violations, such as expiry and exceeded
permitted seats.
Depending on the level of violation, the system sends these notifications and takes these
actions:
n Email and top banner
n Email, top banner and pop-up window
n Top banner, pop-up window and disables policy configuration¹
n Top banner, pop-up window, disables policy configuration¹ and disables new
installations²
¹ All the configuration in the Policy menu is read-only except Export Package and
Export/Import Policies. The Save button is disabled, however, previously saved changes can
be installed.
² All the configuration in the Policy menu is read-only except Export Package and
Export/Import Policies. The Save and Install buttons are disabled.
Role Description
Read-Only Has access to all system aspects, but cannot make any changes.
User
Helpdesk Has the same access as Helpdesk Level 1 and, in addition, full access to
Level 2 Repair Client and Forensics and Remediation Push Operations.
Role Description
Helpdesk Has the same access as Helpdesk Level 2 and, in addition, full access to
Level 3 Manage Virtual Groups and Read-Only access to Software Deployment
Policies.
Power User Has full Read & Write access to the Harmony Endpoint EPMaaS service, but
cannot control the service.
Remote Helps Full Disk Encryption and Media Encryption users with access to
Help User encrypted media.
Service Re No No No No No No Re
Actions ad Permi Permi Permi Permi Permi Permi ad-
(Restart, & ssion ssion ssion ssion ssion ssion Onl
pause or Writ y
terminat e
e the
service)
Reconnect Tool
You can use the Reconnect tool to reconnect all your Endpoint Security clients to a new
Endpoint Management Server.
Windows
Notes:
n If you are using Smart App Control in Windows 11, see "Smart App Control" on
page 601 on how to use the Reconnect tool.
n For Harmony Endpoint Security Client version E87.20 and lower, the
Reconnect tool removes pre-boot users and disables user acquisition while
connecting endpoint clients to the new Endpoint Management Server. To
prevent this issue, you must manually migrate the client database to the new
Endpoint Management Server.
n For Harmony Endpoint Security Client version E87.30 and higher, the
Reconnect tool automatically initiates user acquisition. However, the user must
lock and unlock their computer to complete user acquisition.
The system creates the Reconnect.exe file that contains the details of server that the
endpoint requires to reconnect to the new Management Server.
Notes:
n client_uninstall_password is optional. If you do not specify the
password, the user must enter the password when running the Recovery
tool on their computer. If you use special (non-alphanumeric) characters
in the password, such as !,@, $, enclose the password within quotation
marks. For example,"!1@3$5^7*9".
n If you do not want to show the confirmation message “The reconnect tool
The Endpoint Security client connects to the new Endpoint Management Server.
ii. Stop all the daemons.
iii. Replace the configuration file.
iv. Reload the daemon.
The Reconnect tool runs and reconnects endpoints to the new Endpoint Management
Server.
Note - If Endpoint Security clients with version E85.60 and higher cannot connect to
the new Endpoint Management Server, your Endpoint Security clients may still be
connected to the old Endpoint Management Server. For more information, see
sk92329.
macOS
Note - This is supported only with the Endpoint Security Client version E87.50 and
higher.
To use the Reconnect tool without using the uninstall password on the endpoint:
1. Log in to the Endpoint Manager Server to which you want to connect your Endpoint
Security clients.
2. Go to Service Management and under Reconnect Tool, click For macOS.
The system downloads the reconnect_tool_for_macOS.zip file.
3. Unzip the file.
The Reconnect tool runs and reconnects endpoints to the new Endpoint Management Server.
To use the Reconnect tool using the uninstall password on the computer:
1. Log in to the Endpoint Manager Server to which you want to connect your Endpoint
Security clients.
2. Go to Service Management and under Reconnect Tool, click For macOS to download
the reconnect_tool_for_macOS.zip file.
3. Distribute the zip file to the endpoints.
4. On the endpoint, unzip the file.
The unzipped folder contains the EPReconnect tool.
5. Do one of these:
n To run the Reconnect tool on a terminal server, run:
<path to the Reconnect
tool>/EPReconnectTool.app/Contents/MacOS/EPReconnectTool --
enter-password
Notes:
n For existing Endpoint Security deployments, before upgrading your OS version,
you must first upgrade the Endpoint Security Client to a version that supports
the desired OS version based on the table above.
n For additional information on Windows 7 support, refer to sk164006.
n Windows Operating Systems are supported according to Check Point Client
Support life cycles, also on Virtual Machines. However, there is no dedicated
QA process for all possible variants of Windows. If you encounter a specific
issue related to a different edition of a supported Windows OS version, Check
Point will provide best-effort support through R&D assistance.
Supported
Version Editions Supported Features
starting from
2022 64-bit All E85.40 Compliance, Anti-Malware, Firewall, Application Control, Forensics, Anti-
Ransomware, Anti-Bot, Threat Emulation, Capsule Docs (Standalone
Client), Media Encryption and Port Protection.
2019 64-bit All E85.00 Compliance, Anti-Malware, Firewall, Application Control, Forensics, Anti-
Ransomware, Anti-Bot, Threat Emulation, Capsule Docs (Standalone
Client), Media Encryption and Port Protection.
2016 64-bit All E85.00 Compliance, Anti-Malware, Firewall, Application Control, Forensics, Anti-
Ransomware, Anti-Bot, Threat Emulation, Capsule Docs (Standalone
Client).
2012 R2 64-bit All E85.00 Compliance, Anti-Malware, Firewall, Application Control, Forensics, Anti-
Ransomware, Anti-Bot, Threat Emulation, Capsule Docs (Standalone
Client)
2012 64-bit All E85.00 Compliance, Anti-Malware, Firewall, Application Control, Forensics, Anti-
Ransomware, Anti-Bot, Threat Emulation, Capsule Docs (Standalone
Client)
2008 R2 All E85.00 Compliance, Anti-Malware, Firewall, Application Control, Forensics, Anti-
32/64-bit Ransomware, Anti-Bot, Threat Emulation, Capsule Docs (Standalone
Client)
Notes:
n To support Endpoint Compliance rules for Windows Server 2016 on versions
older than R80.20, see sk122136.
n Windows Server CORE is not supported.
n If you install a client package with features that are not supported on the server,
the installation succeeds but only the supported features are installed.
macOS
macOS Version Supported starting from
Notes:
n For existing Endpoint Security deployments, before upgrading your OS version,
you must first upgrade the Endpoint Security Client to a version that supports
the desired OS version based on the table above.
n Support for macOS 10.15 (Catalina) is declared as "End of Engineering".
Starting from E88.30, new features do not include support for macOS 10.15.
Any version released after September 30, 2024, will not be supported on
macOS 10.15.
Linux
Operating System Version
Amazon Linux 2
OpenSUSE* 15.3
42.3
9.0 - 9.2
15 SP3
Ubuntu 16.04
18.04
20.04
22.04 - 22.04.3
Threat Malici
Data
URL Extrac Zero Passw Safe Search ous
Brow Loss
OS Filteri tion & Phish ord Sear Reputa Script
ser Preven
ng Emula ing Reuse ch tion Protec
tion
tion tion
Windo Chrome Yes Yes Yes Yes Yes Yes Yes Yes
ws
Edge Yes Yes Yes Yes Yes Yes Yes Yes
Chromiu
m
Chrom Chrome 6 Yes Yes Yes Yes Yes Yes Yes Yes
eOS
Notes -
1 By default, the extension is disabled. To enable the extension, see Deploying
Harmony Browse Clients.
2 Browser extension is supported in Safari version 14 and higher.
3 Browser extension is supported in Brave version 1.43.89 and higher.
4 Brave for Windows is supported only with the Endpoint Security client version
E86.70 and higher.
5 Brave and Edge for macOS is supported only with the Endpoint Security client
version E87.40 and higher.
6 ChromeOS is supported only with the Harmony Browse client.
Use Case
You are using the on-premises Security Management Server to manage Harmony Endpoint
Security clients installed on the endpoints. You wish to use the Harmony Endpoint cloud
service on the Infinity Portal for management.
Prerequisites
Make sure that the Security Management Server and the Harmony Endpoint EPMaaS are
running the same versions.
n If the versions are not the same, upgrade the Security Management Server to match the
Harmony Endpoint EPMaaS version.
n To know the Harmony Endpoint EPMaaS version, click Service Management and see
Service Version.
Notes:
n Migration of Security Management Server from an environment with High Availability and
Secondary server to Harmony Endpoint is not supported. For more details, contact
Check Point Support.
n During the import process, the Harmony Endpoint Administrator Portal is locked for use.
Known Limitations
See sk179713.
Note - Infinity Portal supports the upload of files up to 5 GB. If the export file size exceeds
5 GB, contact Check Point Support.
You receive a confirmation mail when the import is complete.
10. Continue with the post-migration steps. For more information, see sk179687.
11. Run the Reconnect tool on all the endpoints to reconnect to the Harmony Endpoint
service on the Infinity Portal. For more information, see "Reconnect Tool" on page 55.
2. Click Download button under Windows or macOS, depending on the destination system.
Notes:
n Admins are recommended not to pre-install Harmony Endpoint when using cloning
utilities like Acronis. It is recommended to install Harmony Endpoint after the clone is
created, or at least to block the initial registration before creating the clone.
n If you have initiated to deploy the Harmony Endpoint Security client on an endpoint
that is not yet added to the domain, see the sk18127 to complete the deployment.
Installation Token
Token-limited installation protects against sending unauthorized copies of exported packages
and installation of packages on computers which do not belong to the organization that created
the packages.
The administrator is responsible for enabling the token-limited installation feature and creating
the token.
If token-limited installation is enabled, then you must enter the token during the registration of
the Endpoint Security server with the Harmony Endpoint Management Server.
The token is limited in time. If the token is expired, the registration is rejected.
4. To set an expiration date, select Enable Expiration and in the Valid until field, click
to select the date for the token expiry.
5. Click Save.
Notes- You can deploy the Initial Client to all your endpoint devices, using a third-
party deployment tool, manually or remotely (see "Remote Installation of Initial Client"
on page 92).
Important - If you want to switch to a US-DHS and EU compliant Anti-Malware blade,
make sure to switch to a complaint Endpoint Security Client before deploying the
client. See "Anti-Malware Settings" on page 101.
Caution - Windows Server 2016 and higher requires that you turn off Microsoft
Windows Defender before you install the Harmony Endpoint Security Client. Perform
the instructions in the sk159373 before you install or contact Check Point Support to
request assistance with the installation.
The Initial Client is the Endpoint Agent that communicates with the Endpoint Security
Management Server.
You can extract the Initial Client from the Tiny Agent.
The improvements include:
n The Tiny Agent has a very small executable (smaller than 1MB).
n Consolidates all the connection parameters in a single executable.
n It can be shared in various forms, enabling fast, easy and seamless first-time
deployment.
n Once combined with the Dynamic Package, it installs only what is necessary for each
machine.
n It is agnostic to the client version.
Click Steps
Linux installScript.sh
macOS BrowserSetup.zip
ChromeOS BrowserSetup_
Overview, and chromeos_Laptop.exe
then click or BrowserSetup_
Download chromeos_
Endpoint on Desktop.exe
the top
banner. n
To download the file using a download link, click and
click Copy download link.
When the download link is ready, the Send the Link by
Email window appears.
a. Click to copy to the link.
b. Share the download link with users (for example,
by email) to download the file.
Overview > a. In the Download & Install Endpoint agent widget, click
Getting Download.
Started > Let's The Download & Install Endpoint Agent window appears.
Start Connect b. Click Online Install.
Your First c. From the Operating System list, select the OS.
Agent d. From the Version list, select the client version.
2. For Windows:
n Run the exe file to install the Harmony Endpoint Security client.
n If you want to use the msi file, then convert the exe file into a msi file:
a. Open the Command Prompt window by selecting Run as administrator.
b. Run:
cd <Path where you have downloaded the exe file>
d. Transfer the msi file to the endpoints and run the msi file to install the
Harmony Endpoint Security client.
3. For macOS:
a. Unzip the file and open the EPS_TINY folder.
b. To install the Harmony Endpoint Security client, do one of these:
n Run the EPNano.app file.
n In the terminal window, run:
./EPNano.app/Contents/MacOS/EPNano
4. For Linux:
n If you downloaded the installScript.sh file, run the file on the endpoint to install the
Harmony Endpoint Security client.
n If you copy the download link, on the Linux machine, run:
a. curl "paste_downlowd_link" -o install.sh
b. chmod+ x install.sh
c. sudo ./install.sh install
Note - You can deploy the Initial Client to all your endpoint devices, using a third-party
deployment tool, manually or remotely (see "Remote Installation of Initial Client" on
page 92).
The Tiny Agent shows simple error messages in cases of network issues (connectivity
problems, proxy issue, and so on).
Error messages and Remediation
Endpoint Setup Exception occurred (either Download the file again and
failed! allocation failed on any check its signature (it could
internal component, or be corrupted), and make
another type of abnormal sure you have enough free
termination) RAM.
Failed to initialize Either we cannot verify our Make sure you have
Endpoint Setup! own signature, or map the enough memory.
installer in the memory.
Failed to parse Failed to parse the URL for File downloaded from the
internal data! downloading eps.msi Management Server
from CDN is corrupted. Contact Check
Point Support.
Failed to create our Either there is some Check Make sure that the
program files folder Point product installed, or Endpoint Security Client is
for config.dat the Administrator cannot not already installed.
create folders in the
Program Files folder
Failed to save Either there is some Check Make sure that the
config.dat Point product installed, or Endpoint Security Client is
the Administrator cannot not already installed.
create folders in program
files folder
Failed to parse Failed to find the server Make sure you downloaded
configuration data config information. the file from the portal.
C:\Windows\System32\LogFiles\WMI\EndpointSetup.etl
Silent Installation
Run:
This package includes the specified components to be installed on the endpoint device.
You can distribute it automatically with deployment rules.
You can configure the policies for the components before or after you deploy the component
package.
Deploy the Endpoint Security component package with deployment rules.
The Vanilla client is similar to the Tiny Agent but receives the connection parameters
separately that prevents unauthorized clients to connect to the Harmony Endpoint
Management Server.
4. Click .
6. Do one of these:
To Do
Install the Vanilla client directly on the a. On the endpoint where you want to
endpoint install the client, open the link in a
browser.
Note - Make sure that the user
has Administrator role in the
endpoint.
Install the Vanilla client remotely on the On the endpoint where you want to install
endpoint the client, run this command as the
Administrator:
EndpointSetup.exe /url <link>
The system downloads the Vanilla client,
installs it and then connects to the Harmony
Endpoint Management Server.
To Do
Install the Vanilla client remotely on the a. Run this command as the
endpoint using third-party distribution Administrator:
applications, for example, Microsoft EndpointSetup.exe /createmsi
InTune /url <link>
The system downloads the EPS.msi
file.
b. Distribute the EPS.msi file using third-
party MDM application. For more
information, see "Remote Installation
of Initial Client" on page 92.
7. When the installation is complete, the Harmony Endpoint Security Client is installed on
the endpoint and connected to the Harmony Endpoint Management Server.
8. Continue with "Deployment Rules" below.
Deployment Rules
Deployment rules let you manage Endpoint Security Component Package deployment and
updates.
Deployment rules work on both Windows OS and macOS. Linux OS is not supported yet.
The Default Policy rule applies to all Endpoint devices for which no other rule in the Rule Base
applies.
For Linux, click distros to view the supported distributable and version. For
example, CentOS or Ubuntu.
Note - You can use the Do not install option to temporarily halt
enforcing software deployment rules to the endpoints, for example,
during maintenance or internal testing of Harmony Endpoint Security
client.
c. Select Capabilities.
n For Linux, only the Anti-Malware blade is supported with the exported
package.
n For capabilities supported by Windows, macOS and Linux, see sk169996.
Caution - The Endpoint Security client package version must match the
client package version selected in the exported package. Otherwise,
the system discards the capabilities selected in the Software
Deployment rule.
See "Installation and Upgrade Settings" on page 394 for local deployment options.
Manual Deployment
You can export a package of Harmony Endpoint or Harmony Browse from the Endpoint
Security Management Server to Endpoint devices using a third-party deployment software, a
shared network path, email or other method.
When you download a package for manual deployment, the Initial Client is already included in
the package for Harmony Endpoint and there is no need to install it separately.
When you create the package for export, you select your set of components.
The package installation program automatically detects the computer type and installs the
applicable components.
n Dependencies Settings
Select the dependencies to include in the package:
l .NET Framework 4.6.1 Installer (60MB) - Recommended for
Windows 7 computers without .NET installed.
l 32-bit support (40MB) - Selected by default. Recommended
for 32-bit computers.
l Visual Studio Tools for Office Runtime 10.050903 (40 MB) -
Recommended if the package includes Capsule Docs.
l Smart preboot (190MB) - Enables the Easy Unlock feature. It
allows you to Accept or Reject a Network One-Time Logon
request or a Network Password Change request from a user
that has forgotten the login credentials of the endpoint or the
endpoint is locked due to invalid login attempts using incorrect
credentials. Such requests are indicated by the icon in the
Asset Management > Computers table. See "Viewing
Computer Information" on page 149. It is supported:
o Only with Endpoint Security client version 86.50 or
higher.
o Only on endpoints running Windows OS.
o Only if the Full Disk Encryption is Check Point
encryption. For more information, see "Configuring Full
Disk Encryption" on page 291.
Note - This feature is available only to customers in the Early
Availability program.
n Anti-Malware Settings
Select the signature to include in the package.
This sets the level of Anti-Malware protection from the time that a
client gets the package until it gets the latest Anti-Malware
signatures from the signature provider:
l Full - Recommended for installing on devices without high-
speed connectivity to the Anti-Malware server.
l Minimum - Selected by default. Recommended for a clean
installation on devices that are connected to the Anti-Malware
server.
l None - Recommended for upgrades only.
ii. Optional: To download the package automatically after the system creates
the package, select the Download package when saved checkbox.
j. Click Finish.
The system starts to create the package. It can take several minutes depending
on the package size. When the package is ready, the system shows Exported
Package created message.
Note - You can duplicate the package configuration for future use. Click the
icon.
macOS EPS_TINY.zip
Linux installScript.sh
macOS BrowserSetup.zip
ChromeOS BrowserSetup_chromeos_Laptop.exe or
BrowserSetup_chromeos_Desktop.exe
1. Go to Overview > Getting Started > Let's Start Connect Your First Agent.
7. Click Download.
The system prepares the package for download.
9. Once the download is complete, continue with "Installing the Exported Package or
Client" on the next page.
You can install the Endpoint Security client using the EPS.msi file through the Command
Line Interface (CLI). To install:
a. Transfer the EPS.msi file to the endpoints.
b. In the endpoint's CLI, run:
msiexec.exe /i <path to msi file>\EPS.msi
Please wait...
===> <location>\EPS.msi
===> <location>\32\EPS.msi
The system creates the msi files for both 64-bit and 32-bit and opens Windows
Explorer windows where the msi files are created.
c. Make a note of the path where msi files are created.
d. In the Command Prompt window, press any key to close.
e. Transfer the msi file to the endpoints and run the msi file to install the Harmony
Endpoint Security client.
For more information, see sk179668.
2. For macOS, distribute the package or file to users' endpoint.
3. For Linux, run the sh script in the users' endpoint.
Browse Client
1. For Windows, distribute the downloaded package or file to users' endpoint or run the
EndpointSetup.exe /CreateMSI on the users' endpoint.
2. For macOS, distribute the package or file to users' endpoint.
3. For ChromeOS, see sk173974.
You can only see the deployment status after the package is successfully installed.
Time Limit Installation
If you have enabled "Installation Token" on page 67, a prompt appears during the Endpoint
Security client installation. The user must enter the Server Authentication Token.
If the server authentication fails, create a new server authentication token with the
appropriate validity period and share it with your users.
3. In the Virtual Groups and VPN Sites screen, in the VPN site section:
i. Click Upload and select the .config file you want to upload.
Note - Only .config file with a maximum file size of 1000 KB is supported.
ii. Click Next and continue with step i in Create an export package. See
"Manual Deployment" on page 80.
To install the Initial Client using Push Operation, see "Remotely Installing the Initial Client" on
page 97.
Best Practice - We recommend that the Deployment Agent has good hardware
specs, network connectivity, availability and a "remote install" compatible Endpoint
Security Client (E83.30 and higher).
You can configure multiple devices in each domain as Deployment Agents with no limitation
on the total count. All devices qualify as an agent for an installation bundle.
To add Active Directory Credentials to the Deployment Agent on the Endpoint Security
Client Screen:
1. Open the Endpoint Security client screen, click Menu and select Advanced.
Note -You must be in the Domain Administrators group in the Active Directory.
Privileges
User must have permission to connect from the Deployment agent computer to the target
computer and create the scheduled task on the target computer.
For additional references, please see Microsoft's guide here: https://docs.microsoft.com/en-
us/windows/win32/api/taskschd/nf-taskschd-itaskservice-connect
Windows Defender
n Windows 10 regards the remote execution of msiexec.exe through the Task Scheduler
as malicious activity. Windows blocks this on the target computer.
n To disable Windows Defender's Anti-Malware with a PowerShell command on the target
devicer: (For Windows server only)
1. Open PowerShell as Administrator.
2. Run:
Uninstall-WindowsFeature -Name Windows-Defender
3. Reboot the computer after the Windows Defender Anti-Malware uninstalls.
n If the remote installation procedure fails, the Windows Defender enables after a restart.
Disable the Windows Defender's Real-Time Protection again.
Other AV Solutions
n We recommend that you disable the Windows Defender and disable or uninstall third-
party anti-virus software on the target computer.
n An attempt to run remote software triggers a notification. The remote deployment
procedure fails.
Enable Access to the Task Scheduler Through the Windows Firewall in a Domain Profile
n When the Windows Firewall blocks the remote connection to the target's Task
Scheduler, run this PowerShell command on the target computer:
Get-NetFirewallProfile -Name Domain | Get-NetFirewallRule | ?
Name -like *RemoteTask-In-TCP-NoScope* | Enable-NetFirewallRule
n Configure these settings on the computer:
1. Navigate to Control Panel > Network and Internet > Network and sharing center
> Advanced sharing settings.
a. Click (+).
b. Select devices that do not have Endpoint installed and are not in the process of
deployment.
Notes:
n To select several non-adjacent entries, press and hold
SHIFT key, click the applicable top entry, and then, click
the applicable bottom entry.
n To clear a selection, press and hold the CTRL key while
To install the Initial Client remotely from the "Asset Management" view
1. After a connection to the Task Scheduler service on Windows OS, the Deployment
Agent registers a new task: "CP_Deployment_{unique ID}".
2. The Deployment Agent runs the task from the domain administrator's account on the
target computer.
3. The Task Scheduler spawns the msiexec.exe to download the client installer and
launch it in silent mode.
4. The installation proceeds with the MSI script instructions.
Security Considerations
n The Deployment Agent does not store the administrator password in clear text.
n The client UI collects the credentials and passes them to the device agent to store in
separate values of a registry key under EP root.
n The password stores as an encryption and the principal name stores in plain text.
n Administrator accounts have access permissions of FULL CONTROL for the registry
key.
n The SYSTEM account has READONLY access permissions for the registry key.
n The user and password never pass to the target devices. They establish the Task
Scheduler connection.
Target devices that fail to install and download the Initial Client, set their status accordingly. In
case of a connection failure, the Deployment Agent tries to connect to the target service three
more times with increasing interval between attempts. The default is ten seconds. This
mechanism increases the success rate in case of network-related issues.
Invalid Credentials
If the domain administrator credentials are invalid, the Deployment Agent stops connecting to
remote targets, and the target device's Operation Status changes to "Access denied due to
Invalid credentials".
Missing Credentials
If the domain administrator credentials are missing, the Deployment Agent stops connecting to
remote targets, and the target device's Operation Status changes to "Deployment agent is not
configured".
Upgrades
Upgrades are seamless to our users. A new type of Push Operation are rolled out and added
to all Harmony Endpoint users.
Anti-Malware Settings
Harmony Endpoint allows you to switch to a United States Domestic Homeland of Security
(DHS) and European (EU) regulations compliant Anti-Malware blade. After you successfully
switch, you must redeploy the compliant Endpoint Security Client on the endpoints either
through Deployment Rules or other methods.
Note - To switch back from the DHS compliant Anti-Malware engine to a non-DHS
compliant Anti-Malware engine, contact Check Point Support.
Heartbeat Interval
Endpoint clients send "heartbeat" messages to the Endpoint Security Management Server to
check the connectivity status and report updates. The time between heartbeat messages is
known as the heartbeat interval. For more information, see Endpoint Security Server and
Client Communication.
Note - The default heartbeat interval is 60 seconds. A shorter heartbeat interval can
cause additional load on the management. A longer heartbeat interval may lead to
less up-to-date logs and reports.
Configuring Alerts
You can configure alerts to receive a notification whenever an event occurs on an endpoint.
Harmony Endpoint supports two types of alerts:
n "Basic Alerts" below
n "Advanced Alerts" on page 107
Note - The Overview view > Operational Overview page has the Active Alerts pane
on the right. This page shows which endpoint computers are in violation of critical
security rules.
Basic Alerts
Basic alerts allows you to receive email notifications for these events:
n Compliance warning
n Failed deployment
n Encryption problem
n Anti-Malware issues
n Policy server out-of-sync
n Anti-Malware License Expiration Date
1. Go to the Endpoint Settings view > Alerts > Basic Alerts, and select a security
violation.
2. Select the applicable alert from the list.
3. In the right section Alert Configuration:
a. Select ON in the top line:
The computer is restricted or about to the restricted
1. In Endpoint Settings > Alerts > at the top, click Email Service Settings.
The Email Service Settings window opens.
2. Enter these details:
n Host Name - Email serve host name.
n From Address - Email address from which you want to send the alerts.
n User Authentication is Required - If email server authentication is necessary,
select this option and enter the credentials in the User Name and the Password
fields.
n Enable TLS Encryption - Select this option if the email server requires a TLS
connection.
n Port - Enter the port number on the email server.
n Test Email - Enter an email address to send the test to, and click Send Test:
l If the verification succeeds, an email is sent to the email address entered
and a success message shows in the Email Service Settings window.
l If the verification fails, an error message shows in the Email Service
Settings window.
Correct the parameters errors or resolve network connectivity issues.
Stand on the error message to see a description of the issue.
3. Click OK to save the email server settings and close the window.
Advanced Alerts
Advanced alerts allows you to receive notifications for security and operational events. The
notification is sent through preferred communication channels configured in Infinity
Playblocks:
n SMS
n Email
n Slack
n Microsoft Teams
Note - Make sure that you have configured Connectors and Notifications profiles in
Infinity Playblocks. For more information, see Infinity Playblocks Administration
Guide.
2. Select an alert.
3. In the right pane:
c. In the Thresholds tab, configure the threshold parameters for the alert:
Threshold (Minimum
Alert
Alert Title number to trigger the
Description
action)
Security Alerts
Threshold (Minimum
Alert
Alert Title number to trigger the
Description
action)
Threshold (Minimum
Alert
Alert Title number to trigger the
Description
action)
Operational Alerts
Threshold (Minimum
Alert
Alert Title number to trigger the
Description
action)
Threshold (Minimum
Alert
Alert Title number to trigger the
Description
action)
Threshold (Minimum
Alert
Alert Title number to trigger the
Description
action)
Threshold (Minimum
Alert
Alert Title number to trigger the
Description
action)
d. On the Messages tab, you can view the Subject and Message of the alert.
e. Click Save.
Note - To create and edit a notification profile in Infinity Playblocks, see Notifications
section in the Infinity Playblocks Administration Guide.
The EPS.msi file contains the Products.json file that has a pre-configured list of Anti-Virus
software products that are automatically deleted when you install the Endpoint Security client
E84.70 or higher. By default, this list contains Symantec, McAfee, and Kaspersky.
You can also uninstall Symantec, McAfee, and Kaspersky manually.
n In PowerShell, run:
Get-WmiObject win32_product -Filter "name like '%any part of the product name%”
n To find the upgrade code using the product code, run:
gwmi -Query "SELECT Value FROM Win32_Property WHERE Property='UpgradeCode'
AND ProductCode='{YourGuid}”
Note - With the Endpoint Security client 86.50 and higher, you can uninstall a product that is
not listed in the default Products.json file by using an updated Products.json that contains the
product. To get the updated Products.json file, contact Check Point Customer Support.
To uninstall a product using the updated Products.json file, open the command prompt window
and run:
msiexec /i EPS.msi REMOVEPRODUCTS="Product"
RPCONFIG="c:\users\admin\downloads\Products.json", where Product is the
Anti-Virus software that you want to uninstall.
Notes -
n Symantec.cloud is not supported by this command. To remove
Symantec.cloud, navigate to
C:\Program Files\Symantec.cloud\PlatformAgent\ and run Uninstall.exe.
n You cannot uninstall software products whose cached msi is not found on your
computer.
Unified Dashboard
The Unified Dashboard shows a consolidated view of the preselected widgets from the
Operational Overview and Security Overview, in addition to Announcement widget. The
Announcement widget shows the latest news in the cyber security industry.
Custom Dashboard
The Custom Dashboard allows you to create personalized dashboards with widgets of your
preference and specify whether the dashboard should be private or public. Private
dashboards are available only for you to view whereas, Public dashboards are available for all
the users with access to the Overview page. However, only the owner of the dashboard can
edit it.
Blank dashboard allows you to create a new dashboard with available widgets. Unified
template allows you to customize the Unified Dashboard.
Note - The Add button is disabled if the widget is already added to the dashboard.
7. By default, all custom dashboards you create are set as Private. To make the custom
dashboard available to all users with access to the Overview page, from the Private list
on the upper-right corner, click Public. The system adds the dashboard under Public
dashboards for other users.
8. Click Save.
The dashboard appears under Custom Dashboard on the left navigation pane, and it is also
listed under My dashboards in the Custom Dashboard page.
2. To edit a dashboard:
a. Expand Custom Dashboard.
b. Click for the dashboard you want to edit and click Edit.
3. To delete a dashboard, expand Custom Dashboard, click for the dashboard you want
to delete and click Delete.
4. To hide a dashboard, expand Custom Dashboard, click for the dashboard you want to
hide and click Hide. The dashboard is removed from the list under Custom Dashboard
on the left navigation pane.
5. To unhide a dashboard, click , hover over the dashboard you want to unhide and click
Add. The dashboard is added to the list under Custom Dashboard on the left navigation
pane.
6. To duplicate a dashboard, click , hover over the dashboard and click Duplicate.
Operational Overview
The Operational Overview page shows the deployment status of Endpoint clients in your
organization, their health status, client versions and operating systems on the clients.
To view the Operational Overview page, click Overview > Operational Overview.
To export the Operation Overview data to a pdf, click Export PDF.
Active Endpoints
The Active Endpoints widget shows the number of active and inactive endpoints.
Click the numbers in the widget to view the endpoints in the "Asset Management View" on
page 149 tab.
Desktops
The Desktops widget shows the number of desktops by Operating System (Windows, macOS,
Linux, and ChromeOS) that have the Endpoint Security client installed.
Laptops
The Laptops widget shows the number of laptops by Operating System (Windows, macOS,
Linux, and ChromeOS) that have the Endpoint Security client installed.
Deployment Status
The Deployment Status widget shows the number of endpoints by deployment status.
Pre-boot Status
The Pre-boot Status widget shows the number of endpoints by pre-boot status.
Encryption Status
The Encryption Status widget shows the number of endpoints by encryption status.
Anti-Malware Update
The Anti-Malware Update widget shows the number of endpoints that had the Anti-Malware
blade updated over different time periods.
Harmony Endpoint Version
The Harmony Endpoint Version widget shows the number of endpoints running a particular
Endpoint Security client version.
Operating System
The Operating System widget shows the number of endpoints running a particular Operating
System.
Alerts
The Alerts widget shows the active alerts on all the endpoints in the account.
Security Overview
Shows the attack statistics of the Endpoint Security clients.
The information is presented in these widgets:
n Hosts Under Attack
n Active/Dormant Attacks
l Active Attacks - Malicious process was executed and the system was infected.
Termination and quarantine of the process or other elements of the attack is
disabled in the policy.
l Dormant Attack - No malicious process was executed but the system was infected.
Quarantine of one of the detected files failed.
n Cleaned/Blocked Attacks
l Cleaned Attack - Malicious process was executed and the system was infected.
Termination and quarantine of all attack elements succeeded.
l Blocked Attack - No malicious process was executed. Quarantine of all detected
files succeeded.
n Infected Hosts
n Attacks Timeline
Note - The Active, Dormant and Cleaned attacks are based on Forensics and
Remediation capability:
n If there is no remediation or the remediation capability is turned off, then attack
status is either Dormant or Blocked.
n If remediation capability is turned on:
l If the process is actively running and the remediation is Terminate, then
Reports
On the Reports page, you can download the reports in the pdf format:
n Threat Analysis Report - Shows the latest security events.
n Threat Analysis Report Anonymized - Shows the latest security events without specific
user names.
n High Risks Cyber Attack Report - Shows the analysis of all the Endpoint Security
events by statuses of the attack pillars.
n Web Activity Checkup - Shows the web activity in the organization.
n Threat Emulation Report - Shows a report about scanned and malicious files.
n Threat Extraction Report - Shows the insights on the downloaded files.
n Software Deployment Report - Shows the deployment status in the organization.
n Policies Report - Shows policies status.
n Vulnerability Management -Shows the detected vulnerabilities.
Note - Available only to customer subscribed to this feature and with server
version R81.10.x and higher.
n Posture Management - Shows Vulnerability Management and patches information.
Note - Available only to customer subscribed to this feature and with server
version R81.10.x and higher.
n Operational Report - Shows the operational status of the endpoints.
n Compliance Report - Shows the compliance status in the organization.
n Check Point Cyber Security Report - Shows the latest security trends as per Check
Point.
Generate Report
To generate a report:
1. Go to Overview > Reports > Generate Report.
3. In the Time Frame list, select Last day, Last 7 days, or Last 30 days.
4. Click Export.
Scheduled Reports
Scheduled Reports allows you to automatically generate reports at the specified date and
time, and email it to the specified recipients.
Notes:
n The report becomes effective 24 hours after you schedule it. For example, if you
schedule for a new report today for 02:00 PM, then it is enforced from the next day at
02:00 PM.
n This feature is not supported for Check Point Cyber Security Reports.
n For performance reasons, it is recommended to schedule reports to run in off-peak
hours. For example, during non-business hours.
n The default time zone for the schedule report is Coordinated Universal Time (UTC).
For example, to schedule the report at 1:00 AM EST, specify the time as 6:00 AM
(depending on Daylight Savings Time).
To schedule a report:
1. Navigate to Overview> Reports and do one of these:
n From the Scheduled Reports page, click Add and from the Name list, select the
report.
n From the Generate Report page, select the report, click and select Schedule
Report.
8. To edit a scheduled report, select the report in the table and click Edit.
9. To delete a scheduled report, select the report in the table and click Delete.
Announcements
The Announcements page shows the latest news and enhancements in Harmony Endpoint.
Browser Settings
Disabling Incognito Mode, BrowserGuest Mode,
and InPrivate Mode
Overview
The browser extension is not installed automatically if the Incognito, Guest or InPrivate mode
is enabled in your browser. We recommend that you disable these modes to secure your
users.
Chrome on Windows
Firefox on Windows
Brave on Windows
To disable Incognito mode, Incognito mode with Tor and BrowserGuest mode:
1. Select Start and type CMD.
2. Right-click Command Prompt and select Run as administrator.
The Command Prompt window appears
3.
To disable Run
Chrome on macOS
Firefox on macOS
3.
To disable Run
3.
To disable Run
4. Press Enter.
3. Run:
REG ADD HKLM\SOFTWARE\Policies\Microsoft\Edge /v
BackgroundModeEnabled /t REG_DWORD /d 0
4. Press Enter.
Note - Before you download SmartConsole, you must change your SmartConsole
administrator password.
c. Click Login.
The SmartEndpoint console manages all Endpoint components, whereas the Harmony
Endpoint manages only Harmony components.
Harmony Endpoint does not support all of SmartEndpoint features. Therefore, there can be
conflicts between configurations in the two platforms. For more information, see "Backward
Compatibility" on page 404.
At the upper-middle of your screen, near the name Harmony Endpoint, click the current
account and select the required account from the drop-down menu.
1. From the left navigation panel, click Global Settings (at the bottom of the panel).
2. In the top left section, click Users.
The list of currently defined users appears.
3. From the top toolbar, click New.
Note - If the administrator you wish to add is not registered in Harmony Endpoint,
they receive a registration invitation to establish login credentials for the portal.
5. Click Add.
n
in Asset Management > Computers indicates a Harmony Browse client. You can
filter for clients using the Agent Installed filter.
n The Overview and Logs menu show the information for both Harmony Browse and
Harmony Endpoint clients.
Limitations
Harmony Browse does not support Push Operations and Threat Hunting.
Note - The General > Description at bottom pane shows the text entered in the
Active Directory for the asset. If no text is entered, it is blank.
Select a View
From the View drop-down on the top left, select a preconfigured view:
n Deployment
n Compliance
n Health
n Full Disk Encryption
n Anti-Malware
n Host Isolation
n Anti-Bot
n Policy Information
n Custom
4. In the Select what will be saved in this view section, select the required checkbox:
n Filters
n Table Columns
5. Click OK.
6. To delete a Custom View:
a. From the View drop-down, go to Custom Views.
Status Icon
The icon in the Status column shows the client or computer status.
Status
Description
Icon
Indicates that a new computer was discovered that has no client installed.
Indicates that the computer was deleted from the Active Directory or from the
Organizational Tree.
Status
Description
Icon
Filters
Use the Filters pane on the top of the screen to filter the information in the table.
To add filters:
1. In the Filters pane, click +.
2. Select the required filter or search for the filter using the Search bar. For information on
the filters, see "Table Filters and Column Description" on the next page.
3. Click Update.
The system updates the table automatically for the added filters.
2. To select the columns for the table, search and select the columns.
3. To change the column position in the table, drag and drop the column to the required
position.
4. Click Update.
Tip - The URL in the address bar of the web browser captures the filters you specify for the
table. You can bookmark the URL to go to the Asset Management > Computers page and
view the table with the specified filters.
Filter/Column
Description
Name
Status Status of the connected computer. For more information, see "Status
Icon" on page 150.
Agent Installed Endpoint Security client or Browse client installed on the computer.
Admin Comment Comment for the device. For example, This computer is used by Bob
and Jane.
Deploy Time Time when the client was installed on the computer.
Filter/Column
Description
Name
Pre-boot Status Full Disk EncryptionPre-boot screen status last update time.
Updated On
Last Logged In Last logged in user name on the Full Disk Encrypted computer.
FDE User
Remote Help Full Disk Encryption locked users that are pending for help (One-
Requests Time Logon or Password Change)
Filter/Column
Description
Name
Dat Date Dat date in a human readable format (Example: 09 Apr 2018 10:52
AM)
Filter/Column
Description
Name
Static Analysis Last time when the Threat Emulation Static Analysis was updated.
Update
Offline Last time when the Threat Emulation Offline Reputation was
Reputation updated.
Update
Threat Hunting Threat Hunting status on the Harmony Endpoint Security Client. The
Status supported statuses are:
n Available - Threat Hunting is installed and running.
n Not Available - Threat Hunting is installed but not running due
to an error. For the error description, see the Threat Hunting
Error Description column.
n Not installed - Threat Hunting is supported by the client but not
installed.
n N/A - Threat Hunting is not supported by the client. Upgrade to
the client version 87.20 or higher.
Filter/Column
Description
Name
Threat Hunting Threat Hunting describes the reason why Threat Hunting is not
Error Description running on the Harmony Endpoint Security Client. The supported
values are:
n Available
n Not installed
n Authentication Failed
n Data Uploading Failed
n Fetching Settings Failed
n URL Creating Failed
n Connection Failed
Note - Threat Hunting Error Description is not supported
by "Filters" on page 151.
Anti-Malware Shows the expiry date and time of the Anti-Malware license.
License
Expiration Date
Browser Status Shows the browser and the Harmony Browse extension status on the
endpoint.
The supported statuses are:
n Not Installed -
o The browser is not installed.
o The browser is installed but not used since the last
reboot.
o The browser is used but the extension is disabled by the
policy.
For example, indicates that the Chrome browser is not
installed.
n Running - The browser is active and the extension was
Filter/Column
Description
Name
Anti-Bot Last Shows the date and time when the signatures of the Anti-Bot blade
Update were last updated. For example, 07 Jun 2023 04:53 PM. The other
statuses are:
n N/A - The Anti-Bot signatures are not updated.
n Not Installed - The Anti-Bot blade is not installed.
Posture Last Shows the status of the latest scan. The statuses are:
Scan Status
n Timed Out
n Waiting For Client
n Blade Not Installed
n Starting Scan - Scan initiated.
n Scan Started - Scan in progress.
n Succeeded
n Failed
n Not Scanned
n Aborted
Note -
n For Windows clients, this feature is supported with Harmony Endpoint Security
client version E88.00 and higher.
n For macOS clients, this feature is supported with Harmony Endpoint Security client
version E88.40 and higher.
Managing Computers
Select the checkbox to the left of the applicable computers and right-click to perform these
actions:
General Actions
View Computer Logs
When the Endpoint client is installed on a computer, information about the computer is sent
to and stored on the Endpoint Security Management Server.
Resetting a computer means deleting all information about it from the server.
Resetting a computer does not remove the object from the Active Directory tree or change
its position in the tree.
Important - You can only reset a computer if the Endpoint client is not installed. If
you reset a computer that has Endpoint installed, important data is deleted and the
computer can have problems communicating with the Endpoint Security
Management Server.
Computer reset:
n Removes all licenses from the computer.
n Deletes Full Disk Encryption Recovery data.
n Deletes the settings of users that can log on to it.
n Removes the computer from Endpoint Security Monitoring.
n Deletes the Pre-boot settings.
n Marks the computer as unregistered.
After you reset a computer, you must reformat it before it can connect again to the Endpoint
Security service.
You may decide to reset a computer if:
n The Endpoint client was uninstalled or the computer is re-imaged.
n It is necessary to reset the computer's configuration before a new Endpoint client is
installed. For example, if the computer is transferred to a different person.
Delete
Removes the asset from the Local or Active Directory and adds it to Deleted Entities in the
Organizational Tree. This operation discards the assets license information. You can use
this operation when you remove an asset from your domain.
Note - If the Endpoint Security client is still installed on the asset, the client continues to
receive the updates from the Endpoint Security Management Server.
To add the asset back to the Active Directory, see Recover.
Recover
Adds the deleted asset back to the Local or Active Directory from Deleted Entities in the
Organizational Tree. The asset's status is not Active until its Endpoint Security client
connects and synchronizes with the Endpoint Security Management Server. You can use
this operation when you add an asset back to the domain.
Note - You can recover only a deleted asset.
Terminate
Warning - Removes the asset from the Harmony Endpoint management permanently. You
cannot recover a terminated asset. We recommend to terminate an asset only if it is
discarded or disposed or the Endpoint Security client is uninstalled.
Directory Scanner
Harmony Endpoint can scan and import users, groups, Organizational units (OUs) and
computers from multiple supported directory domains. See Managing Active Directory
Scanners.
Push Operations
Push
Category Windows macOS Linux
Operations
Push
Category Windows macOS Linux
Operations
Registry Yes No No
Actions
Collect Yes No No
Processes
3. Select the devices on which you want to perform the push operation.
Note - You can perform Run Diagnostics on only one device at a time.
4. Click Next.
5. Configure the operation settings.
Anti-Malware
2FA
Push Operations Description
Required
Push 2FA
Description
Operations Required
Push 2FA
Description
Operations Required
Push 2FA
Description
Operations Required
i. Click Finish.
Agent Settings
Push 2FA
Operati Description Requi
ons red
Deploy Installs the Initial Client on the target devices remotely using No
New any device as the medium to run the push operation. This is
Endpoi suitable if do not have third party tools such as Microsoft
nts System Center Configuration Manager (SCCM) or Intune to
install the client.
Field Description
Push 2FA
Operati Description Requi
ons red
C:\Windows\SysWOW64\config\systemprofile\CPInfo.
n For macOS, client logs are stored in the directory
/Users/Shared/cplogs.
Field Description
Point servers
n Upload CPInfo reports to Corporate
Push 2FA
Operati Description Requi
ons red
Push 2FA
Operati Description Requi
ons red
Files upload
Push 2FA
Operati Description Requi
ons red
Field Description
Push 2FA
Operati Description Requi
ons red
Push 2FA
Operati Description Requi
ons red
Field Description
Push 2FA
Operati Description Requi
ons red
Copy File
File path Full path of the file or folder you want to copy,
including the file or folder name.
Example:
n For File - C:\Users\<user_
name>\Desktop\test.doc
n For Folder -
C:\Users\Username\Desktop\
Push 2FA
Operati Description Requi
ons red
Field Description
name>\Documents
n For Folder - C:\Users\Username2\
Notes:
n The file or folder name you specify
Move File
File path Full path of the file or folder you want to move,
including the file or folder name.
Example:
n For File - C:\Users\<user_
name>\Desktop\test.doc
n For Folder -
C:\Users\Username>\Desktop\
Push 2FA
Operati Description Requi
ons red
Field Description
name>\Documents
n For Folder -
C:\Users\Username1\Documents\
Notes:
n If you provide the full file path, the is
Delete File
Push 2FA
Operati Description Requi
ons red
Security client.
n You cannot create separate VPN sites for each user
Supported fields:
Push 2FA
Operati Description Requi
ons red
Field Description
Push 2FA
Operati Description Requi
ons red
Field Description
Push 2FA
Operati Description Requi
ons red
Field Description
CAPI store)
n p12-certificate
n securityIDKeyFob
n securityIDPinPad
n SoftID (not tested)
n challenge-response (not tested)
Push 2FA
Operati Description Requi
ons red
Push 2FA
Operati Description Requi
ons red
n To notify the user about the push operation, select the Inform user with
notification checkbox.
n To allow the user to post pone the push operation, select the Allow user to
postpone operation checkbox.
7. Under Scheduling:
n To execute the push operation immediately, click Execute operation
immediately.
n To schedule the push operation, click Schedule operation for and click to select
the date.
8. Specify the duration after which the system automatically terminates the unexecuted
push operation (For example, if the Endpoint client is offline):
n 7 days
n Custom
n Never
9. For Push Operations that support 2FA authentication, you are prompted to enter the
verification code.
If you have not enabled 2FA authentication, a prompt appears to enable 2FA
authentication:
n To enable 2FA authentication for your profile, click Profile Setting, and follow
the instructions. For more information, see Infinity Portal Administration Guide.
n To enable 2FA authentication for the current tenant, click Global Settings, and
follow the instructions. For more information, see Infinity Portal Administration
Guide.
10. Click Finish.
11. View the results of the operations on each endpoint in the Endpoint List section (in the
Push Operations menu) at the bottom part of the screen.
Report Description
Report Description
b. Click OK.
c. Click Save.
d. From the top, click Install policy.
Diagnostics
Run Diagnostics
Note - This is supported with Endpoint Security client version E86.80 and higher.
Warning - Only exclude a process if you are sure that the file is not malicious
and is not vulnerable to cyber-attacks.
To view the latest diagnostics report, see "Show Last Diagnostics Report" on the next
page.
2. Select the row of the Run Diagnostics push operation you performed.
3. In the Endpoint List table, under Operation Output column, click View Report.
Note - This is supported with Endpoint Security client version E86.80 and higher.
b. Click Save.
c. From the top, click Install Policy.
4. To add the exclusions to a specific rule, select Device Exclusions Per Rule.
a. Click Create & Review for the rule.
b. Click OK.
c. Click Save.
d. From the top, click Install policy.
Shows the latest diagnostics report. By default, Harmony Endpoint runs the diagnostics
every four hours.
Note - This is supported with the Endpoint Security client version E86.80 and higher.
For more information about the diagnostics report, see Run Diagnostics in "Performing
Push Operations" on page 491.
You can view, create, lock and unlock authorized Pre-boot users. See Authentication-
before-OS-Loads-Pre-boot.htm.
If the operating system does not start on a client computer due to system failure, you can
recover your data from the computer:
n "Check Point Full Disk Encryption Recovery" on page 445
n "BitLocker Recovery" on page 448
n "FileVault Recovery" on page 449
Media Encryption
You can give access to users who are locked out of their Full Disk Encryption protected
computers. See "Giving Remote Help to Full Disk Encryption Users" on page 471.
For the supported applications for scan and patch management, see sk181034.
Note - End-users can also initiate the scan and view the vulnerable CVEs from the
Endpoint Security client (Compliance and Posture).
To view the posture for endpoints, click Asset Management > Posture Management.
If you see the following screen, make sure to configure the posture assessment settings. See
"Configuring Posture Assessment Settings" on page 385.
Vulnerabilities by Severity
The Vulnerabilities by Severity widget shows the total number of vulnerable CVEs by
severity.
The Top 5 Risky Apps widget shows the top five applications with vulnerable CVEs and their
average CVSS score.
For example, if Visual C++ 2008 has different CVEs, then the average CVSS score is 9.3.
The Top Vulnerable Devices widget shows the top five vulnerable endpoints (most vulnerable
CVEs detected).
The number to the left of the machine name indicates the total number of CVEs detected in the
machine.
To view vulnerable CVEs in the machine, click the machine name. It shows the details in the
"Vulnerability Assessment Table" on the next page.
There are two three types of View available for risk assessment:
n Vulnerabilities view - Shows all the vulnerable CVEs and their CVSS score detected in
the endpoints. See "Vulnerability Assessment Table" on the next page
n Devices view - Shows devices that have at least one CVE detected.
Patches By Status
The Patches By Status widget shows the total number of patches by the status.
Click the status to filter the "Vulnerability Assessment Table" on the next page by the status.
Item Description
Opens the Filters widget. You must specify the filter criteria.
Toggle Filters
Scan All Scans all devices for CVEs. See "Scanning Devices" on page 195.
Scan Now Scans selected devices for CVEs. See "Scanning Devices" on
page 195.
Patch Updates patches to the specified CVEs. See "Applying the Patch for
CVEs" on page 196.
Vulnerabilities View
Item Description
CVE Number Click the CVE number to view "CVE Details Widget" on page 194 and all
impacted devices:
n Device Name
n OS
n OS Version
n Last Scanned
n Comment - Add a comment. For example, do not patch this
application.
Last Detected Date and time the CVE was last detected.
First Detected Date and time the CVE was first detected.
Device View
Item Description
Device Name Click the device name to view the "Device Details Widget" on page 194
and all CVEs in the device:
n CVSS Score
n CVE Number
n App Name
n App Version
n Last Detected
n First Detected
n Patch Name
n Patch Size
n Patch Status
o Available - Patch is available for the CVE.
o Cancelled - Deployment is cancelled before patch
installation is completed.
o Not Available
o Update not available - Patch updates are not available.
CVEs.
o Downloading - System is downloading the patch.
o Pending execution - Waiting for other patches in the
bulk to be installed.
o Pending scan - Patch installed successfully. Waiting
Item Description
Updated
o
o Interrupted - The patch installation by Harmony
Last Scan Shows the status of the latest scan. The supported statuses are:
Status
n Timed Out
n Waiting For Client
n Blade Not Installed
n Starting Scan
n Scan Started
n Succeeded
n Failed
n Not Scanned
n Aborted
Last Scanned Date and time the machine was last scanned.
To view the Device Details widget, in the "Vulnerability Assessment Table" on page 190,
under the Device Name column, click a device name.
The Device Details widget shows:
n Operating System name.
n Operating System version.
n Date and time the device was last scanned.
n Number of vulnerabilities detected in the device.
n Number of applications at risk.
n Comment
To view the CVE Details widget, in the "Vulnerability Assessment Table" on page 190, under
the Vulnerabilities view, click a CVE number.
n CVSS score of the device.
n The application with the CVE.
n The version of the application with the CVE.
n Date and time the CVE was last detected.
Scanning Devices
You can scan devices for vulnerable CVEs or to verify if the patch has been applied or not.
Isolating a Device
You can isolate a device from the network until you patch its vulnerable CVEs.
To isolate devices:
1. Go to Asset Management > Posture Management.
2. To isolate specific devices:
Managing Devices
You can configure custom settings for specified devices or device types. These device settings
are typically used as exceptions to settings defined in Media Encryption & Port Protection
rules.
There are two types of devices:
n Storage Device - Removable media device on which users can save data files.
Examples include: USB storage devices, SD cards, CD/DVD media and external disk
drives.
n Peripheral Device - Devices on which users cannot save data and that cannot be
encrypted.
New devices are added manually or are automatically discovered by the Endpoint Server.
You can view Manually added devices or Discovered devices. In the Device Type column,
you can see if the device is a storage device or a peripheral device.
3. Click .
4. Select :
n Storage Device
The New Storage Device window appears.
n Peripheral Device
The New Peripheral Device window appears.
5. Enter these:
n Name - Enter a unique device display name, which cannot contain spaces or
special characters (except for the underscore and hyphen characters).
n Applies to – This setting is valid for peripheral devices only.
n Connection Type- Select the connection type Internal, External or Unknown
(required).
n Category - Select a device category from the list.
n Serial Number - Enter the device serial number. You can use wild card characters
in the serial number to apply this device definition to more than one physical
device. See "Using Wild Card Characters" on page 206.
n Extra Information - Configure whether the device shows as fixed disk device (Hard
Drive with Master Boot Record), a removable device (Media without Master Boot
Record) or None.
n Device ID Filter - Enter a filter string that identifies the device category (class).
Devices are included in the category when the first characters in a Device ID match
the filter string. For example, if the filter string is My_USB_Stick, these devices are
members of the device category:
l My_USB_Stick_40GB
l My_USB_Stick_80GB
n Supported Capabilities:
l Log device events - Select this option to create a log entry when this device
connects to an endpoint computer (Event ID 11 or 20 only).
l Allow encryption - Select this option if the device can be encrypted (storage
devices only).
1. Click Asset Management > Media Devices > Storage & Peripheral.
2. Right-click the applicable device and select Exclude.
3. Configure the required Read Policy and Write Policy (relevant to storage devices only).
For more information on the configuration options, see "Configuring the Read Action" on
page 311 and "Configuring the Write Action" on page 313
4. Define Behavior (relevant for peripheral devices only):
a. From the Rule(s) list, select a rule.
b. From the Access type list, select Accept or Block.
The Discovered devices view lists the details of the devices automatically discovered by the
Endpoint server.
To edit a device:
1. Click Asset Management > Media Devices > Storage & Peripheral.
2. Right-click the applicable device and select Edit.
3. Enter these:
n Name - Enter a unique device display name, which cannot contain spaces or
special characters (except for the underscore and hyphen characters).
n Applies to – This setting is valid for peripheral devices only.
a. To assign the device to an existing group, from the existing group list, select a
group.
b. To assign the device to a new group, in the create a new group field, enter the new
group name.
c. If you do not want to add the device to any group, select do not add to group.
5. Configure the required Read Policy and Write Policy (relevant to storage devices only).
For more information on the configuration options, see "Configuring the Read Action" on
page 311 and "Configuring the Write Action" on page 313.
6. Define Behavior (relevant for peripheral devices only):
a. From the Rule(s) list, select a rule.
b. From the Access type list, select Accept or Block.
c. From the Log type list, select a log.
d. Add details in the Description field.
7. Click Finish.
Because definitions that use wildcard characters apply to more endpoints than those without
wildcards, rules are enforced in this order of precedence:
5. 1234567
Viewing Events
Harmony Endpoint allows you to monitor activities related to storage and peripheral devices as
events and if required, change the device details and status. For example, if a device that
should be allowed was blocked and vice versa.
Column Description
Event Time Date and time when the device was connected to the endpoint.
3. Enter these:
n Name - Enter a unique device display name, which cannot contain spaces or
special characters (except for the underscore and hyphen characters).
n Applies to – This setting is valid for peripheral devices only.
n Connection Type- Select the connection type Internal, External or Unknown
(required).
n Category - Select a device category from the list.
n Serial Number - Enter the device serial number. You can use wild card characters
in the serial number to apply this device definition to more than one physical
device. See "Using Wild Card Characters" on page 206.
n Extra Information - Configure whether the device shows as fixed disk device (Hard
Drive with Master Boot Record), a removable device (Media without Master Boot
Record) or None.
n Device ID Filter - Enter a filter string that identifies the device category (class).
Devices are included in the category when the first characters in a Device ID match
the filter string. For example, if the filter string is My_USB_Stick, these devices are
members of the device category:
l My_USB_Stick_40GB
l My_USB_Stick_80GB
n Supported Capabilities:
l Log device events - Select this option to create a log entry when this device
connects to an endpoint computer (Event ID 11 or 20 only).
l Allow encryption - Select this option if the device can be encrypted (storage
devices only).
When you plan the security policy, think about the security of your network and convenience
for your users. A policy should permit users to work as freely as possible, but also reduce the
threat of attack from malicious third parties.
You can add more rules to each Rule Base and edit rules as necessary. Changes are enforced
after the policy is installed.
Unified Policy
Harmony Endpoint introduces the unified policy for the Endpoint components.
The unified policy lets you control all security components in a single policy. The policy is
composed of a set of rules. Each rule in the policy defines the scope which the rule applies to
and the activated components. This is different from the policy Rule Base in SmartEndpoint,
where each component has its own set of rules.
A Default Policy rule which applies to the entire organization is predefined in your Policy
tab.Policy > Threat Prevention > Policy Capabilities.
Each new rule you create, has pre-defined settings, which you can then edit in the right section
of the screen.
The Threat Prevention policy contains these capabilities which you can edit:
n "Web & Files Protection" on page 224
n "Behavioral Protection" on page 245
n "Analysis & Remediation" on page 250
The Threat Prevention policy contains device rules and user rules.
n You can use user objects only in the user policy, and you can use device objects only in
the device policy.
n There is no default rule for the user policy.
n User rules override device rules.
n You can use the same group in user and device rules at the same time.
n If a group contains both users and devices, the rule is implemented according to the
policy in which the rule is included.
To enable user policy, go to the Endpoint Settings view > Policy Operation Mode, and select
Mixed mode.
Rule Number The sequence of the rules is important because the first rule that matches
traffic according to the protected scope is applied.
Web & Files The configurations that apply to Download Protection, Credential
Protection Protection and Files Protection.
Analysis & The configurations that apply to attack analysis and Remediation.
Response
Search
Policy Mode
Policy mode allows you to:
Notes:
n The Detect only mode provides the basic protection. We recommend that you
use the Detect only policy mode for the first few days to gather, monitor and
analyze the data. Based on the analysis, you must switch to Tuning, Optimized
or configure a Custom policy mode for enhanced protection. If you use the
Detect only policy mode for the Default settings for the entire organization
rule (default) for more than two days, the system shows a banner as a reminder
to configure a stricter policy mode.
If you click Dismiss, the system stops the notification only for you while it
continues to appears for other users.
Policy Mode
Capability
Tuning Detect only Optimized
Advanced
Capabilities
Advanced Settings
Policy Mode
Capability
Tuning Detect only Optimized
URL Filtering Allow user to dismiss the URL Allow user to dismiss
Filtering alert and access the the URL Filtering alert
website is disabled. and access the
Under Categories, Service is website is selected.
selected. Under Categories,
Under Malicious Script Protection: Service is selected.
o Block websites where Under Malicious Script
Malicious Scripts are found Protection:
embedded in the HTML is o Block websites
dismiss the
Malicious
Scripts alert and
access the
website is
selected.
Policy Mode
Capability
Tuning Detect only Optimized
emulate files
under 50 MB is
selected.
o Use Check Point
recommended
emulation
environments is
selected.
Policy Mode
Capability
Tuning Detect only Optimized
processes is selected.
o Connection timeout 600 ms.
Policy Mode
Capability
Tuning Detect only Optimized
Files Run initial scan after Anti-Malware Run initial scan after
Protection - blades installation is selected. Anti-Malware blades
Scan Allow user to cancel scan is installation is selected.
selected. Under Scan targets:
Prohibit cancel scan if more than o Critical areas is
larger than 20
MB is selected.
Advanced
Capabilities
Behavioral Protection
Policy Mode
Capability
Tuning Detect only Optimized
Advanced Settings
Policy Mode
Capability
Tuning Detect only Optimized
Policy Mode
Capability
Detect
Tuning Optimized
only
Advanced Settings
Policy Mode
Capability
Detect
Tuning Optimized
only
disabled.
o Quarantine folder
name is disabled.
is set to
Quarantine.
o Trusted Files is
set to
Terminate.
n Select Custom and set the operation mode manually. For more information, see
"Web & Files Protection" on page 224.
4. Click Save.
5. Click Save & Install.
n Click Align to accept the updates. The system automatically updates to the new settings
for the predefined mode.
n Click Keep to retain the current settings. The policy mode changes to Custom.
URL Filtering
URL Filtering rules define which sites you can access in your organization. The URL Filtering
policy is composed of the selected sites and the mode of operation applied to them.
Note - For each category, click Edit to see the sub-categories you can select.
c. Click OK.
5. Optional: You can select specific URLs to which access is denied. See "Blacklisting" on
the next page.
6. If you want Harmony Endpoint to verify and filter all the URLs accessed by an application
or a process, select the Enable Network URL Filtering checkbox. Otherwise, URL
filtering is applied only to the URLs accessed through a browser.
The selected mode of operation now applies to the selected categories.
The user can access any site which was not selected in one of the categories or which was not
blacklisted.
You can Allow user to dismiss the URL Filtering alert and access the website - This option
is selected by default. This lets you access a site determined as malicious, if you think that the
verdict is wrong. To do this, go to Advanced Settings > URL Filtering.
Blacklisting
You can define specific URLs or domains as blacklisted. These URLs/domains will be blocked
automatically, while other traffic will be inspected by the URL Filtering rules. You can add the
URLs/domain names manually or upload a CSV file with the URLs/domain names you want to
include in the blacklist.
2. In the URLs pane, for each required URL, enter the URL and click the + sign
3. click OK.
Notes:
You can use * and ? as wildcards for blacklisting.
n * is supported with any string. For example: A* can be ADomain or AB or
AAAA.
n ? is supported with another character. For example, A? can be AA or AB
or Ab.
2. Next to the search box, click the sign (import domains list from a 'csv' file).
To export a list of URLs to from the Endpoint Security Management Server to an external
source:
1. Go to Advanced Settings > URL Filtering > Blacklist > Edit.
2. Next to the search box, click the sign (export domains list to a 'csv' file).
3. Click OK.
Threat Emulation detects zero-day and unknown attacks. Files on the endpoint computer are
sent to a sandbox for emulation to detect evasive zero-day attacks. The following files types
are supported:
7z lnk slk
arj O1 tbz2
tbz
bat one2
bz2 tb2
pif
CAB tgz
pdf
csv udf
pkg1
com uue
ppt
cpl wim
pptx
dll wsf2
pps
doc xar2
pptm
docx xlt
potx
dot xls
potm
dotx xlsx
ppam
dotm xlm
ppsx
docm xltx
ppsm
dmg1 xlsm
ps1
dylib1 qcow21
xltm
exe xlsb
rar
gz xla
rtf
hwp xlam
sh1
iso xll
scr
iqy sldm xz
jar zip
Notes:
n 1 These file types are supported only with Harmony Endpoint Security Client version
E87.40 and higher.
n 2 These file types are supported only with Harmony Endpoint Security Client version
E87.60 and higher.
n 3 These file types are supported only with Harmony Endpoint Security Client version
E88.10 and higher.
Threat Extraction proactively protects users from malicious content. It quickly delivers safe
files while the original files are inspected for potential threats.
To see the list of file types which are supported by Threat Emulation and Threat Extraction:
1. Go to Policy > Threat Prevention > Policy Capabilities. In the Capabilities &
Exclusions pane, select Web & Files Protection.
2. In the Web & Files Protection tab, go to Advanced Settings > Threat Emulation >
Override Default File Actions > Edit.
These are the configuration options for supported file types:
n Prevent - Send files for emulation and extraction. For further configuration for
supported files, go to Advanced Settings > Supported Files:
l Get extracted copy before emulation completes - You can select one of
these two options. The system appends .cleaned to the file name. For
example, xxx.cleaned.
o Extract potential malicious elements - The file is sent in its original file
type but without malicious elements. Select which malicious parts to
extract. For example, macros, Java scripts and so on.
o Convert to PDF - Converts the file to PDF, and keeps text and
formatting.
l Suspend download until emulation completes - The user waits for Threat
Emulation to complete. If the file is benign, the gateway sends the original file
to the user. If the file is malicious, the gateway presents a Block page and the
user does not get access to the file. This option gives you more security, but
may cause time delays in downloading files. The system downloads the file
with the original file name.
l Emulate original file without suspending access - The gateway sends the
original file to the user (even if it turns out eventually that the file is malicious).
l Allow - All supported files are allowed without emulation. This setting
overrides the Prevent setting selected in the main page.
n Detect - Emulates original file without suspending access to the file and logs the
incident. The file is blocked if it is malicious or blocked by file extension (Advanced
Settings > Download Protection). If not, the file is downloaded before the emulation is
complete.
n Off - Allow file. No emulation or extraction is done. The download of all supported files is
allowed.
Unsupported Files
File types which are not supported by Threat Emulation and Threat Extraction. Unsupported
files types can be allowed or blocked. To configure, go to Advanced Settings > Download
Protection > Unsupported Files. The settings selected here override the settings selected in
the main page.
Emulation Environments
To define the maximum size of files that are sent for emulation, go to Advanced Settings >
Download Protection > Emulation Environments and specify the file size for Upload and
emulate files under.
Notes -
n Only the Endpoint Security Client version E86.40 and higher support a
maximum file size up to 100 MB. Client versions lower than E86.40
support a maximum file size up to 15 MB.
n Increasing the file size increases the client processing and network
traffic required to process large files.
To select the operating system images on which the emulation is run, go to Advanced
Settings > Download Protection > Emulation Environments, and select one of these options:
Harmony Endpoint allows you to override the default file action for the supported and
unsupported files.
To override the default file actions, navigate to Advanced Settings > Download Protection >
Override default file actions (download).
Custom Settings
n Block downloads when emulation fails due to size limit or connectivity problem -
Select the checkbox to block download of a file if the Threat Emulation of the file fails due
to technical reasons, such as file size limit, no internet connectivity and invalid licenses.
n Block downloads when emulation fails due to file encryption - Select the checkbox to
block download of a file if the Threat Emulation of the file fails to extract the file due to the
file encryption.
Credential Protection
To configure the credential protection policy:
1. Go to Policy > Threat Prevention > Policy Capabilities. In the Capabilities &
Exclusions pane, select Web & Files Protection.
2. In the Web & Files Protection tab, scroll-down to Credential Protection.
This protection includes two components:
Zero Phishing
Phishing prevention checks different characteristics of a website to make sure that a site does
not pretend to be a different site and use personal information maliciously.
There are three configuration options for this protection:
n Prevent - If the site is determined to be a phishing site, users cannot access the site. A
log is created for each malicious site.
n Detect - When a user uses a malicious site, a log is created.
n Off - Phishing prevention is disabled.
For further configuration of the Zero Phishing protection, go to Advanced Settings >
Credential Protection:
n Allow user to dismiss the phishing alert and access the website - Users can select to
use a site that was found to be malicious.
n Send log on each scanned site - Send logs for each site that users visit, whether
malicious or not.
n Allow user to abort phishing scans - Users can stop the phishing scan before it is
completed.
n Scan local HTML files - By default, the Harmony Endpoint extension in Chromium-
based browsers (Chrome, Microsoft Edge, and Brave) cannot access the local HTML
files opened by the browser to scan them for phishing attacks. This setting prompts users
to grant permission to Chromium-based browsers to access and scan local HTML files
on your PC.
Notes:
l You can customize the prompt page. For more information, see"Customized
extensions.
l This feature is supported with the Endpoint Security Client version E86.50 and
higher.
Note - Only the notification is disabled but the browser zero-phishing scan is
performed in the background indicated by the yellow highlight around the input
field.
n Prevent mode - Blocks the user from entering the corporate password and opens
the blocking page in a new tab. If you enable Allow users to dismiss the password
reuse alert and access the website, then it allows the user to dismiss the blocking
page and continue to enter the corporate password.
n Detect & Alert - Blocks the user from entering the corporate password and opens
the blocking page in a new tab and allows the user to dismiss the blocking page
and continue to enter the corporate password.
Notes:
l This option is available only in older releases of Harmony Endpoint.
Safe Search
Search Reputation
Search Reputation is a feature added to search engines that classifies search results based on
URL's reputation.
Notes:
n It is supported only with Google, Bing, and Yahoo search engines.
n To enable this feature, ensure that you set URL Filtering Mode to either
Prevent or Detect.
4. In the Web & Files Protection tab, scroll-down to Search Reputation section and select
a mode:
n On - Turns on the feature.
n Off -Turns off the feature.
When you enable this feature, the icon across the URL in the search results indicate the
classification:
Icon Classification
Note - If the Search Reputation cannot classify a URL, then it does not display an icon
across the URL. If you want such URLs to be classified and blocked, then enable the
Uncategorized checkbox in URL Filtering > Categories > General Use. The Search
Reputation classifies Uncategorized URLs as The website is blocked by the
Administrator.
Force Safe Search is a feature in search engines that acts as an automated filter for potentially
offensive and inappropriate content.
3. In the Web & Files Protection tab, under Force Safe Search, select a mode:
n On - Hides explicit content from the search results.
n Off - User sees the most relevant results for their search, which may include
explicit content like images consisting of violence.
Main features:
n When ‘Force Safe Search’ is on, Harmony Browse turns on Safe Search on the
supported search engines.
n It is supported with Google, Bing, and Yahoo search engines.
n Force Safe Search is off by default.
n Force Safe Search is supported with Google Chrome, and Microsoft Edge browsers.
Files Protection
Protects the files on the file system. To configure the Files Protection policy:
1. Go to Policy > Threat Prevention > Policy Capabilities. In the Capabilities &
Exclusions pane, select Web & Files Protection.
2. In the Web & Files Protection tab, scroll-down to Files Protection.
This protection has two components:
n Anti-Malware Mode - Protection of your network from all kinds of malware threats,
ranging from worms and Trojans to adware and keystroke loggers. Use Anti-Malware to
manage the detection and treatment of malware on your endpoint computers.
There are three configuration options for this protection:
l Prevent - Protects your files from malware threats.
l Detect - Detects the threats, so they appear in the logs, although the virus or
malware are still executable. Use this mode with caution.
l Off - No protection from malware.
Notes -
l Starting from the Endpoint Security Client E83.20, Check Point certified
o ZIP
o Z
o LZIP
o 7Z
o RAR
o ISO
o CAB
o JAR
o BZIP2
o GZIP
o DMG
o XAR
o TAR
o ACE
l The E2 DHS Anti-Malware blade can scan these archive file formats:
o ZIP
o Z
o 7Z
o RAR
o ISO
o CAB
o JAR
o BZIP2
o GZIP
o DMG
o XAR
o TAR
o ACE
n Advanced Capabilities - You can set an action for each of these capabilities separately:
Note - This is supported only with the Harmony Endpoint Security client version
E88.30 and higher.
Advanced
Description
Capability
ThreatCloud Verifies the reputation of files based on their hash in Check Point
Reputation Cloud-Based Database. This feature is supported from E88.50 and
later.
Offline Verifies file reputation by hash using local data. When connected to
Reputation the network, the data gets updated with ThreatCloud's common
hashes for offline verification.
¹Analyzes files without executing them against data models to identify potentially
malicious files.
The supported actions are:
l Prevent - Detects a malicious file, logs the event and quarantines the file.
l Detect - Detects a malicious file and logs the event.
l Off - No protection from malicious file.
3. In the Web & Files Protection tab, in the Advanced Capabilities list, select On.
Note - To view the set action for each capability, click See status.
Advanced Settings
To configure the advanced settings of the threat prevention policy:
1. Go to Policy > Threat Prevention > Policy Capabilities. In the Capabilities &
Exclusions pane, select Web & Files Protection.
2. In the Web & Files Protection tab, click Advanced Settings.
3. Use the following sections to modify the respective settings.
Files Protection
To configure the advanced settings for files protection, go to Advanced Settings > Files
Protections.
General
n Malware Treatment - The malware treatment options let you select what happens to
malware that is detected on a client computer:
l Quarantine file if cure failed - If Endpoint Security cannot repair the file, it is
deleted and put in a secure location from where it can be restored if necessary.
l Delete file if cure failed - If Endpoint Security cannot repair the file, it is deleted.
n Riskware Treatment - Riskware is a legal software that might be dangerous.
Note - If you decrease this value, it can improve the performance of the Anti-
Malware component but reduces security, as clients might not get a reputation
status that shows an item to be zero-day malware.
l Enable web protection - Prevents access to suspicious sites and execution of
malicious scripts Scans files, and packed executables transferred over HTTP, and
alerts users if malicious content is.found.
n Threat Cloud Knowledge Sharing - To share infected information, statistics and
infected file samples with Check Point for analysis, select any of these:
l Allow sending infection info and statistics to Check Point servers for analysis
l Allow sending infected file samples to Check Point servers for analysis
Note - This is supported only with a DHS compliant Harmony Endpoint Security
client.
n Mail Protection - Enable or disable scans of email messages when they are passed as
files across the file system.
Signature
n Frequency
Anti-Malware gets malware signature updates at regular intervals to make sure that it
can scan for the newest threats. These actions define the frequency of the signature
updates and the source:
l Update signatures every [x] hours - Signature updates occur every [x] hours from
the Endpoint Policy Server and the External Check Point Signature Server.
l Signature update will fail after [x] seconds without server response - The
connection timeout, after which the update source is considered unavailable.
n Signature Sources
l External Check point Signature Server - Get updates from a dedicated, external
Check Point server through the internet.
l Other External Source - Get updates from an external source through the internet.
Enter the URL.
n Shared signature source - Get updates from a shared location on an Endpoint Security
client that acts as a Shared Signature Server. This solution is curated for Virtual Desktop
Infrastructure (VDI) environments, but can be leveraged for other scenarios as well. This
makes it possible to protect non-persistent virtual desktops in Virtual Desktop
Infrastructure (VDI) environments. Each non-persistent virtual desktop runs an Endpoint
Security, and gets Anti-Malware and Threat Prevention signatures from a shared folder
on the Shared Signature Server that is a persistent virtual machine.
l Second Priority - Set a fallback update source to use if the selected update source
fails. Select a different option than the first signature source.
l Third Priority - Set a fallback update source to use if the other sources fail.
Note - If only update from local Endpoint Servers is selected, clients that are
disconnected from an Endpoint Security server cannot get updates.
n Shared Signature Server - To set the server as a Shared Signature Server, select the
Set as shared signature server checkbox and enter the local path of the folder. For
example, C:\Signatures. For more information, see "Shared Signatures Server" on
page 540.
Scan
Anti-Malware scans computers for malware at regular intervals to make sure that suspicious
files are treated, quarantined, or deleted.
n Perform Periodic Scan - Select one of these options to define the frequency of the
scans:
l Every Month- Select the day of the month on which the scan takes place and the
Scan start hour.
l Every Week - Select the day of the week on which the scan takes place and the
Scan start hour.
l Every Day - Select the scan start hour.
l Scan on Idle - Specify the idle time duration for the endpoint. The Harmony
Endpoint Security client initiates the initial or periodic Anti-Malware scan only when
the endpoint remains idle for the specified duration. If the device is not idle, the
scan is postponed for 24 hours. After this 24-hour period, the Harmony Endpoint
Security client initiates the initial or periodic Anti-Malware scan, irrespective of
whether the device is idle or in use.
Note - Scan on Idle is not supported with the DHS compliant Anti-Malware blade.
Optional :
l Randomize scan time - Mandatory for Virtual Desktop Infrastructure (VDI). Select
this option to make sure that not all computers do a scan for malware at the same
time. This makes sure that network performance is not affected by many
simultaneous scans. In Start scan and End scan, specify the time range during
which the scan can start and end.
l Run initial scan after the Anti-Malware blades installation.
l Allow user to cancel scan.
l Prohibit cancel scan if more than X Days passed since last successful scan.
n Scan Targets - Select the target for the Anti-Malware scan:
l Critical areas
l Optical drives
l Local drives
l Mail messages
l Removable drives
l Unrecognized devices
l Network devices
Notes:
n Mail messages is not supported with the DHS compliant Anti-Malware blade
in macOS.
n Critical areas is supported with the DHS compliant Anti-Malware blade from
l Skip archives and non executables - Skips scanning of archive file formats (for
example, .zip, 7zip, tar.gz, rar, and so on) and non-executable files (files without
the execute permission).
Note - Skip archives and non executables are not supported with the DHS
compliant Anti-Malware blade.
l Do not scan files larger than - Specify the file size limit. If the file size is larger than
the specified limit, then the system skips scanning the file. The default file size limit
is 20 MB.
Note - The maximum supported file size for the Anti-Malware scan depends
on the endpoint's system specifications, such as CPU, RAM and so on.
Threat Emulation
You can define the default file action for threat emulation.
3. Click OK.
Advanced Capabilities
Browser Settings
Starting from the Harmony Endpoint Security client E87.10, the extension is pinned to the
browser by default for users.
Note - You can unpin the extension only on Chromium browsers, such as Chrome,
Edge and Brave. You cannot unpin an extension in Firefox.
To allow users to unpin the browser extension, clear Always pin the browser extension to the
tool bar under Pin Extension.
Behavioral Protection
Behavioral protection includes Anti-Bot, Behavioral Guard and Anti-Ransomware protections.
n Prevents damage by blocking bot communication to C&C sites and makes sure that no
sensitive information is stolen or sent out of the organization.
The Endpoint Anti-Bot component uses these procedures to identify bot infected computers:
n Identify the C&C addresses used by criminals to control bots
n These web sites are constantly changing and new sites are added on an hourly basis.
Bots can attempt to connect to thousands of potentially dangerous sites. It is a challenge
to know which sites are legitimate and which are not.
The ThreatCloud repository contains more than 250 million addresses that were analyzed for
bot discovery and more than 2,000 different botnet communication patterns. The ThreatSpect
engine uses this information to classify bots and viruses.
Configuring Anti-Bot
Note - Behavioral Guard also parses the email (through an add-in to Microsoft
Outlook) to include the details in the forensics report in the event of a malicious attack
through an email.
The Anti-Ransomware creates honeypot files on client computers, and stops the attack
immediately after it detects that the ransomware modified the files.
You can identify these folders by the lock icon that is associated with the name of the folder.
For example:
n Check Point
n Check-Point
n Sandblast Agent
n Sandblast Zero-Day
n Endpoint
Before ransomware attack can encrypt files, Anti-Ransomware backs up your files to a safe
location. After the attack is stopped, it deletes files involved in the attack and restores the
original files from the backup location.
n Prevent - The attack is remediated. Logs, alerts and a forensic report are created.
n Detect - Logs, alerts and a forensic report are created.
n Off - Nothing is done on the detection, a log is not created
n Enable network share protection - Enables the protection of shared folders on the
network. All shared folders are protected, regardless of the protocol. Remote devices are
not protected.
n Block Volume Encryption tools (BitLocker and Similar Tools): As many ransomwares
use volume encryption software, such as BitLocker to encrypt drives.
Note - This feature is supported with the Harmony Endpoint Security Client
version E86.30 with the default client mode as Detect. With the Harmony
Endpoint Security Client version E86.50 and higher, the default client mode is
Prevent.
n Low memory mode: Significantly reduces memory utilization by retaining only the most
recently matched signatures. However, there is a slight drop in the detection rate. It is
recommended to enable this setting only for system with low memory capacity. This is
supported only with the Endpoint Security Client version E87.30 and higher.
Backup Settings
When Anti-Ransomware is enabled, it constantly monitors files and processes for unusual
activity. Before a ransomware attack can encrypt files,Anti-Ransomware backs up your files to
a safe location. After the attack is stopped, it deletes files involved in the attack and restores
the original files from the backup location.
n Restore to selected location - - By default, files are restored to their original location. To
restore files to a different location, select this option and enter the location to which you
want to restore the files in the Choose location field. Each time files are automatically
restored, they will be put in the selected location.
n Anti-Ransomware maximum backup size on disk - Set the maximum amount of
storage for Anti-Ransomware backups. The default value is 1 GB.
n Backup time interval - Within this time interval, each file is only backed up one time,
even if it is changed multiple times. The default value is 60 minutes.
n Backup Settings - Change default types to be backed up - Click this to see a list of file
types that are included in the Anti-Ransomware backup files. You can add or remove file
types from the list and change the Maximum Size of files that are backed up.
n Disk Usage - By default, Forensics uses up to 1 GB of disk space on the client computer
for data.
Protection mode - Define in which confidence level the incident is analyzed: Always, High,
Medium & High, or Never. The confidence level is how sure Endpoint Security is that a file is
malicious. High confidence means that it is almost certain that a file is malicious. Medium
confidence means that it is very likely that a file is malicious. The default value is Always.
Enable Threat Hunting - Threat Hunting is enabled by default. To learn more about Threat
Hunting, see "Threat Hunting" on page 514.
File Quarantine
Define the settings for files that are quarantined. By default, items are kept in quarantine for 90
days and users can delete items from quarantine.
n File quarantine - Select the confidence level in which Remediation is performed: Always
High, Medium & High, Never. The default value is Medium & HIgh.
n Allow users to delete items from quarantine - When selected, users can permanently
delete items from the quarantine file on their computers.
n Allow users to restore items from quarantine - When selected, users can restore items
from the quarantine file on their computers.
n Copy quarantine files to central location -Enter a central location to which the
quarantined files from the client computers are copied.
File Remediation
Define what happens to the components of an attack that is detected by Forensics. When files
are quarantined, they are deleted and put in a secure location from which they can be restored,
if necessary.
You can manually edit the treatment for each category of file: Malicious, Suspicious, or
Unknown. For each category, you can select:
n Quarantine - Files are deleted and put in a secure location from which they can be
restored, if necessary.
n Delete - Files are permanently deleted.
n Backup -- Delete the file and create an accessible duplicate.
n None -- No action is taken.
Trusted files s are those defined as trusted by the Check Point Reputation Service. The
Remediation options for Trusted Files are:
n Terminate - stop the suspicious process.
n Ignore - Do not terminate processes. Activity is monitored.
Note - Smart Exclusions is supported only with Endpoint Security Client version
E87.40 and higher.
Legacy Exclusions
You can exclude specific objects (exclusions) from inspection by Harmony Endpoint. You can
add exclusions to a rule or create global exclusions that apply to all rules.
Notes:
n You cannot add exclusions for Forensic events triggered by Anti-Bot.
n You cannot add exclusions for Forensic events triggered by Anti-Malware engine that
has no reference event.
n This procedure is not supported for macOS endpoints.
2. Right-click a log to add and configure an exclusion to your endpoint device. This
redirects you to the appropriate rule, section, and capability.
3. Select one of these options to apply the exclusions:
n Effective option: For a specific device or a user rule.
n All options: For a specific rule.
Notes:
n This option is available only for Harmony Endpoint client version E86.20 and later.
n For Harmony Endpoint client version 86.20 or earlier, or for unsupported
blades/capabilities, you are redirected to the relevant rule in the exclusions center to
create exclusions.
2. Click .
4. Click OK.
5. In the bottom right corner of the policy configuration pane, click Save.
Editing an Exclusion
To edit an exclusion:
1. Do one of these:
n Go to Policy > Threat Prevention > Policy Capabilities.
n Go to Policy > Threat Prevention > Global Exclusions.
The Edit Exclusions Center window opens.
2. Expand an exclusion category. For example, Anti-Bot -> URL Filtering Exclusions.
3. If you are editing a local exclusion, expand Local Exclusions. This step does not apply to
Global Exclusions.
4. Select the exclusion you want to edit.
5. Click .
d. (Optional) Comment
e. To apply the changes to all the rules that contain this exclusion, select the Update
all rules checkbox. This step does not apply to Global Exclusions.
f. To add the exclusion to all the rules that does not contain this exclusion, select the
Add to all rules checkbox. This step does not apply to Global Exclusions.
7. Click OK.
8. In the bottom right corner of the policy configuration pane, click Save.
9. From the top, click Install Policy.
Below is the list of supported exclusions.
Anti-Bot Exclusions
You can exclude specific domains from a rule. Click + to add the required domain you want
to exclude from the rule.
Syntax
domain.com n https://www.domain.com -
n http://www.domain.com
n https://domain.com
n http://domain.com
n https://sub.domain.com
n http://sub.domain.com
Harmony Endpoint scans files when you create, open, or close them.
When you exclude a trusted process from inspection, it's file or network operation is not
scanned. Exclude a process only if you are sure, it is not Malware.
Windows
You can exclude only .EXE files.
Syntax:
macOS
Syntax:
Fully qualified path for the trusted executable file.
Example:
/Applications/FileZilla.app/Contents/MacOS/filezilla
Anti-Malware -> Files and Folders Exclusion (system, scheduled and on-demand)
Files and Folder Exclusions are applied to all types of scans except contextual scan. The
reason for configuring exclusions is to reduce the CPU usage of Anti-Malware.
Note - Files and folders must be excluded only if they are located in a Trusted zone
or are considered a low-risk target for viruses.
Windows
Syntax:
Directory paths must end with a backlash.
Examples:
n Directory:
l C:\Program Files\MyTrustedDirectory\
l %programdata%\MyTrustedDirectory\
n Specific file:
l C:\ProgramFiles\MyTrustedDirectory\excludeMe.txt
l %programdata%\MyTrustedDirectory\excludeMe.txt
n File type:
l *.exe
l \\ServerName\Share\folder\file.txt or \\ip_
addres\Share\folder\file.txt depending on a way file is attached.
Note - For Windows, files and folder names are not case-sensitive.
macOS
Syntax:
Directory path, a specific file, or a file type. Environment variables are not supported.
Example:
Trusted directory
n /Users/Shared/MyTrustedDirectory/
Specific file
n /Users/*/Documents/excludeMe.txt
File type
n *.txt
You can exclude some riskware files and infections from the scheduled malware scan on
your computer.
Best Practice:
n Exclude when the specific software is allowed.
n As a temporary exclusion when there is a false positive
detection.
Syntax
Infection name and protection name in your log.
Example:
n EICAR-Test-File
Notes -
n The infection name is case-sensitive.
n If you get a file protection detection, share the file with Check Point to resolve
the file protection.
You can exclude specific folders, domains or SHA1 hashes from the Threat Emulation,
Threat Extraction and Zero-Phishing protection.
Domain exclusions
n Relevant only for Harmony Endpoint extension for Browsers.
n To exclude an IP, in the Element field, enter IP address followed by subnet mask in
the format <X.X.X.X>/ <subnet mask >. For example, to exclude a computer with IP
address 192.168.100.30, enter 192.168.100.30/24.
n Domain exclusions must be added without http, https or any other special characters
except asterisk (*).
domain.com n https://www.domain.com -
n http://www.domain.com
n https://domain.com
n http://domain.com
n https://sub.domain.com
n http://sub.domain.com
SHA1 exclusions -
Notes -
l This is supported with Endpoint Security Client version E88.00 or
higher.
l To view the hash of a macro, see the Description in the Forensic
Details section in the Card of the event. For more information see,
Adding Exclusions from Logs.
Folder exclusions -
n Relevant only for Threat Emulation blade (File system monitoring).
n Folder path cannot contain environment variables.
n When you exclude a folder, enter the folder as a windows path. For example:
C:\Program Files\MyTrustedDirectory\
n If the path of created file begins with exclusion, it will be excluded.
n Folder exclusions support wildcards. These wildcards are supported:
? - Each question mark masks one character.
* - Each star masks zero or more characters.
n It is not advised to add * in the middle of path exclusions, as it may hurt the
performance.
n Exclude network files by path \\ServerName\Share\folder\.This excludes all
files located under \ServerName\Share\folder\\.
You can exclude these elements from the Anti-Ransomware and Behavioral Guard
protection:
n Folder – To exclude a folder or non-executable files
Notes:
n Excluded process will be monitored but not
triggered.
n Excluded protection will not be triggered.
Syntax:
n Folder can contain environment variables
n Folder cannot contain wildcards (*)
n By default, sub-folders are included.
Excluding a Certificate / Process means that files modified / created by a certain process
will not be backed up, or monitored by Anti-Ransomware and Behavioral Guard.
Windows
Syntax:
n You must specify the process name or full path to the process
n Exclusion can contain environment variables
n Wildcards are supported.
Note - This is supported with Endpoint Security client version E86.70 and higher.
Examples:
n Full path
l C:\Program Files\MyTrustedDirectory\
n Process
l C:\Program Files\MyTrustedDirectory\ExcludeMe.exe
n Certificate
l Microsoft
n md5: 0123456789012345
n Protection: win.blocker
macOS
Syntax:
Excluding a Certificate / Process means that files modified / created by a certain process
will not be backed up, or monitored by Anti-Ransomware and Behavioral Guard.
You can exclude a file or process from quarantine. You can define the exclusion by these
criteria: certificate, file, folder, MD5 hash, SHA1 hash, and file extension. When an element
is excluded from quarantine, even if there is a detection of malware, the file is not
quarantined.
Smart Exclusions
Smart Exclusions allows you to add exclusions to one or more capabilities and types easily,
whereas the Legacy Exclusions allows you to add exclusion only for one capability at a time.
With Smart Exclusions, you can:
n Set exclusions to all capabilities and operating systems at once.
n Use standard syntax across all exclusion types.
n Use wider range of wildcard characters for nuanced and customized exclusion patterns.
n Easily enable or disable exclusions with a simple toggle button without the need to delete
exclusions temporarily.
Note - Smart Exclusions is supported only with Endpoint Security Client version
E87.52 and higher for Windows and E87.50 and higher for macOS.
2. Select the rule for which you want to create the exclusion.
3. In the Capabilities & Exclusions pane, click Exclusions Center.
4. Click Go to Smart Exclusions.
e. From the Operating system list, select the operating system to which you want
to apply the exclusion. For example, endpoints running Windows operating
system only. It is not available if you select All supported in the Apply to the
following capabilities section.
Notes:
n Capabilities not relevant to the selected group are not
available.
n For supported syntax and capabilities for exclusion types,
see sk181679.
g.
If the
Exclusion Then
Type is
Process a. In the Process path field, enter the path of the process.
path For example, C:\windows\system\cmd.exe.
b. To specify additional criteria, expand Process path
options, and select:
n Case sensitive
n Trusted process
n Argument and if required, select Regex, and in the
Process a. From the Process hash type list, select the hash type:
hash n MD5
n SHA1
n SHA2
n cdhash (for macOS only)
Process In the Process signer value field, enter the process signer
signer value. For example, Check Point Ltd.
File path a. In the File path field, enter the path of the file. For
example, C:\windows\system\.
b. To specify additional criteria, expand File path options,
and select Case sensitive.
File hash a. From the File hash type list, select the hash type:
n MD5
n SHA1
n SHA2
n cdhash (for macOS only)
File signer In the File signer value field, enter the process signer value.
For example, Check Point Ltd.
If the
Exclusion Then
Type is
e. From the Operating system list, select the operating system to which you want
to apply the exclusion. For example, endpoints running Windows operating
system only. It is not available if you select All supported in the Apply to the
following capabilities section.
Notes:
l Capabilities not relevant to the selected group are not
available.
l Anti-Exploit capability supports only Process path and
Infection/Protection exclusions.
Notes:
n Chained exclusion is supported only with the Exclusion group of the
l Process hash
l Process signer
n With the Harmony Endpoint Security Client version E88 and higher, it
Note - For supported syntax and capabilities for exclusion types, see
sk181679.
j.
If the Exclusion Exclusion
Then
Group is Type
k. Click Finish.
8. Click OK.
9. Click Save & Install.
e. From the Operating system list, select the operating system to which you want
to apply the exclusion. For example, endpoints running Windows operating
system only. It is not available if you select All supported in the Apply to the
following capabilities section.
Notes:
n Capabilities not relevant to the selected group are not
available.
n For supported syntax and capabilities for exclusion types,
see sk181679.
g.
If the
Exclusion Then
Type is
Process a. In the Process path field, enter the path of the process.
path For example, C:\windows\system\cmd.exe.
b. To specify additional criteria, expand Process path
options, and select:
n Case sensitive
n Trusted process
n Argument and if required, select Regex, and in the
Process a. From the Process hash type list, select the hash type:
hash n MD5
n SHA1
n SHA2
n cdhash (for macOS only)
Process In the Process signer value field, enter the process signer
signer value. For example, Check Point Ltd.
File path a. In the File path field, enter the path of the file. For
example, C:\windows\system\.
b. To specify additional criteria, expand File path options,
and select Case sensitive.
File hash a. From the File hash type list, select the hash type:
n MD5
n SHA1
n SHA2
n cdhash (for macOS only)
File signer In the File signer value field, enter the process signer value.
For example, Check Point Ltd.
If the
Exclusion Then
Type is
e. From the Operating system list, select the operating system to which you want
to apply the exclusion. For example, endpoints running Windows operating
system only. It is not available if you select All supported in the Apply to the
following capabilities section.
Notes:
l Capabilities not relevant to the selected group are not
available.
l Anti-Exploit capability supports only Process path and
Infection/Protection exclusions.
Notes:
n Chained exclusion is supported only with the Exclusion group of the
l Process hash
l Process signer
n With the Harmony Endpoint Security Client version E88 and higher, it
Note - For supported syntax and capabilities for exclusion types, see
sk181679.
j.
If the Exclusion Exclusion
Then
Group is Type
k. Click Finish.
6. Click Save.
The exclusions are automatically enforced on the client without installing the policy.
Best Practice - Check Point recommends to follow these steps before migrating to Smart
Exclusions:
1. Go to Policy > Threat Prevention > Policy Capabilities
2. Pick a rule to test the migration and clone the rule.
3. Place the newly created rule at the top.
4. Under Applied To, select a test group.
5. Click Exclusion Center for the newly created rule and export the legacy exclusions
for backup purposes.
6. For the newly created rule, migrate to Smart Exclusions. See "To migrate legacy
exclusions to smart exclusions:" below.
7. Click Save and Install.
8. Go to Logs and filter the logs for the computer in the test group. Verify that there are
no false positives and all the detections are excluded correctly. If there are issues,
contact Check Point Support.
9. Perform the steps 1 through 8 for each rule at a time.
10. Repeat the process for Global Exclusions.
Managing Exclusions
To manage exclusions:
1. To manage smart exclusions for a rule:
a. Go to Policy > Threat Prevention > Policy Capabilities.
b. Select the rule.
c. In the Capabilities & Exclusions pane, click Exclusions Center.
2. To manage global smart exclusions, go to Policy > Threat Prevention > Global
Exclusions.
3. Click Go To Smart Exclusions.
4. To edit an exclusion:
n
Select the exclusion and click .
n Right-click the row and click Edit.
To a change Single-method exclusion to Multi-method exclusion, click Edit in
multi-value wizard at the bottom of the wizard.
Refer to "Adding Exclusions to a Specific Rule" on page 265 to edit the exclusion.
5. To delete exclusions:
n
Select the exclusions and click .
n
Click the row and at the end of the row, click .
n Select the exclusions, right-click and click Delete.
6. To duplicate exclusions:
n
Select the exclusion and click .
n
Click the row and at the end of the row, click .
n Select the exclusion, right-click and click Duplicate.
7. To enable or disable the exclusion, toggle the button in the Status column.
8. To edit Name, Capabilities and Comment:
n Hyper-V
n Web Server (IIS)
n Print Server
Additional Profiles:
n Exclude ConnectWise
n Not a Virus
n Not a Virus TE
n Not a Virus AM
Notes :
n This is supported only with Harmony Endpoint Security Client version E86.60 and
higher.
n Oracle servers are not supported.
Quarantine Management
When Harmony Endpoint components (Forensics and Anti-Ransomware, Anti-Bot, and Threat
Extraction and Threat Emulation), detect malicious files, they can quarantine those files
automatically based on policy. All components use the same Remediation service, that:
n Receives the request to quarantine a file.
n Terminates the file's process, if running.
n Encrypts the file and stores it compressed along with metadata in a protected folder.
Two utilities let administrators and end-users manage quarantined files.
2. Click Import.
3. In the window that opens, browse to select the quarantined file to import.
The file, with its metadata, is imported to the quarantine database from where the utility
is run.
Column Description
Rule Number The sequence of the rules is important because the first rule that matches
traffic according to the protected scope is applied.
Duplicate a rule
Install Policy
Delete a rule
Configuration Options
n Algorithms used
Go to Advanced Settings > Encryption > Choose Algorithm.
Full Disk Encryption can use these encryption algorithms:
l AES-CBC 256 bit (Default)
l XTS-AES 128 bit
l XTS-AES 256 bit
n Volumes encrypted
By default, all drives that are detected after the installation and all visible disk volumes
are encrypted. IRRT are not encrypted.
Go to Advanced Settings > Encryption > Allow Self-Encrypting Drives (SED)
hardware functionality.
Full Disk Encryption probes and uses SED disks that comply with the OPAL standard. If
a compatible system and disk are detected, Full Disk Encryption uses the hardware
encryption on the disk instead of the traditional software encryption.
When using SED drives, leave Encrypt hidden disk volumes checked (which is the
default setting):
l AES encryption is always used with SED drives
l Manage SED drives in the same way as software-encrypted drives.
n Initial Encryption
l Encrypt entire drive - Recommended for computers that are in production and
already have user data, such as documents and emails.
l Encrypt used disk space only - Encrypts only the data. Recommended for fresh
Windows installations.
To enable Pre-boot:
Go to the Policy view > Data Protection > General >.Capabilities and Exclusions > Full Disk
Encryption > click Enable Pre-boot.
Temporary Pre-boot Bypass lets the administrator disable Pre-boot protection temporarily, for
example, for maintenance. It was previously called Wake on LAN (WOL). You enable and
disable Temporary Pre-boot Bypass for a computer, group, or OU from the computer or group
object. The Pre-boot settings in the Full Disk Encryption policy determine how Temporary Pre-
boot Bypass behaves when you enable it for a computer.
Temporary Pre-boot Bypass reduces security. Therefore use it only when necessary and for
the amount of time that is necessary. The settings in the Full Disk Encryption policy set when
the Temporary Pre-boot Bypass turns off automatically and Pre-boot protection is enabled
again.
You can configure the number of minutes the Pre-boot login is displayed before automatic OS
logon.
There are different types of policy configuration for Temporary Pre-boot Bypass:
n Allow OS login after temporary bypass
n Allow bypass script
If you run scripts to do unattended maintenance or installations (for example, SCCM) you
might want the script to reboot the system and let the script continue after reboot. This
requires the script to turn off Pre-boot when the computer is rebooted . Enable this
feature in the Temporary Pre-boot Bypass Settings windows. The Temporary Pre-boot
Bypass script can only run during the timeframe configured in Temporary Pre-boot
Bypass Settings.
FDEControl.exe set-wol-off
FDEControl.exe set-wol-on
The above commands fail with code "13 ( UNAUTHORIZED )" if executed outside the
timeframe specified in the policy.
You can select the Temporary Pre-boot Bypass duration:
n On demand, Once, or Weekly,
n Disable after X automatic logins - Bypass turns off after the configured number of logins
to a computer.
n Disable after X days or hours - Bypass turns off after the configured days or hours
passed.
Note - If you select both Disable after X automatic logins and Disable after X days
or hours, bypass turns off when any of these options occurs.
Best Practice - Select a small number so that you do not lower the security by
disabling the Pre-boot for a long time.
Action Description
Display last The username of the last logged on user shows in the Pre-boot logon
logged on user in window.
Pre-boot That user only needs to enter a password or Smart Card pin to log in
Reboot after [x] n If active, specify the maximum number of failed logons allowed
failed logon before a reboot takes place.
attempts were n This setting does not apply to smart cards. Smart Cards have
made their own thresholds for failed logons.
Verification text Select to notify the user that the logon was successful, halting the boot-
for a successful up process of the computer for the number of seconds that you specify
logon will be in the Seconds field.
displayed for
Action Description
Enable USB Select to use a device that connects to a USB port. If you use a USB
devices in Pre- Smart Card you must have this enabled.
boot environment If you do not use USB Smart Cards, you might need this enabled to
use a mouse and keyboard during Pre-boot.
Enable TPM two- Select to use the TPM security chip available on many PCs during pre-
factor boot in conjunction with password authentication or Dynamic Token
authentication authentication.
(password & The TPM measures Pre-boot components and combines this with the
dynamic tokens) configured authentication method to decrypt the disks.
If Pre-boot components are not tampered with, the TPM lets the
system boot.
See sk102009 for more details.
Enable remote Select to enable remote help without the need of assigning any Pre-
help without pre- boot user to the computer. When giving remote help, select the Pre-
boot user Boot Bypass Remote Help type that performs a One-Time logon. The
setting is only available if Pre-boot is configured to be disabled.
Remote Help Users can use Remote Help to get access to their Full Disk Encryption
protected computers if they are locked out.
Here you configure the number of characters in the Remote Help
response that users must enter.
Full Disk Encryption policy settings enable user acquisition by default. If user acquisition is
disabled, the administrator must assign at least one Pre-boot user account to each client
computer before encryption can start. You can require one or more users to be acquired
before encryption can start. You can also configure clients to continue user acquisition after
Pre-boot is already enabled. This might be useful if a client computer is used by many users,
also called roaming profiles.
Usually a computer has one user and only one user must be acquired. If the computer has
multiple users, it is best if they all log on to the computer for Full Disk Encryption to collect their
information and acquire them.
User acquisition settings
Note - If you need to terminate the acquisition process, for example, if the client fails
to acquire users although an unlimited time period is set, define a new automatic
acquisition policy.
User Assignment
You can view, create, lock and unlock authorized Pre-boot users.
2. Click and select Full Disk Encryption > Preboot User Assignment.
The Authorize Pre-Boot Users window opens. You can see the authorized users for
each device you search.
n Account Details
l Lock user for Pre-boot
l Require change password after first logon - Applies only to password
authentication. Select this option to force users to change their password
after the first pre-boot logon.
n Expiration Settings - Select an expiration date for the user authorization.
The Authorize Pre-Boot Users window opens. You can see the authorized users for
each device you search.
3. In the search box, search for the applicable device.
The list of authorized users to access the device appears.
4. Click on the user on the list to select it and click on the lock icon above the list to lock or
unlock the user.
Configuration options:
Setting Description
Note - To take control of a BitLocker-encrypted device, the target device must have a
Trusted Platform Module (TPM) module installed.
You can do a takeover of BitLocker-encrypted devices that are not managed by Harmony
Endpoint, and make them centrally managed. You can do this using BitLocker Management or
Check Point Full Disk Encryption.
n Define a Full Disk Encryption rule that applies to the entire organization or only to the
entities that need BitLocker Management.
n In BitLocker Encryption Settings, select Windows Default as the Encryption Algorithm.
This is important because it leaves the existing BitLocker encryption in place. Selecting
another algorithm explicitly may result in a re-encryption, if the existing algorithm does
not match the algorithm in the policy. It is a good idea to avoid re-encryption because it
can take a long time. The time it takes depends on the disk size, disk speed and PC
hardware.
To take control of unmanaged BitLocker devices using Check Point Full Disk Encryption:
1. Follow the procedure for "To take control of unmanaged BitLocker devices using
BitLocker Management:" on the previous page.
2. After the devices are under Check Point BitLocker Management, define a rule with
Check Point Full Disk Encryption that applies to the Entire Organization or only to the
entities that need Check Point Full Disk Encryption. See "Check Point Disk Encryption
for Windows" on page 293
Best Practice - When you change the encryption policy for clients from
BitLocker Management to Check Point Full Disk Encryption, the disk on the
client is decrypted and then encrypted. This causes the disk to be in an
unencrypted state for some time during the process. We recommend that
you do not change the encryption policy for entire organization in one
operation. Make the change for one group of users at a time.
Best Practice - Best practice is to only use this feature when there is no Active
Directory available. For customers that use Active Directory, we recommend a
combination of User Acquisition, OneCheck Logon, and Password
Synchronization that will let users use the same credentials for Pre-boot and
Windows login.
If the Pre-boot is required on a computer as part of Full Disk Encryption, users must
authenticate to their computers in the Pre-boot, before the computer boots. Users can
authenticate to the Pre-boot with these methods:
n Password - Username and password. This is the default method.
The password can be the same as the Windows password or created by the user or
administrator.
n Smart Card - A physical card that you associate with a certificate. Users must have a
physical card, an associated certificate, and Smart Card drivers installed.
1. Go to the Policy view > Data Protection > SmartCards > Pre-boot Authentication.
2. Select one of these options:
a. Password - Users can only authenticate with a username and password.
b. Smart Card (requires certificate) - Users can only authenticate with a Smart Card.
Change authentication method only after user successfully authenticates with a
Smart Card - If you select this option, users can authenticate with a password until
all of the requirements for Smart Card authentication are set up correctly. After
users successfully authenticate one time with a Smart Card, they must use their
Smart Card to authenticate. If you configure a user for Smart Card only and do not
select this, that user is not able to authenticate to Full Disk Encryption with a
password
c. Either SmartCard or Password - Users can authenticate with a user name and
password or a SmartCard.
To configure the password for OneCheck Logon, go to Policy > Data Protection > OneCheck
> Password Constraints. These actions define the requirements for the OneCheck password:
Action Description
Use custom requirements If you select this, select the requirements for which
type of characters the password must contain or not
contain:
n Consecutive identical characters, for example,
aa or 33
n Require special characters. These can be: ! "
#$%&'()*+,-./:<=>?@{
n Require digits, for example 8 or 4.
n Require lower case characters, for example g
or t.
n Require upper case characters, for example F
or G.
n Password must not contain user name or full
name.
Minimum length of password Enter the minimum number of characters for a valid
password.
Password can be changed only Enter the minimum number of days that a password
after must be valid before the user can change it.
Password expires after Enter the maximum number of days that a password
can be valid before the user must change it.
You can configure Full Disk Encryption to lock user accounts after a specified number of
unsuccessful Pre-boot login attempts:
n Temporarily - If an account is locked temporarily, users can try to log on again after a
specified time.
n Permanently - If the account is locked permanently, it stays locked until an administrator
unlocks it.
Option Description
Number of failed logins Maximum number of failed logon attempts allowed before
before a user account is an account is permanently locked. The account is locked
permanently locked until an administrator unlocks it.
Remote Help lets users access their Full Disk Encryption protected computers if they are
locked out. The user calls the designated Endpoint Security administrator and does the
Remote Help procedure.
There are two types of Full Disk Encryption Remote Help:
n One Time Login - One Time Login allows access as an assumed identity for one
session, without resetting the password.
If users lose their Smart Cards, they must use this option.
n Remote password change - This option is for users who use fixed passwords and forgot
them.
For devices protected by Media Encryption & Port Protection policies, only remote password
change is available.
Option Description
Allow account to receive Let users get help from an administrator to reset the
remote password change account password (for example, if the user forgets the
help password).
Allow account to receive Let the user get help from an administrator to log on, one
One-Time Logon help time.
One-time logon is for users who have lost their Smart
Card.
It is also useful if the user made too many failed
attempts but does not want to change the password.
Logon Settings
OneCheck Logon Settings define additional settings for how users can access computers.
To configure Logon Settings, go to the Policy view > Data Protection > OneCheck > Logon:
Option Description
Allow logon Lets a different user than the logged on user authenticate in Pre-boot to a
to system system in hibernate mode.
hibernated
by another
user
Allow use of Let user authenticate to use recovery media to recover and decrypt data
recovery from an encrypted system.
media Note: In E80.20 and higher, if this is not selected, users can still access
recovery media that is created with a temporary user and password.
Allow user to Let users change the password on an endpoint client during the Pre-boot.
change his
credentials
from the
endpoint
client
Allow Single Let users use Single Sign On to log on to Pre-boot and Windows when
Sign-On use OneCheck Logon is disabled. Single Sign on applies only to Pre-boot and
Windows and not to different components, such as VPN or Media
Encryption. Users are always allowed to use Single Sign On when
OneCheck Logon is running.
Options Description
Allow OS password reset upon Pre- Reset the OS password after a successful Pre-
boot password reset boot password reset.
To import exclusions:
You can import an exported exclusion file in the JSON format.
a. In the Media Encryption tab, click View Exclusions.
b. Click Import and select the JSON file.
To export exclusions:
a. In the Media Encryption tab, click View Exclusions.
b. Select the exclusion from the list.
c. Click Export.
3. Per each device, configure the options as necessary for: Data Type and Write
Encrypted:
n Data Type - Select one of these options:
l Allow any data - Users can write all file types to storage devices.
l Encrypt business-related data - Users must encrypt all business-related
files written to storage devices. Other files can be written without encryption.
See "Configuring Business-Related File Types" on the next page.
l Encrypt all data - Users must encrypt all files written to storage devices.
l Block any data - Users cannot write any files to storage devices.
Notes:
n If no read policy is allows, the write policy is disabled automatically.
n If Block any Data is selected, Allow encryption and Configure File
Types are disabled.
To import exclusions:
You can import an exported exclusion file in the JSON format.
1. In the Media Encryption tab, click View Exclusions.
2. Click Import and select the JSON file.
To export exclusions:
1. In the Media Encryption tab, click View Exclusions.
2. Select the exclusion from the list.
3. Click Export.
The organization's policy defines access to business and non-business related data.
Business-related files are confidential data file types that are usually encrypted in the
business-related drive section of storage devices. These files are defined as business-related
file types by default:
n Multimedia - QuickTime, MP3, and more.
n Executable - Exe, shared library and more.
n Image - JPEG, GIF, TIF and more.
These files are defined as non-business related file types by default:
n Spreadsheet - Spreadsheet files, such as Microsoft Excel.
n Presentation - Presentation files, such as Microsoft Power Point.
n Email - Email files and databases, such as Microsoft Outlook and MSG files.
n Word - Word processor files, such as Microsoft Word.
To see the list of business-related file types and non-business related file types:
In Harmony Endpoint, go to the Policy view > Data Protection > Capabilities and Exclusions
pane > Media Encryption > Write Policy > Configure File Types > View Mode. Select Non-
Business-Related or Business-Related to see the relevant file types.
Managing Devices
You can configure custom settings for specified devices or device types. These device settings
are typically used as exceptions to settings defined in Media Encryption & Port Protection
rules.
There are two types of devices:
n Storage Device - Removable media device on which users can save data files.
Examples include: USB storage devices, SD cards, CD/DVD media and external disk
drives.
n Peripheral Device - Devices on which users cannot save data and that cannot be
encrypted.
New devices are added manually or are automatically discovered by the Endpoint Server.
You can view Manually added devices or Discovered devices. In the Device Type column,
you can see if the device is a storage device or a peripheral device.
3. Click .
4. Select :
n Storage Device
The New Storage Device window appears.
n Peripheral Device
The New Peripheral Device window appears.
5. Enter these:
n Name - Enter a unique device display name, which cannot contain spaces or
special characters (except for the underscore and hyphen characters).
n Applies to – This setting is valid for peripheral devices only.
n Connection Type- Select the connection type Internal, External or Unknown
(required).
n Category - Select a device category from the list.
n Serial Number - Enter the device serial number. You can use wild card characters
in the serial number to apply this device definition to more than one physical
device. See "Using Wild Card Characters" on page 325.
n Extra Information - Configure whether the device shows as fixed disk device (Hard
Drive with Master Boot Record), a removable device (Media without Master Boot
Record) or None.
n Device ID Filter - Enter a filter string that identifies the device category (class).
Devices are included in the category when the first characters in a Device ID match
the filter string. For example, if the filter string is My_USB_Stick, these devices are
members of the device category:
l My_USB_Stick_40GB
l My_USB_Stick_80GB
n Supported Capabilities:
l Log device events - Select this option to create a log entry when this device
connects to an endpoint computer (Event ID 11 or 20 only).
l Allow encryption - Select this option if the device can be encrypted (storage
devices only).
1. Click Asset Management > Media Devices > Storage & Peripheral.
2. Right-click the applicable device and select Exclude.
3. Configure the required Read Policy and Write Policy (relevant to storage devices only).
For more information on the configuration options, see "Configuring the Read Action" on
page 311 and "Configuring the Write Action" on page 313
4. Define Behavior (relevant for peripheral devices only):
a. From the Rule(s) list, select a rule.
b. From the Access type list, select Accept or Block.
The Discovered devices view lists the details of the devices automatically discovered by the
Endpoint server.
To edit a device:
1. Click Asset Management > Media Devices > Storage & Peripheral.
2. Right-click the applicable device and select Edit.
3. Enter these:
n Name - Enter a unique device display name, which cannot contain spaces or
special characters (except for the underscore and hyphen characters).
n Applies to – This setting is valid for peripheral devices only.
a. To assign the device to an existing group, from the existing group list, select a
group.
b. To assign the device to a new group, in the create a new group field, enter the new
group name.
c. If you do not want to add the device to any group, select do not add to group.
5. Configure the required Read Policy and Write Policy (relevant to storage devices only).
For more information on the configuration options, see "Configuring the Read Action" on
page 311 and "Configuring the Write Action" on page 313.
6. Define Behavior (relevant for peripheral devices only):
a. From the Rule(s) list, select a rule.
b. From the Access type list, select Accept or Block.
c. From the Log type list, select a log.
d. Add details in the Description field.
7. Click Finish.
You can create groups for storage devices. Using device groups facilitates policy management
because you can create exclusion rules for an entire group of devices instead of per one
device each time.
To create a new device group, or click Asset Management > Media Devices > Storage
Device Groups. You can create new groups or edit existing groups.
You can use wild card characters in the Serial Number field to apply a definition to more than
one physical device. This is possible when the device serial numbers start with the same
characters.
For example: If there are three physical devices with the serial numbers 1234ABC, 1234BCD,
and 1234EFG, enter 1234* as the serial number. The device definition applies to all three
physical devices. If you later attach a new physical device with the serial number 1234XYZ,
this device definition automatically applies the new device.
The valid wild card characters are:
The '*' character represents a string that contains one or more characters.
Because definitions that use wildcard characters apply to more endpoints than those without
wildcards, rules are enforced in this order of precedence:
5. 1234567
Viewing Events
Harmony Endpoint allows you to monitor activities related to storage and peripheral devices as
events and if required, change the device details and status. For example, if a device that
should be allowed was blocked and vice versa.
Column Description
Event Time Date and time when the device was connected to the endpoint.
3. Enter these:
n Name - Enter a unique device display name, which cannot contain spaces or
special characters (except for the underscore and hyphen characters).
n Applies to – This setting is valid for peripheral devices only.
n Connection Type- Select the connection type Internal, External or Unknown
(required).
n Category - Select a device category from the list.
n Serial Number - Enter the device serial number. You can use wild card characters
in the serial number to apply this device definition to more than one physical
device. See "Using Wild Card Characters" on page 325.
n Extra Information - Configure whether the device shows as fixed disk device (Hard
Drive with Master Boot Record), a removable device (Media without Master Boot
Record) or None.
n Device ID Filter - Enter a filter string that identifies the device category (class).
Devices are included in the category when the first characters in a Device ID match
the filter string. For example, if the filter string is My_USB_Stick, these devices are
members of the device category:
l My_USB_Stick_40GB
l My_USB_Stick_80GB
n Supported Capabilities:
l Log device events - Select this option to create a log entry when this device
connects to an endpoint computer (Event ID 11 or 20 only).
l Allow encryption - Select this option if the device can be encrypted (storage
devices only).
In Advanced Settings > Authorization Scanning, you can specify authorized and
unauthorized file types for scanning. The authorized and unauthorized scan configures the file
types that you can allow and block.
a. Click .
d. Click OK.
UserCheck Messages
UserCheck for Media Encryption & Port Protection tells users about policy violations and
shows them how to prevent unintentional data leakage. When a user tries to do an action that
is not allowed by the policy, a message shows that explains the policy.
For example, you can optionally let users write to a storage device even though the policy does
not allow them to do so. In this case, users are prompted to give justification for the policy
exception. This justification is sent to the security administrator, who can monitor the activity.
Select any of these checkboxes to enable the UserCheck message:
n Suggest to encrypt device when encryption is not mandatory
n Suggest to encrypt device in order to get write access when inserting
n Suggest to encrypt device in order to get write access when writing
n Notify user that device has been blocked
n Notify user that device has read only access
n Notify when encrypting business related data
Advanced Encryption
n Allow user to choose owner during encryption - Lets users manually define the device
owner before encryption. This lets users create storage devices for other users. By
default, the device owner is the user who is logged into the endpoint computer. The
device owner must be an Active Directory user.
n Allow user to change the size of encrypted media - Lets users change the percentage
of a storage device that is encrypted, not to be lower than Minimum percentage of media
capacity used for encrypted storage or Default percentage of media capacity used for
encrypted storage. .
n Allow users to remove encryption from media - Lets users decrypt storage devices.
n When encrypting, unencrypted data will be - Select one of these actions for
unencrypted data on a storage device upon encryption:
l Copied to encrypted section - Unencrypted data is encrypted and moved to the
encrypted storage device. We recommend that you back up unencrypted data
before encryption to prevent data loss if encryption fails. For example, if there is
insufficient space on the device.
l Deleted - Unencrypted data is deleted.
l Untouched - Unencrypted data is not encrypted or moved.
n Secure format media before encryption - Run a secure format before encrypting the
storage device. Select the number of format passes to do before the encryption starts.
n Change device name and icon after encryption - When selected, after the device is
encrypted, the name of the non-encrypted drive changes to Non Business Data and the
icon changes to an open lock. When cleared, the name of the non-encrypted drive and
the icon do not change after the device is encrypted.
n When encrypting media, file system should be:
l As already formatted -According to the original format.
l ExFAT
l FAT32
l NTFS
Allow user to change the file system of the encrypted storage - After storage was
encrypted in a specific format, the user can change this format to another format.
Site Configuration
Site Actions control when to allow or prevent access to encrypted devices that were encrypted
by different Endpoint Security Management Servers. Each Endpoint Security Management
Server (known as a Site) has a Universally Unique Identifier (UUID). When you encrypt a
storage device on an Endpoint Security client, the Endpoint Security Management Server
UUID is written to the device. The Site action can prevent access to devices encrypted on a
different Endpoint Security Management Server or from another organization. The Site action
is enabled by default.
When a user attaches a storage device, Media Encryption & Port Protection makes sure that
the device matches the UUID the Endpoint Security Management Server UUID or another
trusted Endpoint Security Management Server. If the UUIDs match, the user can enter a
password to access the device. If the UUID does not match, access to the device is blocked.
Allow access to storage devices encrypted at any site - Endpoint Security clients can access
encrypted devices that were encrypted at any site.
Allow access to storage devices encrypted at current site only - Media Encryption Site
(UUID) verification is enabled. Endpoint Security clients can only access encrypted devices
that were encrypted by the same Endpoint Security Management Server.
Lockout Settings
You can configure Media Encryption & Port Protection in the Lockout Settings to lock a device
after a specified number of unsuccessful log in attempts.
Notes:
n If a device is locked temporarily, users can try to authenticate again after
lock.
4. In the Duration for temporary storage device lock field, enter the duration after the
failed log in attempts the system should unlock the device.
Offline Access
Password protect media for access in offline mode - Lets users assign a password to access
a storage device from a computer that is not connected to an Endpoint Security Management
Server. Users can also access the storage device with this password from a non-protected
computer
Allow user to recover their password using remote help - Lets user recover passwords using
remote help.
Copy utility to media to enable media access in non-protected environments - Copies the
Explorer utility to the storage device. This utility lets users access the device from computers
that are not connected to an Endpoint Security Management Server.
Password Constraints
You can specify the password requirements for users to follow to log in to the device.
l In the Minimum length of password field, enter the number of characters required
in the password. The minimum supported length is four characters.
To recover a Media Encryption & Port Protection password with Remote Help assistance
from Harmony Endpoint:
1. Go to Asset Management > Organization > Computers.
2. Click and select Remote Help & Recovery > Media Encryption.
3. Do these:
a. Select the user.
b. In the Challenge field, enter the challenge code that the user gives you. Users get
the Challenge from the Endpoint client.
c. Click Generate Response.
Media Encryption & Port Protection authenticates the challenge code and
generates a Response code..
d. Give the Response code to the user.
e. Make sure that the user can access the storage device successfully.
Port Protection
Port Protection protects the physical port when using peripheral devices.
Peripheral devices are for example, keyboards, screens, blue tooth, Printers, Smart Card,
network adapters, mice and so on.
Note - The device names of macOS ports are prefixed with "MAC_".
o USB Network
o USB Video
o USB HID
o USB Health
o USB Audio
o USB Wireless controller
o USB SmartCard (Supported only with the Endpoint Security Client
version E86.20 and higher.)
o Bluetooth Audio
o Bluetooth Computer
o Bluetooth Health
o Bluetooth HID
o Bluetooth Imaging
o Bluetooth Phone
o Bluetooth Toy
o Bluetooth Wearable
o Printers
n To customize device settings, click Custom and then click Edit.
3. Click New.
7. Click Create.
To import exclusions:
You can import an exported exclusion file in the JSON format.
1. In the Port Protection tab, select the Port Protection Policy.
2. Click Edit.
3. Click Import and select the JSON file.
To export exclusions:
3. Select the device that you want to export from the list.
4. Click Export.
Important - When you create Firewall rules for Endpoint clients, create
explicit rules that allow all endpoints to connect to all the domain controllers
on the network.
Parts of Rules
As opposed to SmartEndpoint GUI, Harmony Endpoint has a unified Rule Base, which
enables the user to view the entire Rule Base at a glance - both inbound and outbound. Both
are sections of the same Rule Base.
These are the parts of the Firewall inbound/outbound rules:
Column Description
Action The action that is done on the traffic that matches the rule - Allow or Block.
Track The tracking and logging action that is done when traffic matches the rule:
n Log - Records the rule enforcement in the Endpoint Security Client
Log Viewer.
n Alert - Shows a message on the endpoint computer and records the
rule enforcement in the Endpoint Security Client Log Viewer.
n None - Logs and Alert messages are not created.
Editing a Rule
1. From the left navigation panel, click Policy > Access & Compliance.
2. Click the rule to select it.
When you edit a rule, a purple indication is added next to it (on the left of the rule).
3. In the right pane, in the section Capabilities & Exclusions, click the Firewall tab.
4. Click the Edit Inbound/Outbound Rulebase button.
5. Make the required changes.
To add a new rule, do one of these:
n From the top toolbar, the applicable option (New Above or New Below)
n Right-click the current rule and select the applicable option (New Above or New
Below)
6. Click OK in the bottom right corner.
7. Click Save in the bottom right corner.
Deleting a Rule
1. Click the rule to select it.
2. From the top toolbar, click the garbage can icon ("Delete rule").
If you are inside the Edit Inbound/Outbound Rulebase view, then a red indication is
added next to it (on the left of the rule).
3. If you are inside the Edit Inbound/Outbound Rulebase view, then click OK in the bottom
right corner.
A host can have multiple interfaces, but no routing takes place. It is an Endpoint device that
receives traffic for itself through its interfaces. (In comparison, a Security Gateway routes
traffic between its multiple interfaces). For example, if you have two unconnected networks
that share a common Endpoint Security Management Server and a Log Server, configure
the common server as a host object.
A host has no routing mechanism, it is not capable of IP forwarding, and cannot be used to
implement Anti-Spoofing.
The Endpoint Security Management Server object is a host.
Enter these properties data to define a host
n Name - A name for the host. The name must start with a letter and can include capital
and small letters, numbers and '_'. All other characters are prohibited
n IPv4 and/or IPv6 addresses of the host you want to use.
n Description (Optional) - A description of the host object.
Networks
A network is a group of IP addresses defined by a network address and a net mask. The net
mask indicates the size of the network.
A Broadcast IP address is an IP address which is destined for all hosts on the specified
network. If this address is included, the Broadcast IP address is considered as part of the
network.
Enter these properties to define a network:
n Name - A name for the network. The name must start with a letter and can include
capital and small letters, numbers and '_'. All other characters are prohibited.
n Network Address (IPv4) and Netmask (IPv4) of the network object you want to use.
or
Network Address (IPv6) and Prefix (IPv6) of the network object you want to use.
n Description (optional)- A description of the network object.
Network Groups
A network group is a collection of hosts, networks, or other groups. The use of groups
facilitates and simplifies network management. When you have the same set of objects
which you want to use in different places in the Rule Base, you can create a group to include
such set of objects and reuse it. Modifications are applied to the group instead of to each
member of the group.
Groups are also used where Harmony Endpoint lets you select only one object, but you
need to work with more than one.
A Domain object lets you define a host or a DNS domain by its name only. It is not
necessary to have the IP address of the site. You can use the Domain object in the source
and destination columns of the Firewall Policy.
Note - The DNS resolution is executed only once the policy is applied, or
following a reboot.
n Description (Optional) - A description of the Domain or Domain group object.
Enter these properties to define a Domain group:
n Name - A name for the Domain. The name must start with a letter and can include
capital and small letters, numbers and '_'. All other characters are prohibited.
n Click the + icon to add the required Domains to the Domain group.
n Description - A description of the Domain group
Address Ranges
An address range is a range of IP addresses on the network, defined by the lowest and the
highest IP addresses. Use an Address Range object when you cannot define a range of IP
addresses by a network IP and a net mask. The Address Range objects are also necessary
for the implementation of NAT and VPN.
Enter these properties to define an address range object:
n Name
n From IP address (IPv4) - To IP address (IPv4) - First and last IPv4 addresses of the
range.
or
From IP address (IPv6) - To IP address (IPv6) - First and last IPv6 addresses of the
range.
n Description (Optional) - A description of the address range.
Security Zones
Creating Objects
Create objects for areas that programs must have access to, or areas that programs must be
prevented from accessing.
Configure objects for each policy or define objects before you create a policy. After you
configure an object, you can use again it in other policies.
To create an object:
1. In the Access view, go to Manage > Manage Firewall Objects > Manage Objects and
Groups
(or, in the in the Access view > go to Edit Inbound/Outbound Rule Base).
Used In
Firewall
The Firewall guards the "doors" to your devices, that is, the ports through which Internet traffic
comes in and goes out.
It examines all the network traffic and application traffic arriving at your device, and asks these
questions:
n Where did the traffic come from and what port is it addressed to?
n Do the firewall rules allow traffic through that port?
n Does the traffic violate any global rules?
The answers to these questions determine whether the traffic is allowed or blocked.
When you plan a Firewall Policy, think about the security of your network and convenience for
your users.
A policy must let users work as freely as possible, but also reduce the threat of attack from
malicious third parties.
Firewall rules accept or drop network traffic to and from Endpoint computers, based on
connection information, such as IP addresses, Domains, ports and protocols.
Note - To add objects to the list , go to the Access view > Manage >
Manage Firewall Objects, and click Create.
Application Control
The Application Control component of Endpoint Security restricts network access for specified
applications. The Endpoint Security administrator defines policies and rules that allow, block
or terminate applications and processes. The administrator can also configure that an
application is terminated when it tries to access the network, or as soon as the application
starts.
This is the workflow for configuring Application Control:
Windows:
1. Set up a Windows device with the typical applications used on protected Endpoint
computers in your organization. This is your reference device. If you have several
different standard images, set up a reference device for each.
2. Generate the list of applications on the computer by running the Appscan tool. This
generates an XML file that contains the details of all the applications on the computer.
3. Upload the Appscan XML file to the Endpoint Security Management Server using
Harmony Endpoint.
4. Configure the action for each application in the Application Control policy. You can
configure which applications are allowed, blocked, or terminated.
5. Install policy.
macOS:
1. Run the Application Scan Push Operation. See "Performing Push Operations" on
page 491.
2. Configure the action for each application in the Application Control policy. You can
configure which applications are allowed, blocked, or terminated.
3. Install policy.
To generate the list of applications, run the Appscan command on the reference device. This
generates an XML file that contains the details of all the applications and operating system
files on the device. In the XML file, each application, and each application version, is uniquely
identified by a checksum. A checksum is a unique identifier for programs that cannot be
forged. This prevents malicious programs from masquerading as other, innocuous programs.
4. Run the Appscan application on your target device with the applicable parameters. See
"Appscan Command Syntax" below.
This creates an Appscan XML file for each disk image used in your environment. When
the scan is complete, an output file is created in the specified directory. The default file
name is scanfile.xml.
Description
Scans the host device and creates an XML file that contains a list of executable programs and
their checksums.
Syntax
Parameters
Parameter Description
Examples
n C:\>appscan /o scan1.xml
This scan, by default, includes .exe files in the current directory and is saved as
scan1.xml.
n C:\>appscan /o scan2.xml /x ".exe;.dll" /s "C:\"
This scan includes all .exe and .dll files on drive C and is saved as scan2.xml.
n C:\>appscan /o scan3.xml /x ".dll" /s c:\program files
This scan includes all .dll files in c:\program files and all its subdirectories. It is
saved as scan3.xml.
n C:\>appscan /s "C:\program files" /e
This scan includes all executable files in c:\program files and all its subdirectories.
It is saved as the default file name scanfile.xml.
Note - Before you upload the Appscan XML file, remove all special
characters, such as trademarks or copyright symbols, from the Appscan XML
.
Supported Actions
Action Description
1. In the Policy view, go to Access and Compliance > Application Control > Application
Management.
2. Select one of these options:
n Terminate on execution - Selected by default. Makes sure that all terminated
applications terminate immediately when they run.
n Terminate on connection - Terminate an application when the application tries to
access the network
App Rules
The Action column shows the permission for each application. Left-click the Action
column to select the action.
The Version column shows the details for each version of the application, including a
unique hash value that identifies the signer of the application version. You can block or
allow specific versions of the same program. Each version has a unique Version
number, Hash, and Created On date.
Custom Rules
1. In the Policy view, go to Access and Compliance > Application Control > Application
Management > Edit Application Control Policy.
2. Click Custom Rules.
3. Click New.
4. Enter a Rule Name.
5. Enter at least one of these details:
Notes:
n Use the wildcard character (*) to match a specific string.
l Enter *abc* to apply the rule for all applications that contain the string
abc in its details. For example, *abc* matches abc, xyzabc, abcxyz,
xyzabcxyz.
l Enter *abc to apply the rule for all applications ending with the string abc
n Publisher
For example, the publisher of Chrome is Google LLC.
To find the publisher of Chrome, on a Windows PC, navigate to C:\Program
Files\Google\Chrome\Application and see the name listed under the Company
column for chrome.
n Version
For example, the version of Chrome is 107.0.5304.107.
To find the version of Chrome, on a Windows PC, navigate to C:\Program
Files\Google\Chrome\Application, right-click chrome and click Properties. Click
the Details tab and see File version.
n File Name
For example, the file name of Chrome is chrome.exe.
To find the file name of Chrome, on a Windows PC, navigate to C:\Program
Files\Google\Chrome\Application.
n Issued By
For example, the issuer of Chrome is DigiCert Trusted G4 Code Signing
RSA4096 SHA384 2021 CAI.
Note:
l If the file has several signatures, the Endpoint Security client checks
all the signatures and applies the rule only if anyone of the
signatures match the specified signature.
l Only certificates with printable ASCII characters are supported.
n Issued To
For example, the issued to for Chrome is Google LLC.
To find the certificate issued to for Chrome, on a Windows PC:
a. Navigate to C:\Program Files\Google\Chrome\Application.
b. Right-click chrome and click Properties.
c. Click the Digital Signatures tab.
d. Click Details.
e. In the General tab, click View Certificate and see Issued to.
Notes:
l If the file has several signatures, the Harmony Endpoint Security
client checks all the signatures and applies the rule only if at least
one of the signatures match the specified signature.
l Only certificates with printable ASCII characters are supported.
n Command Line
For example, the command line of Chrome is C:\Program
Files\Google\ChromeApplication\chrome.exe.
To find the command line for Chrome, on a Windows PC, open Task Manager.
Click the Details tab and see the Command line column for the chrome.exe. If the
Command line column is not visible in the table, right-click the header row, click
Select columns and select Command line checkbox.
Changing the default action for unidentified applications is only supported in backward
compatibility mode.
In addition to Allow, Block and Terminate, there are two more actions that you can configure in
backward compatibility mode:
Unidentified (Allow) - The application is allowed because the default setting for applications
that are imported from the Appscan XML is
Allow, and the administrator did not change this action.
Unidentified (Block) - The application is blocked because the default setting for applications
that are imported from the Appscan XML is Block, and the administrator did not change this
action.
To enable or disable Windows Subsystem for Linux (WSL) on Endpoint Security client
computers:
1. In the Policy view, go to Access and Compliance > Application Control > Windows
Sub-systms for Linux (WSL) Traffic
2. Select Allow Windows Sub-systms for Linux (WSL) Traffic or leave this option cleared.
Developer Protection
Developer Protection prevents developers leaking sensitive information such as RSA keys,
passwords, and access tokens through the Git version control system. It also detects and warn
the developer when using packages with known vulnerabilities.
Developer Protection intercepts git commit commands issued by the developer, and scans
all modified files in a Git repository. It prevents the uploading of private information in plain text
and vulnerable dependencies from Endpoint Security client computers to public locations.
Developer protection is supported on Endpoint Security Client release E84.60 and higher.
Option Explanation
3. Click Save.
4. Install Policy.
Compliance
The Compliance component of Endpoint Security makes sure that endpoint computers comply
with security rules that you define for your organization. Computers that do not comply show
as non-compliant and you can apply restrictive policies to them.
The Compliance component makes sure that:
n All assigned components are installed and running on the endpoint computer.
n Anti-Malware is running and that the engine and signature databases are up to date.
n Required operating system service packs and Windows Server updates are installed on
the endpoint computer through WIndows Servers Update Services.
Note - This is not supported through Windows Settings > Update & Security
on your endpoint computer.
n Only authorized programs are installed and running on the endpoint computer.
n Required registry keys and values are present.
If an object (for example an OU or user) in the organizational tree violates its assigned policy,
its compliance state changes, and this affects the behavior of the endpoint computer:
n The compliant state is changed to non-compliant.
n The event is logged, and you can monitor the status of the computer and its users.
n Users receive warnings or messages that explain the problem and give a solution.
n Policy rules for restricted computers apply. See "Connected, Disconnected and
Restricted Rules" on page 402.
4. Define rule alerts and login policies to enforce the rules after deployment.
This action makes sure that all installed components are running and defines what happens if
they are not running. The action options are:
Action Description
Restrict if assigned Software Restrict network access if one or more Endpoint Security
Blade are not running components are not running.
Monitor if assigned Software Create log entries if one or more Endpoint Security
Blades are not running components are not running. No messages are sent.
Remote Access Compliance Status selects the procedure used to enforce the upon
verification failure from Policy > Access & Compliance > Remote Access Compliance
Status.
The options available are:
n Endpoint Security Compliance - Uses the Endpoint Security policy to control access to
organizational resources.
n VPN SCV Compliance - Uses SCV (Security Configuration verification) settings from
the Security Gateway to control access to organization resources. SCV checks, which
are defined in the Local.scv policy, always run on the client. This option is described in
the "Secure Configuration Verification (SCV)" section of the Remote Access VPN Client
for Windows Administration Guide.
Note - Endpoint Security clients on macOS always get their compliance status
from Endpoint SecurityCompliance, even if VPN Client verification process
will use VPN SCV Compliance is selected.
Many of the Compliance Policy actions contain Action Rules that include these components:
n Check Objects (Checks) - Check objects define the actual file, process, value, or
condition that the Compliance component looks for.
n One of these Action options - What happens when a computer violates the rule:
Action Definition
Observe Log endpoint activity without further action. Users do not know that they
are non-compliant. Non-compliant endpoints show in the Observe state
in the Reporting tab.
Warn Alerts the user about non-compliance and automatically does the
specified Remediation steps.
Send a log entry to the administrator.
Restrict Alerts the user about non-compliance and automatically does the
specified Remediation steps.
Send a log entry to the administrator.
Changes applicable policies to the restricted state after a pre-defined
number of heartbeats (default =5). Before this happens, the user is in
the about to be restricted state. On the monitoring tab, the user is shown
as pre-restricted.
Each Compliance Action Rule contains a Check object that defines the actual file, process,
value or condition that the Compliance component looks for.
Note: To edit the existing check object, click the existing check object.
Option Description
Operating Select the operating system that this Check object is enforced on.
System
Option Description
Check Select one of these options to enable the registry check or clear to
registry key disable it:
and value Registry key and value exist - Find the registry key and value.
If the registry key exists, the endpoint computer is compliant for the
required file.
Registry key and value do not exist - Make sure the registry key and
value do not exist.
If the key does not exist, the endpoint computer is compliant for an
application that is prohibited.
File name Enter the name of the file or executable to look for. To see if this file is
running or not, you must enter the full name of the executable,
including the extension (either .exe or .bat).
Option Description
Match the Make sure that a specific version or range of versions of the file or
file version application complies with the file check.
Match MD5 Find the file by the MD5 Checksum. Click Calculate to compare the
checksum checksum on the endpoint with the checksum on the server.
File is not Select this option and enter the maximum age, in days, of the target
older than file. If the age is greater than the maximum age, the computer is
considered to be compliant. This parameter can help detect recently
installed, malicious files that are disguised as legitimate files.
Check Enable Check domain in order to specify the domain. Select a domain:
Domain
oAny Domain
o Specific Domain
Domain Enter the domain name if the specific domain is selected. Applies only
Name to macOS.
Option Description
Option Description
succeed
o Require all checks to succeed
Each Compliance Action Rule contains one or more Remediation objects. A Remediation
object runs a specified application or script to make the endpoint computer compliant. It can
also send alert messages to users.
After a Remediation object is created, you can use the same object in many Action rules.
Option Description
Operations
Run Custom File Run the specified program or script when an endpoint computer
is not compliant.
URL n Enter the URL of an HTTP or file share server where the file
is located.
n Enter the full path that includes the actual file with one of the
supported extensions (*.bat or *.exe).
n This field can be left empty.
n Make sure the file share is not protected by a username or
password.
Option Description
Run as System Apply system rights for running the executable file. Not all
processes can run with user rights. System rights may be
required to repair registry problems and uninstall certain
programs.
Run as User Apply user rights and local environment variables for running the
executable file.
Messages
Execute Run the executable file only after a user message opens and the
operation only user approves the Remediation action. This occurs when Warn
after user or Restrict is the selected action on a compliance check.
notification
Use same Select that the same text be used for both messages.
message for A Non-Compliant message tells the user that the computer is not
both Non- complaint and shows details of how to become compliant.
Compliant and A Restricted message tells the user that the computer is not
Restricted compliant, shows details of how to achieve compliance, and
messages restricts computer use until compliance is achieved.
The Service Packs Compliance check makes sure that computers have the most recent
operating system service packs and updates installed. The default settings show in the Latest
Service Packs Installed Action Rules.
For more information, see "Compliance Action Rules" on page 375.
Windows Server Update Services (WSUS) allows administrators to deploy the latest Microsoft
product updates.The WSUS compliance check ensures that Windows update are installed on
the Endpoint Security client computer. You can restrict network access of the client computer if
Windows updates have not been installed within a specified number of days. Alternatively, you
can warn the user by means of a pop-up message without restricting access, or log the non-
compliance event without restricting or informing the user
Restrict if Windows Server Updates are Restrict the network access of the user.
not installed
Observe Windows Server Update Create a log, and show a warning message
Services to the user.
Monitor Windows Server Update Services Create a log. The user is not notified.
Do not check Windows Server Update No compliance check. This is the default.
Services
1. Optional: The compliance check makes sure that the Windows updates have been
installed within a specified number of days (default is 90 days).
With Harmony Endpoint, you can perform custom scans on endpoints for Common
Vulnerabilities and Exposures (CVE) in applications.
Notes:
n Supported only for Windows and macOS-based endpoints.
n Supported with the Endpoint Security client version E87.10 and
higher.
Harmony Endpoint periodically scans endpoints against the list of applications specified on the
signature server and detects vulnerable CVEs in applications.
n To allow users to postpone patch updates, specify Max user delay in patch
update and Force patch update after in hours or days.
8. To enforce the patch updates, select the Enable patch updates checkbox:
Note - To apply patch manually, see "Applying the Patch for CVEs" on page 196.
n To allow users to postpone patch updates, select the Enable patch updates &
reboot enforcement checkbox and specify Max user delay in patch update and
Force patch update after in hours or days.
n To enable automatic patch updates, click Advanced Settings and select the
Enable automated patch management checkbox:
a. To specify the interval for patch updates, from the Set automated patch on
list, select Interval, Weekly or Monthly and specify the interval.
b. In the Applications section, specify the application to which you want to apply
the patch and select:
l All applications
l Select specific applications. Search and select one or more
applications.
c. In the Severities section, specify the severities to which you want to apply the
patch and select:
l All Severities
l Select specific severity. Search and select one or more severities.
The Anti-Virus check makes sure that computers have an anti-malware program installed and
updated. The default settings show in the Anti-Virus Compliance Action Rules.
For more information, see "Compliance Action Rules" on page 375.
The About to be restricted state sends users one last warning and gives an opportunity to
immediately correct compliance issues before an endpoint computer is restricted.
The formula for converting the specified time period to minutes is:
<number of heartbeats > * <heartbeat interval (in seconds)> * 60.
User Interface
Default Client User Interface
You can select the default Harmony Endpoint Security Client interface settings or edit them to
customize the Endpoint Security client interface on user computers.
You can change these settings:
n Display client icon - When selected, the client icon shows in the windows notification
area when the Endpoint Security client is installed.
n New client User Interface - Select an interface for the client.
l Default - Applies the default interface specified in the client. Default is the new UI.
l On - Applies the new interface.
l Off - Applies the legacy interface.
n Client language - Select the default language for client. OS Locale indicates the default
OS language.
Note - If the default language is not supported by the client, then system uses
the English language for the client.
n Notification level - You can decide which type of messages can be shown to the user,
and which must not be visible. The administrator can select one of three options:
l Critical only - Do not show any messages unless critical (e.g. system boot
warning) or user interface messages (yes/no questions).
l When-affecting user experience (recommended) - Only show messages related
to operation flows affecting user activity, or requiring user interaction (e.g.
"Malware was detected and removed").
l All - Show all messages.
Note: This change applies to the Endpoint Security Client only. Events are still being
logged on the server, and the administrator can still see everything on the management
interface.
Pre-Boot Images
For each of these graphics, you can select to upload a new image or Revert to Default image:
Size of
Item Description
Image
Pre-boot Background Image Image on Pre-boot screen behind the 800 x 600
smaller logon window pixels
Size of
Item Description
Image
Pre-boot Screen Saver Image that shows when the system is 260 x 128
idle pixels
Pre-boot Banner Image The banner image on the smaller logon 447 x 98
window pixels
The blocking pages above are customizable. The following can be changed per each of them:
1. Company logo (replacing the Check Point logo).
2. Blocking page title.
3. Blocking page description.
The user may preview the change before saving the policy by pressing the preview button.
Note - The preview only works in the Chrome or Edge browsers, when the browser
extension is installed.
Log Upload
The components upload logs to the Endpoint Policy Server.
These log upload options are available:
Option Description
Enable Log Upload Select to enable log upload (this is the default).
Clear to disable log upload.
Minimum number of Upload logged events to the server only after the specified
events before attempting number of events occur.
an upload The default is 1.
Maximum age of event Optional: Upload only logged events that are older than the
before upload specified number of days.
The default is 5 days.
Discard event if older than Optional: Do not upload logged events if they are older than
the specified number of days.
The default is 90 days.
Best Practice - For security reasons, we strongly recommend that you change the default
uninstall password.
Note - If local deployment is enabled for a client, the administrator can still choose whether
clients try to download packages from the Endpoint Security Management Server if packages
are not found in local storage. This option is called: Enable Deployment from server when no
MSI was found in local paths.
2. Put the same packages in local storage location on client computers, for example:
C:\TEMP\EPS\32bit\EPS.msi
3. Go to the Policy view > Client Settings > Installation > Deployment from Local Paths
and URLs
4. Select Allow to install software deployment packages from local folders and URLs.
5. Optional: Select Enable Deployment from Server when no MSI was found in local
paths. When selected, if no MSI file is in the local paths or URLs, the client checks the
Endpoint Security Management Server for packages.
6. Click Deployment Paths and add the package or patch location.
7. Click OK.
8. Go to Deployment Policy > Software Deployment, and create or edit a deployment rule
which includes the package version.
9. Click Save
10. Install Policy to deploy the rule to the clients.
Note - If the version of the Endpoint Security client in the Deployment rule and in the local
file path is not the same, the client is not deployed. If the version on the server and in the local
file path are not the same, an error shows.
General
Authenticated Proxy
2. Enter:
n Proxy - Proxy server address in the format address:host. For example,
192.168.79.157:3128
n Username - User name for the proxy server.
n Password - Password for the proxy server.
3. Click Save.
ThreatCloud helps to keep Check Point protection up-to-date with real-time information.
Note - Check Point does not share any private information with third parties.
Connection Awareness
Connection Awareness - Connection awareness controls how an endpoint enforces its
Connected or Disconnected policy. By default, the client checks connectivity to the Endpoint
Management Server to determine its connectivity state. Alternatively, the administrator can
configure the client's connection status by checking its connectivity to a different network
component, for example, a web server or a router, through ICMP packets or
HTTP/HTTPS/IPv4 requests. If the client can connect to the network component, then its
connection status is Connected. Otherwise, its connection status is Disconnected.
Notes:
n The client triggers HTTP GET requests to the server for connected or disconnected
status in intervals of 30 seconds.
n Connection Awareness is supported with Endpoint Security Client version E85.30
and higher for windows and E87.30 and higher for macOS.
n Some capabilities, such as Full Disk Encryption (FDE) remain active even if the
client's status is disconnected. However, it cannot perform operations that require
connection to the server, such as acquire users from the server or send recovery data
to the server.
Super-Node
What is a Super Node?
A Super Node is a machine running a specially configured Endpoint Security Client that also
consists of server-like and proxy-like capabilities, and which listens on port 4434 by default.
Super Node is a light-weight proxy (based on NGNIX) that allows admins to reduce their
bandwidth consumption and enable offline updates, where only the Super Node needs
connectivity to the update servers.
Note - Super Node is not suitable for offline environments. Endpoint Security clients
must be online and connected to the Harmony Endpoint Management server.
Primary Advantages:
n Reduces site bandwidth usage.
n Reduces server workload.
n Reduces customer expense on server equipment, as there is no need for a local
appliance.
n Improved scale.
Note - You can also use the search bar to search for a device or devices that you want
to define as Super Nodes.
Widgets are created for each entities selected as super nodes.
4. When required devices are added, click Save, as promoting a machine to a Super Node
does not require policy installation. To revert all changes, click Discard.
5. Go to Client Settingsand select the required rule. In the CAPABILITIES &
EXCLUSIONS pane, click General and scroll-down to Super Nodes section.
6. Click + and add Super Nodes with all its specific devices to the relevant Client Settings
rule.
7. Click Save and install the rule.
Note - Super Node settings are rule dependent. It means that Super Nodes defined in the
General tab will be applied only to devices which are related to a specific rule.
Supported Features
Starting in version E86.10, Super Node supports Anti-Malware, Behavioral-Guard & Static
Analysis signature updates. Additionally, software upgrades for Dynamic (EXE) and Windows
installer (MSI) packages, client policies and policy changes are all relayed through Super
Node.
Limitations
n Proxy configuration is not supported.
n By default, the cache max size is 4 GB and will automatically purge files after 7 days of
inactivity. Files stored for a longer time without access are removed from cache.
n Super Node requires an addition of approximately 350 MB to operate properly.
Disable Capabilities
Disable Capabilities allows users to turn on or turn off capabilities, such as Threat Prevention,
Compliance, and so on in the Endpoint Security client.
2. Select the capabilities that can be disabled by the user on the client.
3. To enable the disabled capabilities automatically after a set interval of time:
Note - This is supported only on Windows with Endpoint Security client version
E88.30 and higher.
4. To allow users to disable the capabilities only after entering a password, select the
Protect by password checkbox.
Note - This is supported only on Windows with Endpoint Security client version
E88.30 and higher.
Note - Optionally, from the taskbar, click Manage and select the Manage
Disable Capabilities Protect Password from the list.
b. In the Password field, enter a password and re-enter the password in the Confirm
Password field.
Note - Make sure the password is at least eight characters long, without
spaces, and includes:
n An uppercase letter
n A lower case letter
n A number.
c. Click OK.
5. Click Save & Install.
Network Protection
You can let users disable network protection on their computers.
Network Protection includes these components:
n Firewall
n Application Control
Push Operations
Push Operations are operations that the server pushes directly to client computers with no
policy installation required. You can set the minimum time interval between status updates of
Push Operations.
For more information, see "Performing Push Operations" on page 491.
To set the minimum time interval between status updates of Push Operations:
1. Go to the Policy > Client Settings > General > Push Operation.
2. Set the Minimum interval between status updates of Push Operations.
3. Click Save.
Backward Compatibility
You can manage Endpoint components both through Harmony Endpoint and SmartEndpoint
management console (see "Managing Endpoint Components in SmartEndpoint Management
Console" on page 145). Harmony Endpoint does not support all of the SmartEndpoint
functionalities. Therefore, when you manage Endpoint components both through Harmony
Endpoint and SmartEndpoint, conflicts can arise. When you do an action in SmartEndpoint
that is not supported by Harmony Endpoint, the policy display view in Harmony Endpoint
changes to the policy display view in SmartEndpoint (backward compatible mode).
For example, this is an example of backward compatibility display for the Threat Prevention
policy:
The display view changes back from the backward compatible mode to the regular Harmony
Endpoint view only when the policy enables it.
Policy Operation
The new policy operation mode allows greater flexibility to the user by proving him with a
choice of capability rule applicability. While under the old policy calculation the rule type of
each capability determined whether the capability can work on user or computer, under the
new policy the user has the ability to define for himself which method he wants the capability to
work in (except in cases where it only makes sense for the capability to apply to users or
computers, but not both).
In this new operation mode, most capabilities are "mixed", which means they can function per
users or computers, according to the user’s choice. In each capability, the rules are ordered
both by their assigned environment, from the specific down to the general, as well as by
user/computer applicability: the first rule applies to the users, and if no match is found, the
following rules apply to computers/devices as well.
To view the Policy Operations Mode page, click Endpoint Settings > Policy Operations
Mode.
Old Policy Calculation Mode
IOC Management
IoC stands for Indicators of Compromise. These indicators arrive from various sources, such
as Internet, personal research and so on. Such indicators are not identified by default and you
can block them manually.
For example, if a user receives an indication that a particular URL is malicious, the user can
contact their System Administrator to block access to this URL. The System Administrator tags
this URL as an Indication of Compromise IoC and the policy is enforced on all the endpoints
through the Harmony Endpoint client or the browser extension.
Notes:
n This is supported with the Endpoint Security Client version E86.20 and higher.
n The browser extension that can enforce the IoC policy is supported with the
Endpoint Security Client version E86.50 and higher for Windows and E86.80
and higher for macOS.
n Files with digital signature by trusted signer is not blocked using IoC.
To configure an IoC:
1. In Infinity Portal, go to Policy > Threat Prevention.
2. In the toolbar, select Manage IoC. No need to install policy.
3. In the table that appears, manually add new Indicators of Compromise by type:
Domain checkpoint.com
IP Address 192.168.1.1
URL checkpoint.com/test.htm
4. Hover over the icon next to Type to view the capabilities required for each type:
n URL, Domain and IP require Anti-Bot and URL Filtering capabilities.
n SHA1 and MD5 Hashes require Threat Extraction and Threat Emulation
capabilities.
5. The user can also upload his own manually-created CSV list of indicators.
6. To verify, on the endpoint, access the IoC (for example, a URL). The system blocks the
access to the IoC.
DLP Logs
n Logs are sent for Block, Prevent, and Detect actions.
n File upload and File download events generate log for each handled file, regardless of
whether the event is blocked, prevented, detected, or allowed.
n Text control and Paste events send logs for blocked, prevented, or detected incidents.
Use Case
You are a financial organization aiming to prevent the upload or download of files containing
confidential and sensitive data, such as bank account numbers, tax and revenue details, by
unauthorized users.
Known Limitations
n This feature is supported in EU and US regions only.
n DLP is not applied if the file size is greater than 10 MB.
n DLP is not applied when you drag and drop a folder to upload files, and in such cases,
the upload of the folder gets blocked.
n If the downloaded file is scanned by DLP, it is not sent to Threat Emulation.
Legends Description
2 Date and time (in MM/DD/YY, HH:MM:SS XM format) when the data type
was last modified.
4 Custom tags (category) for the data type. Helps in searching for data types.
Legends Description
5 Matching criteria:
n Pattern
n Keyword
n Dictionary
n Weighted Words
n Template
n File attribute
n Compound (Combination of data types with a logical separator)
n Group (Data type group)
6 The minimum number of times the matching criteria must be present in the
file to trigger the DLP action specified in the policy capability rule. For
example, if the matching criteria is Keyword, the value is credit and the
Matching Threshold is 5, then the system takes the action specified by the
policy capability rule if the file contains the term credit five times or more.
12 Comment.
3. Enter the data type name, object comment (optional) and description.
4. From the Data type recognition method list, select a recognition method:
Note - The
recommended file
formats are Microsoft
Word and .txt.
Threshold=15. Maximum
allowed for
If the file contains six weight for the
occurrences of credit, each keyword.
contributing a Weight of 1. c. If the keyword is a
That is, 1x6=6. As the Max. regular expression,
Weight=3, the final weight is turn on the Regex
3. toggle button.
d. Click Add.
If the file contains eight e. Repeat steps a
occurrences of transaction, through d to add the
each contributing a Weight of next keyword.
2. That is, 2x8=16. As the
Max. Weight=30, the final
weight is 16.
File attribute Applies the action specified Select any of these and
in the policy capability rule if enter a value:
the file: n File name. For
n Matches the specified example, Account
file name. Numbers, Employee
n Size is equal to or Details.
greater than the n File size. File size in
5. Click Next.
Note - This step does not apply to Template and File attribute recognition
methods.
Note - This step does not apply to Template and File attribute recognition
methods.
7. Click Finish.
The new custom data type is listed under Custom Data Types.
8. To permanently save all the changes to the database, click Save at the top.
The change detected window appears.
9. Click Confirm.
10. To discard all the changes, click Discard at the top.
The change detected window appears.
4. To add predefined data types to the group, click in the Predefined Data types field
and select the data type.
5. To add custom data types to the group, click in the Custom Data types field and
select the data type.
6. Click Save.
The new data type group is listed under My Groups.
7. To permanently save all the changes to the database, click Save at the top.
The change detected window appears.
8. Click Confirm.
9. To discard all the changes, click Discard at the top.
The change detected window appears.
2. In the Data Type Name list, expand Custom Data Types or Predefined Data Types and
select the data type.
6. To permanently save all the changes to the database, click Save at the top.
The change detected window appears.
7. Click Confirm.
8. To discard all the changes, click Discard at the top.
The change detected window appears.
9. Click Confirm.
2. In the Data Type Name list, expand the DLP group and select the data type or the group.
3. Click Edit.
Note - In the Check Point Recommended and Predefined Data Types DLP
groups, you can edit only Matching level and Add object comment.
5. Click OK.
6. To permanently save all the changes to the database, click Save at the top.
The change detected window appears.
7. Click Confirm.
8. To discard all the changes, click Discard at the top.
The change detected window appears.
9. Click Confirm.
2. In the Data Type Name list, expand the DLP group and select the data type or the group
within.
3. Click Duplicate.
4. Make the required changes.
5. Click OK.
6. To permanently save all the changes to the database, click Save at the top.
The change detected window appears.
7. Click Confirm.
8. To discard all the changes, click Discard at the top.
The change detected window appears.
9. Click Confirm.
2. In the Data Type Name list, expand the DLP group and select the data type or the group
within.
3. Click Delete.
The Deleting a data type window appears.
5. To permanently save all the changes to the database, click Save at the top.
The change detected window appears.
6. Click Confirm.
7. To discard all the changes, click Discard at the top.
8. Click Confirm.
a. Select a rule.
b. Click Clone and click Clone Above or Clone Below.
Note - If you have selected the default rule, select Clone Above.
Note - Enforcement of DLP for Paste and Text Control events is only
supported for Generative AI sites.
n Inbound events - Inbound data refers to downloading data and sharing content
within internal corporate resources.
4. Click Add.
The Data Protection - New Event window appears.
5. By default, the event is enabled. To disable, turn off the Status toggle button.
6. From the Event type list, select one of these:
n File upload - To apply the DLP rule when you upload a file to an external resource.
n Text control - To apply the DLP rule when you type text in an external resource text
box. For example, in ChatGPT.
n Paste - To apply the DLP rule when you paste content into an external resource.
For example, ChapGPT.
n File download - To apply the DLP rule when you download a file from an internal
resource.
Note - Enforcement of DLP for Paste and Text Control events is only supported
for Generative AI sites.
7. From the Destination type list, select one of these type to which you want to apply the
rule:
Destination
Enter these
type
All N/A
Url In the URL field, enter the web addresses to which you want to apply
the rule.
Domain In the Domain field, enter the domain to which you want to apply the
rule.
Category From the Categories & sub categories list, select one or more
categories.
Notes:
n In Inbound events, you can only choose a URL or Domain.
n In Inbound events, if a source is added for DLP scanning, files
9. To associate data types with an event, in the Data types section, click and select the
data type or a group.
11. To delete an event, select the event that you want to delete and click Delete.
12. To edit an event, select the event that you want to edit, click Edit, make the required
changes and click OK.
13. To disable all events, turn off the Disable all toggle button.
Note - The Paste and Text control events, only have access to the Category level.
Scenarios
Specific Event
Result
Specific Event
Result
Specific Event
Result
Specific Event
Result
Specific Event
Result
Specific Event
Since there are no specific events for the URL, Domain, or Category, the event with the
destination All is selected.
Result
When multiple events are relevant for the same incident, the events with the strict action is
selected.
Specific Event
Result
Specific Event
Since there are no events for the URL, only two events for the Domain domain1.com are
relevant.
Result
Limitations
n We recommend that you avoid modifying policies when you perform this procedure.
n If an export or import fails, you must export or import the file again.
n The import file must be in JSON format.
n If you cancel an import in progress, then the system stops the import but does not revert
the files that were imported prior to canceling the import..
Prerequisites
n You must be an Administrator or a Power user to perform this procedure. The Help-desk
and Read-only users have read-only access to the Export / Import your policy page. All
the other users have no access view the Export / Import your policy page.
n If you are importing policies, ensure that the package or blade version on the target
server and in the import file are the same. Otherwise, the system sets the rules as Do
Not Install.
Exporting Policies
2. Click .
The system initiates the export. When the export is complete, the system downloads the
export file to the default downloads folder. The default name of the export file is export_all_
DD_MM_YYYY_HH_MM.json.
Importing Policies
Note - You can edit the file (for example, Notepad++) to import only policies or rules
you want..
The system initiates the import and shows the status of the import. When the import is
complete, the system shows the 100% Imported successfully message.
Note - You can edit the file to import partial policies or rules.You can edit the file (for
example, Notepad++) to import only policies or rules you want.
Does it work
Capability Comments
offline?
Does it work
Capability Comments
offline?
Threat Emulation and Yes, with the use Communication with the Threat
Anti-Exploit of a local Emulation cloud service is blocked.
appliance.
Client computers send recovery files to the Endpoint Security Management Server so that
you can create recovery media if necessary.
After the recovery, the files are restored as decrypted, like they were before the Full Disk
Encryption installation, and the operating system can run without the Pre-boot.
Full recovery with recovery media decrypts the failed disk and recovers the data. This takes
more time than Full Disk Encryption Drive Slaving Utility and Dynamic Mount Utility that let
you access data quickly.
Recovery Media:
n Is a snapshot of a subset of the Full Disk Encryption database on the client.
n Contains only the data required to do the recovery.
n Updates if more volumes are encrypted or decrypted.
n Removes only encryption from the disk and boot protection.
n Does not remove Windows components.
n Restores the original boot procedure.
Users must authenticate to the recovery media with a username and password. These are
the options for the credentials to use:
n Using SmartEndpoint - Users that are assigned to the computer and have the Allow
use of recovery media permission can authenticate with their regular username and
password. In SmartEndpoint, go to the OneCheck User Settings rule > Advanced >
Default logon settings.
n When you create the recovery media, you can create a temporary user who can
authenticate to it. A user who has the credentials can authenticate to that recovery
media. Users do not require Allow use of recovery media permission to use the
recovery media. Smart Card users must use this option for recovery.
To perform full recovery with recovery media
Step Description
Note - During the decryption process, the client cannot run other programs.
Use this to access specified files and folders on the failed, encrypted disk that is connected
from a different "host" system.
The Drive Slaving Utility is hardware independent.
Full Disk Encryption Drive Slaving Utility replaces older versions of Full Disk Encryption
drive slaving functionality, and supports R73 and all E80.x versions. You can use the Full
Disk Encryption Drive Slaving Utility instead of disk recovery.
Notes:
n On an E80.x client computer with 2 hard disk drives, the Full Disk Encryption
database can be on a second drive. In this case, you must have a recovery
file to unlock the drive without the database.
n Remote Help is available only for hard disk authentication. It is not available
for recovery file authentication.
Note - To unlock a protected USB connected hard disk drive, you must first
start the Drive Slaving Utility, and then connect the disk drive.
After successful authentication, use Windows Explorer to access the disk drive. If you fail to
access the locked disk drive, use the Full Disk Encryption recovery file, then run the Drive
Slaving Utility again.
Note - To prevent data corruption, shut down the system or use a safe removal
utility before you disconnect the USB connected drive.
BitLocker Recovery
BitLocker recovery is the process by which you can restore access to a BitLocker-protected
drive in the event that you cannot unlock the drive normally.
You can use the Recovery Key ID for a computer to find the Recovery Key for an encrypted
client computer.
With the Recovery Key, the user can unlock encrypted drives and perform recoveries.
Important - Treat the Recovery Key like a password. Only share it using trusted and
confirmed channels.
C9F38106-9E7C-46AE-8E88-E53948F11776
After you type a few characters, the Recovery Key ID fills automatically.
4. Click Get Recovery Key.
The recovery key appears. It is a string of numbers that looks like this:
409673-073722-568381-219307-302434-260909-651475-146696
FileVault Recovery
You can help users recover FileVault-encrypted data if they cannot log in to their macOS.
You can help users recover their data or reset their password using a personal recovery key
that is unique to the client computer. You can reset the password remotely.
Password Reset using a Personal Key
If a user forgets the login password, the administrator can send a personal recovery key to
the remote user, to allow them to log in.
The key is a string of letters and numbers separated by dashes.
1. The user locates the serial number of the locked device.
Step Description
1 Find the serial number of the locked device. It is usually printed on the
back of the device.
Step Description
1 Get the serial number of the locked device from the user.
3 From the top toolbar, click and select Remote Help & Recovery >
Recovery > FileVault Recovery.
Step Description
Step Description
A personal key is unique to the client macOS-based computer or device. The key is a string of
letters and numbers separated by dashes.
To recover a user's FileVault-encrypted macOS using the personal key, the administrator
reads the key to the user, and uses the key to decrypt and unlock the computer.
Decrypting and recovering the user's FileVault-encrypted macOS
For example:
For a local user, select the UUID of the user that has:
Type: Local Open Directory User
2. The user interface shows a prompt to allow access. Enter the keychain
password.
The volume is now unlocked.
3. Start the decryption:
diskutil cs list
The user can now reboot the macOS normally. They do not see the FileVault pre-boot
screen.
Notes:
n A user or a device can belong to multiple virtual groups.
n Selecting a certain user or device shows the Active Directory information
or select users or devices first and then create a group from them.
8. Click OK.
Note - You can also perform this procedure from Asset Management >
Organization > Computers. See "Managing Computers" on page 158.
Note - You can also perform this procedure from Asset Management >
Organization > Computers. See "Managing Computers" on page 158.
4. To create and add a specific device or a user to a virtual group, click the group and right-
click the device or user.
5. Select Create and Add to Virtual Group.
The Add Members to Virtual Group window appears.
9. Click OK.
Note - You can also perform this procedure from Asset Management >
Organization > Computers. See "Managing Computers" on page 158.
Notes:
n Harmony Endpoint does not scan groups of the type Distribution in Microsoft
Active Directory.
n If a device belongs to both Microsoft Active Directory and Microsoft Entra ID
domains, then the Microsoft Active Directory takes precedence.
n To move a device from the Microsoft Active Directory domain to Microsoft Entra
ID domain:
a. Disconnect the device from Microsoft Active Directory domain.
b. Register the device with Microsoft Entra ID.
Supported Directory
n Microsoft Active Directory
n Microsoft Entra ID
Prerequisite
Harmony Endpoint requires permissions to scan the directory. Ensure that the directory
account has the following permissions for each directory scanner:
n The Active Directory root
n Child containers and objects
n Deleted objects container - Deleted objects in directory are stored in the Deleted objects
temporarily. Harmony Endpoint compares the objects in the directory with the Deleted
objects container to know the objects that have changed since the last scan.
By default, each Endpoint client sends its path every 120 minutes. In this method, only devices
with Harmony Endpoint installed report their paths, other devices with do not report their
information.
3. From the top toolbar, click (General Actions) and click Directory Scanner.
AD Login n User name (AD) - Enter the user name to access the Active
details Directory.
n Domain name - Enter the domain of the Active Directory.
n Password (AD) - Enter the password to access the Active
Directory.
When you create a new AD scanner, the Organization Directory Scan is automatically
disabled.
Note - You can also reach scanner configuration form through the Endpoint Settings
view > Setup full Active Directory sync.
Note - Harmony Endpoint does not scan groups of the type Distribution in Microsoft
Entra ID.
Limitations
n The Microsoft Entra ID scanner supports Windows only. For macOS devices, use
Microsoft Intune.
n User SmartCard is not supported.
n The user, device or group can be member of only one Administrative unit.
n The maximum characters supported for Display Name is 45.
n Microsoft Entra ID scanner sync stops if the Harmony Endpoint Security server is down
for a duration of 30 days and above. To restart, contact Check Point Support.
n If you have enabled Full Disk Encryption and if the user changes the password, the user
must lock and unlock the device for the new password to take effect.
b. In the window that opens, select Microsoft Graph > Application permissions.
n API Permissions:
o Device.Read.All
o Directory.Read.All
o GroupMember.Read.All
o AdministrativeUnit.Read.All
o User.Read.All
b. In the Add a client secret window, enter a Description and the date it Expires >
click Add.
2. Copy the value of the secret key and keep it in a secure place. This key is necessary for
the Harmony Endpoint portal integration with Microsoft Entra ID.
3. Go to the Overview section, copy these two values, and keep them in a secure place.
n Application (client) ID
n Directory (tenant) ID
Section Description
Sync Period Frequency at which Harmony Endpoint initiates the scan to fetch the
data from Microsoft Entra ID.
Last Sync Date and time when Harmony Endpoint last synced with Microsoft
Entra ID.
Last Full Scan Date and time of the last full scan of the Microsoft Entra ID.
4. Enter these:
a. Directory (Tenant) ID
b. Application Client ID
You can obtain these from your Microsoft Entra ID portal.
c. Secret ID
You can obtain the Secret ID from your Microsoft Entra ID portal.
5. Click Verify.
Note - Make sure that the information you copy from the Microsoft Entra ID
portal are entered accurately. If the verification fails, the following dialog box
appears:
6. Click Next.
7. In the Root Name field, enter a name for the root directory.
8. In the Sync Interval field, specify the interval (in minutes) for the sync between Harmony
Endpoint and Microsoft Entra ID.
9. Click Add.
10. To edit a directory, select the directory and at the top right pane, click .
11. To delete a directory, select the directory and at the top right pane, click .
a. Go to Asset Management.
b. Expand Organization> Organizational Tree > Directories.
The root Microsoft Entra ID should be listed in the table.
7. In the Challenge (from user) field, enter the challenge code that the user gives you.
8. Click Generate Response.
Remote Help authenticates the challenge code and generates a response code.
9. Tell the user to enter the Response Two (to user) text string in the Remote Help window
on the locked computer.
10. Make sure that the user changes the password or has one-time access to the computer
before ending the Remote Help session.
2. The Active Directory server sends the ticket (3) to the client (1).
Endpoint Security Strong Authentication uses the Kerberos network authentication protocol.
To enable the Active Directory server to validate the identity of clients that authenticate
themselves through Kerberos, run the ktpass.exe command on the Active Directory
Server. By running the ktpass command, you create a user that is mapped to the ktpass
service. This creates a Principal Name for the AD server. The Principal Name must have
this format: ServiceName/realm@REALM
Important - After you create the user that is mapped to the ktpass
service, do not make changes to the user. For example, do not change the
password. If you do change the user, the key version increases and you
must update the Version Key in the New Authentication Principal window
in Harmony Endpoint.
cd %WinDir%\System32\
Example:
Parameters:
Sample output:
Targeting domain controller: nac1-dc.nac1.com
Successfully mapped tst/nac1.com to auth-user.
WARNING: pType and account type do not match. This might cause problems.
Key created.
Output keytab to outfile.log:
Keytab version: 0x502
keysize 74 tst/[email protected] ptype 0 (KRB5_NT_UNKNOWN) vno 7 etype 0x17 (RC4-HMAC) keylength 16
(0x32ed87bdb5fdc5e9cba88547376818d4)
servers and the Kerberos server are less than 5 minutes apart.
If the difference in the clock times is more than 5 minutes, a
runtime exception shows and Active Directory authentication
fails. On Gaia, use NTP or a similar service.
n To use Capsule Docs with Single Sign-On, disable the User
Important - Use the Unauthenticated mode only for evaluation purposes. Never
use this mode for production environments. Configure the authentication settings
before moving to production.
Field Description
Version Key Enter the version number according to the Active Directory output
in the vno field.
For example: 7
Field Description
Password Enter (and confirm) the password of the Active Directory Domain
Admin user you created for Endpoint Security use.
For example: 123456
4. Click Add.
5. When you are ready to work in Strong Authentication mode, select Work in
authenticated mode in the Authentication Settings tab.
Important - After you turn on Strong Authentication, wait one minute before you
initiate any client operations.
It takes time for the clients and the Endpoint Security Management Server to
synchronize. During this time, the environment remains unauthenticated, and
some operations fail. The exact amount of time depends on the Active Directory
scanner (see "Managing Active Directory Scanners" on page 457).
After you finished configuring strong authentication for Active Directory, save your changes.
1. In Harmony Endpoint, go to the Policy tab.
2. On the Policy Toolbar, click Save All Changes.
UPN suffixes are part of AD logon names. For example, if the logon name is
[email protected], the part of the name to the right of the ampersand is
known as the UPN suffix. In this case, ad.example.com
When you configure a new user account in AD, you are given the option to select a UPN suffix,
which by default will be the DNS name for your AD domain. It can be useful to have a selection
of UPN suffixes available. If your AD domain name is ad.example.com, it might be more
convenient to assign users a UPN suffix of example.com. To make additional UPN suffixes
available, you need to add them to AD.
Check the service name. Make sure that there are no typing errors and that the format is
correct.
If there was an error, correct it on the Check Point Endpoint Security Management
Server.
Catalog
Description
Item
Favorites Select one of the Logs or View that you marked with the Favorite icon ( )
Recent Select one of the Logs or Views that you opened recently
Logs Select one of the widgets with logs collected from all Harmony Endpoint
clients
Note - Though the interface shows support to export up to one million
logs, you can export a maximum of 10000 entries to a .csv file.
Views Select one of the Views with data from all available blades, services, and
applications
Note - For custom views and reports through SmartView, see the Logging and
Monitoring Administration Guide.
You can open as many tabs as you want providing they show different views.
Use the toolbar on the top to open views, create new views and reports, export them to PDF
and perform relevant actions.
See all collected logs in the Harmony Endpoint Logs view:
Use the time filter (1) and select the relevant options on the Statistics pane (3) to set specific
criteria and customize the search results. Alternatively, you can enter your query in the search
bar. For more details about the Query Language, see "Query Language Overview" on
page 481.
Item Description
1 Time period - Search with predefined custom time periods or define another time
period for the search.
3 Statistics pane - Shows statistics of the events by Blades, Severity of the event
and other parameters.
5 Results pane - Shows log entries for the most recent query.
6 Options - Hide or show a client identity in the Card, and export the log details to
CSV.
Note - You can forward logs to expansion (SIEM). For more information, see Event
Forwarding.
Most query keywords and filter criteria are not case sensitive, but there are some exceptions.
For example, "source:<X>" is case sensitive ("Source:<X>" does not match).
If your query results do not show the expected results, change the case of your query criteria,
or try upper and lower case.
When you use queries with more than one criteria value, an AND is implied automatically, so
there is no need to add it. Enter OR or other boolean operators if needed.
Criteria Values
Criteria values are written as one or more text strings.
You can enter one text string, such as a word, IP address, or URL, without delimiters.
Phrases or text strings that contain more than one word must be surrounded by quotation
marks.
One-word string examples
n John
n inbound
n 192.168.2.1
n some.example.com
n dns_udp
Phrase examples
n "John Doe"
n "Log Out"
n "VPN-1 Embedded Connector"
IP Addresses
IPv4 and IPv6 addresses used in log queries are counted as one word.
Enter IPv4 address with dotted decimal notation and IPv6 addresses with colons.
Example:
n 192.0.2.1
n 2001:db8::f00:d
You can also use the wildcard '*' character and the standard network suffix to search for
logs that match IP addresses within a range.
Examples:
n src:192.168.0.0/16
n src:192.168.1.0/24
n src:192.168.2.*
NOT Values
You can use NOT <field> values with Field Keywords in log queries to find logs for which the
value of the field is not the value in the query.
Syntax:
Example:
NOT src:10.0.4.10
Wildcards
You can use the standard wildcard characters (* and ?) in queries to match variable
characters or strings in log records.
You can use more than the wildcard character.
Wildcard syntax:
n The ? (question mark) matches one character.
n The * (asterisk) matches a character string.
Examples:
n Jo? shows Joe and Jon, but not Joseph.
n Jo* shows Jon, Joseph, and John Paul.
If your criteria value contains more than one word, you can use the wildcard in each word.
For example, 'Jo* N*' shows Joe North, John Natt, Joshua Named, and so on.
Note - Using a single '*' creates a search for a non-empty value string. For example
asset name:*
Field Keywords
You can use predefined field names as keywords in filter criteria.
The query result only shows log records that match the criteria in the specified field.
If you do not use field names, the query result shows records that match the criteria in all fields.
This table shows the predefined field keywords. Some fields also support keyword aliases that
you can type as alternatives to the primary keyword.
Keyword
Keyword Description
Alias
<field name>:<values>
Where:
n <field name> - One of the predefined field names
n <values> - One or more filters
To search for rule number, use the Rule field name.
For example:
rule:7.1
If you use the rule number as a filter, rules in all the Layers with that number are matched.
To search for a rule name, you must not use the Rule field. Use free text.
For example:
Examples:
n source:192.168.2.1
n action:(Reject OR Block)
You can use the OR Boolean operator in parentheses to include multiple criteria values.
Important - When you use fields with multiple values, you must:
n Write the Boolean operator, for example AND.
n Use parentheses.
Boolean Operators
You can use the Boolean operators AND , OR, and NOT to create filters with many different
criteria.
You can put multiple Boolean expressions in parentheses.
If you enter more than one criteria without a Boolean operator, the AND operator is implied.
When you use multiple criteria without parentheses, the OR operator is applied before the
AND operator.
Examples:
Shows log records from the Application and URL Filtering Software Blade where traffic
was blocked.
n 192.168.2.133 10.19.136.101
Shows log entries that match the two IP addresses. The AND operator is presumed.
n 192.168.2.133 OR 10.19.136.101
Shows all log entries from the Firewall, IPS or VPN blades that are not dropped.
The criteria in the parentheses are applied before the AND NOT criterion.
n source:(192.168.2.1 OR 192.168.2.2) AND destination:17.168.8.2
Shows log entries from the two source IP addresses if the destination IP address is
17.168.8.2.
This example also shows how you can use Boolean operators with field criteria.
Exporting Logs
Check Point Log Exporter is an easy and secure method to export Check Point logs over
syslog. Log Exporter is a multi-threaded daemon service which runs on a log server. Each log
that is written on the log server is read by the Log Exporter daemon. It is then transformed into
the applicable format and mapping and sent to the end target.
For more information, see sk122323.
2. Click Add.
The New Logging Service window opens.
3. Fill in the export details:
n Name - Enter a name for the exported information.
n IP Address - Enter the IP Address of the target to which the logs are exported.
n Protocol - Select the protocol over which to export the logs: TCP or UDP.
n Format - Select the export format.
n Port - Select the port over which to export the logs. Only these ports are supported
for outgoing communication: 514, 6514.
n TLS/SSL - Select this checkbox if you want log information to be TLS/SSL
encrypted. The only allowed authentication method through TLS is mutual
authentication. For mutual authentication, the log exporter needs these certificates:
l A *.pem Certificate Authority certificate (must contain only the certificate of
the CA that signed the client/server certificates, not the parent CA).
l A *.p12 format client certificate (log exporter side).
For instructions on how to create the certificates, see "Creating Security
Certificates for TLS Mutual Authentication" below.
4. Click Add.
Notes:
n Make sure to run the openssl commands on a 3rd party CA server
(not on the log exporter device). The log exporter device must have a
connectivity to the CA server.
n The commands are not supported on a Check Point Security
Management Server or a Multi-Domain Server.
Procedure
1. Create a CA certificate
Step Description
Best Practice - We recommend to use the device IP address as the Common Name.
Step Description
Step Description
Step Description
Note - If there is no response from the Endpoint Security client, the Push Operation
will time out after 24 hours. You must reinitiate the Push Operation.
Push
Category Windows macOS Linux
Operations
Push
Category Windows macOS Linux
Operations
Registry Yes No No
Actions
Collect Yes No No
Processes
3. Select the devices on which you want to perform the push operation.
Note - You can perform Run Diagnostics on only one device at a time.
4. Click Next.
2FA
Push Operations Description
Required
Push 2FA
Description
Operations Required
Push 2FA
Description
Operations Required
Push 2FA
Description
Operations Required
Agent Settings
Push 2FA
Operati Description Requi
ons red
Deploy Installs the Initial Client on the target devices remotely using No
New any device as the medium to run the push operation. This is
Endpoi suitable if do not have third party tools such as Microsoft
nts System Center Configuration Manager (SCCM) or Intune to
install the client.
Field Description
Push 2FA
Operati Description Requi
ons red
C:\Windows\SysWOW64\config\systemprofile\CPInfo.
n For macOS, client logs are stored in the directory
/Users/Shared/cplogs.
Field Description
Point servers
n Upload CPInfo reports to Corporate
Push 2FA
Operati Description Requi
ons red
Push 2FA
Operati Description Requi
ons red
Files upload
Push 2FA
Operati Description Requi
ons red
Field Description
Push 2FA
Operati Description Requi
ons red
Push 2FA
Operati Description Requi
ons red
Field Description
Push 2FA
Operati Description Requi
ons red
Copy File
File path Full path of the file or folder you want to copy,
including the file or folder name.
Example:
n For File - C:\Users\<user_
name>\Desktop\test.doc
n For Folder - C:\Users\Username\Desktop\
Push 2FA
Operati Description Requi
ons red
Field Description
name>\Documents
n For Folder - C:\Users\Username2\
Notes:
n The file or folder name you specify is
Move File
File path Full path of the file or folder you want to move,
including the file or folder name.
Example:
n For File - C:\Users\<user_
name>\Desktop\test.doc
n For Folder -
C:\Users\Username>\Desktop\
Push 2FA
Operati Description Requi
ons red
Field Description
name>\Documents
n For Folder -
C:\Users\Username1\Documents\
Notes:
n If you provide the full file path, the is
Delete File
File path Full path of the file you want to delete, including
the file name.
For example, C:\Users\<user_
name>\Desktop\test.doc
Push 2FA
Operati Description Requi
ons red
Security client.
n You cannot create separate VPN sites for each user that
Supported fields:
Field Description
Push 2FA
Operati Description Requi
ons red
Field Description
Push 2FA
Operati Description Requi
ons red
Field Description
Push 2FA
Operati Description Requi
ons red
Field Description
CAPI store)
n p12-certificate
n securityIDKeyFob
n securityIDPinPad
n SoftID (not tested)
n challenge-response (not tested)
Push 2FA
Operati Description Requi
ons red
Push 2FA
Operati Description Requi
ons red
n To notify the user about the push operation, select the Inform user with
notification checkbox.
n To allow the user to post pone the push operation, select the Allow user to
postpone operation checkbox.
7. Under Scheduling:
n To execute the push operation immediately, click Execute operation immediately.
n To schedule the push operation, click Schedule operation for and click to select
the date.
8. Specify the duration after which the system automatically terminates the unexecuted
push operation (For example, if the Endpoint client is offline):
n 7 days
n Custom
n Never
9. For Push Operations that support 2FA authentication, you are prompted to enter the
verification code.
If you have not enabled 2FA authentication, a prompt appears to enable 2FA
authentication:
n To enable 2FA authentication for your profile, click Profile Setting, and follow the
instructions. For more information, see Infinity Portal Administration Guide.
n To enable 2FA authentication for the current tenant, click Global Settings, and
follow the instructions. For more information, see Infinity Portal Administration
Guide.
10. Click Finish.
11. View the results of the operations on each endpoint in the Endpoint List section (in the
Push Operations menu) at the bottom part of the screen.
Certificate Management
Certificate Management allows you to use your certificates to sign the export package. By
default, Check Point certificate is used.
Forensics Data
Harmony Endpoint collects forensics data from endpoints that you can export to a data
analytics tool for analysis and create policies accordingly to prevent attacks. For more
information on forensics, see Automated Attack analysis.
You can perform following actions with the forensics data:
n Exporting to Check Point's Threat Hunting
n "Sending Forensics Data to Third-Party Analytics Tool" on page 522
n "Downloading Forensics Reports" on page 522
Note - Harmony Endpoint exports the forensic data only in the JSON format. Make
sure that the third-party data analytics tool accepts the data in the JSON format.
Threat Hunting
Threat Hunting is an investigative tool which allows for advanced querying on all malicious and
benign forensics events collected from the organization's endpoints with Harmony Endpoint
installed.
n Proactively hunt for advanced attacks by searching for anomalies, and using hunting
leads and enrichment.
Threat Hunting supports:
n Data collection and enrichment - All events are collected through multiple sensors and
sent to a unified repository and enhanced by ThreatCloud, MITRE mapping and alerts
from all the prevention engines.
n Rich toolset for custom queries, drill down and pivoting to suspicious activity.
n Predefined queries and a MITRE dashboard which map all activity and allow a quick start
to proactive hunting.
n Remediation actions per result or a bulk operation integrated in the Threat Hunting flow
(such as file quarantine and kill process).
The data is saved for 7 days, unless you purchased an extended retention license.
Supported Regions
Threat Hunting is supported only for the Infinity Portal tenants (accounts) residing in these
regions:
n Australia
n EU
n India
n United Kingdom
n United Arab Emirates
n US
Supported Versions
n Endpoint Security Client version E84.10 and higher.
n Management version:
l Cloud-only, web management.
l On-premises Management Server - R80.40 and higher.
Item Description
1 Last Day - Time filter for the query. Users can choose between Last Day, Last
2 Days, Last Week and a Custom time period.
3 Let the hunt begin - Click + and define the values to search in the logs. You
can add multiple values and fields at a time.
Item Description
To hunt for threats, you can use predefined queries or by proactively creating your own
queries.
n To use predefined queries:
1. Go to Predefined Hunting Queries or
Click the icon next to the search box and select Predefined.
You can quickly find all active attacks and browse through different malicious
events detected by Endpoint clients.
2. Click the icon next to the search box and select MITRE ATT&CK.
The MITRE ATT&CK dashboard provides real-time visibility on all the techniques
observed by Harmony Endpoint across your endpoints. It maps all raw events to
MITRE Tactics, Techniques, and Procedures (TTPs) regardless of status.
The MITRE ATT&CK dashboard is divided into 12 categories and each category is
a stage in an attack. Each category includes multiple attack techniques.
When you click a technique, a window opens with an explanation about the
technique and a list of predefined queries. Run a query to get a list of the events in
which the specific technique implementation was used.
1. Go to Threat Hunting.
2. Click the + sign next to Let the hunt begin.
3. From the Indicator list, select the filter.
4. From the Operator list, select the condition.
5. In the Add a single value field, enter a value for the indicator.
6. Click Add.
It shows the search results in a timeline. The timeline provides behavioral insights
that indicate anomalies or attacks.
7. To add another filter to the same query, repeat steps 2 to 6.
Note - If you have multiple filters, the system applies the logical AND
operator between the filters.
9. To create a bookmark for a query, see "Saving a Query as a Bookmark" on the next
page.
10. You can also filter the results by date and process.
11. To take remediation action for the filtered results, click Actions and choose any of
these:
l Terminate Process
l Quarantine File
l Trigger Forensic Analysis
l Isolate Machine
12. To export the results to a CSV file, click Actions > Export to CSV.
3. To make the bookmark public, select Shared - available to all system users.
4. To make the bookmark private, select Private - available only to you.
5. In the Name field, enter a query name.
6. From the Importance list, select an importance level for the query detection.
7. In the Select or create tag name field, enter the tag name or select the tag name if
available.
Tags create folders to store bookmarked queries.
8. In the Description field, enter a description for the bookmark.
9. To send email notifications if new activity matches the bookmarked query, select Send
E-mail notifications to mailing list for any new hits checkbox.
Infinity XDR/XPR sends email notifications to the recipients added to the Threat Hunting
Notifications page.
10. Click Save.
1. Go to Threat Hunting.
2. Click the icon next to the search box and select Notifications.
3. From the Recipients list, select the users or enter the email address.
2. From the list of techniques that Maze ransomware uses, select the applicable technique.
For example: Windows Management Instrumentation
3. From the Infinity Portal > Threat Hunting, click the icon on the right side of the search
box, and go to MITRE ATT&CK.
4. In the MITRE ATT&CK dashboard, search for the technique you copied from the Maze
website.
5. Click the technique to see all the events in your organization in which this technique was
used.
Note - Harmony Endpoint does not support to enter user credentials for the
third-party analytics tool for authentication.
3. Click Save.
The system applies the policy to all endpoints.
Endpoints send the forensic data in JSON format to the third-party data analytics tool.
It provides information about attacks and suspicious behavior. The report includes:
n Entry Point - How did the suspicious file enter your system?
n Business Impact - Which files were affected and what was done to them?
n Remediation - Which files were treated and what is their status?
n Suspicious Activity - What unusual behavior occurred that is a result of the attack?
n Incident Details - A complete visual picture of the paths of the attack in your system.
Note - To search the Forensics event using the machine name, enter the
machine name in the search field and click Enter.
3. From the list, double-click the event for which you want to download the report.
The Card window with the log details appears.
4. Scroll-down to Forensics Report section and click Download the Forensics Report.
Note - To view the Forensics Report without downloading, click Open the
Forensics Report.
Two-Factor Authentication
Check Point recommends you to configure two-factor authentication for Harmony Endpoint. To
configure, see Two-Factor Authentication.
Technology Description
Threat Hunting / An Endpoint Linux device deployed with Harmony Linux, constantly
Endpoint updates Check Point Cloud with Indicator of Compromise (IoC) and
Detection and Indicator of Attack (IoA) events.
Response The Threat Hunting technology lets the user proactively search for cyber
(EDR) threats that made it through the first line of defense to the Linux Endpoint
device.
Threat Hunting uses advanced detection capabilities, such as queries
and automation, to find malicious activities and extract hunting leads of
data.
Prerequisites
n Available Internet access for the protected device.
n For RHEL/CentOS, it is necessary to have access to EPEL (Extra Packages for
Enterprise Linux) repository.
n If the device has no internet access, you must enable access to certain URLs. For more
information, see sk116590.
n To enable the Threat Hunting function, make sure that Threat Hunting is enabled in
the applicable policy rule. Navigate to Policy > Threat Prevention > Analysis &
Remediation and ensure Threat Hunting is set to ON.
Notes:
l If Strong/Kerberos authentication is enabled, then HTTP 401 is in the
/var/log/checkpoint/cpla/cpla.log.
l It is necessary to put the keytab file used for authentication set up in the file
/var/lib/checkpoint/cpmgmt/auth.keytab (the file is generated by the ktpass
utility).
To show a list of all the help commands with their descriptions, run:
cpla --help
cpla am --help
To show information about the product and the security modules installed (Anti-Malware,
EDR) run:
cpla info
cpla am info
To show the help for available commands for the installed EDR module, run:
cpla bg --help
cpla bg--help
cpla bg info
Quarantine Commands
To remove a file from quarantine, and restores the file to its original place, run:
To trigger a scan of files in the provided path by the Anti-Malware module, run:
cpla am detections
Note - To limit the number of detections displayed, use the parameter --limit
<number_of_detections>. Default is 100.
cpla bg detections
Note - To limit the number of detections displayed, use the parameter --limit
<number_of_detections>. Default is 100.
Logs
cpla collect-logs
Note - When you use this command, it prepares a Zip file which you can send to the
support manually.
Best Practice - We recommend that you remove any other 3rd party Anti-
Malware solution before you install Harmony Endpointfor Linux.
A virtual machine monitor (the hypervisor) controls the virtual machine that creates the virtual
desktops. All the activity on the deployed virtual desktops occurs on the centralized server.
The "Golden Image" is the base ("Master") desktop image and the model for clone images.
Desktop Pools define the server resources for the virtual desktops and solutions to hold the
latest Anti-Malware signatures on all the virtual desktops.
Virtual desktop software applications support two modes.
n Persistent Mode:
l Each user has a single specific desktop for their solitary use.
l Each user's desktop retains data on the desktop itself between logins and reboots.
l The user's machine is not "refreshed" for other users.
n Non-Persistent Mode:
l Each user has a desktop from a pool of resources. The desktop contains the user's
profile.
l Each user's desktop reverts to its initial state when the user logs out.
l The user's machine is fresh in each instance.
n VMware Horizon 8 version 8.3 (E86.60 for both Persistent Mode and Non-Persistent
Mode)
n Citrix Virtual Apps and Desktops 7 1912
The software environments between and after these versions should work. Earlier versions
may work. Contact Check Point Support for assistance with earlier versions.
2. If you did not disable the Anti-Malware Periodic Scan, then enable the Anti-Malware
Randomized Scan.
Procedure
1. In VMware Horizon, select Automated Desktop Pool in the Type panel of Add
Desktop Pool.
3. In the vCenter Server panel, select Instant Clones or View Composer Linked Clone.
Full Clones are not currently supported.
The Solution:
n One or more Signature Servers responsible to store the latest Anti-Malware signatures in
a shared location.
n Many specially configured clients that load signatures from the shared folder.
n If the shared signatures server is not available, the client uses signatures from the
golden image.
Note - All endpoints connected to the Shared Signature Server must be on the same
domain.
Recommended Steps:
1. Configure a signature server machine.
2. Configure a client machine (golden image).
3. Create a test pool.
4. Deploy the production pool.
6. Assign the new Threat Prevention rule to the new Virtual Group.
7. In the right pane, click the Web & Files Protection tab.
8. Scroll down and click the Advanced Settings button.
9. From the left tree, click Files Protection > Signature.
10. In the Shared Signature Server section, select the “Set as shared signature server”
and enter the local path of the folder.
Example: C:\Signatures
Note - If the folder does not exist, the endpoint creates it automatically.
Setup Validation
Wait 20 minutes to make sure:
n Anti-Malware Signatures version is current.
n Shared Signatures folder exists with Anti-Malware signatures.
Important - If the folder is empty, the setup is not valid.
g. In the right pane, click the Web & Files Protection tab.
h. Scroll down and click the Advanced Settings button.
Important:
n When you apply VDI settings through Policy to Golden Image, you must apply
VDI settings through Policy to cloned Virtual Machines.
1. In VMware Horizon, choose Automated Desktop Pool in the Type panel of Add
Desktop Pool.
Pool Validation
Access a few cloned machines and make sure that:
n Machines connect to the Endpoint Security Management Server.
n Applicable Software Blades run.
n Anti-Malware Signatures are current.
n Machines appear on the Server User Interface.
The Endpoint Security client capabilities for non-persistent virtual desktops are:
n Anti-Malware
l Fully supported when configured with the Shared Signatures Server.
n Compliance, Firewall and Application Control, Remote Access VPN, and URL
Filtering
l Fully supported.
n Forensics
l Partially supported.
o The Forensics database contains data for the current session.
o Forensics Reports generate as usual.
Important - Make sure that you do not disable the Windows Security Center
service.
you upgrade the vDisk through the golden image and not one of the
clones.
l The transfer of a clone back to the golden image is not supported.
Best Practice - Update manually with Update Now from the Endpoint tray
icon at least once a day.
Best Practice - Scan manually with Scan System Now from the Endpoint
tray icon for every signature update.
Assignment to a pre-defined Virtual Group occurs during the Export Package phase.
All clones from this Exported Package enter the computer group upon registration to
the Endpoint Security Management Server.
1. Create a new Virtual Group.
2. Export the applicable packages.
From the left navigation panel, click Policy.
In the Deployment Policy section, click Export Package.
Provision all VDI machines. Once the machines exist, assign them to a policy.
1. Create a new Virtual Group and add all the relevant machines.
2. Create a policy and assign it to the Virtual Group.
Limitations
n VDI Clients must be part of a domain. Workgroup configurations are not supported.
n FDE capability is not supported. Do not enable FDE in packages for Non-Persistent VDI
machines.
n "Anti-Malware Scanning Storms" may occur when the Anti-Virus scan runs at the same
time on multiple Virtual Machines on the same physical server. A serious degradation of
the system performance is possible that can affect disk I/O and CPU utilization.
n The "Repair" push operation does not work for VDI machines.
n The Shared Signature Server does not share signatures with non-persistent desktops if
you clear and select the Set as shared signature server checkbox in the Policy > Web
& Files Protection > Advanced Settings > Files Protection > Signature window. To
resolve this issue, uninstall and redeploy the Endpoint Security client on the Shared
Signature Server.
Appendix
Disabling the Anti-Malware Periodic Scan
"Anti-Malware Scan Storms" can occur when anti-virus scans run at the same time on multiple
virtual machines on the same physical server.
A degradation of system performance is possible that can affect disk I/O and CPU usage.
We recommend that you disable the Anti-Malware periodic scan in one of these ways:
4. Click Save.
5. Install policy.
In SmartEndpoint
1. In the Select action field, select Perform periodic anti-malware can every month.
2. Clear the "Perform Periodic Scan option.
3. Install policy.
1. Connect with the Database Tool (GuiDBEdit Tool) (sk13009) to the Endpoint Security
Management Server.
2. Configure the value false for the attribute enable_schedular_scan.
3. In SmartEndpoint, install policy.
1. In Windows Registry, configure the value 0x0b for the AVSchedOf key:
n On 64-bit operating system:
HKEY_LOCAL_
MACHINE\SOFTWARE\Wow6432Node\CheckPoint\EndPoint
Security\Anti-Malware\AVSchedOf=(DWORD)0x0b
HKEY_LOCAL_MACHINE\SOFTWARE\CheckPoint\EndPoint
Security\Anti-Malware\AVSchedOf=(DWORD)0x0b
Manual Configuration
Note - On Workgroup machines, the "SYSTEM" account does not have network
login rights. This configuration is not supported.
HKEY_LOCAL_
MACHINE\SOFTWARE\WOW6432Node\CheckPoint\Endpoint
Security\Anti-Malware\VdiSignatureServer=(DWORD)0x01
HKEY_LOCAL_MACHINE\SOFTWARE\CheckPoint\Endpoint
Security\Anti-Malware\VdiSignatureServer=(DWORD)0x01
2. Configure the path to the shared signatures folder in the key AVSharedBases:
n On 64-bit operating system:
HKEY_LOCAL_
MACHINE\SOFTWARE\WOW6432Node\CheckPoint\Endpoint
Security\Anti-Malware\AVSharedBases=
(SZ)"DISK:\\Path\\To\\Shared\\Folder"
HKEY_LOCAL_MACHINE\SOFTWARE\CheckPoint\Endpoint
Security\Anti-Malware\AVSharedBases=
(SZ)"DISK:\\Path\\To\\Shared\\Folder"
Notes:
n If you do not configure the path, then the default shared
folder is:
C:\ProgramData\CheckPoint\Endpoint
Security\Anti-Malware\bases\shared
n The default shared folder exists after the first successful
update.
Manual Configuration
HKEY_LOCAL_
MACHINE\SOFTWARE\WOW6432Node\CheckPoint\Endpoint
Security\Anti-Malware\AVBasesScheme=(DWORD)0x01
HKEY_LOCAL_MACHINE\SOFTWARE\CheckPoint\Endpoint
Security\Anti-Malware\AVBasesScheme=(DWORD)0x01
3. In Windows Registry, configure the path to the shared signatures folder in the key
AVSharedBases:
n On 64-bit operating system:
HKEY_LOCAL_
MACHINE\SOFTWARE\WOW6432Node\CheckPoint\Endpoint
Security\Anti-Malware\AVSharedBases=
(SZ)"\\Server\FolderWithSharedSignatures"
HKEY_LOCAL_MACHINE\SOFTWARE\CheckPoint\Endpoint
Security\Anti-Malware\AVSharedBases=
(SZ)"\\Server\FolderWithSharedSignatures"
Notes:
n If you do not configure the path, then the default shared folder is:
C:\ProgramData\CheckPoint\EndpointSecurity\Anti-
Malware\bases\shared
n The default shared folder exists after the first successful update.
Licensing
Licensing is per user. Each user is counted as a seat (using existing SKUs).
Limitations
n User-based policy is not supported. By default, computers will receive the entire
organization policy unless you create a computer-based rule.
n By default, the Endpoint Security client icon is turned off in the notification area (system
tray) for all the users logged on to the server. This is to prevent client notifications
triggered by a specific user action sent to all users. User checks (For example, Malware
detections, upgrade process and push operations) are not displayed. To turn on the
Endpoint Security client icon in the notification area for a specific user, see step 3 in the
procedure below.
n The Logs menu does not show user details. The Terminal Server shows all logged on
users as ntlocal.
n Compliance Remediation Run as User is not supported. For more information, see
"Compliance" on page 370.
n For the Anti-Malware capability:
l Terminal Server exclusions does not support User Environment Variables.
l Scanning and quarantine are supported only for a directory that can be accessed
by the System Account.
l Reporting - When infections are found, the Network Drive appears as "unknown"
when a network drive cannot be accessed by System Account.
n Configure proxy settings for the Windows Server machine in the System Account.
n The Full Disk Encryption blade is not supported.
n The Media Encryption blade is not be supported.
n Windows Subsystem for Linux (WSL) is not be supported.
n Internet Explorer extension is not supported.
Procedure
1. Install the Endpoint Security client package version E86.20 or higher to the Terminal
Server. For more information, see "Deploying Endpoint Clients" on page 66.
2. Enable the Terminal Server mode on the Endpoint Security client through one of these
methods:
n Use the export package or Tiny Agent/ Initial Client:
a. Open the Command Prompt window in Administrator mode and run:
msiexec /i eps.msi TS=1 OR EndpointSetup.exe TS=1.
3. Optional - By default,the Endpoint Security client is turned off in the notification area
(system tray) for all the users logged on to the server. This is to prevent sending
notifications for a specific user action. To turn on the Endpoint Security client icon in the
notification area for a specific user:
a. Remove Self-Protection: Run the passdialog.exe file.
b. When prompted, enter the uninstall password.
c. Navigate to C:\Program Files (x86)\CheckPoint\Endpoint
Security\UIFramework\Bin\WUI and run the cptrayUI.exe file.
Important - MSSP View is only available for customers who are part of the Early
Availability program.
Service Management
On the Service Management page, you can view and manage the service of the MSSP and
their child accounts.
To view the Service Management page, click Overview > MSSP View > Service
Management.
Accounts Info
Click Deployment to view the deployed accounts in the "Account Details Table" on the
next page.
n Number of accounts under evaluation (accounts with evaluation license).
Click Evaluation to view the accounts under evaluation in the "Account Details Table" on
the next page.
n Number of active endpoints. It also shows the change in the number of active endpoints
by percentage in the last 24 hours.
Service Status
The Service Status widget shows the service status of the accounts:
n Running
n Initializing
n Stopped
n Error
n N/A
To sort the accounts by status, click Status. For more details, see "Account Details Table" on
the next page.
Hosting Sites
The Hosting Sites widget shows the number of accounts residing in different data regions.
Item Description
Item Description
MSSP Essentials
The MSSP Essentials page shows the essential details about the MSSP and child accounts.
To view the MSSP Essentials page, click Overview > MSSP View > MSSP Essentials.
To view the details specific to a child account, on the right pane, click , select the account
and click OK.
The MSSP total endpoints widget shows the total number of accounts, including MSSP
accounts, child accounts and active / inactive endpoints.
Click View Accounts to view the MSSP and child account information. For more information,
see "Accounts Info" on page 580.
The Account with issues widget shows the total number of Operational issues and Outdated
capabilities across accounts that have at least one device.
Hover over the widget, click View Accounts to view the details of the account, and their issues.
For more information, see "Issues by Accounts" on page 580.
Service Status
The Service Status widget shows the number of accounts categorized by their Harmony
Endpoint Security client service status.
To view the account by status, click the status. For more information, see "Service Status" on
page 581.
Contracts by Type
The Contracts by type widget shows the number of contracts categorized by their type.
Click the widget to view the number of contracts for each account.
Contracts by Status
The Contracts by status widget shows the number of contracts categorized by their status.
Click the widget to see the validity status of the contracts.
The Active endpoints trend widget shows the line graph of active Harmony Endpoint Security
clients for each account (up to five) over time.
The Top 5 attacked accounts widget shows the top five attacked accounts categorized by
their status.
The statuses are:
n Active - A malicious process attacked and infected the device. Termination and
quarantine of the process or other elements of the attack is failed or disabled in the
policy.
n Blocked - A malicious process does not attack the device as all the infected files are
blocked immediately and quarantined.
n Cleaned - A malicious process attacked and infected the device. The device is cleaned
as the infected files are terminated and quarantined.
n Dormant - A malicious process does not attack, but the device is infected as the
quarantine of one of the infected file fails.
The Top 5 ransomware attacked accounts widget shows the top five accounts targeted by
ransomware attacks.
The statuses are:
n Active - A malicious process attacked and infected the device. Termination and
quarantine of the process or other elements of the attack is failed or disabled in the
policy.
n Cleaned - A malicious process attacked and infected the device. The device is cleaned
as the infected files are terminated and quarantined.
The Top 5 phishing attacked accounts widget shows the top five accounts targeted by
phishing attacks.
The Top 5 accounts with exploit attack attempts widget shows the top five accounts that
have been subject to exploit attack attempts.
Alerts
The Alerts widget shows the active alerts on all the endpoints in the account.
MSSP Dashboard
The MSSP dashboard allows you to create personalized dashboards for the MSSP and child
accounts.
n The Blank dashboard allows you to create a new dashboard with the available widgets.
n The MSSP Essentials template dashboard allows you to customize the "MSSP
Essentials" on page 566 dashboard.
c. From the left pane, select the widget and click Add.
Note - The Add button is disabled if the widget is already added to the
dashboard.
The dashboard appears under Custom Dashboard on the left navigation pane,
and it is also listed under My dashboards in the MSSP Dashboard page.
7. By default, all custom dashboards you create in MSSP Account are set as Private. To
make the custom dashboard available to all users with access to the MSSP Account
page, from the Private list on the upper-right corner, click Public. The system adds the
dashboard under Public dashboards for other users.
Account Dashboard
The Account dashboard allows you to create personalized dashboards for the MSSP account.
n Blank dashboard allows you to create a new dashboard with available widgets.
n Unified template allows you to customize the Unified Dashboard. For more information,
see Unified Dashboard in "Viewing Operational Overview, Security Overview and
Reports" on page 123.
Note - The Add button is disabled if the widget is already added to the
dashboard.
6. Click Save.
7. To share the Account dashboard with other child accounts, on the right pane, click
Share With Accounts, select the account and click Share
2. To edit a dashboard:
a. Expand Custom Dashboard.
b. Click for the dashboard you want to edit and click Edit.
3. To delete a dashboard, expand Custom Dashboard, click for the dashboard you want
to delete and click Delete.
4. To hide a dashboard, expand Custom Dashboard, click for the dashboard you want to
hide and click Hide. The dashboard is removed from the list under Custom Dashboard
on the left navigation pane.
5. To unhide a dashboard, click , hover over the dashboard you want to unhide and click
Add. The dashboard is added to the list under Custom Dashboard on the left navigation
pane.
6. To duplicate a dashboard, click , hover over the dashboard and click Duplicate.
Optional Widgets
You can customize the Custom dashboard by adding these widgets:
The Password reuse attacks by events widget shows the number of password reuse attacks
by their status.
Use the drop down to view the attacks by events, accounts or devices.
Phishing Attacks
The Phishing attacks by events widget shows the number of phishing attacks by their status.
Use the drop down to view the attacks by events, accounts or devices.
Ransomware Attacks
The Ransomware attacks by events widget shows the number of ransomware attacks by
their status.
Use the drop down to view the attacks by events, accounts or devices.
Exploit Attacks
The Exploit attack attempts by events shows the number of exploit attack attempts by their
status.
Use the drop down to view the attacks by events, accounts or devices.
The Malicious site attacks by events widget shows the number of malicious site attacks by
their status.
Use the drop down to view the attacks by events, accounts or devices.
Service Management
You can use the Service Management page to view the overall status of your accounts.
To view the Service Management page, click Overview > MSSP View > Services > Service
Management.
Accounts Info
Issues by Accounts
Item Description
On Over 72h Number of accounts whose last Anti-Malware signature update was more
Ago than 72 hours ago.
Not Running Number of blades that are not running on the Endpoint Security client.
Blades
Service Status
The Service Status widget shows the service status of the accounts:
n Running
n Initializing
n Stopped
n Error
n N/A
To sort the accounts by status, click Status. For more details, see "Account Details Table" on
page 565.
Hosting Sites
The Hosting Sites widget shows the number of accounts residing in different data regions.
Item Description
Item Description
Contracts
You can use the Contracts page to view the contract details of the MSSP and the child
accounts.
To view the Contracts page, click Overview > MSSP View > Contracts.
Accounts Info
The Accounts Contract Distribution widget shows the number of contracts of each type.
Contracts by Accounts
The Contracts by Accounts widget shows the accounts that expired or expire soon.
Click the links to see the related accounts in the "Contract Details Table" below.
Item Description
Max Endpoint Maximum number of endpoints allocated to the account in the contract.
Note - Available only to customer subscribed to this feature and with server
version R81.10.x and higher.
n Posture Management - Shows Vulnerability Management and patches information.
Note - Available only to customer subscribed to this feature and with server
version R81.10.x and higher.
n Policies Reports - A comprehensive report on Threat Prevention capabilities.
n Operational Report - Shows the insights about the operational status of the deployed
endpoints.
n Compliance Report - Shows the compliance status in the organization.
n Check Point Cyber Security Report 2023 - Shows the insights to help your organization
stay secure.
To download a report:
1. Select the report and click Export Report.
The Export Report window appears.
2. In the Time Frame list, select Last day, Last 7 days, or Last 30 days.
3. From the Tenant list, select the required tenant for which you want to download the
report.
4. Click Export.
Global Exclusions
With Global Exclusions in a Managed Security Service Provider (MSSP) account, you can
create exclusions (using Legacy or Smart Exclusions) at one place and sync them with the
child accounts.
To access Global Exclusions, go to Overview > MSSP View > Global Exclusions.
Caution - When you click Save, in addition to the exclusion changes, all the policy
changes that have been saved for the corresponding capability in the child accounts
are also installed on the Endpoint Management Server. For example, if you have
added Anti-Malware exclusions, then all the saved changes related to the Anti-
Malware policy in the child accounts are installed to the Endpoint Management
Server.
Caution - When you click Save, in addition to the exclusion changes, all the policy
changes that have been saved for the corresponding capability in the child accounts
are also installed on the Endpoint Management Server. For example, if you have
added Anti-Malware exclusions, then all the saved changes related to the Anti-
Malware policy in the child accounts are installed to the Endpoint Management
Server.
Click Sync All to sync the exclusions with the child accounts.
Use Case
You are an MSSP with several child accounts that require unique policy settings and frequent
updates:
n You want to assign these unique policy settings to child accounts easily without having to
manually define them for each child account.
n You want to manage policy updates from the parent account and propagate the updates
to child accounts automatically.
Benefits
n Centralized policy management
n Consistent enforcement in policy settings
n Customized policy settings for unique requirements
n Ensures all child accounts are compliant.
1. Access the Harmony Endpoint EPMaaS Administrator Portal with the MSSP account.
2. Click Policy > MSSP View > Template Repository > Threat Prevention.
4. Select the cloned template and in the Capabilities and Exclusions pane, do these:
a. In the Name field, edit the name. For example, Default Settings for All Customers.
b. (Optional) In the Description field, enter a description.
c. To add exclusions, click Exclusions Center. See "Adding Exclusions to Rules" on
page 251.
d. Configure these capabilities, including Advanced Settings:
n "Web & Files Protection" on page 224
n "Behavioral Protection" on page 245
n "Analysis & Remediation" on page 250
5. Click Save.
Note - Make sure the rule is for devices only and it is Connected. To view
device specific rules, change the policy operation mode to Mixed. For more
information, see "Unified Policy" on page 213.
4. In the Capabilities and Exclusion pane, from the MSSP template list, select All
templates.
5. Select the template from the left pane and click Select.
3. To view the child accounts, click the number. The MSSP Templates pop-up appears
and shows the details:
Rule name Policy rule name that uses the template in the child
account.
Status date Last date and time in the server when the child account
checked for the template updates.
4. Select the cloned template and in the Capabilities and Exclusions pane, do these:
a. In the Name field, edit the name. For example, Default Settings for All Customers.
b. (Optional) In the Description field, enter a description.
ii. Capabilities - From the tree, select the necessary capabilities that must be
deployed in the endpoints.
5. Click Save.
4. In the Capabilities and Exclusion pane, from the MSSP template list, select All
templates.
5. Select the template from the left pane and click Select.
6. Click Save & Install.
After the policy is installed, the policy capability settings are disabled (Read-only) and the
changes to the template from the MSSP account are automatically applied to the child
account.
3. To view the child accounts, click the number. The MSSP Templates pop-up appears
and shows the details:
Rule name Policy rule name that uses the template in the child
account.
Status date Last date and time in the server when the child account
checked for the template updates.
Recent Tasks
The running and the queued tasks appear in the Recent Tasks window at the top right of your
screen.
Known Limitations
These are the current known limitations for Harmony Endpoint:
n You cannot perform any action in SmartEndpoint during the download of the Endpoint
Security client package until the download is complete.
n Capsule Docs and Endpoint URL Filtering are not supported.
n When you create a new administrator, you cannot use the "Change password on next
login" option.
n In SmartEndpoint reports, the IP address of the client may be wrong due to network
hops.
n Use SmartEndpoint to switch to SmartConsole and SmartUpdate:
n Distributed Active Directory Scanner: The deletion of a user from an Active Directory is
not detected by the automatic scan and it is not reflected in the organizational tree.
n Unlock On LAN is not working. During Pre-boot, the client device cannot communicate
correctly with the server.
n These versions are not supported with Harmony Endpoint:
l E80.64 Endpoint Security client for macOS
l E80.71 Endpoint Security client for macOS
l E80.89 Endpoint Security client for macOS
n You cannot upgrade from E80.64, E80.71, E80.89 Endpoint Security for macOS clients
to these versions:
l E82.00 Endpoint Security client for macOS
l E82.50 Endpoint Security client for macOS
n When you create a new AD scanner, you cannot scan user certificates from Active
Directory.
n In order to use WSL2 on Windows 10 and 11 with Harmony Endpoint installed you must
alter your firewall configuration. These changes apply only when you use the firewall
blade. For additional information please see sk177207
Appendix
n "Appendix A - Deploying Harmony Endpoint Security Client using SCCM" below
n "Appendix B - Uninstalling the Harmony Endpoint Security Client (For macOS and
Windows)" on the next page
Use Case
If you already use SCCM to manage your organization’s endpoints, you can use it to deploy
Check Point's Harmony Endpoint on these managed endpoints.
Prerequisites
A System Center Configuration Manager (SCCM) account.
Notes -
n The system automatically reboots the endpoint after uninstalling the client
successfully.
n The system deletes the client information on the Endpoint Management Server
after the configured period of time (default is 30 days).
For more information on the Uninstall Client Push Operation, see "Performing Push
Operations" on page 491.