Falcon LogScale 1.203.0 GA (2025-08-26)

Version?Type?Release Date?Availability?End of SupportSecurity UpdatesUpgrades From?Downgrades To?Config. Changes?
1.203.0GA2025-08-26

Cloud

2026-10-31No1.150.01.177.0No

Hide file download links

Show file download links

Bug fixes and updates

Deprecation

Items that have been deprecated and may be removed in a future release.

  • The EXTRA_KAFKA_CONFIGS_FILE configuration variable has been deprecated and planned to be removed no earlier than version 1.225.0. For more information, see RN Issue.

  • rdns() has been deprecated and will be removed in version 1.249. Use reverseDns() as an alternative function.

Behavior Changes

Scripts or environment which make use of these tools should be checked and updated for the new configuration:

  • Automation and Triggers

    • Logs regarding the status of the scheduled search job now have the fields category=ScheduledSearch and subCategory=Job, instead of having category=Job and no subCategory.

      For more information, see Query Scheduling.

New features and improvements

  • Configuration

    • The PDF Render Service now supports TLS/HTTPS connections for enhanced security. This allows the service to operate in secure environments with encrypted communication.

      The following environment variables enable the TLS feature:

      • TLS_ENABLED - Set to true to enable HTTPS mode

      • TLS_CERT_PATH - Path to TLS certificate file

      • TLS_KEY_PATH - Path to TLS private key file

      • TLS_CA_PATH - Optional CA certificate path

      When TLS is enabled, the service supports TLS versions 1.2 and 1.3. The service maintains backward compatibility - when TLS_ENABLED is not set or false, it operates in HTTP mode.

      This enhancement improves security for Schedule PDF Reports generation in enterprise environments requiring encrypted connections.

      For more information, see PDF Render Service.

Fixed in this release

  • Dashboards and Widgets

    • Fixed an issue that allowed users to save a dashboard using the FixedList Parameter without a defined value, causing dashboard exports to fail.

Known Issues

  • Storage

    • For clusters using secondary storage where the primary storage on some nodes in the cluster may be getting filled (that is, the storage usage on the primary disk is halfway between PRIMARY_STORAGE_PERCENTAGE and PRIMARY_STORAGE_MAX_FILL_PERCENTAGE), those nodes may fail to transfer segments from other nodes. The failure will be indicated by the error java.nio.file.AtomicMoveNotSupportedException with message "Invalid cross-device link".

      This does not corrupt data or cause data loss, but will prevent the cluster from being fully healthy, and could also prevent data from reaching adequate replication.

Improvement

  • User Interface

    • Improved query parameter detection accuracy for queries using parameters with special characters:

      • Now correctly identifies parameters with . characters in the name (for example, ?http.method).

      • Properly detects quoted parameter names in default value syntax (for example, ?{"http.method"="GET"})

Recent Package Updates

