Which action is performed as the final step of the NIST incident response plan?
Correct Answer: A
The final step in the NIST incident response plan is updating incident response procedures based on lessons learned from the incident.
Question 82
Which two statements apply to creating scripts in Cortex XSOAR? (Choose two.)
Correct Answer: B,D
Scripts in Cortex XSOAR can be scheduled to run at specific times and can execute with higher permissions to perform privileged actions.
Question 83
A Security Operations Analyst is reviewing a Cortex XDR incident involving a critical Windows server. The alert indicates 'Local Analysis- Malicious Executable' and 'Behavioral Threat Protection - Ransomware'. Upon initial investigation, it's clear the attacker attempted to execute a known ransomware variant that Cortex XDR successfully blocked. However, the analyst needs to confirm no residual threats exist and collect specific details about the blocked execution attempt, including the full command line, process ancestry, and any related file modifications, without directly accessing the server. What is the most comprehensive and efficient workflow within Cortex XDR to achieve this post-block forensic analysis?
Correct Answer: C
For deep post-block analysis of an alert within Cortex XDR, leveraging the built-in incident and endpoint telemetry is key. C: Incident Timeline and Causality Chain: This is the most comprehensive and efficient workflow within Cortex XDR. The 'Incident Timeline' provides a chronological view of all events related to an incident. The 'Causality Chain' is a powerful visualization that maps the relationships between processes, files, and network connections, clearly showing the parent-child relationships, command lines, and actions taken (like process creation, file modifications). Clicking on nodes in the causality chain reveals raw event details. For highly specific data points not immediately obvious, 'XDR Query' (or XQL) allows analysts to construct precise queries against the collected endpoint logs (which include process execution details, file events, etc.) to pull exactly what's needed. This allows for detailed forensic analysis without touching the endpoint. A: Alert details and Live Terminal: Alert details provide some information, but are often summarized. 'Live Terminal' is for active intervention or ad-hoc investigation, not for structured, historical forensic analysis, and directly accessing the server was explicitly excluded by the question. B: Endpoint details and Event Log: While useful, directly navigating the 'Event Log' for an endpoint can be overwhelming for a specific incident analysis. The 'Causality Chain' (Option C) provides a much more focused and intuitive view of the incident's relevant events. D: Collect Forensic Data (full image/memory dump): This is overkill for confirming a blocked execution and collecting specific details. Full disk images and memory dumps are resource-intensive and time-consuming to collect and analyze, typically reserved for deeper, complex investigations where the XDR telemetry is insufficient, or for court-ready evidence. The question asks for efficiency and specific details about the blocked attempt, which XDR's telemetry already provides. E: Threat Analysis report: While Cortex XDR provides significant context, it doesn't automatically generate a standalone 'Threat Analysis' report for every single blocked threat with all the specific details requested. The information is available, but it's distributed within the incident/endpoint telemetry that needs to be navigated, primarily through the causality chain and raw events.
Question 84
A sophisticated persistent threat (APT) actor establishes a foothold on a server via a supply chain compromise. Over several weeks, the actor performs reconnaissance, deploys custom malware, establishes C2 communication, and slowly exfiltrates data, interspersed with periods of inactivity. A single alert might not be triggered for each activity. From a Cortex XDR perspective, which of the following is the most effective approach for the SOC to detect and investigate this low-and-slow APT, primarily relying on Log Stitching's advanced capabilities?
Correct Answer: C
APT attacks are characterized by their stealth and multi-stage nature, often avoiding individual high-fidelity alerts. Log Stitching's strength here is its ability to connect subtle, low-fidelity events over long durations. By identifying the causal links and temporal relationships between unusual login attempts, specific process spawns, and intermittent C2 communications, Cortex XDR can stitch these seemingly innocuous events into a coherent, high-fidelity incident representing the full APT kill chain. Expanse integration further enriches this by providing external attack surface context. Options A, B, D, and E are insufficient or impractical for detecting such a sophisticated, low-and-slow threat.
Question 85
During a post-incident review of a ransomware attack, your team wants to understand how Cortex XSIAM's 'Attack Surface Management' (ASM) capabilities could have provided earlier detection or prevention. Specifically, which aspects of XSIAM's ASM would have been most valuable in identifying the initial weak point that allowed the ransomware to enter and spread, even if the primary alert was generated by behavioral detection?
Correct Answer: A
Cortex XSIAM's Attack Surface Management (ASM) is designed to proactively identify and manage external-facing risks. For a ransomware attack, the initial entry point is often through an exposed vulnerability or misconfiguration. Option A directly addresses this by stating ASM would highlight unpatched CVEs on internet-facing systems and identify unnecessary open ports/services, which are classic weak points for initial access. Option B describes post-compromise detection. Option C misrepresents ASM's purpose. Option D describes identity management, not ASM. Option E is too simplistic; ASM provides rich context beyond just software lists.