New Traps 4.2 Endpoint Security Manager (ESM)

traps 4.2.png

As change is the only constant in the universe, we are happy to introduce these new features that the latest version of Traps Endpoint Security Manager 4.2 has.

The following topics describe the new features introduced in Traps Endpoint Security Manager (ESM) 4.2. For additional information on how to use the new features in this release, refer to the Traps Endpoint Security Manager Administrator’s Guide.

Features	Description
Linux Support	You can now manage endpoint security policy for Linux servers in the ESM Console. Traps for Linux extends exploit protection using the following exploit protection modules: Brute Force Protection, ROP Mitigation, Shellcode Protection, and Kernel Privilege Escalation Protection. To monitor the Linux servers in your organization, you can view security events that occur on your Linux endpoints in the ESM Console. Traps for Linux is supported on Linux distributions as listed in the Palo Alto Networks Compatibility Matrix .
Trusted Signer Management	For Windows and Mac endpoints, you can now add a signer to the trusted signer whitelist in the ESM Console. When a file is signed by a trusted signer, Traps permits the file to run. For Windows endpoints, Traps evaluates any trusted signers you add as highly trusted signers in the malware evaluation flow.
Virtual Groups	To enable you to easily apply policy, agent action, and agent settings rules to groups of endpoints, you can now define virtual groups in the ESM Console. Virtual groups enable you to group endpoints based on static characteristics such as hostname or unique ID or dynamic characteristics such as domain, IP address, range, or subnet. You can also add existing groups to a static virtual group to create a nested virtual group of endpoints. In addition, you can also search agent log pages by virtual group.
Granular Child Process Evaluation	You can now configure more granular settings to define which processes are permitted to run child processes on your endpoints. When you configure the child process malware protection module, you can allow specific parent processes to launch child processes and optionally configure additional execution criteria such as command-line arguments. This can be helpful if your organization uses applications in a way where Traps could identify them as malicious when they are actually used for legitimate purposes. For example, if you need to run script engines from an intranet website running Internet Explorer, you can whitelist the specific use while still protecting Internet Explorer from malicious script engines.
Traps Support for Windows Server 2008 with .NET 4.5	You can now install Traps on Windows Server 2008 with .NET 4.5.