Skip to content

Commit fc673ae

Browse files
jpipkin1kimsauce
andauthored
Update docs/security/threat-intelligence/threat-intelligence-vendor-switch.md
Co-authored-by: Kim (Sumo Logic) <[email protected]>
1 parent e7513bc commit fc673ae

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/security/threat-intelligence/threat-intelligence-vendor-switch.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,11 +26,11 @@ Beginning April 1, 2025, customers can experiment with the Intel 471 feed by ref
2626

2727
Sumo Logic's native security applications will be updated to support this vendor change. To take advantage of the new Intel 471 feed, customers only need to update queries in their custom apps by April 30, 2025. For examples of queries using the `lookup` operator, see the dashboards in the [Threat Intel Quick Analysis](/docs/integrations/security-threat-detection/threat-intel-quick-analysis/#threat-intel-optimization) app.
2828

29-
## How do I know if I ought to update a search or dashboard?
29+
## How do I know if I need to update a search or dashboard?
3030

31-
If you reference `json field=raw` or `parse field=raw` (or `raw_threat`, in the case of the `threatip` operator), you are extracting vendor-specific data that might need to be updated.
31+
If your queries reference `json field=raw` or `parse field=raw` (or `raw_threat`, in the case of the `threatip` operator), you are extracting vendor-specific data that might need to be updated.
3232

33-
Additionally, the Intel 471 source at present includes no domain or email indicators, instead prioritizing IP addresses, URLs, and file hashes.
33+
Additionally, the Intel 471 source currently does not include domain or email indicators, instead prioritizing IP addresses, URLs, and file hashes.
3434

3535
## How can I translate CrowdStrike-specific fields to Intel 471-specific fields?
3636

0 commit comments

Comments
 (0)