Cortex XSOAR concepts, including incidents, integrations, playbooks, scripts, commands, war room, indicators, playground.
It is important to familiarize yourself with Cortex XSOAR components, UI terminology, and key concepts.
All Cortex XSOAR content is organized in packs. Packs are groups of artifacts that implement use cases in the product. Content packs are created by Palo Alto Networks, technology partners, consulting companies, MSSPs, customers, and individual contributors. Content packs may include a variety of different components, such as integrations, scripts, playbooks, and widgets.
Incidents are potential security data threats that SOC administrators identify and remediate. There are several incident triggers, including:
Security alerts from third-party services, such as SIEM, mail boxes, data in CSV format, or from the API
Cortex XSOAR includes several out-of-the-box incident types, and users can add custom incident types with custom fields, as necessary.
Incident fields are used for accepting or populating incident data. You create incident fields to hold information received from third-party integrations, manual input, or via the API.
You can define integrations with your third-party security and incident management vendors. You can then trigger events from these integrations that become incidents. Once the incidents are created, you can run playbooks on these incidents to enrich them with information from other products in your system, which helps you complete the picture. In most cases, you can use rules and scripts to determine if an incident requires further investigation or can be closed based on the findings. This enables your analysts to focus on the minority of incidents that require further investigation.
Marketplace is the central location for installing, exchanging, contributing, and managing all of your content, including playbooks, integrations, scripts, fields, layouts, and more.
The Marketplace allows you to:
Leverage content from the Cortex XSOAR community: Continuously extend Cortex XSOAR with proven use cases contributed by SecOps users and Cortex XSOAR partners.
Discover top rated, validated content: Identify the best content offerings recommended by your peers and validated by the world’s leading cybersecurity company. Discover how to increase automation with the tools you already have and browse through community best practices.
Solve your toughest security use cases: Deploy turn-key security workflows that span integrations, playbooks, dashboard layouts, and reports with a single click.
Updating Marketplace Content
When a content pack is available for update, you see an Updates waiting in Marketplace notification in the side menu. You can update to the latest content version or to a specific version. All dependent content packs update automatically with the content pack. We recommend periodically reviewing your installed Marketplace packs for any available updates, and updating, as required.
Integrations are third-party tools and services that the Cortex XSOAR platform works with to orchestrate and automate SOC operations.
Cortex XSOAR 8 currently does not support the IoT Security Third-party Integrations Add-on. For more information, see the IoT Security documentation.
In addition to third-party tools, you can create your own integration using the Bring Your Own Integration (BYOI) feature.
The following lists some of the integration categories available in Cortex XSOAR. The list is not exhaustive, and highlights the main categories:
Analytics and SIEM
Data Enrichment & Threat Intelligence
Forensics and Malware Analysis
A configuration of an integration. You can have multiple instances of an integration, for example, to connect to different environments. If you are an MSSP and have multiple tenants, you can configure a separate instance for each tenant.
Playbooks are self-contained, fully documented prescriptive procedures that query, analyze, and take action based on the gathered results. Playbooks enable you to organize and document security monitoring, orchestration, and response activities. There are several out-of-the-box playbooks that cover common investigation scenarios. You can use these playbooks as-is, or customize them according to your requirements. Playbooks are written in YAML file format using the COPS standard.
A key feature of playbooks is the ability to structure and automate security responses, which were previously handled manually. You can reuse playbook tasks as building blocks for new playbooks, saving you time and streamlining knowledge retention.
Scripts can access all Cortex XSOAR APIs, including access to incidents, investigations, share data to the War Room, and so on. Scripts can receive and access arguments, and you can password protect scripts.
The Scripts section includes a Script Helper, which provides a list of available commands and scripts, ordered alphabetically.
Cortex XSOAR has two types of commands:
System commands - Commands that enable you to perform Cortex XSOAR operations, such as clearing the playground or closing an incident. These commands are not specific to an integration. System commands are entered in the command line using a
External commands - Integration-specific commands that enable you to perform actions specific to an integration. For example, you can quickly check the reputation of an IP address. External commands are entered in the command line using a
!. For example,
The different commands and playbook tasks are tied together by the Cortex XSOAR context. Every incident and playbook has a place to store data called the context. The context stores the results from every integration command and every automation script that is run. It is a JSON storage for each incident. Whether you run an integration command from the CLI or from a playbook task, the output result is stored into the JSON context in the incident or the playground. For example, the command
!whois query="paloaltonetworks.com" returns the data and stores the results into the context.
The War Room is a collection of all investigation actions, artifacts, and collaboration pieces for an incident. It is a chronological journal of the incident investigation. You can run commands and playbooks from the War Room and filter the entries for easier viewing.
Indicators and Indicator Types
DBot can simplify your incident investigation process by collecting and analyzing information and artifacts found in War Room entries. Cortex XSOAR analyzes indicators to determine whether they are malicious. Using indicator types reveals predefined, regular expressions in the War Room.
Hits are indicators that are determined to have a malicious verdict, and were previously identified in the network. The verdict is the indicator's level of maliciousness, determined manually or by hypersearch scripts. If a hypersearch script identifies an indicator, the source is DBot.
There are many out-of-the-box indicator types, but you can add custom indicator types as necessary. The following is a list of some of the indicator types, but the list is not exhaustive:
IP address (IP4, IP6)
File hash (SHA-1, MD5)
When you add an indicator type, you can add formatting, enhancement and reputation scripts, as well as reputation commands. Formatting scripts modify how the indicator displays in the War Room and reports. Enhancement scripts enable you to gather additional data about the highlighted entry in the War Room. Reputation scripts calculate the reputation score for an entry that DBot analyzed, for example,
DataIPReputation, which calculates the reputation of an IP address. Reputation commands (such as
!ip for IP addresses) are an alternate way to calculate an indicator’s reputation score (verdict) and gather additional data about the indicator. Reputation commands and reputation scripts are executed when enriching a specific indicator type (for example, when the indicator is extracted from an incident).
The Playground is a non-production environment where you can safely develop and test scripts, APIs, commands, and more. It is an investigation area that is not connected to a live (active) investigation.
To erase a playground and create a new one, in the Cortex XSOAR CLI run the
You can create scheduled events using jobs. Jobs are triggered either by time-triggered events or feed-triggered events. For example, you can define a job to trigger a playbook when a specified TIM feed finishes a fetch operation that included a modification to the list.