New Features

Atlas Components for Discover

Four new Discover components are now available directly on an Atlas page, each usable by hand or through the Atlas agent.

• Discovery profile create/edit
  • Build and edit discovery profiles with guided guardrails for satellite caps, port-scan restrictions, and distributed scan bounds.
  • Sample prompt: Create a new discover scan profile.
• Unmanaged asset inventory
  • Review your unmanaged asset inventory without leaving Atlas.
  • Sample prompt: Show me unmanaged assets discovered in the last 7 days.
• Locations management
  • Add, edit, and review locations directly from Atlas.
  • Sample prompt: Add a new location called West Coast DC and assign it to the 10.40.0.0/16 network.
• Networks management
  • Manage your networks directly from Atlas.
  • Sample prompt: List all discover networks that are defined.

Improvements

• Upgraded various third-party libraries to newer versions.

Resolved Issues

• Fixed an issue where the discoverInterfaces query would return an error when a request asked only for a total record count without selecting any interface fields.
• Fixed an issue where CSV import routes for managing Locations were incorrectly available to the Atlas agent. They are no longer accessible through Atlas.
• Fixed an issue where label imports were incorrectly available to the Atlas agent. They are no longer accessible through Atlas until file upload support is added.
• Fixed an issue where a failed background task could poll indefinitely, allowing the Locations CSV export button to re-enable and start a second export before the first one finished.
• Fixed an issue where an import could get stuck and fail to restart after a transient database connection error.
• Fixed an issue where the interface and locations export endpoints were incorrectly flagged as read-only for Atlas agent tooling, even though each download deletes the underlying export file.
• Fixed an issue where Atlas agent tool annotations for the interface export endpoint incorrectly indicated the route had no side effects and could be called repeatedly with the same result.
• Fixed an issue where the import step error indicator could remain stuck in an error state after a previously failing step was skipped on a later import.
• Fixed an issue where a transient error retrieving satellite names could cause an entire import step to fail, even though the scan results had already been successfully merged.

Improvements

• Improved the reliability of Discover configuration changes so that database updates are fully committed before dependent actions, such as republishing profiles, are triggered.
• Upgraded various third-party libraries to newer versions.

Resolved Issues

• Fixed an issue where a discoverInterfaces query that requested only a total record count, without selecting any interface fields, returned an Internal Server Error.
• Fixed an issue where editing a network linked to a distributed profile might delay republishing the updated definition.

Known Issues

Cloud Instance sensors show "Content Not Available" after upgrading to 4.19.100

Starting in Discover 4.19.100, Discover no longer requires a set of Core Content sensors for its own internal processing, including Cloud Instance Account, Cloud Instance Type, and Cloud Instance Zone. As a result, Discover stopped automatically keeping these sensors registered with TDS.

The sensors themselves are unaffected and continue to function normally — they are simply no longer registered with TDS. Reports referencing these sensors will show "Content Not Available" instead of the expected data.

Resolution

To show the impacted sensor data in reports, register the Cloud Instance Account, Cloud Instance Type, and Cloud Instance Zone sensors with TDS.

1. From the Main menu, go to Modules > Interact > Overview.
2. Click Settings and then click Registration and Collection.
3. Use the filters to find each sensor.
4. Select Actions > Add.

Improvements

• Improved the efficiency of processing a large number of network configurations.
• Updated PowerShell scripts for Discover to run in AllSigned mode.
• Updated the REST API to reject not valid location IDs when writing location permissions.
• Moved the Label Gallery to a new URL.
• Upgraded various third-party libraries to newer versions.

Resolved Issues

• Fixed an issue where editing a network linked to a distributed profile might delay republishing the new definition.
• Fixed an issue where selecting the Lost value in a chart navigated to an incorrect page. It now links to the Lost Interface label page.

Improvements

• Profiles configured to exclude isolated endpoints now enforce an isolation stability check before launching a scan. Scans will not start until the endpoint's isolation status has been stable for 5 minutes; if that condition is not met, Discover retries up to 10 times at 5-minute intervals. This prevents scans from running against stale isolation attributes and resolves a class of false positives where isolated endpoints appeared to have been scanned.
• Upgraded various third-party libraries to newer versions.

Resolved Issues

• Fixed a regression where the periodic satellite profile validation incorrectly set DISABLED profiles to ERRORED. Because the profile sync loop treats ERRORED profiles as active, this caused explicitly disabled profiles to be republished, undoing the user's disable action.
• Fixed an issue where a DISABLED profile could retain live scan configuration items if the disable flow had previously failed to clean them up (for example, due to the regression in DISCOVER-8037). The periodic profile sync now detects and removes any lingering configuration for profiles in DISABLED status.
• Fixed an issue where editing a network in a way that invalidated associated profiles would unconditionally set all affected profiles to ERRORED, including those that were DISABLED or in the process of being disabled. The profile sync loop would then republish those profiles, overriding the user's explicit disable. Profiles that are DISABLED or DISABLING are now skipped during network-edit invalidation.
• The DiscoverInterface.cloudInstances and DiscoverInterface.cloudTags GraphQL fields were removed in Discover 4.19.73 without a prior deprecation notice, breaking existing integrations. Both fields have been restored. They are now formally deprecated and return empty data (Centralized Scanning, their data source, has been removed); clients should migrate away from them. The deprecation reason is visible via schema introspection.

