Skip to content

Commit 7ea6452

Browse files
committed
Add notes about Cloud SIEM admins
1 parent 8a1e414 commit 7ea6452

File tree

6 files changed

+72
-16
lines changed

6 files changed

+72
-16
lines changed

blog-service/2025-01-16-security.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,16 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
1111

1212
<a href="https://help.sumologic.com/release-notes-service/rss.xml"><img src={useBaseUrl('img/release-notes/rss-orange2.png')} alt="icon" width="50"/></a>
1313

14-
We’re excited to introduce Sumo Logic Threat Intelligence, a new feature set that enables you to seamlessly import threat intelligence indicator files directly into Sumo Logic to aid in security analysis. Sumo Logic Threat Intelligence will help you stay ahead of emerging threats and enhance your security posture.
14+
We’re excited to introduce Sumo Logic Threat Intelligence, a powerful feature set that enables you to seamlessly import threat intelligence indicator files directly into Sumo Logic to aid in security analysis. Threat intelligence indicators are individual data points about threats that are gathered from external sources about various entities such as host names, file hashes, IP addresses, and other known targets for compromise.
1515

16-
Threat intelligence indicators are individual data points about threats that are gathered from external sources about various entities such as host names, file hashes, IP addresses, and other known targets for compromise.
16+
To see threat intelligence indicators, go to **Manage Data > Logs > Threat Intelligence**. Once indicators are ingested and appear on the **Threat Intelligence** tab, you can use them to search logs for threats.
1717

18-
To see threat intelligence indicators, go to **Manage Data > Logs > Threat Intelligence**. Once you ingest indicators and they appear on the **Threat Intelligence** tab, you can use them to search logs for threats.
18+
Sumo Logic Threat Intelligence will help you stay ahead of emerging threats and enhance your security posture.
1919

2020
[Learn more](/docs/security/threat-intelligence/).
2121

22-
<img src={useBaseUrl('img/security/threat-intelligence-tab-example.png')} alt="Threat Intelligence tab" style={{border: '1px solid gray'}} width="800" />
22+
<img src={useBaseUrl('img/security/threat-intelligence-tab-example.png')} alt="Threat Intelligence tab" style={{border: '1px solid gray'}} width="800" />
23+
24+
:::note
25+
Only Cloud SIEM administrators can add threat intelligence indicators to the system. However, all Sumo Logic users can run queries against the indicators to uncover threats.
26+
:::

docs/integrations/security-threat-detection/threat-intel-quick-analysis.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,9 +27,11 @@ import AppInstall from '../../reuse/apps/app-install.md';
2727

2828
## Threat Intel optimization
2929

