An analyst wants to create a detection rule that triggers when any process attempts to perform code injection into the lsass.exe process, regardless of whether the file hash of the source process is known to be malicious. Which type of rule should be created?
In the Cortex XDR environment, rules are categorized by what they monitor:
BIOC (Behavioral Indicator of Compromise) (B): These rules are designed to detect behavioral patterns and techniques rather than specific files. In this scenario, the behavior is the injection into a sensitive system process (lsass.exe). Since attackers constantly change file hashes to evade signature-based detection, a BIOC rule is the most effective defense because it focuses on the 'action' (the 'how') which is much harder for an attacker to change.
IOC (Indicator of Compromise) (A): These are based on static artifacts like specific file hashes, IP addresses, or domain names. If the hash is unknown, an IOC rule would not trigger.
Analytics Alert (D): These are generated automatically by the platform's Machine Learning engine when activity deviates from a baseline. While it might catch this, it is not a 'manually created rule' by an analyst for a specific known-bad behavior.
Where is the data retrieved by an integration task (such as a user's email address or a file's reputation) stored within an incident so that other playbook tasks can access it?
Context Data is a crucial architectural component of Cortex XSOAR. It acts as a temporary, JSON-formatted 'scratchpad' for each incident.
Data Flow: When a playbook task runs (e.g., !ad-get-user), the output is written to the Context Data. Subsequent tasks can then 'read' from this data to make decisions. For example, a conditional task can check if the user's department in the Context Data is 'Finance' before deciding to escalate the incident.
Persistence: Unlike the War Room (which is a chronological log of events), Context Data stores the latest state of information in a structured way that the automation engine can programmatically interact with.
An administrator needs to prevent users from connecting unauthorized USB flash drives to their corporate workstations to reduce the risk of data exfiltration. Which Cortex XDR feature should be configured?
Device Control is a specific module within the Cortex XDR agent settings designed to manage and restrict the use of peripheral devices.
Granular Management: It allows administrators to define policies for various device types, most commonly USB Storage devices. You can set these to 'Allow,' 'Block,' or 'Read-Only.'
Exclusions: Policies can be granular, allowing specific vendor IDs (VID) or product IDs (PID) while blocking all others.
Visibility: When a device is blocked, Cortex XDR generates a log entry, providing the SOC with visibility into who is attempting to use unauthorized hardware.
Which response action in Cortex XSIAM would be unavailable to a SOC analyst investigating an incident involving a Linux server?
Cortex XSIAM (and XDR) agents provide a wide array of response actions, but these capabilities vary based on the operating system of the endpoint.
File Search and Destroy: This specific automated management action---which allows an administrator to search for a file across multiple endpoints and delete it in one click---is currently supported for Windows and macOS endpoints. It is not a native automated response action for Linux in the same 'Search and Destroy' menu context.
Supported Linux Actions: * Live Terminal (B): Analysts can initiate a remote SSH-like session to Linux endpoints for manual investigation.
Running a Script (C): Analysts can execute Python scripts on Linux endpoints to gather data or perform custom remediation.
Halting Network Access (D): Also known as Endpoint Isolation, this allows the analyst to cut off all network traffic to the Linux server except for the connection to the Cortex console.
Which dashboard or module in Cortex XSIAM provides visibility into unmanaged devices, unauthorized shadow IT, and cloud assets that do not currently have a Cortex agent installed?
Cloud Discovery & Exposure (part of the broader Attack Surface Management/ASM capabilities in XSIAM) is designed to solve the problem of 'blind spots' in an organization's infrastructure.
Unmanaged Assets: While the Asset Inventory shows what is currently managed, Cloud Discovery looks for what isn't. It scans cloud environments (AWS, Azure, GCP) and public-facing IP ranges to find servers or storage buckets that were created without the security team's knowledge.
Risk Identification: It identifies assets that are missing the Cortex agent or have exposed ports (like RDP or SSH open to the internet), allowing the SOC to proactively secure the attack surface before an attacker finds the same vulnerabilities.
Paul Thompson
8 days agoHenrik Bernard
14 days agoRebecca Jackson
18 days agoCharles Collins
28 days agoThomas Young
1 month agoAditya Singh
2 months agoSarah Wright
2 months agoFrancesco Garcia
2 months agoThomas Petit
2 months agoBushra Choudhury
2 months agoJoseph White
3 months agoThomas Phillips
3 months agoAna Colombo
3 months agoVikram Reddy
3 months agoRohan Reddy
3 months agoPallavi Chopra
4 months agoCortex XDR Harris
4 months agoCortex XSOAR Anderson
3 months agoCortex XSIAM Harris
2 months agoHamza Mirza
4 months ago