You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We’re excited to introduce [autosave for playbooks](/docs/platform-services/automation-service/automation-service-playbooks/#autosave), a feature designed to make workflow changes seamless by automatically saving your progress as draft and preventing accidental data loss. Here's what's new:
21
+
* Playbooks now automatically save your changes, including node updates, connections, and position adjustments.
22
+
* Multiple changes made in quick succession are saved together to improve performance.
23
+
* Visual indicators display the saving status whether in progress, successfully saved, or failed.
24
+
* Warnings appear when users attempt to close or navigate away from a playbook with unsaved changes.
25
+
* Users can enable or disable auto-save as needed.
26
+
27
+
##### AuditService:
28
+
29
+
* Removed the `Body` field from the email audit log to enhance security and optimize log storage
30
+
31
+
#### Bug Fixes
32
+
33
+
* Playbooks:
34
+
* Fixed granular field path drill-down in textArea for arrays with array output fields.
35
+
* Resolved issue where the Authorizer value in playbook action nodes was not persisting on the UI.
Copy file name to clipboardExpand all lines: docs/cse/administration/create-use-network-blocks.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,13 +50,14 @@ When Cloud SIEM looks for the network block address `10.128.0.1`, it will ret
50
50
51
51
Follow these instructions to create a network block using the Cloud SIEM UI. For information about creating multiple network blocks by file upload, see [Upload a CSV file of network blocks](#upload-a-csv-file-of-network-blocks).
52
52
53
-
1.[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the top menu select **Content > Network Blocks**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Cloud SIEM > Network Blocks**. You can also click the **Go To...** menu at the top of the screen and select **Network Blocks**.
54
-
1. On the **Create Network Block** popup:
53
+
1.[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the top menu select **Content > Network Blocks**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Cloud SIEM > Network Blocks**. You can also click the **Go To...** menu at the top of the screen and select **Network Blocks**.
54
+
1. Click **Add Network Block**.
55
+
1. On the **Add Network Block** popup:
55
56
1.**Address Block**. Enter a CIDR block that identifies a contiguous range of IP addresses.
56
57
1.**Label**. Enter a meaningful name for the network block.
57
58
1.**Internal**. Leave the toggle switched to the right (green) if you want to mark IP addresses that match the network block as Internal. This allows you to filter on the IP addresses in rule expressions, as described below in [Using enrichment fields](#using-enrichment-fields), below.
58
59
1.**Suppress Signals**. Leave the toggle switched to the left (red) if you do not want to suppress signals on IP addresses in the network block. Otherwise, switch the toggle to the right (green).
Copy file name to clipboardExpand all lines: docs/cse/get-started-with-cloud-siem/intro-for-analysts.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -400,7 +400,7 @@ But what if you want to be alerted right away when a certain rule is triggered?
400
400
You want to be alerted right away when your new custom match rule is triggered. Create a custom insight that looks for only this rule.
401
401
402
402
1.[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the top menu, select **Content > Custom Insights**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Cloud SIEM > Custom Insights**. You can also click the **Go To...** menu at the top of the screen and select **Custom Insights**.
403
-
1. Click **Create**.
403
+
1. Click **Add Custom Insight**.
404
404
1. Give your custom insight a name.
405
405
1. Under **When Signals are created from the following** select **rules**.
406
406
1. In **Type to add a rule**, search for the rule you created in [Write a match rule](#write-a-match-rule) and add it to your custom insight.
Copy file name to clipboardExpand all lines: docs/cse/match-lists-suppressed-lists/suppressed-lists.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,11 +14,11 @@ Cloud SIEM supports several types of [signal suppression](/docs/cse/records-sign
14
14
15
15
You can create suppressed lists from the Cloud SIEM UI or using the Cloud SIEM API. A suppressed list can contain a set of indicators—IPs, hostnames, or any other type that you can use in a match list—and then any signal that has a record containing a listed indicator will be suppressed.
Note that the list has a **Target Column**, which you define when you create the list. The target column indicates what type of record fields should be compared to the suppressed list, for example, hostnames, URLs, domains, IP addresses, usernames, and so on. For more information, see [How are suppressed lists used](#how-are-suppressed-lists-used).
21
+
Note that each suppressed list has a **Target Column**, which you define when you create the list. The target column indicates what type of record fields should be compared to the suppressed list, for example, hostnames, URLs, domains, IP addresses, usernames, and so on. For more information, see [How are suppressed lists used](#how-are-suppressed-lists-used).
22
22
23
23
When you create a suppressed list, you can choose one of the following as its target column.
24
24
@@ -75,24 +75,24 @@ A suppressed list can contain up to 50,000 items.
75
75
Perform the steps below to create a suppressed list and add an indicator to it using the Cloud SIEM UI.
76
76
77
77
1.[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the top menu select **Content > Suppressed Lists**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Cloud SIEM > Suppressed Lists**. You can also click the **Go To...** menu at the top of the screen and select **Suppressed Lists**.
1. On the **Add Suppressed List** popup, enter the following:
80
80
1.**Name**. Name of the suppressed list.
81
81
1.**Description**. Enter a description for the list.
82
-
1.**Time to Live (hours)**. (Optional) Enter the number of hours after which the entries on the list should expire.
83
82
1.**Target Column**. The type of record field to which items on the list should be compared.
84
83
:::note
85
84
If you want to create a custom target column, click **Manage Custom Columns**. For more information, see [Custom Match List Columns](/docs/cse/match-lists-suppressed-lists/custom-match-list-columns).
86
85
:::
87
-
1. Click **Create**.
86
+
1. **Time to Live (hours)**. (Optional) Enter the number of hours after which the entries on the list should expire.
87
+
1. Click **Save**.
88
88
1. The suppressed list now appears on the **Suppressed Lists** page.
89
89
1. Click the name of the suppressed list to open it.
90
-
1. On the **Suppressed List > Details** page, click **Add List Item**. <br/><img src={useBaseUrl('img/cse/add-list-item.png')} alt="Add list item" style={{border: '1px solid gray'}} width="800"/>
91
-
1. On the **New Suppressed List Item** popup, enter:
90
+
1. On the **Suppressed List > Details** page, click **Add Suppressed List Item**. <br/><img src={useBaseUrl('img/cse/add-list-item.png')} alt="Add list item" style={{border: '1px solid gray'}} width="800"/>
91
+
1. On the **Add Suppressed List Item** popup, enter:
92
92
1.**Value**. The value of the entity. Make sure the value you enter is of the same type as the type you selected as the target column for the list. For example, if the target column is Domain, enter a domain.
93
93
1.**Description**. (Optional) Enter a description of the list item.
94
94
1.**Expiration**. (Optional) The date and time at which the list item should be removed from the list.
95
-
1. Click **Add** to add the item to the list.
95
+
1. Click **Save** to add the item to the list.
96
96
1. The item now appears on the list.
97
97
98
98
## Import a list of indicators
@@ -127,7 +127,7 @@ specified:
127
127
### Upload file
128
128
129
129
1. On the **Suppressed Lists** page, click the name of the list.
130
-
1. Click **Import Indicators**.
130
+
1. Click **Import Items**.
131
131
1. On the import popup:
132
132
1. Drag your file onto the import popup, or click to navigate to the file, and then click Import.
133
133
1. Optionally, you can enter an expiration for the indicators on the list. If you do, it will override any expirations that are defined in the file. Enter the expiration in any ISO date format. For example: `2022-12-31`
Copy file name to clipboardExpand all lines: docs/cse/records-signals-entities-insights/configure-custom-insight.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ When the conditions of a custom insight configuration are met during the current
30
30
To create a custom insight:
31
31
32
32
1.[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the top menu, select **Content > Custom Insights**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Cloud SIEM > Custom Insights**. You can also click the **Go To...** menu at the top of the screen and select **Custom Insights**.
33
-
2. Click **Create** on the **Custom Insights** page.
33
+
2. Click **Add Custom Insight** on the **Custom Insights** page.
34
34
3. The **Configure the Custom Insight** popup appears. <br/><img src={useBaseUrl('img/cse/custom-insight.png')} alt="Configure an insight" style={{border: '1px solid gray'}} width="600"/>
35
35
4. In the **Name** field, enter a name for the custom insight.
36
36
5. If you want the custom insight to be generated based on one or more rules firing signals, jump to step 6, below. Otherwise:
Copy file name to clipboardExpand all lines: docs/cse/records-signals-entities-insights/tags-insights-signals-entities-rules.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,9 +87,8 @@ Note that in addition to tags that you manually assign to an insight, an insight
87
87
### UI for tagging a custom insight
88
88
89
89
1.[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the top menu select **Content > Custom Insights**. <br/>[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Cloud SIEM > Custom Insights**. You can also click the **Go To...** menu at the top of the screen and select **Custom Insights**.
90
-
1. Navigate to a custom insight.
91
-
1. The UI for tagging is at the bottom of the **Then Create a Signal** area of the insight editor.
92
-
1. To add a tag, follow the instructions in [Add a schema key tag](#applya-schema-key-tag) or [Add a keyword tag](#apply-a-keyword-tag).<br/><img src={useBaseUrl('img/cse/custom-insight.png')} alt="Tag a custom insight" style={{border: '1px solid gray'}} width="600"/>
90
+
1. Navigate to a custom insight and select it.
91
+
1. The UI for tagging is at the bottom of the **Then Create a Signal** area of the insight editor. To add a tag, follow the instructions in [Add a schema key tag](#applya-schema-key-tag) or [Add a keyword tag](#apply-a-keyword-tag).<br/><img src={useBaseUrl('img/cse/custom-insight.png')} alt="Tag a custom insight" style={{border: '1px solid gray'}} width="600"/>
Copy file name to clipboardExpand all lines: docs/cse/records-signals-entities-insights/view-manage-entities.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -119,7 +119,7 @@ the entity appears.
119
119
| p |**Related Entities**. Entities related to the current entity. |
120
120
| q |**Automations**. [Automations](/docs/cse/automation/automations-in-cloud-siem/#view-results-of-an-automation) that have been run on the entity. |
121
121
| r |**Create Insight**. You can use this option to create an insight on the entity, as described below in [Create an insight](#create-an-insight), below. |
122
-
| s | The **Current State** section lists signals that were generated for the entity during the current [detection window](/docs/cse/records-signals-entities-insights/set-insight-generation-window-threshold/) that are not already part of an insight. (The detection window is the period over which Cloud SIEM evaluates signals, which is 14 days, by default. The detection window is configured on the **Content > Custom Insights** page in the Cloud SIEM UI.) |
122
+
| s | The **Current State** section lists signals that were generated for the entity during the current [detection window](/docs/cse/records-signals-entities-insights/set-insight-generation-window-threshold/) that are not already part of an insight. (The detection window is the period over which Cloud SIEM evaluates signals, which is 14 days, by default. The detection window is configured on the **Custom Insights** page in the Cloud SIEM UI.) |
123
123
124
124
Below the **Current State** section there may be a **Prior Activity** section. This section lists signals that were generated for the entity prior to the current detection window, and all insights for the entity.
Copy file name to clipboardExpand all lines: docs/get-started/training-certification-faq.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -188,9 +188,9 @@ Certified users become technical experts on setting up, managing and optimizing
188
188
In this course, you'll create starter SOC queries as dashboard panels. These advanced operator queries help you monitor user activity across the globe, failed logins, land speed violations, brute force attacks, and more. You will create parameterized lookup tables for easy panel or dashboard pivots. You will learn how to export the starter SOC dashboard you created for use in your own environment. Lastly, you will be able to detect and investigate IOCs with the use of our embedded CrowdStrike database, which monitors malicious IPs addresses, and apply scheduled views as a best practice.
189
189
-->
190
190
191
-
**Sumo Logic Certified - Cloud SIEM Fundamentals**. Learn how Cloud SIEM ingests your data and turns it into actionable security Insights. Get hands-on practice with threat investigation, take actions on Insights, and learn the basics of SOC content creation, like writing rules and custom Insights.
191
+
**Sumo Logic Certified - Cloud SIEM Fundamentals**. Learn how Cloud SIEM ingests your data and turns it into actionable security Insights. Get hands-on practice with threat investigation, take actions on Insights, and learn the basics of SOC content creation, like writing rules and custom insights.
192
192
193
-
**Sumo Logic Certified - Cloud SIEM Administration**. Learn how to set up data ingestion for Cloud SIEM, including writing custom log and ingest mappings. Customize your environment with a deep dive into custom rules and Insight Actions.
193
+
**Sumo Logic Certified - Cloud SIEM Administration**. Learn how to set up data ingestion for Cloud SIEM, including writing custom log and ingest mappings. Customize your environment with a deep dive into custom rules and insight actions.
194
194
195
195
**Sumo Logic Certified - Cloud SOAR Fundamentals**. Learn how to automate your security operations center with playbooks, dashboards, and reports. Watch a playbook run in real time and export a customized dashboard.
0 commit comments