Changes to Default Behavior in 2026
Focus
Focus
Device Security

Changes to Default Behavior in 2026

Table of Contents

Changes to Default Behavior in 2026

Review changes to default behavior in Device Security.
Where Can I Use This?What Do I Need?
  • Device Security (Managed by Strata Cloud Manager)
  • (Legacy) IoT Security (Standalone portal)
One of the following subscriptions:
  • Device Security subscription for an advanced Device Security product (Enterprise, OT, or Medical)
  • Device Security X subscription
Review the following changes to default behavior in Device Security.

Changes to Default Behavior Introduced in February 2026

The following table details the changes in default behavior for Device Security in Strata Cloud Manager, introduced in February 2026.
ComponentChange
All pages
The Device Security banner no longer appears on pages that aren't part of the tabbed navigation.
Device Details and Asset Inventory
The Last Activity attribute for devices now comes from two new, distinct timestamp attributes. The Last Network Activity attribute reflects only network traffic, while the Last Third-Party Activity attribute reflects third-party integrations data. The Last Activity attribute displays the latest activity timestamp between Last Network Activity and Last Third-Party Activity.
Device Details and Asset Inventory
The AD Join Status now uses information from traffic in addition to existing information from third-party CIE integrations.

Changes to Default Behavior Introduced in January 2026

The following table details the changes in default behavior for Device Security in Strata Cloud Manager, introduced in January 2026.
ComponentChange
Firewalls
On the Firewalls page, the filter bar moved into the Firewalls table to reflect the limited scope of filtered data.
Assets
When downloading the Assets Inventory, the web interface now shows an estimated download time.
Query Builder
Throughout the web interface, all pages and workflows now use the new Query Builder. The behavior of the Query Builder may be fixed depending on the capability of the feature or workflow where it appears.