|
| 1 | +--- |
| 2 | +title: Threat Intelligence |
| 3 | +disable_toc: false |
| 4 | +further_reading: |
| 5 | +- link: "security/cloud_siem/detection_rules" |
| 6 | + tag: "Documentation" |
| 7 | + text: "Create custom detection rules" |
| 8 | +--- |
| 9 | + |
| 10 | +## Overview |
| 11 | + |
| 12 | +Datadog provides built-in [threat intelligence][1] for Cloud SIEM logs. This article explains how to extend that functionality by enriching logs with your own custom threat intelligence feeds. |
| 13 | + |
| 14 | +## Bring your own threat intelligence |
| 15 | + |
| 16 | +Cloud SIEM supports enriching and searching logs using threat intelligence indicators of compromise (IOCs) stored in Datadog reference tables. [Reference Tables][7] allow you to combine metadata with information already in Datadog. |
| 17 | + |
| 18 | +### Storing indicators of compromise in reference tables |
| 19 | + |
| 20 | +Threat intelligence is supported in the CSV format, and requires a table for each Indicator type (for example, IP address) and requires the following columns: |
| 21 | + |
| 22 | +#### CSV structure for IP address |
| 23 | + |
| 24 | +| Field | Data | Description | Required | Example | |
| 25 | +|-------------------|-------|-------------------------------------------------------------------------------------------------|----------|----------------------------------| |
| 26 | +| ip_address | text | The primary key for the reference table in the IPv4 dot notation format. | true | 192.0.2.1 | |
| 27 | +| additional_data | json | Additional data to enrich the logs. | false | `{"ref":"hxxp://example.org"}` | |
| 28 | +| category | text | The threat intel [category][8]. This is used by some out-of-the-box detection rules. | true | Malware | |
| 29 | +| intention | text | The threat intel [intent][9]. This is used by some out-of-the-box detection rules. | true | malicious | |
| 30 | +| source | text | The name of the source and the link to its site, such as your team and your team's wiki. | true | `{"name":"internal_security_team", "url":"https://teamwiki.example.org"}` | |
| 31 | + |
| 32 | +<div class="alert alert-info">JSON in a CSV requires double quoting. The following is an example CSV.</div> |
| 33 | + |
| 34 | +``` |
| 35 | +ip_address,additional_data,category,intention,source |
| 36 | +192.0.2.1,"{""ref"":""hxxp://example.org""}",scanner,suspicious,"{""name"":""internal_security_team"", ""url"":""https://teamwiki.example.org""}" |
| 37 | +192.0.2.2,"{""ref"":""hxxp://example.org""}",scanner,suspicious,"{""name"":""internal_security_team"", ""url"":""https://teamwiki.example.org""}" |
| 38 | +192.0.2.3,"{""ref"":""hxxp://example.org""}",scanner,suspicious,"{""name"":""internal_security_team"", ""url"":""https://teamwiki.example.org""}" |
| 39 | +``` |
| 40 | + |
| 41 | +### Uploading and enabling your own threat intelligence |
| 42 | + |
| 43 | +Datadog supports creating reference tables either by a manual upload or by periodically retrieving the data from Amazon S3, Azure storage, or Google Cloud storage. |
| 44 | + |
| 45 | +**Notes**: |
| 46 | +- It can take 10 to 30 minutes to start enriching Logs after creating a table. |
| 47 | +- If a primary key is duplicated, it is skipped and an error message about the key is displayed. |
| 48 | + |
| 49 | +On a new [reference table][2] page: |
| 50 | + |
| 51 | +1. Name the table. The table name is referenced in the Threat Intelligence setting. |
| 52 | +1. Upload a local CSV or import a CSV from a cloud storage bucket. The file is normalized and validated. |
| 53 | +1. Preview the table schema and choose the IOC column as the Primary Key. |
| 54 | +1. Save the table. |
| 55 | +1. In [Threat Intel][3], locate the new table and toggle it on to enable it. |
| 56 | + |
| 57 | +#### Using cloud storage |
| 58 | + |
| 59 | +When the reference table is created from cloud storage, it is refreshed periodically. The entire table is replaced. Data is not merged. |
| 60 | + |
| 61 | +See the related reference table documentation for: |
| 62 | + |
| 63 | +- [Amazon S3][4] |
| 64 | +- [Azure storage][5] |
| 65 | +- [Google Cloud storage][6] |
| 66 | + |
| 67 | +#### Troubleshooting cloud imports |
| 68 | + |
| 69 | +If a reference table is not refreshing, open the reference table's settings menu and select **View Change Events**. |
| 70 | + |
| 71 | +**View Change Events** opens a page in **Event Management** showing potential error events for the ingestion. You can also filter in **Event Management** using the reference table name. |
| 72 | + |
| 73 | +In Datadog Event Management, it may appear that data has been fetched from the cloud, but it can take a few additional minutes for those changes to propagate to Threat Intelligence. Other useful cloud import details to remember: |
| 74 | + |
| 75 | +- The expected latency before updated enrichments are available when a source is uploaded or updated is 10 to 30 minutes. |
| 76 | +- How to know when the updates are applied: The changes are visible in the reference table or in the logs. Select the **View Change Events** link from settings on the reference table detail page to see the related events. |
| 77 | +- The update replaces the entire table with the new data. |
| 78 | +In case of a duplicated primary key, the rows with the duplicated key are not written, and an error is shown in the reference table detail page. |
| 79 | + |
| 80 | +## Threat intelligence in the user interface |
| 81 | + |
| 82 | +To enable Cloud SIEM threat intelligence data for reference tables: |
| 83 | +1. Navigate to [Threat Intelligence][3]. |
| 84 | +1. For the table you want to see Cloud SIEM threat intelligence data, click the dropdown menu in the **Enabled** column and select Cloud SIEM. |
| 85 | + |
| 86 | +After applying a reference table to Cloud SIEM, all incoming logs are evaluated against the table using a specific Indicator of Compromise (IoC) key, such as an IP address. If a match is found, the log is enriched with relevant Threat Intelligence (TI) attributes from the table, which enhances detection, investigation, and response. |
| 87 | + |
| 88 | +A threat intelligence reference table can be shared across multiple security products. |
| 89 | + |
| 90 | +## Further reading |
| 91 | + |
| 92 | +{{< partial name="whats-next/whats-next.html" >}} |
| 93 | + |
| 94 | +[1]: /security/threat_intelligence/#threat-intelligence-sources |
| 95 | +[2]: https://app.datadoghq.com/reference-tables/create |
| 96 | +[3]: https://app.datadoghq.com/security/configuration/threat-intel |
| 97 | +[4]: /reference_tables/?tab=amazons3#create-a-reference-table |
| 98 | +[5]: /reference_tables/?tab=azurestorage#create-a-reference-table |
| 99 | +[6]: /reference_tables/?tab=googlecloudstorage#create-a-reference-table |
| 100 | +[7]: /reference_tables/ |
| 101 | +[8]: /security/threat_intelligence/#threat-intelligence-categories |
| 102 | +[9]: /security/threat_intelligence/#threat-intelligence-intents |
0 commit comments