Sumo Logic Release Notes

Follow

52 release notes curated from 6 sources by the Releasebot Team. Last updated: Nov 17, 2026

Get this feed:

Sumo Logic Products

  • Nov 17, 2026
    • Date parsed from source:
      Nov 17, 2026
    • First seen by Releasebot:
      Nov 17, 2026
    Sumo Logic logo

    Sumo Logic

    New Sender Address for Email Notifications (Manage)

    Sumo Logic now sends Monitor, Scheduled Search, Automation Service, and related system notifications from [email protected]. Update email allowlists and rules; message content and delivery behavior remain unchanged.

    Email notifications from Monitors, Scheduled Searches, and Automation Service are now sent from [email protected]. The same sender is used for related system emails, including notifications about reaching the scheduled search email limit, a suppressed scheduled search, a removed scheduled search, and a failed dashboard report. Allowlist this address and update any email filters, inbox rules, distribution lists, or automated workflows that depend on the previous sender. Only the sender address changes. Subject lines, email templates, recipients, attachments, notification content, and delivery logic stay the same. Account sign-up, email verification and change, password reset, and other transactional account emails are not affected and keep their existing sender.

    Original source
  • Nov 13, 2026
    • Date parsed from source:
      Nov 13, 2026
    • First seen by Releasebot:
      Nov 14, 2026
    Sumo Logic logo

    Sumo Logic

    AI Observability App (Apps)

    Sumo Logic releases its AI Observability app in Limited Availability, with preconfigured dashboards and monitors to track AI and LLM application health, performance, cost, and behavior using enriched OpenTelemetry traces.

    The Sumo Logic app for AI Observability is in Limited Availability, providing early access to observability capabilities designed to monitor and understand AI workloads. This release offers an opportunity to explore the capabilities and share feedback as we continue to enhance the experience ahead of its planned transition to an in-product experience.

    The app provides preconfigured dashboards and monitors to track the health, performance, cost, and behavior of AI and LLM applications using OpenTelemetry trace spans enriched with GenAI Semantic Convention (gen_ai.*) attributes. Learn more.

    For additional information, see the instrumentation guides for OpenLLMetry and OpenTelemetry.

    Original source
  • All of your release notes in one feed

    Join Releasebot and get updates from Sumo Logic and hundreds of other software products.

    Create account
  • Nov 11, 2026
    • Date parsed from source:
      Nov 11, 2026
    • First seen by Releasebot:
      Nov 13, 2026
    Sumo Logic logo

    Sumo Logic

    SAML Destination URL Validation (Manage)

    Sumo Logic strengthens SAML single sign-on security by validating identity provider Destination URLs against the configured ACS URL. Mismatches trigger login warnings during the initial rollout and will be rejected starting January 29, 2027.

    Sumo Logic now validates the Destination URL in the SAML response from your identity provider (IdP) against the Assertion Consumer Service (ACS) URL configured in your Sumo Logic SAML configuration. This follows Section 3.5.5.2 of the SAML 2.0 Bindings specification and strengthens the security of your single sign-on (SSO) setup. Learn more.

    Rollout

    • November 16, 2026. Users in organizations with a mismatch see a warning once per session at login. Logins are not blocked.
    • January 29, 2027. Sumo Logic rejects logins with a mismatched Destination URL.

    info

    SSO administrators need to set both the ACS URL and the Destination URL in their IdP to match the Assertion Consumer URL on the SAML page in Sumo Logic before January 29, 2027.

    Original source
  • Oct 30, 2026
    • Date parsed from source:
      Oct 30, 2026
    • First seen by Releasebot:
      Nov 2, 2026
    Sumo Logic logo

    Sumo Logic

    Apps, Collection, and Automation Service Integrations - October Release

    Sumo Logic expands automation integrations, apps, and Cloud-to-Cloud sources with new threat intelligence and case management actions, improved Jira workflows, refreshed dashboards, and broader GitHub Copilot user metrics support.

    This release includes enhancements to automation service integrations, apps, and Cloud-to-Cloud (C2C) sources, with new actions, improved functionality, updated dashboards, and expanded data support.

    Automation service integrations enhancements

    ZeroFox V2. Added new CTI enrichment actions and improved existing actions.

    CrowdStrike Falcon. Expanded the integration with new Case Management actions and deprecated legacy Incident actions.

    Atlassian Jira Cloud.

    Improved Jira Cloud issue creation and updates for multiline/HTML descriptions and due-date inputs.

    Added custom priority support to the Jira Cloud integration used by Cloud SOAR playbooks.

    Atlassian Jira V2. Added custom priority support to the Atlassian Jira V2 integrations used by Cloud SOAR playbooks.

    ThreatConnect V3. Added tag modes to the Update Indicators action and fixed a bug in the Search Intelligence action.

    App enhancements

    Flex (v1.0.5). Updated monitor conditions for better alert notifications.

    GitHub Copilot (v1.0.1). Updated dashboards to reflect the new data schema and added user metrics dashboards.

    C2C source enhancements

    Claude Compliance (v2.0.6). Updated data format of local session messages.

    GitHub Copilot (v2.0.0). Migrated legacy endpoints and integrated support for user metrics.

    Original source
  • Oct 30, 2026
    • Date parsed from source:
      Oct 30, 2026
    • First seen by Releasebot:
      Nov 2, 2026
    Sumo Logic logo

    Sumo Logic

    Manage Features for Your Organization (Manage)

    Sumo Logic adds Manage Features, letting paid customers enable or disable features directly in the Organizations UI.

    We're excited to introduce the Manage Features capability for all paid customers. With this, you can opt in or opt out of specific Sumo Logic features for your organization directly from the Organizations UI without needing to raise a request with Sumo Logic support. Learn more.

    Original source
  • Similar to Sumo Logic with recent updates:

  • Oct 29, 2026
    • Date parsed from source:
      Oct 29, 2026
    • First seen by Releasebot:
      Oct 29, 2026
    Sumo Logic logo

    Sumo Logic

    Classic UI Deprecated for New Standalone Accounts (New UI)

    Sumo Logic makes its current UI the default for newly created standalone accounts starting October 29, 2026, removing their option to switch to Classic. Existing accounts and parent organizations remain unaffected for now, with no data migration required.

    Effective October 29, 2026, newly created standalone Sumo Logic accounts default to the Sumo Logic UI and no longer have the option to switch to the Classic UI. Parent organizations, their child organizations, and existing accounts are not affected and keep their current UI settings for now.

    New accounts default to the Sumo Logic UI. Standalone accounts created through self-service signup or partner provisioning no longer have the option to switch to the Classic UI.

    Other accounts are unaffected. Existing customers, parent organizations, and their child organizations keep their current UI settings at this stage.

    No data migration needed. Your data carries over automatically between the Classic UI and the New UI.

    Classic UI continues winding down. The Classic UI will eventually be retired for all accounts. We'll share the exact date as it's confirmed.

    Learn more about the Sumo Logic UI, or see the Classic UI documentation if your account still has access to it.

    Original source
  • Oct 28, 2026
    • Date parsed from source:
      Oct 28, 2026
    • First seen by Releasebot:
      Oct 29, 2026
    Sumo Logic logo

    Sumo Logic

    JSON Unroll for HTTP Log Sources (Collection)

    Sumo Logic now splits JSON arrays from HTTP log sources into individual messages while preserving top-level metadata.

    HTTP log sources can now automatically split JSON arrays into individual log messages while preserving top-level metadata. Learn more.

    Original source
  • Oct 28, 2026
    • Date parsed from source:
      Oct 28, 2026
    • First seen by Releasebot:
      Oct 28, 2026
    Sumo Logic logo

    Sumo Logic Collector by Sumo Logic

    Installed Collector Version 19.540-2

    Sumo Logic Collector upgrades its Java runtime and Jackson dependency to address security vulnerabilities.

    In this release, we've upgraded the Collector JRE and a dependency to address security vulnerabilities.

    Security fixes

    Upgraded Collector JRE to Amazon Corretto Version 17.0.21.0.10 to address CVE-2026-91403 by distrusting the compromised eMudhra emSign root CA.

    Upgraded com.fasterxml.jackson.core:jackson-databind to 2.21.8 to address CVE-2026-110879.

    Original source
  • Oct 26, 2026
    • Date parsed from source:
      Oct 26, 2026
    • First seen by Releasebot:
      Nov 17, 2026
    Sumo Logic logo

    Cloud SIEM by Sumo Logic

    Enrichments in Cloud SIEM

    Cloud SIEM adds an Enrichments tab on entity, signal, and insight pages, making enrichment data easier to review with filtering, optional hiding of empty fields, links, and threat indicator labels. Enrichments also support expiration, external links, and reputation values.

    Enrichments add additional information to objects in Cloud SIEM. Enrichments tab You can view the results of enrichments in Cloud SIEM by navigating to the Enrichments tab (which will appear on the entity, signal, and insight details pages if there are any enrichments to display): Keep in mind that: • Enrichments are grouped by entity, not by enrichment source. • The list can be filtered. • Empty fields (fields with a null or empty value) can be optionally hidden. • Links, if set by the enrichment, will be displayed and open in a new tab if clicked. • Threat indicator labels, if set by the enrichment, will be displayed. Enrichment attributes The enrichment schema includes support for the following optional attributes: • expiresAt. Defines when the enrichment should be auto-deleted from Cloud SIEM (by default, enrichments will never be auto-deleted). • externalUrl. Defines a link that will be displayed with an enrichment (for example, to include a link to the VirusTotal details page for this entity, put the link in this field). • reputation. Associates a threat indicator with this enrichment data. The allowable values are malicious, suspicious, and notflagged. The default is not to display any reputation. Enrichment size There is a 1 MB limit on the size of enrichments attached to an entity. If too much data is contained in the enrichment, you may get an error. To resolve the problem, reduce the enrichment content to a smaller payload: • If the playbook generating the enrichment is attaching full objects (for example, full alert context in JSON), try selecting only the key fields needed for investigation. • Instead of attaching raw results, extract and send only key indicators. • If multiple enrichments are being added at once, consider breaking them into smaller chunks or prioritizing only the most relevant ones.

    Original source
  • Oct 23, 2026
    • Date parsed from source:
      Oct 23, 2026
    • First seen by Releasebot:
      Oct 24, 2026
    Sumo Logic logo

    Sumo Logic Collector by Sumo Logic

    Clobber Rate Limiting for Collector Registration (OpenTelemetry Collector)

    Sumo Logic Collector now rate-limits repeated OT Collector registrations with clobber enabled to prevent machines from replacing each other’s collectors.

    OT Collector registrations that use clobber: true are now rate limited for each collector name. After about 50 registration attempts with the same name within an hour, Sumo Logic rejects further attempts with an HTTP 429 response. This prevents multiple machines that share a collector name from repeatedly deleting and re-registering each other's collectors. To avoid the limit, use a unique collector_name for each machine, and use clobber only to replace a collector that is no longer running. Learn more.

    Original source
  • Oct 22, 2026
    • Date parsed from source:
      Oct 22, 2026
    • First seen by Releasebot:
      Oct 22, 2026
    Sumo Logic logo

    Sumo Logic

    In-App Tabs for Dashboards and Metrics (Search)

    Sumo Logic adds Dashboard and Metrics support to in-app tabs, letting users switch alongside Log Search without losing context.

    In-app tabs now support Dashboards and Metrics in the New UI, in addition to Log Search. You can keep Log Search, Dashboard, and Metrics tabs open together in a single browser window and switch between them without losing context. This makes it easier to move between investigating logs, reviewing dashboards, and exploring metrics without opening extra browser tabs. In-app tabs are available if you have enabled the Enable in-app tabs preference. Learn more.

    Original source
  • Oct 20, 2026
    • Date parsed from source:
      Oct 20, 2026
    • First seen by Releasebot:
      Nov 17, 2026
    Sumo Logic logo

    Cloud SIEM by Sumo Logic

    Convert Sigma Rules

    Cloud SIEM adds a Sigma backend that converts detection rules into import-ready Cloud SIEM rule JSON, with field mappings, automatic entity selectors, MITRE ATT&CK tags, and confidence scoring to help teams migrate Sigma rule libraries.

    Convert Sigma Rules Sigma is a generic and open signature format for SIEM systems that allows security teams to write detection rules once in Sigma and convert them to different SIEM query languages. Security engineers can automatically translate their Sigma detection rules into Sumo Logic Cloud SIEM rule syntax through a Sigma CLI plugin, eliminating the manual effort of rewriting rules and accelerating the migration of existing Sigma rule libraries to Cloud SIEM. The translated rules detect the same threats and behaviors as the original Sigma rules with high fidelity. Sumo Logic backend for Sigma The pySigma backend for Sumo Logic converts Sigma detection rules into Cloud SIEM rule JSON, ready for import via the CSE API. It includes field mappings for 70+ log sources, automatic entity selector assignment, MITRE ATT&CK tag mapping, and confidence scoring. Sigma plugin directory: https://sigmahq.io/docs/digging-deeper/backends.html#sumologic PyPI package: https://pypi.org/project/pysigma-backend-sumologic/ Source code and documentation: https://github.com/SumoLogic/pySigma-backend-sumologic Install the Sumo Logic backend Option 1 — Install via Sigma CLI (recommended if you already have Sigma CLI installed): sigma plugin install sumologic Option 2 — Install via pip (also installs Sigma CLI if not already present): pip install sigma-cli pysigma-backend-sumologic Sigma resources Sigma Rule Repository - Contains the Sigma detection ruleset defined in YAML. pySigma - A Python SDK that translates Sigma rules into other query languages. Sigma CLI - A command-line tool for converting Sigma rules. Sigma backends - Overview of available backend plugins with links to their repositories. Poetry - Sigma uses Poetry to package and distribute its code bases. Overview of converting Sigma rules into Cloud SIEM rule format For full documentation, see the pySigma Sumo Logic backend. TIP For a general overview of how to convert Sigma rules to a backend, see Converting Sigma Rules. Following is a brief overview of how to convert your Sigma rules into Cloud SIEM rule format: 1. Install the Sumo Logic backend. 2. Create a repository to store your Sigma rules. 3. Create rules in Sigma rule format and place them into your repository. For sample rules, see the Sigma Rule Repository. For example, here is a test-rule.yml file in Sigma format: title: Suspicious PowerShell Execution status: experimental description: Detects PowerShell execution from the command line. tags: - attack.execution - attack.t1059.001 logsource: category: process_creation product: windows detection: selection: CommandLine|contains: 'powershell' condition: selection level: medium 4. Use Sigma CLI to convert your Sigma rule to Cloud SIEM format. For example, run the following to convert a single rule: sigma convert -t sumologic_cse_rule -p sumologic_cse test-rule.yml -o test-rule.json To convert a directory of rules into a single file: sigma convert -t sumologic_cse_rule -p sumologic_cse -s ./rules/ -o rules.json The -s (--skip-unsupported) option skips rules that can't be converted and continues with the rest. Without it, the conversion stops at the first unsupported rule and no file is written. If you omit -o, the JSON is printed to the console. 5. The conversion generates a JSON file that defines the rule in Cloud SIEM rule format. The following output is abbreviated: { "rules": [ { "content_type": "RULE", "enabled": true, "is_prototype": true, "name": "Suspicious PowerShell Execution", "description_expression": "Detects PowerShell execution from the command line.\n\nLog Source:\n- Category: process_creation\n- Product: windows", "expression": "commandLine matches /.*powershell.*/", "entity_selectors": [ {"entity_type": "_hostname", "expression": "device_hostname"}, {"entity_type": "_username", "expression": "user_username"}, {"entity_type": "_process", "expression": "baseImage"} ], "score_mapping": {"default": 3, "type": "constant", "field": null, "mapping": []}, "tags": ["_mitreAttackTactic:TA0002", "_mitreAttackTechnique:T1059.001"], "category": "Execution", "conversion_metadata": { "sigma_status": "experimental", "mapping_confidence": {"overall_score": 0.691, "threshold_used": 0.25, "blocked": false} } } ] } 6. Before importing, review the conversion_metadata.mapping_confidence.warnings of each converted rule. For example, a warning that a log source has no vendor/product mapping means the rule has no metadata_vendor or metadata_product filter and may match records from other log sources. 7. Import the JSON rule file into Sumo Logic using the Cloud SIEM API or UI. To import the JSON file using the UI: i. Access the rules list view. New UI. In the main Sumo Logic menu select Cloud SIEM > Rules. You can also click the Go To... menu at the top of the screen and select Rules. Classic UI. In the top menu select Content > Rules. ii. Click the Import button. iii. Select the JSON file generated by the conversion. How Sigma rule attributes are converted • Severity. The Sigma level maps to the rule score: critical=8, high=6, medium=3, low=1, informational=1. Rules without a level get a score of 3. • Status. The Sigma status sets enabled and is_prototype. stable rules are enabled and not prototypes; test and experimental rules are enabled as prototypes; deprecated and unsupported rules are disabled. Rules without a status are enabled and not prototypes. • MITRE ATT&CK tags. Sigma attack.* tags map to Cloud SIEM tags. For example, attack.execution becomes _mitreAttackTactic:TA0002 and attack.t1059.001 becomes _mitreAttackTechnique:T1059.001. • Entity selectors. Entity selectors are assigned automatically based on the log source category. For example, process creation rules get hostname, username, and process selectors. • Confidence scoring. Each field mapping receives a confidence score from 0 to 1. If the lowest score falls below the threshold (default 0.25), conversion of that rule is blocked, and the error message lists the fields that failed and the threshold needed to allow the conversion. Conversion options Pass options to the backend with -O key=value. For example: sigma convert -t sumologic_cse_rule -p sumologic_cse -O min_confidence=0.0 test-rule.yml Option | Default | Description min_confidence | 0.25 | Minimum mapping confidence score required to convert a rule. Set to 0.0 to disable the threshold. rule_source | user | Value of the rule_source field on converted rules. include_conversion_timestamp | true | Include a conversion_timestamp in the conversion metadata. Set to false for reproducible output that's easier to compare between runs. include_confidence_metadata | true | Include mapping_confidence in the conversion metadata. fail_on_unmapped_logsource | false | Block conversion of rules whose log source has no vendor/product mapping. For the full list of options and known limitations, see the pySigma Sumo Logic backend documentation.

    Original source
  • Oct 16, 2026
    • Date parsed from source:
      Oct 16, 2026
    • First seen by Releasebot:
      Oct 22, 2026
    Sumo Logic logo

    Sumo Logic

    Updated Retention Options for Metrics Transformation Rules (Manage)

    Sumo Logic updates metrics transformation rules with 400-day retention options and migrates existing 15-day rules.

    Metrics transformation rules now offer updated retention options. Retention for matching metrics is Do Not Store or 400 days, and aggregate retention for aggregated metrics is standardized to 400 days. Rules that already use 15-day retention get migrated to 400 days. Learn more.

    Original source
  • Oct 14, 2026
    • Date parsed from source:
      Oct 14, 2026
    • First seen by Releasebot:
      Oct 18, 2026
    Sumo Logic logo

    Sumo Logic Collector by Sumo Logic

    Installed Collector Version 19.539-1

    Sumo Logic Collector strengthens security with updated Java and dependency versions that address multiple vulnerabilities, and fixes a macOS startup issue affecting some installations and upgrades.

    In this release, we've upgraded Collector dependencies and the JRE to address security vulnerabilities and fix a macOS startup issue.

    Security fixes

    • Upgraded Collector JRE to Amazon Corretto Version 17.0.20.12.1.
    • Upgraded com.fasterxml.jackson.core:jackson-core to 2.21.7 to address CVEs (CVE-2026-89407 and CVE-2026-89425).
    • Upgraded com.fasterxml.jackson.core:jackson-databind to 2.21.7 to address CVEs (CVE-2026-91776 and CVE-2026-91777).
    • Upgraded io.netty packages to 4.2.19.Final to address CVEs (CVE-2026-89044, CVE-2026-93488, CVE-2026-93491, and CVE-2026-93558).
    • Upgraded org.bouncycastle:bcpkix-jdk18on to 1.86 to address CVEs (CVE-2026-17508, CVE-2026-71888, CVE-2026-71889, and CVE-2026-71892).
    • Upgraded org.bouncycastle:bcprov-jdk18on to 1.86 to address CVEs (CVE-2026-17508, CVE-2026-18036, CVE-2026-18040, CVE-2026-71889, and CVE-2026-71891).

    Bug fixes

    • Fixed a macOS issue in the previous release, where the collector did not start after installation or upgrade on some computers.
    Original source
  • Oct 12, 2026
    • Date parsed from source:
      Oct 12, 2026
    • First seen by Releasebot:
      Oct 18, 2026
    Sumo Logic logo

    Sumo Logic

    Google Workspace Activities (Collection)

    Sumo Logic adds a Google Workspace Activities source to collect and analyze activity data for better visibility and security.

    The new Sumo Logic source for Google Workspace Activities, enabling seamless collection of Google Workspace activity data.

    This source helps you monitor user activities and analyze events for improved visibility and security. Learn more.

    Original source
Releasebot

Curated by the Releasebot team

Releasebot is an aggregator of official release notes from hundreds of software vendors and thousands of sources.

Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.