Add a New Restriction Rule
Table of Contents
4.2 (EoS)
Expand all | Collapse all
-
- Set Up the Endpoint Infrastructure
- Activate Traps Licenses
-
- Endpoint Infrastructure Installation Considerations
- TLS/SSL Encryption for Traps Components
- Configure the MS-SQL Server Database
- Install the Endpoint Security Manager Server Software
- Install the Endpoint Security Manager Console Software
- Manage Proxy Communication with the Endpoint Security Manager
- Load Balance Traffic to ESM Servers
-
- Malware Protection Policy Best Practices
- Malware Protection Flow
- Manage Trusted Signers
-
- Remove an Endpoint from the Health Page
- Install an End-of-Life Traps Agent Version
-
-
- Traps Troubleshooting Resources
- Traps and Endpoint Security Manager Processes
- ESM Tech Support File
-
- Access Cytool
- View the Status of the Agent Using Cytool
- View Processes Currently Protected by Traps Using Cytool
- Manage Logging of Traps Components Using Cytool
- Restore a Quarantined File Using Cytool
- View Statistics for a Protected Process Using Cytool
- View Details About the Traps Local Analysis Module Using Cy...
- View Hash Details About a File Using Cytool
Add a New Restriction Rule
Create a new restriction rule to define limitations
on where and how executable files run on endpoints.
- Configure a new restriction rule.SelectandPoliciesMalwareRestrictionsAdda new rule.
- From the action menuAdd.
- Select the type of restriction rule you are adding.Select one of the following options and then configure settings according to the type of restriction you are adding to your security policy:
- Execution Path Restriction—Restrict access to local or remote files and folders. For more information, see Block Execution from Local and Network Folders.
- Network Folder Behavior—Restrict access to all network folders except for those in the whitelist. For more information, see Whitelist a Network Folder.
- External Media—For more information, see Define External Media Restrictions and Exemptions.
- Child Processes (Pre-4.0 Agents)—Block malicious child processes spawned from legitimate processes.
- Java (Pre-4.0 Agents)—Prevent untrusted Java applets from executing objects using browsers and add specific trusted processes to whitelists so they can run on endpoints as needed.
- (Optional) Add Conditions to the rule. By default, a new rule does not contain any conditions.To specify a condition, select theConditionstab, select the condition in the Conditions list, and thenAddit to the Selected Conditions list. Repeat this step to add more conditions, as needed. You can also define new Conditions.
- (Optional) Define the Target Objects to which to apply the rule.To define a smaller subset of target objects, select theObjectstab, and then enter one or moreAD Users,AD Computers,AD Groups,AD Organizational Unit,Existing Endpoints, orExisting Groupsin the Include or Exclude areas. The Endpoint Security Manager queries Active Directory to verify the users, computers, groups, or organizational units. The ESM Console also offers autocompletion as you type for existing endpoints and existing virtual groups.
- (Optional) Review the rule name and description. The ESM Console automatically generates the rule name and description based on the rule details but permits you to change these fields, if needed.To override the autogenerated name, select theNametab, clear theActivate automatic descriptionoption, and then enter a rule name and description of your choice.
- Save the restrictions rule.Do either of the following:
- Savethe rule without activating it. This option is only available for inactive, cloned, or new rules. When you are ready to activate the rule, select the rule from thepage and then clickPoliciesMalwareRestrictionsActivate.
- Applythe rule to activate it immediately.
After saving or applying a rule, you can return to theRestrictionspage at any time toDeleteorDeactivatethe rule.