Skip to content

Commit 6cb41fa

Browse files
shivani-sumoshivani-sumo
authored
Merge branch 'main' into Update-OneLogin-app
2 parents 23f912b + e6c3bdc commit 6cb41fa

File tree

8 files changed

+314
-55
lines changed

8 files changed

+314
-55
lines changed

‎blog-csoar/2025-09-04-applicaton-update.md‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
title: September 3, 2025 - Application Update
3+
hide_table_of_contents: true
4+
image: https://help.sumologic.com/img/reuse/rss-image.jpg
5+
keywords:
6+
- automation service
7+
- cloud soar
8+
- soar
9+
---
10+
11+
import useBaseUrl from '@docusaurus/useBaseUrl';
12+
13+
## August release
14+
15+
### Changes and enhancements
16+
17+
#### Platform
18+
19+
Default action limit increased to 500.
20+
21+
#### Integrations
22+
23+
* [UPDATED] [Trend Micro Vision One](/docs/platform-services/automation-service/app-central/integrations/trend-micro-vision-one/)
24+
* Fixed type SHA1 issue in action Add Object To Suspicious Object List and Delete Object From Suspicious Object List.
25+
* Added SHA256 support in action Add Object To Suspicious Object List and Delete Object From Suspicious Object List.
26+
* [UPDATED] [CrowdStrike Falcon](/docs/platform-services/automation-service/app-central/integrations/crowdstrike-falcon/)
27+
* Resolved timeout issues across all actions, including daemons and enrichment queries, for improved stability and performance.
28+
* [UPDATED] [ManageEngine Desktop Central](/docs/platform-services/automation-service/app-central/integrations/manage-engine-desktop-central/)
29+
* Added support for both Cloud and On-prem based account type authentication.
30+
31+
### Bug Fixes
32+
33+
#### Playbooks
34+
35+
* Fixed a bug causing false loop detection in playbook execution.
36+
* Fixed operator inconsistencies within conditions for condition and filter nodes.
37+
38+
#### Integrations
39+
40+
Resolved installation error for App Central integrations conflicting with existing custom integrations of the same name.
41+
42+
#### Incidents
43+
44+
Fixed unlimited file upload vulnerability in the Incident documentation feature.

‎docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/aws-lambda/nodejs.md‎

Lines changed: 36 additions & 36 deletions
Original file line numberDiff line numberDiff line change
@@ -14,18 +14,18 @@ To obtain tracing data from AWS Lambda functions developed in Node.js, you can u
1414

1515
**Sumo Logic OTel NodeJS Lambda layer supports:**
1616

17-
* nodejs16.x, nodejs18.x and nodejs20.x runtimes
17+
* nodejs18.x or later
1818
* x86_64 and arm64 architectures
1919

2020
## Sumo Logic Distribution for OpenTelemetry Lambda Layer
2121

