Use the War Room for real-time investigation into an incident, to filter war room entries, and to disable indicator notifications.
Within Cortex XSOAR, real-time investigation is facilitated through the War Room, which is powered by ChatOps and helps analysts to do the following:
Run real-time security actions through the CLI, without switching consoles.
Run security playbooks, scripts and commands.
Collaborate and execute remote actions across integrated products.
Capture incident context from different sources.
Document all actions in one source.
Converse with others for joint investigations.
Cortex XSOAR also provides machine learning insights to suggest the most effective analysts and command-sets. Each incident has a unique War Room.
To access the War Room:
If you have an Admin role, click Playground in My Incidents on the sidebar.
ctrl + alt + kand then
Type any command in the CLI at the bottom of the page.
When you open the War Room, you can see a number of entries such as commands, notes, evidence, tasks, etc., in several formats such as Markdown, HTML and so on. When Markdown, HTML or geographical information is received the content is displayed in the relevant format.
You can do the following actions for each artifact entry.
You can edit, format or delete your own entries. If an entry has been changed, a History link will appear where you can view all changes to the entry.
Mark as Evidence
Opens the Mark as evidence window where you specify the evidence details to be saved in the Evidence Board. The Evidence Board stores key artifacts for current and future analysis. You can add evidence in the Case Info tab, the Evidence Board, or the War Room.
Mark as note
Marks the incident as note. Notes can help the analyst understand why certain action was taken and assists future decisions. You can add them also in the Case Info tab.
View artifact in new tab
Opens a new tab for the artifact.
Detach from task
Removes a task from the artifact.
Attach to a task
Adds a task to the artifact.
Downloads an artifact according to the entry type, such txt files for text, json for a JSON entry, etc.
Add any relevant tags to use, which helps you find relevant information.
You can run various commands in the CLI, by typing the following:
!: Integration commands, scripts, and built-in commands. For example, add evidence, assign an analyst, etc.
/: System commands/operations. For example, add notes, close an investigation, etc.
@: User tagging. Send notifications to administrators, teams, analysts, etc.
You can edit incidents, create a report, add child incidents, and so on, as described in Incident Actions.
You can add any filter by selecting the checkbox. The following are the types of War Room entities by which you can filter:
Commands and playbook tasks
Entry IDs are used to uniquely identify War Room entries in Cortex XSOAR. Entry IDs take the format
<ENTRY_IDENTIFER>@<INCIDENT_ID>, for example,
54925dc3-a972-4489-8bef-793331fa6c77@1. Many out-of-the-box commands and scripts use entry IDs arguments to pass in files as inputs. To find the entry ID of an entry in the War Room, click on the vertical ellipsis icon at the upper right of the entry, then copy the ID value.
Cortex XSOAR does not index notes, chats, and pinned as evidence entries.