|
| 1 | +--- |
| 2 | +title: Global Known-Good Indicators |
| 3 | +description: "Learn how Datadog-managed known-good indicators reduce false-positive threat intelligence matches in Cloud SIEM." |
| 4 | +further_reading: |
| 5 | +- link: /security/threat_intelligence/ |
| 6 | + tag: documentation |
| 7 | + text: Threat Intelligence |
| 8 | +- link: /security/cloud_siem/ingest_and_enrich/threat_intelligence/ |
| 9 | + tag: documentation |
| 10 | + text: Bring Your Own Threat Intelligence |
| 11 | +- link: /security/cloud_siem/triage_and_investigate/ioc_explorer/ |
| 12 | + tag: documentation |
| 13 | + text: IOC Explorer |
| 14 | +--- |
| 15 | + |
| 16 | +## Overview |
| 17 | + |
| 18 | +Datadog maintains a global list of known-good indicators for Cloud SIEM. These indicators identify infrastructure or artifacts that Datadog has determined should not be treated as threatening, even when they appear in a third-party threat intelligence feed. |
| 19 | + |
| 20 | +When an incoming log contains an exact match for a global known-good indicator, Cloud SIEM prevents that match from being treated as a threat intelligence finding. This reduces false positives from broadly benign infrastructure while preserving the original log for investigation. |
| 21 | + |
| 22 | +Global known-good indicators are managed by Datadog. You cannot add, remove, or configure these entries for your organization. |
| 23 | + |
| 24 | +## How global known-good indicators work |
| 25 | + |
| 26 | +**Flow**: Incoming log → global known-good check in Cloud SIEM log processing → threat intelligence enrichment → known-good matches are not treated as threat intelligence findings. |
| 27 | + |
| 28 | +Cloud SIEM evaluates global known-good indicators while it enriches incoming logs with threat intelligence: |
| 29 | + |
| 30 | +1. Cloud SIEM extracts supported indicators from the log. |
| 31 | +1. Cloud SIEM checks for an exact match against the Datadog-managed known-good list. |
| 32 | +1. If an indicator is known good, Cloud SIEM does not treat it as a threat intelligence finding. |
| 33 | +1. The original log remains available in Log Explorer for correlation and investigation. |
| 34 | + |
| 35 | +Global known-good indicators affect new logs after the list has propagated through Cloud SIEM processing. They do not change enrichment that was already stored on historical logs. |
| 36 | + |
| 37 | +## Supported indicators and matching |
| 38 | + |
| 39 | +Global known-good indicators support exact matches for: |
| 40 | + |
| 41 | +- IP addresses |
| 42 | +- Domains |
| 43 | +- SHA-256 file hashes |
| 44 | + |
| 45 | +The known-good list does not use partial domains, wildcard patterns, or CIDR ranges. |
| 46 | + |
| 47 | +## Use global known-good indicators during investigations |
| 48 | + |
| 49 | +Global known-good indicators reduce noise from known false-positive threat intelligence matches. They do not exclude logs from ingestion, retention, or other security analysis. |
| 50 | + |
| 51 | +Continue to investigate relevant log context, detections, and behavioral evidence. An indicator that is known good in one context can still be associated with suspicious activity in another context. |
| 52 | + |
| 53 | +For information about Datadog-curated threat intelligence, see [Threat Intelligence][1]. To add organization-managed threat intelligence, see [Bring Your Own Threat Intelligence][2]. |
| 54 | + |
| 55 | +## Further reading |
| 56 | + |
| 57 | +{{< partial name="whats-next/whats-next.html" >}} |
| 58 | + |
| 59 | +[1]: /security/threat_intelligence/ |
| 60 | +[2]: /security/cloud_siem/ingest_and_enrich/threat_intelligence/ |
0 commit comments