Refer to the following articles before you begin
Harmony Endpoint Best Practice configuration
The following section explains how to set the Best Practice configuration
- Note that this is just the initial recommended configuration, and from this point any organization should tailor the solution to their needs in order to maximize the utilization
- At the moment, you can get more granular control through SmartEndpoint
Step By Step - Web Console - Harmony Endpoint Best Practice configuration
Table of contents:
- Web & Files Protection
- Behavioral Protection
- Analysis & Remediation
Policy Description |
Policy Configuration |
Web & Files Protection |
 |
Best Practice - URL Filtering
Set to Prevent
Check Security Check Legal Liability/Regulatory compliance
Additional categories should be enabled according to organizational and regulatory needs
Add URLs to the Black list for specific use cases
Exclude specific URLs if needed It is less recommended to globally allow users to dismiss the alert and access the website |
 |
Best Practice - Download protection
Stage 1 - Set to Prevent
Choose to suspend until emulation completes
Unsupported files - Allow download (Fail Open) |
 |
Best Practice - Download protection
Stage 2 - Choose to Get extracted copy before emulation completes
Before enabling make sure to educate users that they receive a clean copy without any active content and if the file is not malicious they are able to receive it from the SandBlast Agent Browser extension |
 |
Best Practice - Files protection
Set Anti-Malware Prevent to ON
Set Files Threat Emulation Detect to ON
Anti-Malware periodic scan every month and update signature interval every 4 hours
It is possible to perform periodic scans in shorter interval and to allow users to cancel the scan up to one month
Remember that SandBlast Agent include real time protection during runtime so an Anti-Malware periodic scan can be in longer intervals to support users productivity |
 |
Behavioral Protection |
 |
Best Practice - Anti-Bot
Set to Prevent
|
 |
Best Practice - Behavioral Guard & Anti-Ransomware
Set to Prevent
Enable network share protection if needed to recover from file encryption when network shares are used |
 |
Best Practice - Anti-Exploit
Stage 1 - Set to Detect
Monitor for events that can cause applications interruptions before moving to prevent |
 |
Best Practice - Anti-Exploit
Stage 2 - Set to Prevent
Once confidence is achieved that all applications work without interruptions
Changing Anti-Exploit mode requires reboot to reload all monitored applications and complete the mode change |
 |
Analysis & Remediation |
 |
Best Practice - Automated attack analysis (Forensics)
Set Enable protection to ON Set Enable Threat Hunting to ON |
 |
Best Practice - Remediation & Response
Set Attack remediation to ON
It is recommended to Terminate trusted processes for full attack chain remediation
Set File quarantine to ON
For critical locations or Power users it is possible to allow users to restore items from quarantine |
 |
Step By Step - SmartEvent - Harmony Endpoint Best Practice configuration
Table of Contents:
-
Anti-Ransomware, Behavioral Guard and Forensics settings
-
Anti-Bot settings
-
SandBlast Agent Threat Extraction, Threat Emulation, Zero Phishing and Anti-Exploit settings
-
Anti-Malware settings
-
Exclusions
Anti-Ransomware, Behavioral Guard and Forensics settings
Anti-Bot Settings
Harmony Endpoint Threat Extraction, Threat Emulation, Zero Phishing and Anti-Exploit settings
Anti-Malware configuration - use default settings

Exclusions
It is recommended to create exclusions before the first deployment - through the planning phase. Exclusions can also be created through the first deployment phase on the Test/POC group of assets.
During the learning mode phase notice the following for exclusions:
- Internally trusted processes or certified applications that create FPs or load.
- Do not exclude the OS (Microsoft/Apple) certificate
- Internally trusted and protected domains
How to exclude?
|
This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.
|