During an investigation of an alert with a completed playbook, it is determined that no indicators exist from the email "indicator@test.com" in the Key Assets & Artifacts tab of the parent incident. Which command will determine if Cortex XSIAM has been configured to extract indicators as expected?
The correct answer is C, the !checkIndicatorExtraction text='indicator@test.com' command.
This command specifically verifies if Cortex XSIAM has been correctly configured to extract indicators from given text. It ensures that the text provided ('indicator@test.com') would indeed be recognized and extracted as an indicator under the current configuration of Cortex XSIAM.
Other provided commands do not directly verify the indicator extraction configuration:
Option A: IcreateNewIndicator manually creates an indicator; it does not validate extraction capability.
Option B: !extractIndicators attempts extraction immediately but does not verify existing configuration explicitly.
Option D: Iemailvalue command is generally for creating or querying email indicators, not verifying extraction configuration.
Therefore, the explicit functionality for checking if indicator extraction is configured correctly within Cortex XSIAM is precisely covered by !checkIndicatorExtraction.
Reference Extract from Official Document:
'Verify if Cortex XSIAM is correctly configured to extract indicators using the command !checkIndicatorExtraction text=<value>.'
This exact description confirms that option C is the correct answer to validate the configuration explicitly.
Which feature terminates a process during an investigation?
The correct answer is B -- Live Terminal.
In Cortex XSIAM, the Live Terminal feature allows analysts to initiate an interactive command-line session with an endpoint directly from the management console. During an investigation, analysts can use Live Terminal to issue commands---including those that terminate suspicious or malicious processes running on the endpoint.
'Live Terminal provides analysts with a direct command line on the endpoint, enabling actions such as process termination during investigations.'
Document Reference: XSIAM Analyst ILT Lab Guide.pdf
Exact Page: Page 15 (Endpoints section)
How would Incident Context be referenced in an alert War Room task or alert playbook task?
The correct answer is A -- ${parentIncidentContext}.
This syntax is the correct variable for referencing the incident context within playbook and War Room tasks, enabling data to be accessed from the parent incident during alert investigation or automation steps.
''Use ${parentIncidentContext} in War Room and playbook tasks to reference the context of the parent incident.''
Document Reference: EDU-270c-10-lab-guide_02.docx (1).pdf
Page: Page 39 (Incident Handling and Playbook Automation section)
===========
What is the cause when alerts generated by a correlation rule are not creating an incident?
The correct answer is A -- The rule is configured with alert severity below Medium.
By default, in Cortex XSIAM, only alerts with a severity of Medium or higher will automatically generate incidents. If a correlation rule creates alerts with severity set below Medium (such as Low or Informational), these alerts will not result in the automatic creation of an incident. This ensures that incident queues are not filled with low-priority events.
'Incidents are generated only for alerts with severity of Medium or higher. Alerts below this threshold will not automatically create incidents.'
Document Reference: XSIAM Analyst ILT Lab Guide.pdf
Page: Page 28 (Alerting and Detection section)
===========
SCENARIO:
A security analyst has been assigned a ticket from the help desk stating that users are experiencing errors when attempting to open files on a specific network share. These errors state that the file format cannot be opened. IT has verified that the file server is online and functioning, but that all files have unusual extensions attached to them.
The security analyst reviews alerts within Cortex XSIAM and identifies malicious activity related to a possible ransomware attack on the file server. This incident is then escalated to the incident response team for further investigation.
Upon reviewing the incident, the responders confirm that ransomware was successfully executed on the file server. Other details of the attack are noted below:
* An unpatched vulnerability on an externally facing web server was exploited for initial access
* The attackers successfully used Mimikatz to dump sensitive credentials that were used for privilege escalation
* PowerShell was used on a Windows server for additional discovery, as well as lateral movement to other systems
* The attackers executed SystemBC RAT on multiple systems to maintain remote access
* Ransomware payload was downloaded on the file server via an external site "file io"
QUESTION STATEMENT:
Which forensics artifact collected by Cortex XSIAM will help the responders identify what the attackers were looking for during the discovery phase of the attack?
The correct answer is D -- Shell history.
The Shell history artifact provides a detailed record of commands executed during interactive shell sessions (such as via PowerShell or command prompt) on Windows and Linux systems. Reviewing this artifact enables responders to reconstruct the attacker's activity during the discovery phase, showing exactly what directories, files, and commands were accessed or run, and what the attackers were searching for.
'The Shell history artifact allows responders to see what commands were executed during the attack, providing insight into attacker intent and discovery activities.'
Document Reference: XSIAM Analyst ILT Lab Guide.pdf
Page: Page 46 (Incident Handling section, Causality and Forensics)
Youlanda
3 days agoZona
11 days agoGerald
18 days agoRaul
25 days agoRaina
1 month agoChandra
1 month agoCraig
2 months agoMattie
2 months agoReed
2 months agoYolande
2 months agoGregg
3 months agoLorrie
3 months agoAudry
3 months agoBlondell
3 months agoChu
3 months agoKiley
4 months agoAnnelle
4 months agoWalker
4 months ago