Best Practice to Enable Software Blades
We recommend you to enable the Software Blade Specific security solution (module): (1) On a Security Gateway, each Software Blade inspects specific characteristics of the traffic (2) On a Management Server, each Software Blade enables different management capabilities. and the operating modes in the order shown in the table below.
-
Add exclusions before you enable a Software Blade.
-
Enable the Software Blade on a test group before you enable it on the organization level.
Order |
Software Blade |
Operating Mode |
Applicable Group Level |
||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
|||||||||||||
|
Forensics |
|
|
||||||||||||
|
Anti-Ransomware and Behavioral Guard1 |
|
|
||||||||||||
|
|
|
|||||||||||||
|
Anti-Exploit 1 |
|
|
||||||||||||
|
Anti-Bot |
|
|
||||||||||||
|
Analysis and Remediation 1 |
|
|
1 Add exclusions before enabling the blade.
-
For Citrix Anti-Malware, click here.
-
For Microsoft Terminal Server Anti-Virus
Check Point Software Blade on a Security Gateway that uses real-time virus signatures and anomaly-based protections from ThreatCloud to detect and block malware at the Security Gateway before users are affected. Acronym: AV., click here.
-
For FSLogix Anti-Virus, click here.
2 Schedule the scan during non-active period.
3 To add exclusions, see sk122706.