---
title: Threat Intel Filebeat Module (v7.x) Indicator Match
description: This rule is triggered when indicators from the Threat Intel Filebeat module (v7.x) has a match against local file or network observations. Rule type:...
url: https://www.elastic.co/elastic/docs-builder/docs/3167/reference/security/prebuilt-rules/rules/_deprecated/threat_intel_filebeat7x
products:
  - Elastic Security
---

# Threat Intel Filebeat Module (v7.x) Indicator Match
<warning>
  This rule has been deprecated as of 2022/01/12.
</warning>

This rule is triggered when indicators from the Threat Intel Filebeat module (v7.x) has a match against local file or
network observations.
**Rule type**: threat_match
**Rule indices**:
- auditbeat-*
- endgame-*
- filebeat-*
- logs-*
- packetbeat-*
- winlogbeat-*

**Rule Severity**: critical
**Risk Score**: 99
**Runs every**: 1h
**Searches indices from**: `now-65m`
**Maximum alerts per execution**: 100
**References**:
- [[https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-threatintel.html](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-threatintel.html)](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-threatintel.html)

**Tags**:
- Elastic
- Windows
- Elastic Endgame
- Network
- Continuous Monitoring
- SecOps
- Monitoring

**Version**: 100
**Rule authors**:
- Elastic

**Rule license**: Elastic License v2

## Investigation guide


## Triage and Analysis


### Investigating Threat Intel Indicator Matches

Threat Intel indicator match rules allow matching from a local observation such as an endpoint event that records a file
hash with an entry of a file hash stored within the Threat Intel Filebeat module. Other examples of matches can occur on
an IP address, registry path, URL and imphash.
The matches will be based on the incoming feed data so it's important to validate the data and review the results by
investigating the associated activity to determine if it requires further investigation.
If an indicator matches a local observation, the following enriched fields will be generated to identify the indicator, field, and type matched.
- `threatintel.indicator.matched.atomic` - this identifies the atomic indicator that matched the local observation
- `threatintel.indicator.matched.field` - this identifies the indicator field that matched the local observation
- `threatintel.indicator.matched.type` - this identifies the indicator type that matched the local observation


#### Possible investigation steps:

- Investigation should be validated and reviewed based on the data (file hash, registry path, URL, imphash) that was matched
  and viewing the source of that activity.
- Consider the history of the indicator that was matched. Has it happened before? Is it happening on multiple machines?
  These kinds of questions can help understand if the activity is related to legitimate behavior.
- Consider the user and their role within the company, is this something related to their job or work function?


### False Positive Analysis

- For any matches found, it's important to consider the initial release date of that indicator. Threat intelligence can
  be a great tool for augmenting existing security processes, while at the same time it should be understood that threat
  intelligence can represent a specific set of activity observed at a point in time. For example, an IP address
  may have hosted malware observed in a Dridex campaign six months ago, but it's possible that IP has been remediated and
  no longer represents any threat.
- Adversaries often use legitimate tools as network administrators such as `PsExec` or `AdFind`, these tools often find their
  way into indicator lists creating the potential for false positives.
- It's possible after large and publicly written campaigns, curious employees might end up going directly to attacker infrastructure and generating these rules


### Response and Remediation

- If suspicious or malicious behavior is observed, immediate response should be taken to isolate activity to prevent further
  post-compromise behavior.
- One example of a response if a machine matched a command and control IP address would be to add an entry to a network
  device such as a firewall or proxy appliance to prevent any outbound activity from leaving that machine.
- Another example of a response with a malicious file hash match would involve validating if the file was properly quarantined,
  review current running processes looking for any abnormal activity, and investigating for any other follow-up actions such as persistence or lateral movement


## Rule Query

```kuery
file.hash.*:* or file.pe.imphash:* or source.ip:* or destination.ip:* or url.full:* or registry.path:*
```