Improvements

• Upgraded various third-party libraries to newer versions.

Resolved Issues

• Fixed an issue where some Scan Profiles would not be published correctly, leading to "profile failed to load" errors

Known Issues

• The following Discover GraphQL fields cloudtags, cloudtagname, cloudtagvalue, and cloudInstance were removed before being deprecated, which is cause errors in any integrations that reference these fields. These fields are related to functionality that was never introduced to Tanium Cloud should not be populated with any meaningful data. We are working towards restoring these fields with null values and formally deprecating them.

New Features

• Enabled a new Guide Notification for Discover that notifies users when more than 10%+ of managed interfaces are lost over the past 24 hours.
• Enabled a new Guide Notification for Discover when the unmanaged interface discovery count increase by 10%+ in last 24 hours.
• Enabled Tanium Ask to answer questions about Discover Labels.
• Enabled satellite scan profiles to support network sizes up to 65,536.

Improvements

• Upgraded various third-party libraries to newer versions.
• Removed all remaining Centralized Scan Profiles artifacts following end of support for the feature.
• Upgraded various third-party libraries to newer versions.
• Re-added icons to the interfaces list view.

Resolved issues

• Fixed an issue where newly-isolated endpoints would start scanning as if they weren't isolated
• Fixed an issue where loading the Locations views were taking 30 to 60 seconds to load.
• Fixed an issue where Profiles could not have both Standard and VPN Networks as exclusions at the same time.
• Fixed an issue where interface exports fail when any permissions are present.
• Fixed an issue where Profiles with multiple Network inclusions or exclusions would only display one Network.
• Fixed an issue where "Lost Interfaces" count on the Overview page was displayed 0 when it shouldn't be.
• Fixed an issue on the Profiles page where the Reimport Scan results and Create Profile button no longer have a space in between them.
• Fixed an issue where a failure during the initial execution of schedulePeriodicActivity at service startup could cause the service to crash and restart repeatedly.
• New indexes added to the InterfaceLocations table.
• Fixed an issue where reports generated with sorting on a non-visible column caused the report to error.
• Fixed an issue when viewing import results from "Yesterday".

Improvements

• Exclusion/Inclusion Profile count now included in Networks list
• Interface Details are now in a flyout instead of on a separate page.
• Profile Details page now shows the profile status.
• On the Profiles detail page, the satellite same now hyperlinks to the corresonding satellite details page.
• A 10mb file size is now enforced on all uploads, including Location .CSVs
• On the Profile lists page in the detailed view, listed networks now link to corresponding network details page.
• Updated third party dependency
• Port ranges and lists are now validated without needing to submit the form.
• Deleting a Label now shows a notification when successful.
• Upgraded various third-party libraries to newer versions.

Resolved issues

• Fixed an issue where Import Frequency setting was not validated to prevent micsonfigured values and breaking manual imports.
• Fixed an issue where interfaces could be purged during the application of locations.
• Fixed an issue in profile editing where the previous value for additional ports could persist when only "top 1000" is selected.
• Fixed an issue where networks would disappear when multiple were added to network inclusions or exclusions. The network pills will now wrap on the profile detail page.
• Fixed an issue with Network names being spaced incorrectly on the Profile Details page.
• Fixed an issue where Profiles list in Interface detail page are displayed incorrectly.
• Fixed a typo in, "A scan is already in progress". This status is now indicated with a green loading circle.
• Fixed an issue with the Add Label dropdown for adding manual Labels.
• Fixed an issue where Label filters using deprecated properties would display as "" instead of showing a warning indicating that the field is no longer supported.
• Fixed an issue causing service restarts caused by activity failures after startup.
• Fixed an issue causing locations to be calculated twice.
• Fixed an issue causing location calculations to fail if import overlapped at scale.

Improvements

• Introduced a brand new, dedicated page to manage and modify networks to be used when configuring scan profiles.
• The same network can no longer be included in a profile's network inclusion and exclusion configuration.
• Improved performance and stability when processing large locations files.
• Upgraded various third-party libraries to newer versions.

Resolved issues

• Fixed an issue where Connect jobs were timing out when Locations were being applied.
• Fixed an issue where Locations were getting applied to IPv6 interfaces inefficiently.
• Fixed an issue where the profile name was unclickable on the Profile list view after publishing edits to the profile.
• Fixed an issue where scan exclusions were not showing up on the profile view page.
• Updated definitionPurge Stale Interfaces label to use "Last Seen older than 7 days" for new Discover installations.

Improvements

• Resolved an issue where distributed profile statuses were stuck in an invalid state.
• The option to exclude Zone Servers from profiles has been hidden.
• Contact support workflows now link directly to our "How to Submit a Support Case" help article for clearer guidance on getting help.
• Improved user experience by adding a loading state when profiles are refreshing.
• Resolved an issue to ensure profile compatibility with the latest endpoint tools
• Various improvements to support future Discover functionality.
• Upgraded various third-party libraries to newer versions.

Resolved issues

• Fixed an issue where spaces were not being handled properly when defining defining multiple networks.
• Fixed an issue where invalid IPv4 endings were not handled properly.
• Fixed an issue when updating disabled distributed profiles where they would being limited to 4096 IPs in their inclusions.