Skip to content

Commit fb434f9

Browse files
Update solutions/security/get-started/enable-threat-intelligence-integrations.md
1 parent 0aa12e8 commit fb434f9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

solutions/security/get-started/enable-threat-intelligence-integrations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ There are a few scenarios when data won’t display in the Threat Intelligence v
7474
## Add a custom integration [custom-ti-integration]
7575

7676
1. Set up a way to [ingest data](ingest-data-to-elastic-security.md) into your system.
77-
2. Update the `securitySolution:defaultThreatIndex` [advanced setting](../../../solutions/security/get-started/configure-advanced-settings.md#update-threat-intel-indices) by adding the appropriate index pattern name after the default {{fleet}} threat intelligence index pattern (`logs-ti*`), for example, `logs-ti*`,`custom-ti-index*`.
77+
2. Update the `securitySolution:defaultThreatIndex` [advanced setting](configure-advanced-settings.md#update-threat-intel-indices) by adding the appropriate index pattern name after the default {{fleet}} threat intelligence index pattern (`logs-ti*`), for example, `logs-ti*`,`custom-ti-index*`.
7878

7979
::::{note}
8080
Threat intelligence indices aren’t required to be ECS compatible. However, we strongly recommend compatibility if you’d like your alerts to be enriched with relevant threat indicator information. You can find a list of ECS-compliant threat intelligence fields at [Threat Fields](https://www.elastic.co/guide/en/ecs/{{ecs_version}}/ecs-threat.html).

0 commit comments

Comments
 (0)