Skip to content

Commit 1d9ff65

Browse files
authored
Merge branch 'main' into update-pause-scheduled-views
2 parents 54a0a09 + 1de9bf4 commit 1d9ff65

File tree

3 files changed

+38
-8
lines changed

3 files changed

+38
-8
lines changed

blog-cse/2025-10-28-content.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
title: October 28, 2025 - Content Release
3+
image: https://assets-www.sumologic.com/company-logos/_800x418_crop_center-center_82_none/SumoLogic_Preview_600x600.jpg?mtime=1617040082
4+
keywords:
5+
- log mappers
6+
- parsers
7+
hide_table_of_contents: true
8+
---
9+
10+
This content release includes:
11+
- New mappers for Crowdstrike Falcon events.
12+
- Updates to existing mappers for Crowdstrike Falcon, F5, and Okta events to support additional fields and events.
13+
- Updates to F5 Networks and Okta SSO parsers.
14+
15+
Changes are enumerated below.
16+
17+
### Log Mappers
18+
- [New] CrowdStrike Falcon Host API IdpDetectionSummaryEvent
19+
- [New] CrowdStrike Falcon Identity Protection
20+
- [Updated] CrowdStrike UserActivity Logs
21+
- [Updated] F5 Authentication Catch All
22+
- [Updated] F5 HTTPd Audit - Custom Parser
23+
- [Updated] F5 Session and adfs proxy - Custom Parser
24+
- [Updated] Okta Authentication - auth_via_AD_agent
25+
- [Updated] Okta Authentication - auth_via_mfa
26+
- [Updated] Okta Authentication - auth_via_radius
27+
- [Updated] Okta Authentication - sso
28+
- [Updated] Okta Authentication Events
29+
- [Updated] Okta Catch All
30+
- [Updated] Okta Security Threat Events
31+
32+
### Parsers
33+
- [Updated] /Parsers/System/F5/F5 Syslog
34+
- [Updated] /Parsers/System/Okta/Okta

docs/cse/administration/create-cse-context-actions.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,8 @@ When you save the action, the URL template will be populated with your Sumo Logi
8787

8888
`{{sumobaseurl}}/ui/#/search/@{{timestamp[ms]-30m}}@_index=sec_record* AND user_username = {{value}}`
8989

90+
The `{{sumobaseurl}}` parameter applies to context actions that run a Sumo Logic log search. Assuming your Cloud SIEM instance is configured to communicate with the Sumo Logic platform, when you create an action that runs a Sumo Logic search, Cloud SIEM will automatically insert this placeholder in your URL template—you don’t need to explicitly insert `{{sumobaseurl}}` placeholder yourself.
91+
9092
### Create an URL to an external service
9193

9294
To create a URL to be sent to an external service, enter the URL in the format required by the external service, and use the `{{value}}` parameter placeholder for the target entity, record field, or IOC. 
@@ -121,12 +123,6 @@ The table below defines the parameters you can use in the URL template for a con
121123

122124
You can insert any field from the target of a context action into the action URL with the `{{field_name}}` placeholder. For example, you could include `device_ip` in the URL with `{{device_ip}}`.  
123125

124-
### Sumo Logic Base URL
125-
126-
The `{{sumobaseurl}}` parameter applies to context actions that run a Sumo Logic log search.
127-
128-
Assuming your Cloud SIEM instance is configured to communicate with the Sumo Logic platform, when you create an action that runs a Sumo Logic search, Cloud SIEM will automatically insert this placeholder in your URL template—you don’t need to explicitly insert `{{sumobaseurl}} `placeholder yourself.
129-
130126
### Timestamp
131127

132128
When you run an action on a Cloud SIEM record, if that record has a [timestamp](/docs/cse/schema/schema-attributes) field value, you can insert the timestamp in UTC format into the URL using the `{{timestamp}}` parameter.

docs/integrations/containers-orchestration/vmware.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,8 +26,8 @@ See the [vSphere product page](https://www.vmware.com/products/vsphere.html) for
2626

2727
The Sumo Logic vCenter logs source and vCenter metrics source use the installed collector to gather the following data from VMware:
2828

29-
* VMware Events using the Events API. See [Events API](https://code.vmware.com/apis/196/vsphere/doc/vim.event.EventManager.html) for more details.
30-
* VMware Metrics using the Performance API. For more information, see [Performance API](https://code.vmware.com/apis/196/vsphere/doc/vim.PerformanceManager.html).
29+
* VMware Events using the Events API. See [Events API](https://developer.broadcom.com/xapis/vsphere-web-services-api/latest/vim.event.EventManager.html) for more details.
30+
* VMware Metrics using the Performance API. For more information, see [Performance API](https://developer.broadcom.com/xapis/vsphere-web-services-api/latest/vim.PerformanceManager.html).
3131

3232
The dashboards provide real-time monitoring with visual data displays, allowing you to analyze events and performance metrics for efficient detection and troubleshooting.
3333

0 commit comments

Comments
 (0)