30-
The Threat Intel Quick Analysis app provides baseline queries. You can further optimize and enhance these queries for the log and events types being scanned for threats. Use the following guidelines to customize your threat intel queries:
30+
The app provides baseline queries that utilize the [`threatlookup` search operator](/docs/search/search-query-language/search-operators/threatlookup/) to look for threat intelligence data. To see the queries, open a [dashboard in the app](#viewing-threat-intel-quick-analysis-dashboards), click the three-dot kebab in the upper-right corner of the dashboard panel, and select **Open in Log Search**.
3131

32-
* Filter out unwanted logs before you use the [`threatlookup` search operator](/docs/search/search-query-language/search-operators/threatlookup/)
32+
You can further optimize and enhance these queries for the log and events types being scanned for threats. Use the following guidelines to customize your threat intel queries:
33+
34+
* Filter out unwanted logs before you use the `threatlookup` search operator
3335
* Use keywords
3436
* Use the `where` operator
3537
* Use general search optimization [rules](/docs/search/get-started-with-search/build-search/best-practices-search.md)
Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
:::note
2+
Only Cloud SIEM administrators can add threat intelligence indicators to the system. However, all Sumo Logic users can [run queries against threat intelligence indicators](/docs/security/threat-intelligence/find-threats/) to uncover threats.
3+
:::

docs/security/threat-intelligence/about-threat-intelligence.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,16 @@ description: Introduction to Sumo Logic's threat intelligence capabilities.
77

88
import useBaseUrl from '@docusaurus/useBaseUrl';
99
import Iframe from 'react-iframe';
10+
import CloudSIEMThreatIntelNote from '../../reuse/cloud-siem-threat-intelligence-note.md';
1011

1112
Threat intelligence, often abbreviated as *threat intel*, is information that helps you prevent or mitigate cyber attacks. *Threat intelligence indicators* are individual data points about threats that are gathered from external sources about various entities such as host names, file hashes, IP addresses, and other known targets for compromise. You can import files containing threat intelligence indicators directly into Sumo Logic to aid in security analysis.
1213

1314
Threat intelligence indicators can help security analysts leverage a large body of information to surface potential threats. For example, say that a threat intelligence database has an indicator that correlates a certain IP address with known malicious activity. Because of this correlation, analysts can assume log messages with that IP address are more likely to be part of a real cyber attack.
1415

1516
Once you [ingest indicators](#ingest-threat-intelligence-indicators) and they appear on the [Threat Intelligence tab](/docs/security/threat-intelligence/threat-intelligence-indicators/#threat-intelligence-tab), you can use them to search logs for threats. See [Find threats with log queries](/docs/security/threat-intelligence/find-threats/) to learn how.
1617

18+
<CloudSIEMThreatIntelNote/>
19+
1720
Watch this micro lesson to learn about Sumo Logic's threat intelligence features.
1821

1922
<Iframe url="https://www.youtube.com/embed/wQzprl93GU4?rel=0"
@@ -46,7 +49,6 @@ You do not need to be assigned these role capabilities to [find threats with log
4649
### Ingest threat intelligence indicators
4750

4851
To search logs that contain correlations to threat intelligence indicators, you must first ingest the indicators. You can ingest indicators using:
49-
* **The Threat Intelligence tab**. See [Add indicators in the Threat Intelligence tab](/docs/security/threat-intelligence/threat-intelligence-indicators/#add-indicators-in-the-threat-intelligence-tab).
5052
* **A collector**. See:
5153
* [CrowdStrike Threat Intel Source](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/crowdstrike-threat-intel-source)
5254
* [Intel471 Threat Intel Source](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/intel471-threat-intel-source)
@@ -58,14 +60,16 @@ To search logs that contain correlations to threat intelligence indicators, you
5860
* [uploadNormalizedIndicators API](https://api.sumologic.com/docs/#operation/uploadNormalizedIndicators)
5961
* [uploadCsvIndicators API](https://api.sumologic.com/docs/#operation/uploadCsvIndicators)
6062
* [uploadStixIndicators API](https://api.sumologic.com/docs/#operation/uploadStixIndicators)
63+
* **The Threat Intelligence tab**. See [Add indicators in the Threat Intelligence tab](/docs/security/threat-intelligence/threat-intelligence-indicators/#add-indicators-in-the-threat-intelligence-tab).
6164

6265
See [Upload formats](/docs/security/threat-intelligence/upload-formats/) for the format to use when uploading indicators using the **Threat Intelligence** tab or APIs.
6366

67+
<CloudSIEMThreatIntelNote/>
68+
6469
:::note
6570
* Sumo Logic's threat intelligence data store only ingests simple threat indicators, not complex indicators that outline a series of steps or entities that make up an attack. Nor does it ingest actors, malware, or other object types.
6671
* The limit of the number of indicators that can be uploaded in one API call is 100.
6772
* When you add indicators, the event is recorded in the Audit Event Index. See [Audit logging for threat intelligence](#audit-logging-for-threat-intelligence).
68-
6973
:::
7074

7175
## Typical workflow

docs/security/threat-intelligence/find-threats.md

Lines changed: 46 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ description: Perform searches to find matches to data in threat intelligence ind
77

88
import useBaseUrl from '@docusaurus/useBaseUrl';
99

10-
Once you [ingest threat intelligence indicators](/docs/security/threat-intelligence/about-threat-intelligence/#ingest-threat-intelligence-indicators), you can perform searches to find matches to data in the indicators using the `threatlookup` search operator.
10+
You can use the `threatlookup` search operator to find matches to indicators in the Sumo Logic [threat intelligence](/docs/security/threat-intelligence/) data store.
1111

12-
The `threatlookup` operator allows you to search logs for matches in threat intelligence indicators. For example, use the following query to find logs in all `sec_record*` indexes with a `srcDevice_ip` attribute correlated to a threat indicator with a high confidence level (greater than `50`):
12+
For example, use the following query to find logs in all `sec_record*` indexes with a `srcDevice_ip` attribute correlated to a threat indicator with a high confidence level (greater than `50`):
1313

1414
```
1515
_index=sec_record*
@@ -19,8 +19,51 @@ _index=sec_record*
1919
| count by _timeslice
2020
```
2121

22-
For more information, see [`threatlookup` search operator](/docs/search/search-query-language/search-operators/threatlookup/).
22+
For syntax and examples, see [`threatlookup` search operator](/docs/search/search-query-language/search-operators/threatlookup/).
2323

2424
<!-- Add this back once we have support for the cat search operator.
2525
You can also [run threatlookup with the cat search operator](/docs/search/search-query-language/search-operators/threatlookup/#run-threatlookup-with-the-cat-search-operator) to search the entire store of threat intelligence indicators.
2626
-->
27+
28+
## Threatlookup queries in dashboards
29+
30+
The `threatlookup` search operator is used for queries in some dashboards, including [dashboards in the Threat Intel Quick Analysis app](/docs/integrations/security-threat-detection/threat-intel-quick-analysis/#viewing-threat-intel-quick-analysis-dashboards). These queries provide great examples of how to use the operator.
31+
32+
To see `threatlookup` used in a query:
33+
1. Open the Threat Intel Quick Analysis app.
34+
1. Navigate to a dashboard, such as **Overview**.
35+
1. Click the three-dot kebab in the upper-right corner of the dashboard panel.
36+
1. Select **Open in Log Search**.
37+
1. Look for `threatlookup` used in a query.
38+
39+
For example, here is the query used for the **Threat Count** panel in the [Threat Intel Quick Analysis - IP](#ip) dashboard:
40+
41+
```
42+
_sourceCategory=<source-category-name>
43+
| parse regex "(?<ip_address>\b\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3})"
44+
| where ip_address != "0.0.0.0" and ip_address != "127.0.0.1"
45+
| count as ip_count by ip_address
46+
47+
| threatlookup singleIndicator ip_address
48+
49+
// normalize confidence level to a string
50+
| if (_threatlookup.confidence >= 85, "high", if (_threatlookup.confidence >= 50, "medium", if (_threatlookup.confidence >= 15, "low", if (_threatlookup.confidence >= 0, "unverified", "unknown")))) as threat_confidence
51+
52+
// filter for threat confidence
53+
| where threat_confidence matches "*"
54+
55+
//rename to match threat_<foo> convention
56+
| %"_threatlookup.actors" as threat_actors
57+
| %"_threatlookup.type" as type
58+
| %"_threatlookup.threat_type" as threat_type
59+
60+
//convert threat valid from to human readable time
61+
| toLong(%"_threatlookup.valid_from" * 1000) as %"_threatlookup.valid_from"
62+
| formatDate(%"_threatlookup.valid_from", "MM-dd-yyyy") as threat_valid_from
63+
64+
| where type matches "ipv4-addr*" and !isNull(threat_confidence)
65+
66+
| if (isEmpty(threat_actors), "Unassigned", threat_actors) as threat_actors
67+
68+
|sum (ip_count) as threat_count
69+
```

docs/security/threat-intelligence/threat-intelligence-indicators.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ description: Learn how to add and manage indicators from threat intelligence sou
66
---
77

88
import useBaseUrl from '@docusaurus/useBaseUrl';
9+
import CloudSIEMThreatIntelNote from '../../reuse/cloud-siem-threat-intelligence-note.md';
910

1011
The **Threat Intelligence** tab shows the indicators that have been added to your threat intelligence data store. Use this tab to add and manage your threat intelligence indicators. You can add indicators from a number of sources, including TAXII, ThreatQ, iDefense, and many others. Threat intelligence indicators imported to Sumo Logic not only integrate with your existing core Sumo Logic deployment, but also Cloud SIEM and Cloud SOAR.
1112

@@ -19,7 +20,6 @@ You can also add threat intelligence indicators using a collector or the API. Se
1920

2021
[**New UI**](/docs/get-started/sumo-logic-ui/). To access the **Threat Intelligence** tab, in the top menu select **Configuration**, and then under **Logs** select **Threat Intelligence**. You can also click the **Go To...** menu at the top of the screen and select **Threat Intelligence**.
2122

22-
2323
<img src={useBaseUrl('img/security/threat-intelligence-tab.png')} alt="Threat Intelligence tab" style={{border: '1px solid gray'}} width="800" />
2424

2525
1. **+ Add Indicators**. Click to upload files that [add threat intelligence indicators](#add-indicators-in-the-threat-intelligence-tab).
@@ -36,16 +36,16 @@ You can also add threat intelligence indicators using a collector or the API. Se
3636

3737
## Add indicators in the Threat Intelligence tab
3838

39-
To add threat intelligence indicators in the **Threat Intelligence** tab, you must upload files containing the indicators in a format that can be consumed by Sumo Logic.
39+
You can add threat intelligence indicators using a collector, API, or the **Threat Intelligence** tab. This section describes how to add indicators in the **Threat Intelligence** tab. For information on the other methods, see [Ingest threat intelligence indicators](/docs/security/threat-intelligence/about-threat-intelligence/#ingest-threat-intelligence-indicators).
40+
41+
<CloudSIEMThreatIntelNote/>
4042

4143
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic/).In the main Sumo Logic menu, select **Manage Data > Logs > Threat Intelligence**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui/). In the top menu select **Configuration**, and then under **Logs** select **Threat Intelligence**. You can also click the **Go To...** menu at the top of the screen and select **Threat Intelligence**.
4244
1. Click **+ Add Indicators**. The dialog displays. <br/><img src={useBaseUrl('img/security/threat-intelligence-add-indicators.png')} alt="Add threat intelligence indicators" style={{border: '1px solid gray'}} width="500" />
43-
1. Select the format of the file to be uploaded:
45+
1. Select the format of the file to be uploaded (see [Upload formats](/docs/security/threat-intelligence/upload-formats/) for the format to use in the file):
4446
* **Normalized JSON**. A normalized JSON file.
4547
* **CSV**. A comma-separated value (CSV) file.
4648
* **STIX 2.x JSON**. A JSON file in STIX 2.x format. When choosing this format, you must enter the name of the source in the **Source** field provided.
47-
48-
See [Upload formats](/docs/security/threat-intelligence/upload-formats/) for the format to use in the file.
4949
1. Click **Upload** to upload the file.
5050
1. Click **Import**.
5151

0 commit comments

Comments
 (0)