22-
[Sumo Logic Distribution for OpenTelemetry Lambda Layer version 1.17.2](https://github.com/SumoLogic/sumologic-otel-lambda/tree/release-nodejs-v1.17.2/nodejs) provides packed [OpenTelemetry NodeJS](https://github.com/open-telemetry/opentelemetry-js) libraries that automatically instrument Lambda functions. The biggest advantage of installing Sumo Logic OTel Lambda as a layer is disabling/enabling instrumentation of the Lambda function without changing the code.
22+
[Sumo Logic Distribution for OpenTelemetry Lambda Layer version 2.0.0](https://github.com/SumoLogic/sumologic-otel-lambda/tree/release-nodejs-v2.0.0/nodejs) provides packed [OpenTelemetry NodeJS](https://github.com/open-telemetry/opentelemetry-js) libraries that automatically instrument Lambda functions. The biggest advantage of installing Sumo Logic OTel Lambda as a layer is disabling/enabling instrumentation of the Lambda function without changing the code.
2323

2424
### Lambda function requirements
2525

2626
It is very simple to instrument your AWS NodeJS Lambda function using the Sumo Logic Distro for Lambda layer. You'll need the following:
2727

28-
* NodeJS v16.x or newer
28+
* NodeJS v18.x or later
2929
* Lambda layers add permissions
3030
* Sumo Logic OTLP/HTTP Source endpoint URL - To send spans from the instrumented Lambda function to Sumo Logic you need an endpoint URL from an existing or new [OTLP/HTTP source](/docs/send-data/hosted-collectors/http-source/otlp).
3131

@@ -56,47 +56,47 @@ The following are the Sumo Logic OTel Lambda layers for AWS Region for amd64 (x8
5656

5757
| AWS Region | ARN |
5858
|:--|:--|
59-
| af-south-1 | arn:aws:lambda:af-south-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
60-
| ap-east-1 | arn:aws:lambda:ap-east-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
61-
| ap-northeast-1 | arn:aws:lambda:ap-northeast-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
62-
| ap-northeast-2 | arn:aws:lambda:ap-northeast-2:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
63-
| ap-northeast-3 | arn:aws:lambda:ap-northeast-3:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
64-
| ap-southeast-1 | arn:aws:lambda:ap-southeast-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
65-
| ap-southeast-2 | arn:aws:lambda:ap-southeast-2:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
66-
| ca-central-1 | arn:aws:lambda:ca-central-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
67-
| eu-central-1 | arn:aws:lambda:eu-central-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
68-
| eu-north-1 | arn:aws:lambda:eu-north-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
69-
| eu-south-1 | arn:aws:lambda:eu-south-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
70-
| eu-west-1 | arn:aws:lambda:eu-west-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
71-
| eu-west-2 | arn:aws:lambda:eu-west-2:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
72-
| eu-west-3 | arn:aws:lambda:eu-west-3:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
73-
| me-south-1 | arn:aws:lambda:me-south-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
74-
| sa-east-1 | arn:aws:lambda:sa-east-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
75-
| us-east-1 | arn:aws:lambda:us-east-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
76-
| us-east-2 | arn:aws:lambda:us-east-2:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
77-
| us-west-1 | arn:aws:lambda:us-west-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
78-
| us-west-2 | arn:aws:lambda:us-west-2:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v1-17-2:1 |
59+
| af-south-1 | arn:aws:lambda:af-south-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
60+
| ap-east-1 | arn:aws:lambda:ap-east-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
61+
| ap-northeast-1 | arn:aws:lambda:ap-northeast-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
62+
| ap-northeast-2 | arn:aws:lambda:ap-northeast-2:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
63+
| ap-northeast-3 | arn:aws:lambda:ap-northeast-3:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
64+
| ap-southeast-1 | arn:aws:lambda:ap-southeast-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
65+
| ap-southeast-2 | arn:aws:lambda:ap-southeast-2:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
66+
| ca-central-1 | arn:aws:lambda:ca-central-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
67+
| eu-central-1 | arn:aws:lambda:eu-central-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
68+
| eu-north-1 | arn:aws:lambda:eu-north-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
69+
| eu-south-1 | arn:aws:lambda:eu-south-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
70+
| eu-west-1 | arn:aws:lambda:eu-west-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
71+
| eu-west-2 | arn:aws:lambda:eu-west-2:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
72+
| eu-west-3 | arn:aws:lambda:eu-west-3:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
73+
| me-south-1 | arn:aws:lambda:me-south-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
74+
| sa-east-1 | arn:aws:lambda:sa-east-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
75+
| us-east-1 | arn:aws:lambda:us-east-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
76+
| us-east-2 | arn:aws:lambda:us-east-2:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
77+
| us-west-1 | arn:aws:lambda:us-west-1:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
78+
| us-west-2 | arn:aws:lambda:us-west-2:663229565520:layer:sumologic-otel-lambda-nodejs-x86_64-v2-0-0:1 |
7979

8080
### Sumo Logic Distro Lambda layers for AWS Region - arm64 (arm) architecture
8181

8282
The following are the Sumo Logic OTel Lambda layers for AWS Region for arm64.
8383

8484
| AWS Region | ARN |
8585
|:----------------------------------------|:-----------------------------------------------------------------------------|
86-
| ap-northeast-1 | arn:aws:lambda:ap-northeast-1:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v1-17-2:1 |
87-
| ap-northeast-3 | arn:aws:lambda:ap-northeast-3:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v1-17-2:1 |
88-
| ap-southeast-1 | arn:aws:lambda:ap-southeast-1:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v1-17-2:1 |
89-
| ap-southeast-2 | arn:aws:lambda:ap-southeast-2:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v1-17-2:1 |
90-
| eu-central-1 | arn:aws:lambda:eu-central-1:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v1-17-2:1 |
91-
| eu-west-1 | arn:aws:lambda:eu-west-1:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v1-17-2:1 |
92-
| eu-west-2 | arn:aws:lambda:eu-west-2:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v1-17-2:1 |
93-
| us-east-1 | arn:aws:lambda:us-east-1:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v1-17-2:1 |
94-
| us-east-2 | arn:aws:lambda:us-east-2:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v1-17-2:1 |
95-
| us-west-2 | arn:aws:lambda:us-west-2:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v1-17-2:1 |
86+
| ap-northeast-1 | arn:aws:lambda:ap-northeast-1:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v2-0-0:1 |
87+
| ap-northeast-3 | arn:aws:lambda:ap-northeast-3:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v2-0-0:1 |
88+
| ap-southeast-1 | arn:aws:lambda:ap-southeast-1:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v2-0-0:1 |
89+
| ap-southeast-2 | arn:aws:lambda:ap-southeast-2:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v2-0-0:1 |
90+
| eu-central-1 | arn:aws:lambda:eu-central-1:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v2-0-0:1 |
91+
| eu-west-1 | arn:aws:lambda:eu-west-1:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v2-0-0:1 |
92+
| eu-west-2 | arn:aws:lambda:eu-west-2:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v2-0-0:1 |
93+
| us-east-1 | arn:aws:lambda:us-east-1:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v2-0-0:1 |
94+
| us-east-2 | arn:aws:lambda:us-east-2:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v2-0-0:1 |
95+
| us-west-2 | arn:aws:lambda:us-west-2:663229565520:layer:sumologic-otel-lambda-nodejs-arm64-v2-0-0:1 |
9696

9797
## Sumo Logic Distribution for OpenTelemetry Lambda container instrumentation
9898

99-
[Sumo Logic Distribution for OpenTelemetry Lambda Layer version 1.17.2](https://github.com/SumoLogic/sumologic-otel-lambda/tree/release-nodejs-v1.17.2/nodejs) also provides packed [OpenTelemetry NodeJS](https://github.com/open-telemetry/opentelemetry-js) libraries for container-based Lambda functions.
99+
[Sumo Logic Distribution for OpenTelemetry Lambda Layer version 2.0.0](https://github.com/SumoLogic/sumologic-otel-lambda/tree/release-nodejs-v2.0.0/nodejs) also provides packed [OpenTelemetry NodeJS](https://github.com/open-telemetry/opentelemetry-js) libraries for container-based Lambda functions.
100100

101101
:::note
102102
The instructions below support only [AWS Base Images for Lambda](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-images.html).
@@ -107,12 +107,12 @@ The instructions below support only [AWS Base Images for Lambda](https://docs.aw
107107
Instrumentation of container-based AWS Lambda function requires some changes in the Dockerfile and image rebuild. You'll need the following:
108108

109109
* Docker
110-
* NodeJS v16.x or newer
110+
* NodeJS v18.x or later
111111
* Sumo Logic OTLP/HTTP Source endpoint URL - To send spans from the instrumented Lambda function to Sumo Logic you need an endpoint URL from an existing or new [OTLP/HTTP source](/docs/send-data/hosted-collectors/http-source/otlp).
112112

113113
### Lambda function image changes
114114

115-
1. Download and extract Sumo Logic OTel Lambda archive with instrumentation packages specific for your architecture - [amd64 (x86_64)](https://github.com/SumoLogic/sumologic-otel-lambda/releases/download/nodejs-v1.17.2/opentelemetry-nodejs-amd64.zip) or [arm64](https://github.com/SumoLogic/sumologic-otel-lambda/releases/download/nodejs-v1.17.2/opentelemetry-nodejs-arm64.zip).
115+
1. Download and extract Sumo Logic OTel Lambda archive with instrumentation packages specific for your architecture - [amd64 (x86_64)](https://github.com/SumoLogic/sumologic-otel-lambda/releases/download/nodejs-v2.0.0/opentelemetry-nodejs-amd64.zip) or [arm64](https://github.com/SumoLogic/sumologic-otel-lambda/releases/download/nodejs-v2.0.0/opentelemetry-nodejs-arm64.zip).
116116
1. Add extracted instrumentation libraries to the image in the `/opt` directory. See the following Dockerfile example:
117117
```sh
118118
FROM public.ecr.aws/lambda/nodejs:16-arm64

‎docs/cse/records-signals-entities-insights/view-manage-entities.md‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ This topic has information about the **Entities** page in Cloud SIEM UI, which l
1515

1616
The **Entities** page is useful for monitoring entities that are close to having an insight created. On the **Entities > Details** page, you can view signals and insights for an entity, and, as desired, manually create an insight from signals associated with the entity.
1717

18-
You can also update the [tags](/docs/cse/records-signals-entities-insights/tags-insights-signals-entities-rules/), [suppression](/docs/cse/records-signals-entities-insights/about-signal-suppression/) state, and [criticality](/docs/cse/records-signals-entities-insights/entity-criticality/) assigned to entities, as described below in the [Update multiple entities](#update-multiple-entities) section below. 
18+
You can also update the [tags](/docs/cse/records-signals-entities-insights/tags-insights-signals-entities-rules/), [suppression](/docs/cse/records-signals-entities-insights/about-signal-suppression/) state, and [criticality](/docs/cse/records-signals-entities-insights/entity-criticality/) assigned to entities, as described below in the [Update multiple entities](#update-multiple-entities) section. 
1919

2020
:::sumo Micro Lesson
2121

@@ -60,6 +60,10 @@ You can create custom entity types as well. For more information, see [Create a
6060

6161
When a signal is fired, if an entity doesn’t already exist in Cloud SIEM for the item that the signal fired on, Cloud SIEM creates an entity for it. For more information about entities and signal and insight generation, see [Insight Generation Process](/docs/cse/get-started-with-cloud-siem/insight-generation-process).
6262

63+
:::note
64+
Entity names have a limit of 512 characters. If an entity's name value is 512 characters or longer, the system discards the log, and as a result, no signal is generated.
65+
:::
66+
6367
## About the Entities list page
6468

6569
[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). To view entities, click **Entities** at the top of the screen.
@@ -109,7 +113,7 @@ the entity appears.
109113
| o | **Timeline**. A timeline appears for the entity's activity over a three-day period. For more information, see [About the Entity Timeline tab](#about-the-entity-timeline-tab).|
110114
| p | **Related Entities**. Entities related to the current entity. |
111115
| q | **Automations**. [Automations](/docs/cse/automation/automations-in-cloud-siem/#view-results-of-an-automation) that have been run on the entity. |
112-
| 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. |
116+
| 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). |
113117
| 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.) |
114118

115119
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. 

0 commit comments

Comments
 (0)