Threat Intel Concepts

Cortex XSOAR provides threat intelligence management. TIM concepts include fetch indicators, configure indicators, and export indicators. Threat intel management
Indicators are artifacts associated with incidents, and are an essential part of the incident management and remediation process.
These are the key concepts associated with threat intel management in Cortex XSOAR.

Fetch indicators

Cortex XSOAR includes integrations that fetch indicators from either a vendor-specific source, such as AutoFocus, or from a generic source, such as a CSV or JSON file.

Common indicator data model

When indicators are ingested, regardless of their source, they have a unified, common set of indicator fields, including traffic light protocol (TLP), expiration, reputation, and tags.

Indicator smart merge

The same indicator can originate from multiple sources and be enriched with multiple methods (integrations, scripts, playbooks, and so on). Cortex XSOAR implements a smart merge logic to make sure indicators are accurately scored (reputation) and aggregated.

Indicator timeline

The indicator timeline is in table format and displays an indicator’s complete history, including the first seen and last seen timestamp, changes made to indicator fields, and more.

Indicator expiration

When ingesting and processing millions of indicators on a daily basis, it’s important to control whether or not they are active or expired, and to define how and when indicators are expired. Cortex XSOAR offers multiple options to set indicator expiration.

Storing indicators

If you plan to ingest and process a large number of indicators, you should consider migrating to Elasticsearch.

Export indicators

You can export indicators as a hosted list, an EDL, or a TAXII collection. This enables your SIEM or firewall to ingest or pull the indicator list to update policy rules. The supported list file types are JSON, CSV, and TXT.

Exclusion list

Indicators added to the exclusion list are disregarded by the system, and are not created or involved in automated flows such as indicator extraction.

Feed-based job

You can define a job to trigger a playbook when the specified feed or feeds finish a fetch operation that included a modification to the list. The modification can be a new indicator, a modified indicator, or a removed indicator.

Recommended For You