Whitelist a Network Folder

To prevent attack scenarios that are based on writing malicious executable files to remote folders, you can create a restriction rule to block all executable files run from specific folders. To enable executable files to run from known trusted network locations, you can create a Network Folder Behavior restriction rule to whitelist the file or remote folder path.
When you enable this rule, Traps blocks all executable files that run from network locations except for those expressly whitelisted in the rule. When a user attempts to open an executable file from a network folder that is not specified in the whitelist, Traps blocks the attempt and reports the security event to the ESM Server.
  1. Begin a new restriction rule:
    1. Select PoliciesMalwareRestrictions.
    2. From the action menu manage-hidden-menu-icon.png , Add a new restriction rule.
    3. Select Network Folder Behavior.
  2. Select the option to Restrict file execution from all network folders except the locations listed below.
  3. Click the add folder icon 3.1-add-folder-icon.png , to Add the file or folder path in uniform naming convention (UNC) format.
    To whitelist a folder, you must terminate the path with a wildcard. For example, \\networkpath\temp\* matches any file launched from the \\networkpath\temp\ folder or subfolder).
    For additional syntax examples, see Wildcards and Variables in Policy Rules.
  4. Repeat the previous step to add multiple paths as needed.
  5. (Optional) Add Conditions to the rule. By default, a new rule does not contain any conditions.
    To specify a condition, select the Conditions tab, select the condition in the Conditions list, and then Add it to the Selected Conditions list. Repeat this step to add more conditions, as needed. To add a condition to the Conditions list, see Define Activation Conditions for a Rule on Windows Endpoints.
  6. (Optional) Define the Target Objects to which to apply the restriction rule. By default, a new rule applies to all objects in your organization.
    To define a subset of target objects, select the Objects tab, and then enter one or more Users, Computers, Groups, Organizational Unit, or Existing Endpoints in the Include or Exclude areas. The Endpoint Security Manager queries Active Directory to verify the users, computers, groups, or organizational units or identifies existing endpoints from previous communication messages.
  7. (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 the Name tab, clear the Activate automatic description option, and then enter a rule name and description of your choice.
  8. Save the restrictions rule.
    Do either of the following:
    • Save the 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 the PoliciesMalwareRestrictions page and then click Activate.
    • Apply the rule to activate it immediately.
    After saving or applying a rule, you can return to the Restrictions page at any time to Delete or Deactivate the rule.

Related Documentation