Add a New Malware Security Profile
From the Cortex XDR management console, you can configure
what action Cortex XDR agents take when known malware and unknown
files try to run.
Malware
security profiles allow you to configure the action
Cortex
XDR
agents take when known malware and
unknown files try to run on Windows, Mac, Linux, and Android endpoints.By
default, the
Cortex
XDR
agent
will receive the default profile that contains a pre-defined configuration
for each malware protection capability supported by the platform.
To fine-tune your Malware security policy, you can override the
configuration of each capability to block the malicious behavior
or file, allow but report it, or disable the module. For each setting
you override, clear the option to Use Default
.To
configure a Malware 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 andMalwareas the profile type.
- Identify the profile.
- 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 theCortexXDRagent to examine executable files, macros, or DLL files on Windows endpoints, Mach-O filesor DMG fileson Mac endpoints, ELF files on Linux endpoints, or APK files on Android endpoints.
- Configure theAction Mode—the behavior of theCortexXDRagent—when malware is detected:
- Block—Block attempts to run malware.
- Report—Report but do not block malware that attempts to run.
- (Android only)Prompt—Enable theCortexXDRagent to prompt the user when malware is detected and allow the user to choose to allow malware, dismiss the notification, or uninstall the app.
- Disabled—Disable the module and do not examine files for malware.
- Configure additional actions to examine files for malware.By default,CortexXDRuses the settings specified in the default malware security profile and displays the default configuration in parenthesis. When you select a setting other than the default, you override the default configuration for the profile.
- (Windows, Mac starting with)CortexXDRagent 7.4, Linux starting withCortexXDRagent 7.5Quarantine Malicious Executables / Mach-O / ELF files—By default, theCortexXDRagent blocks malware from running but does not quarantine the file. Enable this option to quarantine files depending on the verdict issuer (local analysis, WildFire, or both local analysis and WildFire).The quarantine feature is not available for malware identified in network drives.
- Upload—Enable the<file_type>files for cloud analysisCortexXDRagent to send unknown files toCortexXDR, and forCortexXDRto send the files to WildFire for analysis. With macro analysis, theCortexXDRagent sends the Microsoft Office file containing the macro. The file types that theCortexXDRagent analyzes depend on the platform type. WildFire accepts files up to 100MB in size.
- Treat Grayware as Malware—Treat all grayware with the sameAction Modeyou configure for malware. Otherwise, if this option is disabled, grayware is considered benign and is not blocked.
- Action on Unknown to WildFire—Select the behavior of theCortexXDRagent when an unknown file tries to run on the endpoint (Allow,Run Local Analysis, orBlock). With local analysis, theCortexXDRagent uses embedded machine learning to determine the likelihood that an unknown file is malware and issues a local verdict for the file. If you block unknown files but do not run local analysis, unknown files remain blocked until theCortexXDRagent receives an official WildFire verdict.
- ()CortexXDRagent 7.5 and later for Windows onlyAction when WildFire verdict is Benign with Low Confidence—Select the behavior of theCortexXDRagent when a file with Benign Low Confidence verdict from WildFire tries to run on the endpoint (Allow,Run Local Analysis, orBlock). With local analysis, theCortexXDRagent uses embedded machine learning to determine the likelihood that an unknown file is malware and issues a local verdict for the file. If you block these files but do not run local analysis, they remain blocked until theCortexXDRagent receives a high-confidence WildFire verdict. To enable this capability, ensure that WildFire analysis scoring is enabled in your Global Agent Settings.
- For optimal user experience, Palo Alto Networks recommends you set the action mode to eitherAlloworRun Local Analysis.
- Action on Benign LC verdict is supported from agent version 7.5 and above. For agent version 7.4.X, action on Benign LC verdict is the same as the action for files with Unknown verdict.
- (Windows only)Examine Office Files From Network Drives—Enable theCortexXDRagent to examine Microsoft Office files in network drives when they contain a macro that attempts to run. If this option is disabled, theCortexXDRagent will not examine macros in network drives.
(Windows only) As part of the anti-malware security flow, theCortexXDRagent leverages the OS capability to identify revoked certificates for executables and DLL files that attempt to run on the endpoint by accessing the Windows Certificate Revocation List (CRL). To allow theCortexXDRagent access the CRL, you must enable internet access over port 80 for Windows endpoints running Traps 6.0.3 and later releases, Traps 6.1.1 and later releases, orCortexXDR7.0 and later releases. If the endpoint is not connected to the internet, or you experience delays with executables and DLLs running on the endpoint, please contact Palo Alto Networks Support. - (Optional) Add files and folders to your allow list to exclude them from examination.
- +Adda file or folder.
- Enter the path and pressEnteror click the check mark when done. You can also use a wildcard to match files and folders containing a partial name. Use?to match a single character or*to match any string of characters. To match a folder, you must terminate the path with * to match all files in the folder (for example,c:\temp\*).
- Repeat to add additional files or folders.
- Add signers to your allow list to exclude them from examination.When a file that is signed by a signer you included in your allow list attempts to run,
- +Adda trusted signer.
- Enter the name of the trusted signer (Windows) or the SHA1 hash of the certificate that signs the file (Mac) and pressEnteror click the check mark when done. You can also use a wildcard to match a partial name for the signer. Use?to match any single character or*to match any string of characters.
- Repeat to add additional folders.
CortexXDRagent evaluates the signer name using the CN (Common Name) value in the digital signature, while theCortexXDRconsole can display in the Alerts table both the O (Organization) value and the CN (Common Name).
- (Windows, Mac, and Linux only) ConfigureBehavioral Threat Protection.Behavioral threat protection requires Traps agent 6.0 or a later release for Windows endpoints, and Traps 6.1 or later versions for Mac and Linux endpoints.With Behavioral threat protection, the agent continuously monitors endpoint activity to identify and analyze chains of events—known as causality chains. This enables the agent to detect malicious activity in the chain that could otherwise appear legitimate if inspected individually. A causality chain can include any sequence of network, process, file, and registry activities on the endpoint. Behavioral threat protection can also identify behavior related to vulnerable drivers on Windows endpoints. For more information on data collection for Behavioral Threat Protection, see Endpoint Data Collected by Cortex XDR.Palo Alto Networks researchers define the causality chains that are malicious and distribute those chains as behavioral threat rules. When theCortexXDRagent detects a match to a behavioral threat protection rule, theCortexXDRagent carries out the configured action (default is Block). In addition, theCortexXDRagent reports the behavior of the entire event chain up to the process, known as the causality group owner (CGO), that theCortexXDRagent identified as triggering the event sequence.To configureBehavioral Threat Protection:
- Define theAction modeto take when theCortexXDRagent detects malicious causality chains:
- Block(default)—Block all processes and threads in the event chain up to the CGO.
- Report—Allow the activity but report it toCortexXDR.
- Disabled—Disable the module and do not analyze or report the activity.
- Define whether to quarantine the CGO when theCortexXDRagent detects a malicious event chain.
- Enabled—Quarantine the CGO if the file is not signed by a highly trusted signer. When the CGO is signed by a highly trusted signer or powershell.exe, wscript.exe, cscript.exe, mshta.exe, excel.exe, word.exe or powerpoint.exe, theCortexXDRagent parses the command-line arguments and instead quarantines any scripts or files called by the CGO.
- Disabled(default)—Do not quarantine the CGO of an event chain nor any scripts or files called by the CGO.
- (Windows only, requires a) Define theCortexXDRagent 7.2 or a later releaseAction Mode for Vulnerable Drivers Protection.Behavioral threat protection rules can also detect attempts to load vulnerable drivers. As with other rules, Palo Alto Networks threat researchers can deliver changes to vulnerable driver rules with content updates.
- Block(default)—Block all attempts to run vulnerable drivers.
- Report—Allow vulnerable drivers to run but report the activity.
- Disabled—Disable the module and do not analyze or report the activity.
- (Optional) Add files that you do not want theCortexXDRagent to terminate when a malicious causality chain is detected to your allow list. The allow list does not apply to vulnerable drivers.
- +Adda file path.
- Enter the file path you want to exclude from evaluation. Use?to match a single character or*to match any string of characters.
- Click the checkmark to confirm the file path.
- Repeat the process to add any additional file paths to your allow list.
- (Windows only)Respond to Malicious Causality Chains.When theCortexXDRagent identifies a remote network connection that attempts to perform malicious activity—such as encrypt endpoint files—the agent can automatically block the IP address to close all existing communication, and block new connections from this IP address to the endpoint. WhenCortexXDRblocks an IP address per endpoint, that address remains blocked throughout all agent profiles and policies, including any host-firewall policy rules. You can view the list of all blocked IP addresses per endpoint from theAction Center, as well as unblock them to re-enable communication as appropriate.This module is supported withCortexXDRagent 7.3.0 and later release.
- Select theAction Modeto take when theCortexXDRagent detects remote malicious causality chains:
- Enabled(default)—Terminate connection and block IP address of the remote connection.
- Disabled—Do not block remote IP addresses.
- To allow specific and known safe IP address or IP address ranges that you do not want theCortexXDRto block, add these IP addresses to your allow list.+Addand then specify the IP address.
- (Windows only) ConfigureRansomware Protection.
- Define theAction modeto take when theCortexXDRagent detects ransomware activity locally on the endpoint or in pre-defined network folders:
- Block(default)—Block the activity.
- Report—Allow the activity but report it toCortexXDR.
- Disabled—Disable the module and do not analyze or report the activity.
- Choose whether you want theCortexXDRagent toQuarantine Malicious Processwhen ransomware is detected.The quarantine option is only available if theAction modeisBlock.
- Configure the ransomware moduleProtection mode.By default, the protection mode is set toNormalwhere the decoy files on the endpoint are present, but do not interfere with benign applications and end user activity on the endpoint. If you suspect your network has been infected with ransomware and need to provide better coverage, you can apply theAggressiveprotection mode. The aggressive mode exposes more applications in your environment to theCortexXDRagent decoy files, while also increasing the likelihood that benign software is exposed to decoy files, raising false ransomware alerts, and impairing user experience.
- (Windows only) Configure theCortexXDRagent toPrevent Malicious Child Process Execution.
- Select theAction Modeto take when theCortexXDRagent detects malicious child process execution:
- Block—Block the activity.
- Report—Allow the activity but report it toCortexXDR.
- To allow specific processes to launch child processes for legitimate purposes, add the child process to your allow list with optional execution criteria.+Addand then specify the allow list criteria including theParent Process Name,Child Process Name, andCommand Line Params. Use?to match a single character or*to match any string of characters.If you are adding child process evaluation criteria based on a specific security event, the event indicates both the source process and the command line parameters in one line. Copy only the command line parameter for use in the profile.
- (Windows and Mac only) Enable endpoint file scanning.Periodic scanning enables you to scan endpoints on a reoccurring basis without waiting for malware to run on the endpoint. Periodic scanning is persistent, and if the scan is scheduled to start while the endpoint is powered-off, then scan will be initiated when the endpoint is powered-on again. The scheduling of future scans is not affected by this delay. To better understand how the agent scans the endpoint, refer to Scan an Endpoint for Malware.When periodic scanning is enabled in your profile, theCortexXDRagent initiates an initial scan when it is first installed on the endpoint, regardless of the periodic scanning scheduling time.
- Configure theAction Modefor theCortexXDRagent to periodically scan the endpoint for malware:Enabledto scan at the configured intervals,Disabled(default) if you don’t want theCortexXDRagent to scan the endpoint.
- To configure the scan schedule, set the frequency (Run WeeklyorRun Monthly) and day and time at which the scan will run on the endpoint.Just as with an on-demand scan, a scheduled scan will resume after a reboot, process interruption, or operating system crash.
- (To include removable media drives in the scheduled scan, enable theWindows only)CortexXDRagent toScan Removable Media Drives.
- Add folders you your allow list to exclude them from examination.
- Add (+) a folder.
- Enter the folder path. Use?to match a single character or*to match any string of characters in the folder path (for example,C:\*\temp).
- PressEnteror click the check mark when done.
- Repeat to add additional folders.
- (Windows Vista and later Windows releases) EnablePassword Theft Protection.SelectEnabledto enable theCortexXDRagent to prevent attacks that use the Mimikatz tool to extract passwords from memory. When set toEnabled, theCortexXDRagent silently prevents attempts to steal credentials (no notifications are provided when these events occur). TheCortexXDRagent enables this protection module following the next endpoint reboot. If you don’t want to enable the module, selectDisabled.This module is supported with Traps agent 5.0.4 and later release.
- (Windows only) Configure theNetwork Packet Inspection Engine.By analyzing the network packet data, theCortexXDRagent can detect malicious behavior already at the network level and provide protection to the growing corporate network boundaries. The engine leverages both Palo Alto Networks NGFW content rules, and newCortexXDRcontent rules created by the Research Team which are updated through the security content.This module is supported withCortexXDRagent 7.5.0 and later release.
- Define theAction modeto take when theCortexXDRagent detects malicious behavior:
- Terminate Session(default)—Drop the malicious connections. In case of an outgoing connection, also terminate all associated processes.
- Report—Allow the packets in your network but report it toCortexXDR.
- Disabled—Disable the module and do not analyze or report the activity.
- (Linux only) EnableLocal File Threat Examination.The Local Threat-Evaluation Engine (LTEE) enables theCortexXDRagent to detect webshells and optionally quarantine malicious PHP files on the endpoint.This module is supported withCortexXDRagent 7.2.0 and later release.
- Select theAction Modeto take when theCortexXDRagent detects the malicious behavior.
- Enable—Enable theCortexXDRagent to analyze the endpoint for PHP files arriving from the web server and alert of any malicious PHP scripts.
- Disable—Disable the module and do not analyze or report the activity.
- Quarantine malicious files.WhenEnabled, theCortexXDRagents quarantine malicious PHP files on the endpoint. The agent quarantines newly created PHP files only, and does not quarantine updated files.
- (Optional) Add files and folders to your allow list to exclude them from examination.
- +Adda file or folder.
- Enter the path and pressEnteror click the check mark when done. You can also use*to match files and folders containing a partial name. To match a folder, you must terminate the path with * to match all files in the folder (for example,/usr/bin/*).
- Repeat to add additional files or folders.
- (Linux only) ConfigureReverse Shell Protection.The Reverse Shell Protection module enables theCortexXDRagent to detect and optionally block attempts to redirect standard input and output streams to network sockets.
- Define theAction Modeto take when theCortexXDRagent detects the malicious behavior.
- Block—Block the activity.
- Report—Allow the activity but report it toCortexXDR.
- Disabled—Disable the module and do not analyze or report the activity.
- (Optional) Add processes to your allow list that must redirect streams to network sockets.
- +Adda connection.
- Enter the path of the process, and the local and remote IP address and ports.Use a wildcard to match a partial path name. Use a*to match any string of characters (for example,*/bash). You can also use a*to match any IP address or any port.
- PressEnteror click the check mark when done.
- Repeat to add additional folders.
- 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
Recommended videos not found.