During a recent internal purple team exercise, the following recommendation is given to the detection...

The recommendation requires detecting and preventing the command line invocation of Python (e.g., python.exe or py.exe) on Windows endpoints, specifically for non-technical business units. This involves identifying a specific behavior (command line execution of Python) and enforcing a preventive action (e.g., blocking the process). In Cortex XDR,Behavioral Indicators of Compromise (BIOCs)are used to define and detect specific patterns of behavior on endpoints, such as command line activities, and can be paired with aRestriction profileto block the behavior.

Correct Answer Analysis (B):ABehavioral Indicator of Compromise (BIOC)rule should be implemented. The BIOC can be configured to detect the command line invocation of Python by defining conditions such as the process name (python.exe or py.exe) and the command line arguments. For example, a BIOC rule might look for process = python.exe with a command line pattern like cmd.exe /c python*. This BIOC can then be added to a Restriction profile to prevent the execution of Python by non-technical business units, which can be targeted by applying the profile to specific endpoint groups (e.g., those assigned to non-technical units).

Why not the other options?

A. Analytics Behavioral Indicator of Compromise (ABIOC): ABIOCs are analytics-driven rules generated by Cortex XDR’s machine learning and behavioralanalytics, not user-defined rules. They are not suitable for creating custom detection and prevention rules like the one needed here.

C. Correlation: Correlation rules are used to generate alerts by correlating events across multiple datasets (e.g., network and endpoint data), but they do not directly prevent behaviors like command line execution.

D. Indicator of Compromise (IOC): IOCs are used to detect specific artifacts (e.g., file hashes, IP addresses) associated with known threats, not to detect and prevent behavioral patterns like command line execution.

Exact Extract or Reference:

TheCortex XDR Documentation Portalexplains BIOC rules: “Behavioral Indicators of Compromise (BIOCs) can detect specific endpoint behaviors, such as command line invocation of processes like Python, and prevent them when added to a Restriction profile” (paraphrased from the BIOC section). TheEDU-260: Cortex XDR Prevention and Deploymentcourse covers detection engineering, stating that “BIOCs are used to detect and block specific behaviors, such as command line executions, on Windows endpoints” (paraphrased from course materials). ThePalo Alto Networks Certified XDR Engineer datasheetincludes “detection engineering” as a key exam topic, encompassing BIOC rule creation.