Indicator Type Profile - Threat Intel Management Guide - 6.5 - Cortex XSOAR - Cortex - Security Operations

Cortex XSOAR Threat Intel Management Guide

Cortex XSOAR
Creation date
Last date published
Threat Intel Management Guide

Each indicator type has its own 'profile' that allows XSOAR to recognize it across the platform. Below are the related fields. During the auto-extract flow, the order of execution is regex, formatting script, reputation command, reputation script.




A meaningful name for the indicator type.


The regular expression (regex) by which to identify indicators for this indicator type.

Formatting Script

Modifies how the indicator displays in Cortex XSOAR.

Formatting scripts must be tagged indicator-format in order to appear in the dropdown for the indicator type.

Reputation Command

Calculates the reputation of indicators of this type. The verdict (reputation) is only associated with the specific indicator on which it’s run (not the indicator type). The command returns the reputation of the indicator as an entry with entry context and in some cases also returns context values that can be mapped to the custom fields of the indicator. The results of the reputation command do not print to the war room in the auto-extract flow.


Select the Indicator Layout.

Reputation Script

The output of the reputation script is a verdict score, which is used as the basis for the indicator verdict. Reputation scripts must be tagged reputation in order to appear in the dropdown for the indicator type.

The results of reputation scripts do not print to the war room in the extraction flow.

Enhancement Script

The enhancement script is not part of the indicator extraction flow, and are run manually on the indicator type. For example, domain reputation, email reputation, parse email files, etc.

After indicators are identified, you can go to the indicator quick view, click the Actions button and run an enhancement script directly on an indicator. In order for these scripts to be available in the drop-down menu, they need the enhancement tag.

When you run an enhancement script, it is the equivalent of running the script at the CLI in the War Room. The script can write to context, return an entry, etc.

Excluded these Integrations for the reputation command

Integrations to exclude when calculating the verdict, evaluating, and enriching indicators of this indicator type. Only applies to the indicator extraction and enrichment mechanism, does not apply when directly running reputation commands such as !ip, !url, !domain, etc.

Indicator Expiration Method

The method by which to expire indicators of this type. The expiration method that you select is the default expiration method for indicators of this indicator type.

The expiration can also be assigned when configuring a feed integration instance, which overrides the default method.

  • Never Expire: indicators of this type never expire.

  • Time Interval: indicators of this type expire after the specified number of days or hours.

Context path for verdict value (Advanced)

When an indicator is extracted, the entry data from the command is mapped to the incident context. This path defines where in context the data is mapped.

Context value of verdict (Advanced)

The value of this field defines the actual data that is mapped to the context path.

Cache expiration in minutes (Advanced)

The amount of time (in minutes) after which the cache for indicators of this type expire. The default is 4,320 minutes (three days). The cache enables you to limit API requests by only updating indicators after a specific time period has passed. The cache can not be cleared manually.


Indicator cache expiration rules only apply to automatic enrichment, triggered by the enrichIndicators command. If you run reputation commands, such as !ip, the commands will execute and the indicator will be updated if there is new information, even if the cache has not expired.