Indicator reputation affects how the indicator is processed and handled in Cortex XSOAR.
An indicator’s reputation is assigned according to the reputation returned by the source with the highest reliability. In cases where multiple sources with the same reliability score return a different reputation for the indicator, the worst reputation is taken.
Indicators are assigned a reputation on a scale of 0 to 3.
In this example, two 3rd-party integrations, VirusTotal and AlienVault, return a different reputation for the same indicator. VirusTotal returns a reputation of Good, and AlienVault returns a reputation of Bad. The indicator’s reputation will be Bad.
In this example, two sources with different reliability scores return a different reputation for the same indicator. The first source is a TAXII feed with a reliability score of C - Fairly reliable, and the second source is a CSV feed with a reliability score of B - Usually reliable. The TAXII feed returns a reputation of Bad and the CSV feed returns a reputation of Good. The indicator’s reputation will be Good because the CSV reliability score is higher than that of the TAXII feed.
The reliability of an intelligence-data source influences the reputation of an indicator and the values for indicator fields when merging indicators.
Indicator fields are merged according to the source reliability hierarchy. This means that when there are two different values for a single indicator field, the field will be populated with the value provided by the source with the highest reliability score.
In rare cases, two sources with the same reliability score might return different values for the same indicator field. In these cases, the field will be populated with the most recently provided source.
For the field types Tags and Multi-select, all values are appended, nothing is overridden.
A user manually updates the reputation of an indicator.
A script with the
reputationtag, which calculates the reputation of an indicator. For example, the
DataDomainReputationscript evaluates the reputation of a URL or domain.
An integration or service that evaluates the reputation of an indicator. For example, the
urlscan.iointegration evaluates the reputation of a URL.
A: Completely reliable
The feed reliability is applied at the integration instance level.
B: Usually reliable
C: Fairly reliable
D: Not usually reliable
F: Reliability cannot be judged
Indicators can have the status Active or Expired, which is determined by the
expirationStatusfield. When indicators expire, they still exist in Cortex XSOAR, meaning they are still displayed and you can still search for them. A job runs every hour to check for newly expired indicators.
By default, indicators are expired according to either the expiration interval configured for the indicator type to which the indicator belongs, or to never expire.
This is the hierarchy by which indicators are expired.
A user manually expires an indicator. This method overrides all other methods.
The expiration method configured for an integration instance, which overrides the method defined for the indicator type.
The expiration method defined for the indicator type to which this indicator belongs (interval or never). This is the default expiration method for an indicator.
Recommended For You
Recommended videos not found.