A critical server in your environment is suspected of being compromised. You observe unusual outbound connections to a public cloud IP range not typically used by your organization. However, the connections are to common ports (e.g., 443, 80). Cortex XDR has not flagged these as malicious, but your threat intelligence suggests this IP range has recently been associated with command and control (C2) infrastructure. You need to leverage Cortex XDR to confirm the C2, identify the associated process, and understand the data exfiltration attempt. Which of the following Cortex XDR capabilities would you utilize in conjunction to effectively hunt for and confirm this sophisticated C2 activity, even if it's currently evading standard detections?
Correct Answer: B
Option B is the most effective and sophisticated approach for proactive threat hunting when standard detections are not triggering. XQL is paramount for flexible, ad-hoc querying across diverse telemetry (network, process, etc.) to specifically look for the suspicious IP range and correlate it with endpoint activities. Once a process is identified, analyzing its 'Causality Chain' in XDR Pro Analytics provides the full context of its execution. 'Live Terminal' then allows for deep, real-time inspection of the live process, memory, and network connections, which is crucial for confirming C2 and data exfiltration, especially if no files are involved. Option A is reactive and might miss the process. Option C is too broad and relies on passive monitoring. Option D is an external control and doesn't leverage XDRs hunting capabilities. Option E is insufficient, as the C2 might not involve new executables, and 'Threat Intelligence Management' might not immediately reflect this specific, nuanced C2.
Question 72
A security incident involving a suspected insider threat is being investigated. The incident response lead wants to ensure that all actions taken within the War Room are transparent, auditable, and attributable to specific team members. Furthermore, sensitive information shared (e.g., internal IP addresses, employee IDs) must be handled securely within the War Room environment. How does Cortex XSOAR's War Room inherently address these requirements, and what features contribute to this?
Correct Answer: B
Option B accurately describes how Cortex XSOAR's War Room inherently addresses transparency, auditability, and secure handling of sensitive data. Every action in the War Room is meticulously logged with user and timestamp details, providing a complete audit trail. XSOAR's robust Role-Based Access Control (RBAC) is critical for managing who can access or modify specific incident data, including sensitive information. Integration with secure credential management systems further enhances the security posture by preventing hardcoding of sensitive credentials within playbooks or scripts. The platform's design ensures that all collaboration and data exchange within the War Room environment are auditable and secure.
Question 73
During a red team exercise, an attacker successfully bypassed the organization's EDR by exploiting a zero-day vulnerability in a popular browser, then used an undocumented technique to perform process hollowing and inject shellcode into a legitimate system process. The EDR, relying on known signatures and common behavioral patterns, missed this highly evasive attack. Which specific characteristic of Cortex XDR's detection engine, as part of its 'Prevention First' approach, would have been most likely to detect and prevent such an advanced, evasive threat, even without a prior signature?
Correct Answer: B
This scenario describes a highly evasive, zero-day attack designed to bypass typical EDRs. Cortex XDR's 'Prevention First' approach goes beyond just signatures and common behavioral patterns. Option B accurately describes its multi-layered, AI-driven detection engine. Behavioral Threat Protection (BTP) identifies anomalous process behavior (like process hollowing or injection) even if the specific malware is unknown. Machine learning analyzes file characteristics (static analysis) and execution behavior to detect polymorphic or custom malware without relying on signatures. This combination is designed to catch sophisticated, evasive threats that a standard EDR, often more reliant on known indicators, would miss.
Question 74
A global financial institution uses Cortex XSIAM to monitor its highly regulated environment. They have a strict policy that no agents can be installed on certain legacy critical production servers due to vendor support agreements. However, network-level visibility for these servers is still required for compliance and threat detection. Furthermore, the institution heavily relies on Microsoft 365 for collaboration and email. Which Cortex XSIAM sensor types would be best suited to address these specific requirements, and what data would they ingest?
Correct Answer: A
Given the constraint of 'no agents on legacy critical production servers,' Network Sensors become the primary solution for gaining visibility into these systems. They can passively collect network flow data (NetFlow/lPFlX) or even full packet captures (if deployed strategically via SPAN/TAP ports) without installing any software on the servers themselves. For Microsoft 365, Cloud Sensors (specifically API integrations with Microsoft Graph Security API or similar) are designed to ingest audit logs, security events, and activity data directly from the M365 platform. This combination directly addresses both challenges.
Question 75
An organization relies heavily on Palo Alto Networks Cortex XSOAR for security orchestration, automation, and response. A major incident involving ransomware has encrypted critical data across multiple departments. During the eradication phase, the incident response team needs to deploy a custom script to remove persistence mechanisms left by the ransomware and distribute a decryption tool. This script needs to run on hundreds of affected endpoints. Which XSOAR playbook command or integration would be most suitable and efficient for this task, ensuring proper execution and feedback?
Correct Answer: D
Option D is the most suitable and efficient. XSOAR excels at automating tasks across a large number of endpoints. The '!exec- remote-command' (or similar endpoint-management integration command, depending on the specific endpoint integration) allows for remote execution of scripts on designated systems, which is exactly what's needed for eradication. Option A is for communication. Option B is for incident creation, not execution. Option C shows a generic API call, but without a specific integration handling 'endpoint.execute_script' , it's not as direct as 'exec-remote-command'. Option E is highly inefficient and impractical for hundreds of endpoints.