Add a New Exploit Security Profile
From the Cortex® XDR™ management console, you can customize exploit protection capabilities in each Exploit security profile.
Exploit security profiles allow you to configure the action the
XDRagent takes when attempts to exploit software vulnerabilities or flaws occur. To protect against specific exploit techniques, you can customize exploit protection capabilities in each Exploit security profile.
By default, the
XDRagent will receive the default profile that contains a pre-defined configuration for each exploit capability supported by the platform. To fine-tune your Exploit security policy, you can override the configuration of each capability to block the exploit behavior, allow the behavior but report it, or disable the module.
To define an Exploit security profile:
- Add a new profile.
- FromCortexXDR, selectand select whether toEndpointsPolicy ManagementPreventionProfiles+ New ProfileCreate NeworImport from Filea new profile.New imported profiles are added and not replaced.
- Select the platform to which the profile applies andExploitas the profile type.
- Define theGeneral Information.
- Enter a uniqueProfile Nameto identify the profile. The name can contain only letters, numbers, or spaces, and must be no more than 30 characters. The name you choose will be visible from the list of profiles when you configure a policy rule.
- To provide additional context for the purpose or business reason that explains why you are creating the profile, enter a profileDescription. For example, you might include an incident identification number or a link to a help desk ticket.
- Configure the action to take when theCortexXDRagent detects an attempt to exploit each type of software flaw.
To view which processes are protected by each capability, see Processes Protected by Exploit Security Policy .ForKnown Vulnerable Process Protection, enable to automatically protect endpoints from attacks that try to leverage common operating system mechanisms for malicious purposes. Select either toBlock(default) orReport. When enabled, select whether to also enable theJava Deserialization Protection. If enabled, the same action mode defined for theKnown Vulnerable Process Protectionis inherited.Attackers can use existing mechanisms in the operating system to execute malicious code. By enabling this capability, XDR agent Add the following section in Windows Exploit ProfileKnown Vulnerable Processes ProtectionAction Mode - Block (default) / Report / DisabledInheriting from action mode - Java Deserialization Protection - Enabled / Disabled (default)When the Action mode of Known Vulnerable Processes Protection is set to disabled the Jave protection becomes greyed out and is disabled as well regardless of its value.If enabled, the action mode - report or block is inherited from the main setting.ForLogical Exploits Protection, you can also configure a block list for the DLL Hijacking module. The block list enables you to block specific DLLs when run by a protected process. The DLL folder or file must include the complete path. To complete the path, you can use environment variables or the asterisk (*) as a wildcard to match any string of characters (for example,*/windows32/).ForExploit Protection for Additional Processes, you also add one or more additional processes.In Exploit Security profiles, if you change the action mode for processes, you must restart the protected processes for the following security modules to take effect on the process and its forked processes: Brute Force Protection, Java Deserialization, ROP, and SO Hijacking.
- Block—Block the exploit attack.
- Report—Allow the exploit activity but report it toCortexXDR.
- Disabled—Disable the module and do not analyze or report exploit attempts.
- Default—Use the default configuration to determine the action to take.CortexXDRdisplays the current default configuration for each capability in parenthesis. For example,Default (Block).
- (Windows only) Configure how to address unpatched known vulnerabilities in your network.If you have Windows endpoints in your network that are unpatched and exposed to a known vulnerability, Palo Alto Networks strongly recommends that you upgrade to the latest Windows Update that has a fix for that vulnerability.If you choose not to patch the endpoint, theUnpatched Vulnerabilities Protectioncapability allows theCortexXDRagent to apply a workaround to protect the endpoints from the known vulnerability. It takes theCortexXDRagent up to 6 hours to enforce your configured policy on the endpoints.
This workaround applies only to the specific Windows versions listed as exposed to these CVEs, and requires aCortexXDRagent 7.1 or later and content 167-51646 or later. This workaround in not recommended for non-persistent, stateless, or linked-clone environments. In some cases, enabling this workaround can affect the network functionality on the endpoint.
- Do not modify system settings(default)—Do not modify the IPv4 and IPv6 settings currently set on the endpoint, whether the current values are your original values or values that were modified as part of this workaround.
- Modify system settings until the endpoint is patched—If the endpoint is already patched, this option does not modify any system settings. For unpatched endpoints, theCortexXDRagent runs the following commands to temporarily modify the IPv4 and IPv6 settings until the endpoint is patched. After the endpoint is patched for CVE-2021-24074, CVE-2021-24086, and CVE-2021-24094, all modified Windows system settings as part of this workaround are automatically reverted to their values before modification. Palo Alto Networks strongly recommends that you review these commands before applying this workaround in your network to ensure your critical business components are not affected or harmed:netsh int ipv6 set global reassemblylimit=0, this command disables IPv6 fragmentation on the endpoint.netsh int ipv4 set global sourceroutingbehavior=drop, this command disables LSR / loose source routing for IPv4.
- Revert system settings to your previous settings—Revert all Windows system settings to their values before modification as part of this workaround, regardless of whether the endpoint was patched or not.
- Savethe changes to your profile.
- You can do this in two ways: You canCreate a new policy rule using this profilefrom the right-click menu or you can launch the new policy wizard fromPolicy Rules.
Recommended For You
Recommended videos not found.