The following LogScale packages have been updated within the last month.

  • Package Changes

    • cisco/meraki has been updated to v1.5.2.

      • Enhanced authentication event parsing with improved regex pattern for authentication messages

      • Added support for AnyConnect VPN connection success and failure events with detailed field extraction

      • Added authentication event categorization with proper event types

      For more information, see Package cisco/meraki Release Notes.

    • okta/sso has been updated to v1.4.1.

      • Fixed user agent field mapping from user_agent.device.name to user_agent.os.name

      • Updated CPS version to 1.1.0

      For more information, see Package okta/sso Release Notes.

    • darktrace/detect has been updated to v2.0.0.

      • Added support for CEF-formatted DCIP logs with new event.dataset "darktrace.dcip"

      • Enhanced MITRE ATT&CK technique and tactic mapping using objectArray functions

      • Improved field mappings for threat intelligence data

      • Updated parser to 3.0.0

      For more information, see Package darktrace/detect Release Notes.

    • darktrace/detect has been updated to v1.5.0.

      • Added support for email events

      • Updated parser to 2.3.0

      For more information, see Package darktrace/detect Release Notes.

    • cloudflare/zerotrust has been updated to v1.4.0.

      • Added severity mapping based on risk score

      • Added event.kind = alert for zone-scoped-http-requests when severity is present

      • Added event.action mapping from Vendor.SecurityAction

      • Added array deduplication for event.category[] and event.type[]

      • Updated email field normalization to convert all email addresses to lowercase

      • Enhanced DNS event action mapping to use coalesce function for better field resolution

      • Updated parser version to 2.3.0 and CPS version to 1.1.0

      For more information, see Package cloudflare/zerotrust Release Notes.

    • cisco/ios has been updated to v1.7.1.

      • Added support for additional timezone formats including BST, CEST, GMT, IST, JST, SAST, WAT, and WIB

      For more information, see Package cisco/ios Release Notes.

    • tausight/ephi-risk-posture has been updated to v1.2.1.

      • Updated ECS version from 8.17.0 to 9.0.0

      • Updated CPS version from 1.0.0 to 1.1.0

      • Replaced rename() function calls with direct field assignments for improved performance

      • Fixed email.from.address field mapping to use array:append instead of direct array assignment

      • Added metadata-source.yaml file for package metadata

      For more information, see Package tausight/ephi-risk-posture Release Notes.

    • okta/sso has been updated to v1.4.2.

      • Enhanced timestamp parsing to handle events without published timestamp field

      • Improved target array parsing with better regex matching for JSON structure

      • Fixed handling of error message events that lack timestamp information

      • Updated parser version to 2.4.2

      For more information, see Package okta/sso Release Notes.

    • cloudflare/zerotrust has been updated to v1.5.0.

      • Enhanced bulk log processing with improved batched event handling

      • Added SHA256 hash generation for batched events to track event relationships

      • Improved JSON parsing structure for better event separation

      • Updated parser version to 2.4.0

      For more information, see Package cloudflare/zerotrust Release Notes.

    • cisco/firepower has been updated to v1.7.1.

      • Updated CPS version to 1.1.0

      • Enhanced regex patterns for improved log parsing accuracy

      • Added support for user domain and username extraction in connection events

      • Improved multi-event code parsing for SSL VPN events (725001-9, 12, 13, 16, 21, 22)

      • Added event.outcome field for configuration and connection info events

      • Enhanced parsing for Group/User/IP patterns in VPN connection logs

      • Moved syslog severity code mapping to end of parser for better performance

      For more information, see Package cisco/firepower Release Notes.

    • fortinet/fortigate has been updated to v1.3.5.

      • Updated CPS version to 1.1.0

      • Updated parser version to 2.1.4

      • Removed drop statements for fields (Vendor.time, Vendor.eventtime, Vendor.date, Vendor.tz, Vendor.ts, Vendor.srcmac, Vendor.source_mac, Vendor.dir, Vendor.direction, Vendor.service)

      For more information, see Package fortinet/fortigate Release Notes.

    • aws/cloudtrail has been updated to v2.0.2.

      • Added support for IdentityCenterUser identity type

      • Improved handling of identity center user identities

      For more information, see Package aws/cloudtrail Release Notes.

    • radware/alteon has been updated to v1.2.1.

      • Updated ECS version to 9.0.0

      • Removed deprecated alteon-syslog parser

      • Fixed field assignment operations to use direct assignment instead of rename operations

      • Updated parser version to 1.1.1

        ### Version 1.2.0

      Parser renaming and Deprecation notice

      The old parser alteon-syslog is deprecated, and replaced by the new parser radware-alteon. While the old parser will remain available during a tranisition period, all future changes will only go into the new radware-alteon parser. We recommend switching to the newer parser as soon as possible, to make for the smoothest upgrade. The old alteon-syslog parser will be removed at some point in the future. In your data, the field #type contains the name of the parser, so any queries you may have that searches for this field need to accomodate this change.

      Duplicated vendor fields dropped in new parser

      The old alteon-syslog parser would duplicate certain fields, which the new radware-alteon parser will not. The fields which were previously duplicated, would be present both under the Vendor namespace (e.g. Vendor.srcIp), and as a field mapped to CPS (e.g. source.ip). If the value of two such fields is byte-for-byte the same, the new parser will no longer preserve the vendor-specific field, but only the CPS field. If the value of the two fields differ, both fields will be preserved. This means the following fields will no longer be present in the parsed data, when using the new parser:

      • Vendor.keys.DstIP

      • Vendor.keys.DstPort

      • Vendor.keys.Method

      • Vendor.keys.ResponseCode

      • Vendor.keys.SrcIp

      • Vendor.keys.URL

      • Vendor.keys.UserAgent

      • Vendor.keys.WAFObservedIP

        ### Version 1.0.1

      • Adds logic to detect event.outcome for http requests based on status code

      • Adds comments to better explain the logic of the temporary fields

      • Bumps parser version to 1.0.1

        ### Version 1.0.0

      • Adds new event.module and Cps.version fields

      • Removes the Product field

      • Sets following tags: Cps.version, Vendor, ecs.version, event.dataset, event.kind, event.module, event.outcome, observer.type

      • Bug fix: making event.category field an array

      For more information, see Package radware/alteon Release Notes.

    • okta/sso has been updated to v1.4.3.

      • Enhanced target array parsing with improved regex pattern to handle whitespace variations in JSON structure

      • Fixed parsing of target arrays with flexible spacing between "target" field and array brackets

      For more information, see Package okta/sso Release Notes.

    • aws/cloudtrail has been updated to v2.1.0.

      • Updated parser version to 4.0.0

      • Enhanced event categorization and typing for various AWS actions

      • Changed observer.type from "iam" to "identity" for IAM-related events

      • Updated AssumeRole and AssumeRoleWithSAML event categorization from authentication to iam

      • Modified ConsoleLogin event dataset from "cloudtrail.iam" to "cloudtrail.auth"

      • Added UserAuthentication event handling with authentication category

      • Improved event type mappings by removing "info" type from several actions

      • Enhanced StartInstances and RunInstances categorization from configuration to host

      • Added GenerateDataKey event handling with configuration category and creation type

      • Updated wildcard matching to be more specific and removed default fallback categorization

      For more information, see Package aws/cloudtrail Release Notes.

    • cisco/duo has been updated to v3.0.0.

      • Vendor fields are now aliased to the client namespace where source was previously used, as client better describes the role of devices initiating authentication flows whereas source is intended for network details

      • client fields are aliased to source at the end of the parser to avoid a breaking change. This allows the source fields to be easily removed from the parser at a later date

      • event.dataset of duo.administrator is now assigned when Vendor.action = * AND Vendor.isotimestamp = * rather than when Vendor.description = * (as "description":null often occurs, meaning that the Vendor.description field is not created)

      • Categorization now matches on event.dataset first, then event.action to handle repeat event.action values across different log types (e.g., event.action of enrollment appears in both Authentication and Telephony logs)

      • Added use of user.target fields - with logic implemented to make sure this is only applied on applicable event

      • Added parsing of nested JSON in duo.activity logs from the fields: Vendor.actor.details/Vendor.target.details/Vendor.old_target.details

      • Removed the Host fields section for duo.authentication and duo.trustmonitor events. As auth_device is the MFA device used in the auth process - not the host on which the event happened. Also Vendor.target fields are not present in this log type. So this section was not accurate

      • Moved the determination of event.outcome after the default values are set in categorization - so that these default values can be overwritten when outcome information is available in the event

      • Updated the handling of object arrays to use objectArray:eval() instead of concatArray and splitString

      • Added observer.type := "identity"

      • Additional normalization of ECS fields

      • Updates to the assignment of event.category for cloudsso_update_routing_rule and user_restore events

      • Updated CPS version to 1.1.0

      • Updated ECS version to 9.0.0

      • Updated parser version to 3.0.0

      For more information, see Package cisco/duo Release Notes.

    • cisco/ise has been updated to v1.3.4.

      • Added parsing for CmdSet field to extract command line information into process.command_line field

      • Enhanced command parsing to filter and extract command arguments from TACACS authorization logs

      • Updated parser version to 2.0.7 and CPS version to 1.1.0

      For more information, see Package cisco/ise Release Notes.