Collect New Process Information
By default, Traps protects the most commonly used and well-known processes on your endpoints. In addition, when WildFire is enabled, Traps automatically reports unknown executable files to the Endpoint Security Manager. If WildFire is disabled, it is recommended to create an agent settings rule to enable Traps to collect the names of any new processes that are run on the endpoints and report them to the Endpoint Security Manager. The ESM Console displays the processes as Unprotected on the Process Management page.
- Create a new agent settings rule.Select SettingsAgentSettings and then Add a new rule.
- Enable the collection of new processes on the endpoints.Select Process Management and then enable the option to Collect new process information.When Traps detects new processes, Traps reports the processes to the ESM Server. The ESM Console lists the new processes on the PoliciesExploitProcess Management page as unprotected processes. From there you can change the protection type (see View, Modify, or Delete a Process). After changing the protection type, you can then use it to Create an Exploit Protection Rule.
- (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 to add more conditions as needed. To add a condition to the Conditions list, see Define Activation Conditions for a Rule on Windows Endpoints or Define Activation Conditions for a Rule on Mac Endpoints.
- (Optional) Define the Target
Objects to which to apply the agent settings 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.
- (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.
- Save the agent settings rule.Do either of the following:
After saving or applying a rule, you can return to the Settings page at any time to Delete or Deactivate the rule.
- 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 SettingsAgentSettings page and then click Activate.
- Apply the rule to activate it immediately.
- On a regular basis, review the list of unprotected processes
and evaluate whether add them to existing security rules or create
new rules to protect them.
- Select PoliciesExploitProcess Management.
- Filter or sort the table by the Unprotected protection type.
- Review each process and decide whether to change the
- Change the protection type to Provisional, if you want to use the process in a security rule run as a test.
- Change the protection type to Protected to take advantage of existing rules that apply to all processes. See View, Modify, or Delete a Process. You can also add the process to rules that apply to specific processes, as needed.
Manage Service Protection
Manage Agent Tampering Protection Agent tampering protection allows you to protect the Traps agents running on your endpoints. For flexible, granular control over agent tampering ...
Process Protection Types
Process Protection Types The ESM Console categorizes each process by a Protection Type: Protected —Indicates that the process is actively protected by exploit protection rules ...
Create an Exploit Protection Rule
Create an Exploit Protection Rule An exploit protection rule uses exploit protection modules (EPMs) to protect processes in your organization from specific exploitation techniques. Each ...
Define Java Restrictions
Define Java Restrictions The Java restriction rule is supported in Traps 3.4 and earlier releases. To restrict Java processes from running specific child processes on ...
Define Child Process Restrictions
Define Child Process Restrictions The child process restriction rule is supported in Traps 3.4 and earlier releases. To restrict child processes on endpoints running Traps ...
Uninstall or Upgrade Traps on the Endpoint
Uninstall or Upgrade Traps on the Endpoint Create a new agent actions rule to uninstall Traps from the target objects or upgrade Traps using software ...
Maintain the Endpoints and Traps
Maintain the Endpoints and Traps On a daily or weekly basis, perform the following actions: Examine the Dashboard to verify that the Traps agent is ...
Add a New Agent Settings Rule
Add a New Agent Settings Rule For each agent settings rule, you can specify organizational objects, conditions, and Traps preferences to apply. Agent settings rules ...
Define Memory Dump Preferences
Define Memory Dump Preferences When a protected process crashes or terminates abnormally, Traps records information about the event including the contents of memory locations and ...