Skip to content

Commit 44c8256

Browse files
committed
Add SentinelOne and Signal Sciences
1 parent d410d0a commit 44c8256

File tree

3 files changed

+38
-124
lines changed

3 files changed

+38
-124
lines changed

docs/cse/ingestion/ingestion-sources-for-cloud-siem/palo-alto-firewall.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,8 +13,7 @@ To ingest Palo Alto Firewall data into Cloud SIEM:
1313
1. [Configure a Syslog source](/docs/send-data/installed-collectors/sources/syslog-source/#configure-a-syslog-source) on a collector. When you configure the source, do the following:
1414
1. Click the **+Add Field** link, and add a field whose name is `_siemForward` and value is *true*. This will ensure all logs for this source are forwarded to Cloud SIEM.
1515
1. Add another field named `_parser` with value */Parsers/System/Palo Alto/PAN Firewall CSV*. This ensures that the Palo Alto Firewall logs are parsed and normalized into structured records in Cloud SIEM.
16-
1. Define destination for the logs. <br/>In this step you create a server profile where you can define the log destination. This will be the host name, port and protocol (TLS) of the Sumo Logic Cloud Syslog source.
17-
<br/>To create a server profile specifying the log destination, do the following:
16+
1. Create a server profile to define the log destination. The profile will contain the host name, port and protocol (TLS) of the Sumo Logic Cloud syslog source:
1817
1. Login to the Palo Alto Networks Web interface as an administrative user.
1918
1. Select **Device** tab > **Server Profiles** > **Syslog**.
2019
1. Click **Add** at the bottom of the screen and provide endpoint details and a profile name, such as `Sumo_Logs_Profile01`.
Lines changed: 12 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -1,64 +1,23 @@
11
---
22
id: sentinelone
3-
title: SentinelOne - Cloud SIEM
3+
title: Ingest SentinelOne Data into Cloud SIEM
44
sidebar_label: SentinelOne
55
description: Learn how to collect SentinelOne log messages and send them to Sumo Logic to be ingested by Cloud SIEM.
66
---
77

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

10-
This section has instructions for collecting SentinelOne log messages for CEF and Syslog ingest and sending them to Sumo Logic to be ingested by Cloud SIEM.
10+
This article has instructions for collecting SentinelOne log messages for CEF and Syslog ingest and sending them to Sumo Logic to be ingested by Cloud SIEM. (To collect data such as activities, agents, and threats, use the [SentinelOne Mgmt API Source](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/sentinelone-mgmt-api-source/).)
1111

12-
To collect data such as activities, agents, and threats, use the [SentinelOne Mgmt API Source](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/sentinelone-mgmt-api-source/).
13-
14-
## Step 1: Configure collection
15-
16-
In this step, you configure a Cloud Syslog Source to collect SentinelOne log messages. You can configure the source on an existing Hosted Collector or create a new collector. If you’re going to use an existing collector, jump to [Configure a Cloud Syslog Source](#configure-a-cloud-syslog-source) below. Otherwise, create a new collector as described in [Configure a Hosted Collector](#configure-a-hosted-collector) below, and then create the Cloud Syslog Source on the collector.
17-
18-
### Configure a Hosted Collector
19-
20-
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**.
21-
1. Click **Add Collector**.
22-
1. Click **Hosted Collector.**
23-
1. The **Add Hosted Collector** popup appears. <br/><img src={useBaseUrl('img/cse/add-hosted-collector.png')} alt="Add hosted collector" style={{border: '1px solid gray'}} width="500"/>
24-
1. **Name**. Provide a Name for the Collector.
25-
1. **Description**. (Optional)
26-
1. **Category**. Enter a string to tag the output collected from the source. The string that you supply will be saved in a metadata field called `_sourceCategory`
27-
1. **Fields**
28-
1. If you are planning that all the sources you add to this collector will forward log messages to Cloud SIEM, click the **+Add Field** link, and add a field whose name is `_siemForward` and value is *true*. This will cause the collector to forward all of the logs collected by all of the sources on the collector to Cloud SIEM.
29-
1. If all sources in this collector will be Sentinel One sources, add an additional field with key `_parser`; set the value to:
30-
* */Parsers/System/SentinelOne/SentinelOne CEF* if your logs are in CEF format.
31-
* */Parsers/System/SentinelOne/SentinelOne Syslog* if your logs are in Syslog format.
32-
33-
### Configure a Cloud Syslog Source
34-
35-
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**
36-
1. Navigate to the Hosted Collector where you want to create the source.
37-
1. On the **Collectors** page, click **Add Source** next to the Hosted
38-
Collector.
39-
1. Select **Cloud Syslog**
40-
1. The page refreshes. <br/><img src={useBaseUrl('img/cse/cloud-syslog-source.png')} alt="Cloud syslog source" style={{border: '1px solid gray'}} width="500"/>
41-
1. **Name**. Enter a name for the source. 
42-
1. **Description**. (Optional) 
43-
1. **Source Host**. (Optional) Enter a string to tag the messages collected from the source. The string that you supply will be saved in a metadata field called `_sourceHost`.
44-
1. **Source Category**. Enter a string to tag the output collected from the source. The string that you supply will be saved in a metadata field called `_sourceCategory`. Make a note of the source category. You’ll supply it in Step 2 below.
45-
1. **Fields**
46-
1. If you have not configured the Installed Collector to forward all sources in the collector to Cloud SIEM, click the **+Add Field** link, and add a field whose name is `_siemForward `and value is *true*.
47-
1. If you have not configured the collector to parse all sources in the collector with the same parser, click the **+Add Field** link, and add a field whose name is `_parser`; set the value to:
12+
To ingest SentinelOne data into Cloud SIEM:
13+
1. [Configure a Syslog source](/docs/send-data/installed-collectors/sources/syslog-source/#configure-a-syslog-source) on a collector. When you configure the source, do the following:
14+
1. Click the **+Add Field** link, and add a field whose name is `_siemForward` and value is *true*. This will ensure all logs for this source are forwarded to Cloud SIEM.
15+
1. To ensure that the SentinelOne logs are parsed and normalized into structured records in Cloud SIEM, add another field whose name is `_parser` and set the value to:
4816
* */Parsers/System/SentinelOne/SentinelOne CEF* if your logs are in CEF format.
4917
* */Parsers/System/SentinelOne/SentinelOne Syslog* if your logs are in Syslog format.
50-
1. Click **Save**.
51-
1. Make a note of the **Token** and **Host** that are displayed. You’ll supply them in [Step 2](#step-2-configure-sentinelone) below.
52-
53-
## Step 2: Configure SentinelOne
54-
55-
In this step you configure SentinelOne to send log messages to the Sumo Logic platform. If you have a SentinelOne account, you can follow directions on the SentinelOne Support [knowledge base](https://support.sentinelone.com/hc/en-us/articles/360007044894-Syslog-Integration-with-Sumo-Logic), or the instructions in Step 2 of [Collecting Logs for SentinelOne](/docs/send-data/collect-from-other-data-sources/collect-logs-sentinelone/#step-2-configure-syslog-messages) topic.
56-
57-
## Step 3: Verify ingestion
58-
59-
In this step, you verify that your logs are successfully making it into Cloud SIEM. 
60-
61-
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the top menu select **Configuration**, and then under **Incoming Data** select **Log Mappings**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Cloud SIEM Integrations** select **Log Mappings**. You can also click the **Go To...** menu at the top of the screen and select **Log Mappings**.
62-
1. On the **Log Mappings** tab search for "SentinelOne" and check the **Records** columns.
63-
1. For a more granular look at the incoming records, you can also use the Sumo Logic platform to search for SentinelOne security records.<br/><img src={useBaseUrl('img/cse/sentinelone-search.png')} alt="SentinelOne search" style={{border: '1px solid gray'}} width="400"/>
64-
 
18+
1. Make a note of the **Source Category**, **Token**, and **Host** that are displayed in the configuration UI. You’ll supply them in the next step.
19+
1. Configure SentinelOne to send log messages to the Sumo Logic platform. If you have a SentinelOne account, you can follow directions on the SentinelOne Support [knowledge base](https://support.sentinelone.com/hc/en-us/articles/360007044894-Syslog-Integration-with-Sumo-Logic), or the instructions in [Step 2 of the *Collecting Logs for SentinelOne* article](/docs/send-data/collect-from-other-data-sources/collect-logs-sentinelone/#step-2-configure-syslog-messages).
20+
1. To verify that your logs are successfully making it into Cloud SIEM:
21+
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the top menu select **Configuration**, and then under **Incoming Data** select **Log Mappings**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Cloud SIEM Integrations** select **Log Mappings**. You can also click the **Go To...** menu at the top of the screen and select **Log Mappings**.
22+
1. On the **Log Mappings** tab search for "SentinelOne" and check the **Records** columns.
23+
1. For a more granular look at the incoming records, you can also use the Sumo Logic platform to search for SentinelOne security records.<br/><img src={useBaseUrl('img/cse/sentinelone-search.png')} alt="SentinelOne search" style={{border: '1px solid gray'}} width="400"/>
Lines changed: 25 additions & 69 deletions
Original file line numberDiff line numberDiff line change
@@ -1,77 +1,33 @@
11
---
22
id: signal-sciences-waf
3-
title: Signal Sciences WAF - Cloud SIEM
3+
title: Ingest Signal Sciences WAF Data into Cloud SIEM
44
sidebar_label: Signal Sciences WAF
55
description: Lean how to collect Signal Sciences WAF log messages and sending them to Sumo Logic to be ingested by Cloud SIEM.
66
---
77

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

10-
This section has instructions for collecting Signal Sciences WAF log messages and sending them to Sumo Logic to be ingested by Cloud SIEM.
11-
12-
## Step 1: Configure collection
13-
14-
In this step, you configure an HTTP Source to collect Signal Sciences WAF log messages. You can configure the source on an existing Hosted Collector or create a new collector. If you’re going to use an existing collector, jump to [Configure an HTTP Source](#configure-an-http-source) below. Otherwise, create a new collector as described in [Configure a hosted collector](#configure-a-hosted-collector) below, and then create the HTTP Source on the collector.
15-
16-
### Configure a Hosted Collector
17-
18-
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**.
19-
1. Click **Add Collector**.
20-
1. Click **Hosted Collector.**
21-
1. The **Add Hosted Collector** popup appears. <br/><img src={useBaseUrl('img/cse/add-hosted-collector.png')} alt="Add hosted collector" style={{border: '1px solid gray'}} width="500"/>
22-
1. **Name**. Provide a Name for the Collector.
23-
1. **Description**. (Optional)
24-
1. **Category**. Enter a string to tag the output collected from the source. The string that you supply will be saved in a metadata field called `_sourceCategory`.
25-
1. **Fields**. If you are planning that all the sources you add to this collector will forward log messages to Cloud SIEM, click the **+Add Field** link, and add a field whose name is `_siemForward` and value is *true*. This will cause the collector to forward all of the logs collected by all of the sources on the collector to Cloud SIEM.
26-
:::note
27-
It’s also possible to configure individual sources to forward to Cloud SIEM, as described in the following section.
28-
:::
29-
30-
### Configure an HTTP Source
31-
32-
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Manage Data > Collection > Collection**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Data Collection** select **Collection**. You can also click the **Go To...** menu at the top of the screen and select **Collection**.
33-
1. Navigate to the Hosted Collector where you want to create the source.
34-
1. On the **Collectors** page, click **Add Source** next to a Hosted Collector.
35-
1. Select **HTTP Logs & Metrics**
36-
1. The page refreshes. <br/><img src={useBaseUrl('img/cse/http-source.png')} alt="HTTP source" style={{border: '1px solid gray'}} width="600"/>
37-
1. **Name**. Enter a name for the source. 
38-
1. **Description**. (Optional) 
39-
1. **Source Host.** (Optional) Enter a string to tag the messages collected from the source. The string that you supply will be saved in a metadata field called `_sourceHost.`
40-
1. **Source Category**. Enter a string to tag the output collected from the source. The string that you supply will be saved in a metadata field called `_sourceCategory`. Make a note of the source category. You’ll supply it in [Step 2](#step-2-configure-signal-sciences-waf) below.
41-
1. **SIEM Processing.** Click the checkbox to configure the source to forward log messages to Cloud SIEM.
42-
1. **Advanced Options for Logs**. For information about the optional advance options you can configure, see [HTTP Logs and Metrics Source](/docs/send-data/hosted-collectors/http-source/logs-metrics/).
43-
1. Click **Save**.
44-
1. Make a note of the HTTP Source URL that is displayed. You’ll supply it in [Step 2](#step-2-configure-signal-sciences-waf) below.
45-
46-
## Step 2: Configure Signal Sciences WAF
47-
48-
In this step you configure Signal Sciences WAF to send log messages to the Sumo Logic platform.
49-
50-
1. Go to the **SigSci Site Tools > Integrations** in the **SigSci** dashboard.
51-
1. Click **Add** for **Generic Webhook**.
52-
1. Paste the HTTP Source URL from the previous step into the **Webhook URL** field and click **Add**.
53-
54-
For more information on Generic Webhooks refer to the [Generic Webhooks](https://docs.fastly.com/signalsciences/integrations/generic-webhooks/) page in Fastly help.
55-
56-
## Step 3: Cloud SIEM Ingest Configuration
57-
58-
In this step, you configure a Sumo Logic Ingest Mapping in Cloud SIEM for the source category assigned to your source or collector you configured in [Step 1](#step-1-configurecollection). The mapping tells Cloud SIEM the information it needs to select the right mapper to process messages that have been tagged with that source category. 
59-
60-
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the top menu select **Configuration**, and then under **Integrations** select **Sumo Logic**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Cloud SIEM Integrations** select **Ingest Mappings**. You can also click the **Go To...** menu at the top of the screen and select **Ingest Mappings**.
61-
1. On the **Ingest Mappings** tab, click **+ Add Ingest Mapping**.
62-
1. On the **Add Ingest Mapping** popup:
63-
* **Source Category**. Enter the category you assigned to the HTTP Source or Hosted Collector in [Step 1](#step-1-configurecollection)
64-
* **Format**. Enter *JSON.*
65-
* **Vendor**. Enter *SignalSciences*.
66-
* **Product**. Enter *WAF*
67-
* **Event ID**. Enter *.\**
68-
1. Click **Create** to save the mapping.
69-
70-
## Step 4: Verify ingestion
71-
72-
In this step, you verify that your logs are successfully making it into Cloud SIEM. 
73-
74-
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the top menu select **Configuration**, and then under **Incoming Data** select **Log Mappings**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Cloud SIEM Integrations** select **Log Mappings**. You can also click the **Go To...** menu at the top of the screen and select **Log Mappings**.
75-
1. On the **Log Mappings** page search for "Signal Sciences" and check the **Records** columns. <br/><img src={useBaseUrl('img/cse/signal-sciences-record-volume.png')} alt="Signal Sciences record volume" style={{border: '1px solid gray'}} width="800"/>
76-
1. For a more granular look at the incoming records, you can also search the Sumo Logic platform for Signal Sciences WAF security records.
77-
 
10+
To ingest Signal Sciences data into Cloud SIEM:
11+
1. [Configure an HTTP Logs and Metrics source](/docs/send-data/hosted-collectors/http-source/logs-metrics/#configure-an-httplogs-and-metrics-source) on a collector. When you configure the source, do the following:
12+
1. Select the **Forward to SIEM** option in the source configuration UI. This will ensure all logs for this source are forwarded to Cloud SIEM.
13+
1. Make note of the **Source Category**. You'll supply it in a later step.
14+
1. After saving the source, click the **Show URL** link and make note of the HTTP source URL. You'll supply it in a later step.
15+
1. Configure Signal Sciences WAF to send log messages to the Sumo Logic platform:
16+
1. Go to the **SigSci Site Tools > Integrations** in the **SigSci** dashboard.
17+
1. Click **Add** for **Generic Webhook**.
18+
1. Paste the HTTP source URL from the previous step into the **Webhook URL** field and click **Add**.
19+
For more information on Generic Webhooks refer to the [Generic Webhooks](https://docs.fastly.com/signalsciences/integrations/generic-webhooks/) page in Fastly help.
20+
1. Configure a Sumo Logic Ingest Mapping in Cloud SIEM for the source category assigned to the source. The mapping tells Cloud SIEM the information it needs to select the right mapper to process messages that have been tagged with that source category. 
21+
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the top menu select **Configuration**, and then under **Integrations** select **Sumo Logic**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Cloud SIEM Integrations** select **Ingest Mappings**. You can also click the **Go To...** menu at the top of the screen and select **Ingest Mappings**.
22+
1. On the **Ingest Mappings** tab, click **+ Add Ingest Mapping**.
23+
1. On the **Add Ingest Mapping** popup:
24+
* **Source Category**. Enter the category you assigned to the HTTP source you created earlier. 
25+
* **Format**. Enter *JSON.*
26+
* **Vendor**. Enter *SignalSciences*.
27+
* **Product**. Enter *WAF*
28+
* **Event ID**. Enter *.\**
29+
1. Click **Create** to save the mapping.
30+
1. To verify that your logs are successfully making it into Cloud SIEM:
31+
1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the top menu select **Configuration**, and then under **Incoming Data** select **Log Mappings**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the top menu select **Configuration**, and then under **Cloud SIEM Integrations** select **Log Mappings**. You can also click the **Go To...** menu at the top of the screen and select **Log Mappings**.
32+
1. On the **Log Mappings** page search for "Signal Sciences" and check the **Records** columns. <br/><img src={useBaseUrl('img/cse/signal-sciences-record-volume.png')} alt="Signal Sciences record volume" style={{border: '1px solid gray'}} width="800"/>
33+
1. For a more granular look at the incoming records, you can also search the Sumo Logic platform for Signal Sciences WAF security records.

0 commit comments

Comments
 (0)