Secure Endpoint 11.2 release notes

This topic describes the software updates included in Secure Endpoint 11.2, along with subsequent hotfixes and upgrades. In addition to the specific changes detailed here, each release also includes broader system enhancements designed to strengthen security, optimize performance, and enhance overall stability.

To view the software updates that apply to the Secure Endpoint Agent, see the Secure Endpoint Agent release notes - Version 11.2.

Depending on the Absolute product licenses associated with your account, and your Absolute data center, some of the following features, enhancements, and fixes may not be available to you.

Features and enhancements

Web Usage reports now use a new high-performance database, delivering faster, more reliable report generation. You can also now customize the report date range and choose from multiple aggregation options, including totals and daily, weekly, or monthly averages, to analyze website activity at the level of detail you need. As part of this update:

  • The Web Usage (Last 7 Days), Web Usage (Trending), and Web Subscriptions reports have been retired. All custom reports based on these reports have also been removed.

  • The configuration for standard work hours has been moved to Account Settings, ensuring that your daytime and evening usage definitions are easily accessible and consistently applied across all Web Usage reports.

Improvements and fixes

Feature/Area Details
Absolute APIs
  • The following endpoints are now available in the Freeze resource:
  • In the Playbook resource, an InputType parameter is now returned when you run the Get playbook templates endpoint. It indicates the type of content contained in the parameter, such as URL, Credentials, or File.
Account settings

  • Single Sign-On now supports only the following encryption methods: AES-128-GCM, AES-192-GCM, AES-256-GCM, AES-256-CBC, RSA-OAEP, or RSA-OAEP-MGF1P. For security reasons, other encryption methods are no longer supported.
Application Resilience

  • Application Resilience policies for Carbon Black Cloud now support version 4.2.x or higher, including updated detection for the application's new architecture.

  • The Application Resilience policy for the following applications now supports an additional default signer name:

    • Trellix Endpoint Security Agent (formerly FireEye Endpoint Agent): FireEye (Musarubra US LLC)

    • BlackBerry CylancePROTECT: Arctic Wolf Networks, Inc.

    • Ivanti Secure Access Client: Ivanti, Inc.

    • Dell Encryption: Dell Technologies Inc.

    These updates reflect the current signers used by the respective services.

    In addition, the default signer name for F5 BIG-IP Edge Client was updated from F5 Inc. to F5, Inc.
Dashboards

  • Previously, when exporting a dashboard widgets based on the Web usage, Device usage, or Application usage data source, the exported report was empty if the widget configuration included a metric filter. This issue is now fixed.

  • Fixed an issue where the Time in focus (total) column header was missing from the report when you exported a widget based on the Web usage data source.

  • When a filter contains a long value, such as a local IPv6 address, the value now wraps correctly to the next line.

  • When a widget is based on the Devices data source, you can now filter the widget’s data by the Last core agent connection field.
Device Details

  • Each device’s Policies page has been improved to show comprehensive information about a device’s activated policies.

    The page now shows the activation status of all policies responsible for data collection, and the device’s activated Application Resilience policies. It also shows the date and time when the policy was last activated or updated, and the date and time when the policy last detected new data on the device. Learn more

  • The date range on the History page now defaults to Last 1 year instead of Last 30 days. All events logged during the past year are now automatically loaded. As a result, the Load an additional 30 days option has been removed.
Device usage

  • Previously, the Average daily usage and Usage level fields were recalculated only when a new device usage payload was sent to the Absolute Monitoring Center. This issue is now fixed. These fields are now recalculated on a daily basis to ensure that they reflect the correct value based on the 30-day period prior to the current date.
History > Events

  • When a theft report is created for a missing device, the associated events are now logged in the correct order: the Missing device found event is now logged before the Theft report created event. In addition, the Missing device found event now explicitly states that the event was triggered by a new theft report.
License Management

  • Fixed an issue where manual license assignment requests could fail to complete when multiple licenses of the same type were available. Previously, if the first license in the sequence was exhausted, the system could become unresponsive during the transition to the next available license. Manual assignment now correctly uses all available licenses to ensure the process completes successfully.
Mac support

  • The Secure Endpoint Agent for Mac now supports macOS 27 and runs natively on devices with Apple silicon, without relying on the Rosetta translation environment.

    macOS 27 requires agent version 11.1.0.2 or higher.
Playbooks (Absolute Rehydrate)
Reports

  • Recipients of scheduled reports can now unsubscribe from future deliveries directly from the report email by clicking a unique link in the footer. This self-service option removes the recipient from the distribution list without requiring action from the report owner or a console login.
User Management and permissions

  • The Device Usage reports permission, which is no longer applicable, has been removed from the Roles page in User Management.

    To allow a custom role to view device usage on the Dashboard, assign the View permission for Device reports. To allow a custom role to view and export device usage events on the History page in Device Details, assign the View permission for both Device reports and Audit Event History.

  • To view or export location related events on the History page in Device Details, the View permission for Geolocation is now required. To view locations below city level, the Address-level view permission for Geolocation is now also required.