Rapid7 Threat Command CVEs Correlation
This rule is triggered when CVEs collected from the Rapid7 Threat Command Integration have a match against vulnerabilities that were found in the customer environment.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Log source category
- event_index
MITRE ATT&CK mappings
Not mapped to ATT&CK.
References
| Reference | Cited by |
|---|---|
| docs.elastic.co/integrations/ti_rapid7_threat_command | Only this detection cites it |
| www.elastic.co/guide/en/beats/filebeat/current/filebeat-module-threatintel.html | 9 |
From the source
- At source
- Open at source
- Upstream identifier
- 3a657da0-1df2-11ef-a327-f661ea17fbcc
- Tagged by the source as
- Data Source: Elastic EndgameData Source: NetworkData Source: Rapid7 Threat CommandData Source: WindowsOS: WindowsResources: Investigation GuideRule Type: Threat MatchUse Case: Asset VisibilityUse Case: Continuous MonitoringUse Case: Vulnerability
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Aug 27, 2026
- Version
- 1