elastic / elastic/detection-rules
[New Rule] GreyNoise IP Address IOC Correlation
- Dominant language
- Python
- Stars
- 2.7k
- Forks
- 696
- Avg merge
- 4d 17h
- Merged PRs (30d)
- 87
Description
### Description
This rule aims to correlate IP addresses found in event data with GreyNoise threat intelligence indicators to identify potentially malicious or suspicious activity. The rule avoids matching against GreyNoise’s own logs (`event.module: "ti_greynoise"`) to ensure external observations are flagged.
### Rule Configuration
**Source Custom Query**
`NOT event.module : "ti_greynoise"`
**Indicator Index Patterns**
`logs-ti_greynoise_latet.ip*`
**Indicator Index Query**
`@timestamp >= "now-7d/d"`
**Indicator Mapping**
| Field | Indicator index field |
|-------------------|------------------------|
| `source.ip` | `threat.indicator.ip` |
| `destination.ip` | `threat.indicator.ip` |
**Required Fields**
`threat.indicator.ip`
**Indicator Prefix Override**
`greynoise.ip`
**Related Integration**
`GreyNoise`
**Tags**
```
[
"IP Address IOC",
"Elastic",
"Threat Intelligence",
"GreyNoise"
]
```
### Target Ruleset
threat_intel
### Target Rule Type
Indicator Match
### Tested ECS Version
8.17.0
### Query
_No response_
### New fields required in ECS/data sources for this rule?
_No response_
### Related issues or PRs
_No response_
### References
_No response_
### Redacted Example Data
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.