IMPORTANT: This site is planned to be decommissioned in 2026. Visit the Tanium Resource Center for all Tanium release notes, user guides, and support information. To view release notes in the Resource Center, see Tanium Release Notes.
IMPORTANT: If you are using semi-annual releases for on premises, see the Release notes for 2024H1 semiannual release, Release notes for 2024H2 semiannual release, or Release notes for 2025H1 semiannual release on the Tanium Resource Center.
Effective October 15, 2024: On prem release notes on the Tanium Knowledge Base are frozen. For release notes related to 7.4 or 7.5 Server and Solutions, see the Monthly updates for Tanium Version 7.4 and 7.5 Server and Solutions on the Tanium Resource Center.
Tanium Cloud Release Notes Attack Path Mapping
Tanium Cloud Release Date: 19 November 2026
Improvements
- Added seven new attack path detections for the Java4Shell vulnerability (CVE-2026-114938, remote code execution in the Java runtime). The new detections cover Internet-exposed Java services and web properties observed in EASM data, Tanium-managed endpoints that report the vulnerability, and the cloud, identity, and on-premises targets reachable from them.
Tanium Cloud Release Date: 18 November 2026
Improvements
- The Attack Path Mapping User, Attack Path Mapping Operator, and Attack Path Mapping service account roles now include the Read data graph privilege on the Microsoft Entra ID content set. Users with the User or Operator role can read all Microsoft Entra ID graph data, including identities that do not appear on attack paths. Until Tanium Data Service defines this privilege, these roles show a harmless unknown-privilege warning.
- Users with the Attack Path Mapping User or Attack Path Mapping Operator role can now open attack path details and node details without also holding an Interact or administrator role.
- Blast radius now follows every relationship type that an attack path crosses between its entry point and its target, so more crown jewels appear within three hops of a node on a displayed path. Detected attack paths and their scores do not change.
- You can now designate Tanium-managed endpoints as crown jewels by node ID. Detected attack paths do not change unless you designate an endpoint as a crown jewel.
Tanium Cloud Release Date: 9 November 2026
Important Notes
- Modified detection logic on EC2 instances related to instance metadata endpoint settings and IMDSv1 in order to tighten detections and reduce false positives.
- The IMDSv1 internet-exposed instance crown jewel designation and the Enforce IMDSv2 recommended action no longer apply to an EC2 instance whose instance metadata endpoint is disabled.
- Attack Path Mapping now reads the severity of a vulnerability observed in EASM data from the linked CVE record's CVSS v3 severity, matching External Attack Surface, instead of the discovery provider's severity. Detections and recommended actions that depend on vulnerability severity might match a different set of findings at their next run, and a vulnerability with no linked CVE record carries no severity.
Features
- Added three new Attack Path detections for Ollama LLM vulnerabilities, Bleeding Llama (CVE-2026-7482, memory disclosure) and Probllama (CVE-2024-37032, remote code execution).
- The new detections focus on Internet-exposed Ollama LLM services that could allow attackers to steal credentials, elevate privileges, or gain access to enterprise and Cloud assets.
- Added the Attack Path Summary tiles to the top of the Attack Paths Overview: open attack paths, open paths that reach a crown jewel, and choke points. Each count opens the matching list.
- Added the Crown Jewel Exposure panel to the Attack Paths Overview, which ranks crown jewels by the open attack paths that reach them and shows the Critical count for each. A count opens the Attack Paths list scoped to that crown jewel.
- Node Details can now open for a node on its own, without an attack path. It shows the name of the node, type, properties, crown jewel designation, choke point metrics, blast radius, and endpoint identity and exposure.
- Updated and improved the new Choke Points "Fix-First" list with additional remediation information and guidance for specific findings. The Choke Points recommended actions now cover several additional conditions: roles with wildcard permissions, critical vulnerabilities observed by EASM, administrative service Internet exposure, nested groups that provide Tier0 privileges, endpoint policy non-compliance, and more.
Improvements
- In Crown Jewel Exposure and Entry Point Exposure, the crown jewel or entry point name opens Node Details for that node.
- In Choke Points, the choke point name opens Node Details for that node.
- In the Attack Paths list, the terminal name and each crown jewel name open Node Details for that node.
- The Crown Jewels cell in the Attack Paths list now shows the crown jewels on the path one per line, with a +N control that opens the full list when a path has more than three.
- The Entry Point Exposure counts now open the Attack Paths list showing only the paths that start at that entry point, so the list total matches the count.
- The attack path list API now accepts an entry element id filter, alongside the existing terminal element id filter, to return only the paths that start at one node.
- The Choke Points known-exploited and weaponized-vulnerability recommended actions now appear on the entities carrying a vulnerability, instead of the vulnerabilities themselves.
- Atlas prompts and templates can now open Attack Paths lists with any list filter and search text already applied, for example internet-exposed and EASM observed, or paths ending at specific nodes.
- The Attack Paths list, Entry Point Exposure and Crown Jewel Exposure offer an Open Integrations Gallery action when no attack paths have been detected.
- The no-attack-paths note on theEASM Convergence panel also offers the Open Integrations Gallery action.
- Clicking a bar in EASM Convergence opens the Attack Paths list as a page panel, as the other panels do.
- The Attack Paths and Choke Points lists now search once typing pauses instead of on every keystroke.
- In Attack Path Explorer, the panel for a vulnerability observed in EASM data shows the linked CVE record's CVSS v3 severity.
- Crown Jewel Exposure, Entry Point Exposure and Choke Points now carry a subtitle that says how each list is ranked and what a count opens.
- In Node Details, a metric label that does not fit its column ends in an ellipsis and shows its full text in a tooltip.
- Attack Path Mapping now records IPv4 and IPv6 addresses for each endpoint on its graph node, and Blast Radius results include them. Detected paths do not change.
- Attack Path Mapping now records each endpoint's domain name and cloud instance hostname on its graph node.
- Azure network security group detections were rewritten to run more efficiently in large environments.
- Several detections that check IAM policies now run those checks only on candidate paths, improving detection time in large environments.
- AWS detections that trace an exposed instance or load balancer to an instance role were rewritten to run more efficiently in large environments.
- Upgraded several internal dependencies.
Resolved Issues
- Corrected an issue where the hop labels in the Blast Radius graph sat one ring closer to the focal node than the band they named, so a node appeared one hop further away than it was.
- Corrected an issue where Attack Path Mapping could repeatedly restart, and its API become unavailable, when a sensor it requests at startup was not installed on the tenant.
Tanium Cloud Release Date: 2 November 2026
Important Notes
- An attack path's severity steps and path edges are now listed from the entry point to the terminal, whatever direction its detection rule is written, so the Why this severity? panel reads in the same order as the drawn route. Paths whose score depended on how their rule was written now score consistently, so the severity of some existing paths may change at their next detection.
Features
- The Attack Paths page template is now the Attack Paths Overview and includes the Choke Points list below the Attack Paths list. Pages already created from the earlier template are unchanged.
- Added the Entry Point Exposure panel to the Attack Paths Overview, which ranks Entry Points by the open attack paths that start at them and shows the crown jewels reachable from each. An Entry Point that is itself a Crown Jewel carries the Crown Jewel badge.
- Added the EASM Convergence panel to the Attack Paths Overview, which shows four nested counts on one scale: open attack paths, those that EASM observed, those also internet-exposed, and the Critical paths among those. Clicking a bar opens the Attack Paths list with the matching filters applied.
Improvements
- The Attack Paths list now shows a severity bar above the grid with the Critical, High, Medium, and Low counts for the paths that match the current filters. Clicking a band or its legend item filters the list by that severity, and the column filter menu and Clear filters follow.
- The Attack Paths list has a new CVEs column, hidden by default, that lists the CVE ids on each path, with a Contains filter. An Atlas prompt or a template can open the list with a CVE id filter already applied, and a CVE id typed in the search box also matches the paths that carry it. A path whose rule names a CVE only as a condition lists no ids.
- The attack path list APIs now serve the CVE ids on each path and accept a CVE id filter, so a CVE-to-path question in Atlas is answered from Attack Path Mapping.
- An Atlas prompt or a template can now open the Choke Points list with its search text and node type filter already applied, and an operator's search and sort survive a page refresh.
- In Attack Path Explorer, the hop, node, and evidence counts now sit beside the severity badge, and the View path details button sits above the graph.
- Attack path list and detail responses in the Attack Path Mapping v2 API now include the node type of the path's entry point alongside the terminal type. Paths detected before this release get the value from stored node data, and the field is empty when the entry point's type is unknown.
- Attack Path Mapping now links managed endpoints to cloud instances and identities via correlations much more efficiently in large deployments.
- Attack Path Mapping now generates and updates correlations for nodes between different environments and identity providers hourly instead of every 15 minutes.
- Several existing detections were updated to improve efficiency and timing for larger environments and environments with larger cloud instance and identity datasets.
- Upgraded several internal dependencies.
Resolved Issues
- Fixed an issue where the detection linking a vulnerable web property to an EC2 instance role with full IAM authority timed out and reported nothing on deployments where many web properties share an IP address.
Tanium Cloud Release Date: 29 October 2026
Important Notes
- The Choke Points list no longer credits a node for an attack path that ends at that node, because protecting the target does not remediate the path. # Paths and the other path counts now include only the paths that a node sits in the middle of, and a Crown Jewel in the middle of a path is credited the same way as any other node. On deployments where a node was credited for paths that end at it, its counts go down and its Fix-First Rank can change.
- Vendor-managed cloud policies and built-in role definitions, such as an AWS managed policy or an Azure built-in role, are no longer eligible as choke points. They cannot be edited; the fix is to detach them from the identities that hold them, and those identities already earn the credit. Customer-managed policies and custom role definitions remain eligible.
Improvements
- An Atlas prompt can now open the Attack Paths list with any of its filters and its search text already applied, for example only Internet-exposed paths that EASM observed, or only the paths that end at a given node. The applied filters appear in the search box and the column filter menus and can be cleared.
- A template can now open the Attack Paths list with search text and column filters already applied, and panels saved with the earlier severity-only setting keep that filter.
- When the Attack Paths list has no paths at all, it now explains that attack paths are built from identity and cloud data and points to the Integration Gallery to connect an identity or cloud provider, instead of showing the filter-mismatch message. A list that is only filtered down to zero keeps the existing message.
- In Attack Path Explorer, clicking a node whose Node Details peek is open now closes the peek, and clicking a different node switches to that node.
Resolved Issues
- Fixed an issue where the KEV column in the Attack Paths list was always empty, even when a path included a vulnerability in the Known Exploited Vulnerabilities catalog.
- Fixed an issue where the KEV flag and the Data sources row in Node Details were empty for every path. Attack Path Mapping now derives the KEV flag from the CVE nodes on the path, so the Explorer card, the list column, and the peek agree.
- Fixed an issue where the Properties tab in Node Details and in the evidence panel showed "No further details are available" next to the load error when a node's details failed to load. The tab now shows only the error notice, and an endpoint's sensor rows still appear.
- The attack path, choke point, and path membership list APIs now reject a sort that names the same column twice, and paging continues past rows with very long names instead of failing on the next page request.
- The # Paths drill-down now opens the same paths that the count credits, so the list and the count agree.
Tanium Cloud Release Date: 28 October 2026
Important Notes
- The Choke Points list now includes only nodes that an operator can act on directly: assets, groups and roles, and customer-managed policies and role definitions. Shared definition nodes (such as a CVE, a software version, a tag, or a machine image) and finding records no longer appear as choke points, because the fix for them is on the assets that carry them, and those assets already earn the credit.
- On deployments where a CVE was listed as a choke point, that row is removed and the rows below it move up one Fix-First Rank. Nothing else in the list changes.
- The Recommended Actions hints for a CVE in the Known Exploited Vulnerabilities (KEV) catalog with a vendor patch available and for a weaponized CVE applied only to CVE rows, so they do not appear in this release. They return on the asset that carries the CVE in a later release.
Improvements
- Recommended Actions hints in the Choke Points list now name the affected resource or account, for example "Enforce IMDSv2 on <instance>" instead of a generic label.
- The removal-impact section of Node Details now names each downstream Crown Jewel that the node does not fully cut off and states how many other open attack paths still reach it, so you can see how many more paths must close before the node becomes a true cut.
- Node Details and the evidence panel for an EASM host or web property now include a View host in EASM or View web property in EASM link that opens the EASM Host Details or Web Property Details view in the side drawer, or as a new panel from +. The link appears only when the console can open that EASM view and the asset has the identifier that EASM needs.
- The Overview tab of an EASM asset's evidence panel now says how the asset matches the attack path, in the same wording as its EASM Observations row (for example, "Shares its host name with <node>"), with a link to each node it reached. It replaces the Observed Through and Exposes lists for EASM assets.
- Traversal confidence in Path details is now shown on the connector between two nodes, with a visible label, so it is clear that confidence belongs to the step between nodes rather than to a node.
- Node Details now uses the node data that the attack path already loaded, so the header and the Designation section agree on whether a node is a Crown Jewel.
Resolved Issues
- Fixed an issue where a crown jewel designation that failed to load was shown as not a crown jewel. Attack Path Mapping now shows a warning with a Retry button when it is unable to load the crown jewel designations for an attack path, and the warning for nodes with limited detail also has a Retry button.
- Fixed an issue where the Exposure section of Node Details could show an endpoint with no vulnerability findings when the findings failed to load. The section now shows a load error with a Retry button.
- Fixed an issue where a long server message under Show error detail in the Blast Radius panel or the Exposure section of Node Details extended past a narrow side drawer and clipped the Retry button. The message now wraps, and the disclosure matches the other collapsible sections in the panel.
Tanium Cloud Release Date: 26 October 2026
Important Notes
- This release adds the new Choke Points "Fix-First" list, a ranked view of the nodes whose remediation, mitigation, or corrective action closes the most open attack paths.
- The Choke Points "Fix-First" list includes a Recommended Actions column providing remediation hints for choke points where Tanium can identify the most effective resolution.
- This release also adds new attack path detections for the recently identified PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619).
- The new detections cover Internet-exposed and EASM-observed web services, cloud provider assets, Tanium-managed endpoints, and the on-premises, cloud, and identity-based targets reachable from them.
- Attack paths that pass through a CVE with a weaponized exploit no longer score Low when the CVSS vector of the CVE rates exploitation as difficult. Some of these paths show a higher severity after their next detection.
Features
- Added the Choke Points list, which ranks the nodes whose remediation closes the most open attack paths. Columns include Fix-First Rank, EASM & Internet-Exposed, Choke Point, # Paths, Critical Paths Closed, Crown Jewels Reachable, Crown Jewels Protected, Entry Points Cut, Correlated Paths, and Recommended Actions.
- Fix-First Rank orders the list by outcome: the critical paths a node closes, the crown jewels it protects, the entry points it cuts, and the open paths it sits on.
- Recommended Actions lists remediation hints for conditions detected on choke points, such as a missing MFA registration, wildcard permissions policies, or CVEs in the Known Exploited Vulnerabilities (KEV) catalog that have a vendor patch or software update available. The column shows up to two hints and a +N more expander. A dash means that APM found no listed condition on the node, not that no remediation exists.
- Nodes that close the same set of paths are grouped as equivalent cut points under one row.
- Added nine new attack path detections for the PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619).
- The detections cover Internet-exposed web services or load-balanced websites that EASM data marks as affected or that report PHP versions earlier than the fixed version for their branches, and Tanium-managed endpoints that report the vulnerabilities. They also cover the targets reachable from those systems, services, and assets: AWS instance roles with broad permissions, top-tier Entra ID administrative accounts, and Active Directory computer accounts with delegation to domain controllers.
- A path that reaches an EC2 instance role is reported only when the instance metadata endpoint is enabled, because the credential step that the detection describes cannot happen when the endpoint is disabled.
Improvements
- Renamed Internet-facing to Internet-exposed in the Attack Paths list, Node Details, and the Blast Radius panel.
- Added help tooltips to the Internet-Exposed column in the Attack Paths list.
- An attack path is Internet-exposed when it starts at a node with a public IP address or host name. A node is Internet-exposed when it has a public IP address or host name.
- EASM Observations rows in Path details now read as a sentence that names the EASM asset once, says how it matched the path (for example, by a shared public IP address or host name), and names the nodes that it reached. When the path starts at an EASM-discovered asset, the first row says so.
- Revised error messages, empty states, and notices across Attack Path Mapping for consistency. For example, "Couldn't load..." messages now read "Unable to load...".
- Updated the list component column headers for capitalization, consistency, and spacing.
- In exported Attack Paths and Choke Points grids, the Initial access and Internet-exposed column headers are now Initial Access and Internet-Exposed, and EASM & Internet Exposed is now EASM & Internet-Exposed.
- Changed View Blast Radius in Node Details and View path details in the Attack Path Explorer from links to buttons.
- When Node Details, Blast Radius, or the Attack Paths list fails to open from another view, the error notice now names which view failed and appears in place instead of as a toast notification.
- A detail view that is promoted from the side drawer to a panel now keeps the same title.
- Improved loading time for the Attack Paths list and for path counts in Node Details in deployments with many attack paths.
Resolved Issues
- Fixed an issue in environments with many Active Directory computer records where the task that correlates Tanium-managed endpoints with their cloud instance, Entra ID device, or Active Directory computer records could fail, so attack paths that depend on those correlations were not detected.
- Fixed an issue where a closed attack path lost its EASM Observed marker, its EASM asset on the drawn path, and its EASM Observations rows. A closed path now keeps the evidence it had when it closed.
- Paths that closed before this release do not regain the marker until they are detected again.
- Fixed an issue where Path details showed the old title and description of an updated detection when another detection kept the attack path open.
- Fixed an issue where each row in Path details showed the confidence of any relationship leaving that node instead of the confidence of its next step on the attack route.
- Each row now shows one confidence, for its step on the route or for the relationship that joins it to the path.
- Fixed a counting issue where the Paths to count in the Paths tab of Node Details could exceed the total and the Paths through count showed 0, because the two counts were calculated at different times.
- Fixed an issue where truncated text in the Attack Paths list, the Choke Points list, and the Attack Path Explorer title could not be read in full.
- Truncated text now shows its full value in a tooltip, and the tooltip no longer appears when nothing is truncated.
- Fixed an issue where the Paths tab in Node Details scrolled sideways and cut off a label in a narrow side drawer.
- Fixed an issue where wrapped text in the Attack Paths list and the Choke Points list sat at the top of the row while other cells were centered.
Tanium Cloud Release Date: 21 October 2026
Important Notes
- In the Attack Path Explorer, details for a path or a node now open in a resizable side drawer. The fixed details column on the right side of the Explorer has been removed, and the in-place Blast Radius mode in the Explorer is replaced by a View Blast Radius button in Node Details.
- Zooming in the Attack Path Explorer and Blast Radius graphs now uses zoom buttons instead of the mouse wheel or trackpad scroll, so page scrolling no longer stops when the pointer is over a graph.
- Attack path severity no longer applies a reduction when a path steps from a Tanium-managed endpoint to the cloud instance, Azure virtual machine, or Active Directory computer record for the same machine. Attack paths that include one of these steps may show a higher severity after their next detection.
Features
- Added a side drawer to the Attack Path Explorer for attack path and node details, with breadcrumb navigation between a path and its nodes.
- Path details shows the full attack path summary, a Why this severity? breakdown that lists the vulnerabilities and harder-to-abuse steps on the path with their exploitability weights, and a count of hops, nodes, and evidence records. The Explorer shows the same summary line under the path title, with a View path details link.
- Node Details is organized into Overview, Properties, and Paths tabs. Overview shows the node's badges, such as Crown Jewel and Choke Point, how many open attack paths run through the node, and which reachable crown jewels would be fully cut off if the node were removed. The Paths tab shows how many open attack paths reach or pass through the node, by severity, and for a crown jewel, where those paths start.
- Evidence nodes on a path, such as an EASM-observed host or an internet exposure record, open in the same tabbed layout.
- Added an EASM Observed column and filter to the Attack Paths list, and an EASM Observed badge and EASM Observations section in Path details, to show when EASM data discovered an asset on the path or observed a resource on the path from the internet. The marker does not change severity or score.
- EASM-discovered nodes on the Attack Path Explorer and Blast Radius graphs carry an EASM badge, in the same way CVE nodes carry a KEV badge.
- Added the attack path ID to Path details, with a button to copy it, so a specific finding can be shared with a colleague or Tanium Support.
Improvements
- Node names are now consistent across the Attack Paths list, the Attack Path Explorer, Node Details, and Blast Radius, because every view now uses the same naming.
- Names that look like email addresses in the Attack Paths list are no longer rewritten as "<domain> Domain User", so a user can be recognized by name.
- Internet exposure nodes are now named by the type of exposure, for example Internet Exposure (IP) or Internet Exposure (FQDN). Open Node Details to see the exposed address.
- Load balancer listeners, ECS tasks, and ECS container instances are now named from their own properties, such as the load balancer name and protocol, instead of an opaque identifier.
- Node type names now include the provider, for example AWS IAM Role, Entra ID Role, or EASM Host, so types that share a name across providers can be told apart.
- The Internet-facing column and filter in the Attack Paths list now reflect whether the path starts from an internet-exposed entry, including an EASM-discovered asset, instead of whether a vulnerability on the path is reachable. Closed paths keep their last detected value.
- Updated the titles, descriptions, entry classes, and pivot techniques of the attack path detections to use clearer, more consistent wording, including internet-exposed in place of internet-facing. Detection logic is unchanged.
- Attack path severity now treats the step from a Tanium-managed endpoint to the cloud instance, Azure virtual machine, or Active Directory computer record for the same machine as a correlation rather than an attacker step, so paths that cross one of these steps are no longer capped at Medium severity.
- Node scores in Node Details are now computed along the attack route from the real entry point, so a vulnerability or evidence node attached to a path no longer reports that no crown jewel is reachable from it.
- The Blast Radius panel now names the node in its title, shows a clicked node's details in the same labeled layout as Node Details, and stacks the details below the graph when the panel is narrow. A Low or unknown severity now shows a neutral badge instead of Pending in the Attack Paths list.
- Blast Radius now explains why a result may be incomplete, such as a result limit, a shallower search depth, paths that could not be shown, or partial visibility, instead of showing one generic message.
- View Blast Radius is now a button above the tabs in Node Details, so it is visible on the Overview, Properties, and Paths tabs.
- The Attack Path Explorer graph is now oriented around the attack route, so evidence nodes no longer appear to be the start of an attack.
- Removed redundant nested borders and padding from the attack path panels.
Resolved Issues
- Corrected an issue where the Attack Paths list could appear stuck or empty, with no message, when a page of results failed to load. Load errors in attack path panels now show a message with a Retry button.
- Corrected an issue where Node Details for a computer could fail to load identity and exposure information when one of the underlying sensors was not collected in the deployment. Information that is available is now shown and the missing field is omitted.
- Resolved a rounding issue where an EPSS score such as 0.99998 was displayed rounded up to 1.00.
- Updated verbiage to address an issue where the Paths tab in Node Details labeled some terminal nodes as "Paths through this node" instead of "Paths to this node", including on attack paths with more than one terminal.
- Corrected an issue where the Top entry points count in the Paths tab did not match the number of entry points listed.
- Resolved an issue where a CVE's raw severity value was not shown on the Properties tab in Node Details.
- Addressed a display issue where some attack paths that enter through an internet-exposed cloud resource showed two internet exposure nodes for the same IP address.
- Fixed an issue where an attack path finding could remain open after a second detection that matched it was retired.
- Corrected an issue where open attack path findings from a superseded detection revision were not closed, so they kept the previous title and description after the detection was updated.
- Identified and applied a solution for when the Attack Path Explorer graph could keep a stale zoom level after its panel or the browser window was resized, so the graph appeared zoomed out or clipped at the edges.
- Corrected an issue where the Hops count for an attack path included relationships to nodes off the route from the entry to the terminal, so the count could disagree with the numbered steps in Path details.
- Stored paths pick up the corrected count on their next detection.
- Corrected an issue where existing crown jewel designations could lose their marker while one of the crown jewel designation rules was failing, instead of being kept until the rule recovered.
Tanium Cloud Release Date: 30 September 2026
Improvements
- Adjusted attack path scoring weights for role-assumption and Active Directory delegation relationship types to better reflect their relative exploitability.
- Expanded the Blast Radius traversals to include additional credential, policy, encryption, membership, and delegation relationship types.
Resolved Issues
- Corrected an issue where the Blast Radius view could experience an error and show a node as having zero reachable crown jewels as a result.
- Corrected an issue where requesting Blast Radius for a highly connected node could fail with an error due to the volume of returned results.
Tanium Cloud Release Date: 29 September 2026
Important Notes
- This release of Tanium Attack Path Mapping (APM) broadens attack path coverage by surfacing findings beyond crown jewel-terminated attack paths. APM no longer requires that an attack path terminate at a crown jewel to produce a valid finding.
- This gives customers a fuller picture of exploitable attack paths across their environment, while confidence ranking and severity scoring continue to establish clear priority.
- Attack path severity continues to be anchored by Tanium and customer-designated crown jewel presence as the highest-weighted factor.
- Severity and confidence scoring have been re-tuned for this release to keep signal-to-noise high and prioritization clear, even as more findings may be surfaced.
- A path's severity now reflects the highest-value crown jewel found anywhere along the path, not only at its terminal, so more attack paths are visible without losing prioritization accuracy.
- Redesigned the Attack Path Explorer and Blast Radius node icon system around three categories (Identity, Asset, Finding) and a collection of icon shapes shared across categories, for more consistent and readable graphs.
Features
- Added separate Terminal and Crown Jewels columns to the Attack Paths list component, along with a filter for whether a path contains a crown jewel.
- Added visibility into a finding's EASM exposure and asset evidence, such as internet-facing hosts or web properties, alongside the structural attack path in the Attack Path Explorer.
- Selecting an evidence node opens a read-only details pane; hop counts continue to reflect only the structural path.
- Added additional crown jewel designation for Azure role assignments that grant Owner, User Access Administrator, Contributor, Role Based Access Control Administrator, or a broad Key Vault administrator role at the tenant root or a management group scope.
- Added crown jewel designation for the Azure Owner, Contributor, and User Access Administrator role definitions.
- Added additional crown jewel designation for AWS, Entra ID, and Microsoft Active Directory roles, built-in accounts, and non-human identities (NHI).
Improvements
- Attack path nodes for AWS ECR image scan and GuardDuty findings now draw with the finding icon instead of the AWS provider icon, matching the other vulnerability and misconfiguration findings.
- Crown jewels shown on the Attack Paths list and in path details now display a readable name instead of a raw element ID or security identifier, and can be searched or filtered by that name.
- Added new, expanded, and refined attack path detection coverage across Tanium External Attack Surface Management (EASM), AWS, Azure, Microsoft Entra ID, Active Directory, Tanium managed endpoints, and multi-provider scenarios, with over 100 new detections added, and 29 existing detections improved for accuracy and coverage.
- Added fallback graphics for existing APM providers so that APM displays each provider's correct icon shape and color instead of a generic icon.
- Added several new edge patterns and colors for previously unstyled edge types in the attack path graph, including internet exposure correlation, certificate correlation, additional vulnerability and misconfiguration finding edges, and EASM evidence and exposure edges.
- Added a dedicated placeholder icon shown inside a recognized provider's correct shape and color when a node type has no dedicated icon yet.
- Removed the crown jewel Provenance column and filter from the Attack Paths list, and moved the crown jewel provenance information from the attack path detail pane to the appropriate Node Details pane's designation information (provenance, reason, set by, last changed) when viewing a crown jewel.
- Choke Point scoring now credits a node for protecting any crown jewel downstream on its path, not only when the path's terminal is a crown jewel, and a path with no crown jewel still contributes to convergence scoring, at a reduced weight.
- Narrowed automatic crown jewel designation for Microsoft Entra ID directory roles to the four highest-confidence Tier 0 roles (Global Administrator, Privileged Role Administrator, Hybrid Identity Administrator, and Application/Cloud Application Administrator).
- Changed AWS RDS crown jewel designation to be based on multi-AZ deployment or extended automated snapshot retention, signals of a genuinely critical database, instead of public accessibility alone.
- Narrowed the AWS KMS customer master key crown jewel designation to keys protecting a data-bearing resource, such as a snapshot, volume, secret, database, table, file system, or training job, and lowered its severity value to reflect the narrower, more precise scope.
- Removed automatic crown jewel designation of EC2 instances based solely on an attached wildcard IAM policy.
- Removed automatic crown jewel designation based on Active Directory Remote Desktop Users or Remote Management Users group membership, since it describes a lateral-movement vector rather than asset value.
- Removed automatic crown jewel designation of a device based solely on being owned by a privileged Microsoft Entra ID user, since that describes a pivot path to the identity rather than the device's own value.
- Removed automatic crown jewel designation of S3 buckets based solely on internet-exposed access-block configuration, since exposure alone does not indicate the bucket holds valuable data.
- Added curated Node Details fields for Azure virtual machine, network security group, security rule, and network interface nodes.
- Redesigned the Attack Paths list toolbar into a single row showing an "X of Y attack paths" count, a search box, and a Clear filters button that appears when a filter or search is active and resets the list to show all detected paths, including closed ones.
- Added sorting support for additional Attack Paths list columns, including Status, Internet-facing, Ransomware, Botnet, and EPSS.
Resolved Issues
- Fixed an issue where exporting the Attack Paths list to CSV or PDF, or hovering a truncated cell, showed the KEV column's internal filter value instead of Yes or blank.
- Fixed an issue where the Node Details panel's "Closest crown jewel" hop count and its count of Crown Jewels reachable only through that node could read as contradictory even though both were correct.
- Fixed an issue where the Attack Path Explorer detail panel and the Blast Radius node details pane showed a persistent native scrollbar instead of the standard hover-to-show scrollbar.
- Fixed an issue where a crown jewel marker edge could point to the wrong node after data was re-ingested, which could cause a genuinely designated crown jewel to be treated as undesignated.
- Fixed an issue where several on-premises Active Directory crown jewel designation rules matched privileged groups by their English display name instead of their security identifier, which could cause a renamed or localized privileged group to go undesignated.
- Fixed an issue where a single failing crown jewel designation rule could indefinitely block cleanup of stale crown jewel markers for other resource classes.
- Fixed the AWS Lambda wildcard and privilege-escalation crown jewel designation rules to designate the function's execution role, the asset actually at risk, instead of the Lambda function itself.
- Fixed an issue where the AWS IAM user wildcard and self-escalation crown jewel designation rule could never match any inline policy due to an incorrect graph traversal, and added detection for the same condition on managed policies.
- Reduced unnecessary re-fetching of node details in the Attack Path Explorer when the browser window regains focus.
- Fixed an issue where the AWS KMS customer master key crown jewel designation rule could fail to run due to a query error.
- Fixed an issue where APM could miscount the path summary's cross-environment hop count.
- Fixed an issue where the severity breakdown's exploit maturity value could show as an untranslated raw string instead of its localized label when the value was returned in lowercase form.
- Fixed a calculation error that prevented the on-premises Active Directory unconstrained-delegation crown jewel designation rule from matching as designed.
- Fixed an issue where filtering or searching the Attack Paths list by a detection rule ID could return no results for paths whose only contributing rule association had since closed.
- Fixed a rare race condition where a reopen or start-remediation request could occur at the moment a finding was being closed by the system, which could leave that finding incorrectly reopened.
- Fixed a race condition where two concurrent requests to change an attack path's status (close, reopen, suppress, or remediation state) could conflict.
- Fixed an issue where the DNS name field for AWS load balancer nodes in the Node Details pane was always empty due to a property name mismatch.
- Fixed an issue where the CVSS score field for CVE nodes in the Node Details pane was always empty.
- Fixed an issue where selecting more than one Severity band in the Attack Paths list filter returned paths of every severity instead of only the selected bands.
- Fixed an issue where show/hide column selections in the Attack Paths list were not remembered after a page refresh.
- Fixed an issue where a long detection rule title could overflow the rule switcher in the path detail pane instead of wrapping within it.
- Fixed an issue where two hybrid-bridge edge types, connecting on-premises Active Directory computers and Azure virtual machines to their Tanium-managed endpoint counterpart, rendered as plain default lines instead of the hybrid-bridge line style.
- Corrected several issues where nodes rendered with a generic gray icon instead of their intended icons.
- Fixed an issue where searching the Attack Paths list by certain keywords, such as tier-0, exploitable, database, Kerberos, or vulnerability, returned no results even when matching paths existed.
- Fixed an issue where the Attack Path Name column in the Attack Paths list could not be resized, unlike the other default columns.
- Fixed an issue where the Blast Radius and Attack Path Explorer graph views were pinned to a fixed height and did not expand to fill a resized panel.
Tanium Cloud Release Date: 18 August 2026
Improvements
- Expanded attack path detection with additional coverage of:
- On-premises Active Directory delegation and group-membership paths to Tier 0.
- Paths from AWS Application Load Balancers to EC2 instance roles.
- AADInternals and Mimikatz activity on managed endpoints.
- Microsoft Entra ID and Intune device-ownership paths to Tier 0.
- Improved and corrected existing attack path detections.
Resolved Issues
- Fixed an issue where Choke Point scoring credited a Crown Jewel for protecting itself, which could cause it to outrank genuine upstream choke points in the remediation priority list.
- Fixed an issue where some nodes could display the wrong type, name, and icon in the Attack Path Explorer and Blast Radius views, even though the Node Details pane showed the correct information.
- Fixed an issue where the "View all paths" error message could remain visible in the Attack Path Explorer after you select a different node.
- Fixed an issue where date filters on the Attack Paths list could include or omit an extra hour of results near a Daylight Saving Time change.
- Fixed an issue where node exposure summaries used inconsistent pluralization, for example "1 vulnerabilities" and "1 KEV".
- Fixed an issue where a Blast Radius error message could be partially hidden behind the Return to Path view button.
- Fixed an issue where Entry, Crown Jewel, and Blast Radius node names could display inconsistently.
- Fixed an issue where extraneous text could appear in node names.
- Fixed an issue where attack path step descriptions had inconsistent text formatting and overlapping rows.
- Fixed an issue where asking Tanium Atlas to "show me my choke points" returned Tanium Impact reach data instead of Attack Path Mapping choke point analysis.
- Fixed an issue where an attack path panel could display more than one title.
Tanium Cloud Release Date: 31 July 2026
Features
- Added support for Microsoft Active Directory and Microsoft Azure data sources. Attack Path Mapping (APM) now maps attack paths that begin, pass through, or terminate on Microsoft AD and Azure assets, alongside existing Tanium-managed endpoint, Entra ID, AWS, and EASM coverage.
- Added Confidence, a new rating shown alongside Severity for every attack path.
- Confidence is a separate rating from Severity: it reflects how certain APM is that a specific path is real, not how damaging the path would be.
- Each hop in a path is individually rated across four levels: Confirmed (a scanned vulnerability or an actual group membership), Session-confirmed (an observed session an attacker could reuse), Partially confirmed (a grant that exists on paper but isn't yet proven usable), and Assumed (a plausible, known technique with no direct evidence in your environment).
- A path's overall Confidence reflects its single weakest hop, so a path is never shown as more trustworthy than its least-proven step.
- Confidence never modifies or lowers Severity. The two ratings are shown independently.
Improvements
- Improved the context and details APM provides in the Attack Path Explorer details pane:
- Why this severity shows the factors behind a path's severity band (terminal value, exploitability of each vulnerable hop, and reachability) in plain language, never as a raw score.
- Per-hop and path confidence shows each hop's confirmed-versus-assumed status and the path's overall confidence rating.
- Why this choke point shows the reasoning behind a node's choke-point designation.
- Explanations render only for the factors available for a given finding.
- Crown Jewel details now show more about how and why a node was designated as a Crown Jewel (provenance).
- The details pane shows a Crown Jewel's class, whether its designation is a Tanium default or a customer override, the reason for the designation, who set an override, and when it last changed.
- Every Crown Jewel now carries a Terminal Value weighting reflecting how much compromising it would actually matter (for example, a Global Admin role is weighted higher than a Helpdesk Admin role), modeled on the MITRE Crown Jewels Analysis (CJA) framework.
- You can pivot from a Crown Jewel directly to a filtered list of every other attack path that reaches it.
- Choke Point analysis now shows the reasoning behind every choke point:
- Why the node was identified as a choke point.
- How many attack paths would close if the node were remediated, mitigated, quarantined, or otherwise addressed.
- How many Crown Jewels the node protects, computed as a true "cut": Crown Jewels that would actually become unreachable if the node were removed, not simply Crown Jewels that happen to share a path through it.
- Each choke point is individually scored by how effectively addressing it reduces the overall paths to Crown Jewels.
- The Attack Paths list component now supports more ways to filter, sort, and understand each finding.
- New sortable/filterable columns: First Detected, Last Seen, and Closed (These columns are hidden by default and can be enabled by column controls.)
- New filters for scoring-derived attributes: internet-facing entry, exploit maturity (Weaponized / Functional / Proof of Concept), ransomware association, botnet association, and EPSS threshold.
- New Initial Access column and filter, classifying how a path's entry point was reached (network exploit, managed endpoint, or valid account).
- Crown Jewel and Path Name columns are now sortable and filterable by substring. Severity and KEV filters now support multiple selections at once.
- The list defaults to showing only Open attack paths, with a Status column and filter to also view Closed paths.
- When an attack path is produced by more than one detection rule, the path details pane shows a rule switcher so you can review each contributing rule individually.
- Selecting any node in the Attack Path Explorer now always shows a populated, formatted details pane, including curated field sets for AWS, EASM, Entra ID, and Active Directory node types.
- Attack Path Mapping ships with an expanded detection rule library, adding attack paths across on-premises Active Directory, Azure, and combined endpoint, AD, and cloud-provider scenarios.
- Added several improvements to Attack Path Severity scoring. Severity is now computed from exploitability combined with target value across the entire attack path. New exploitability inputs include EPSS, exploit maturity, ransomware and botnet association, asset reachability, initial-access type, and a difficulty weighting for every identity, permission, delegation, and hybrid-bridge hop along the path, including the new Active Directory and Azure bridge edges. A single hard-to-abuse hop anywhere in the chain meaningfully lowers a path's severity.
- Improved Choke Point scoring to enhance how APM calculates the set of Crown Jewels that would actually become unreachable if a node were remediated. A node's Choke Score is now composed from convergence, Crown Jewel value, and cut-leverage factors.
- Blast Radius counts that hit an internal result limit are now shown as "N+" with a "limited" indicator instead of being displayed as an exact count.
- Attack Path Mapping now reads Comply, EASM, and Cloud Entity Provider vulnerability data from Tanium Data Service native CVE nodes.
Resolved Issues
- Crown Jewel designations set by Tanium defaults now always include a reason, and designation overrides persist reliably through Attack Path Mapping periodic reconciliation.
- Improved attack path detection reliability: invalid or disconnected paths are now rejected before they can appear as findings, and duplicate detections of the same real route are correctly recognized and counted as a single finding.
- Corrected inconsistent typography in Attack Path Mapping Atlas UI components.
- Resolved an issue where suppressed and remediation-complete attack paths continued to appear as open in the default Attack Paths list view.
- Fixed a display issue where the Attack Path Explorer could fail to render any nodes for a path, showing only an "incomplete path" warning.
- Resolved an issue where two AWS detection rules could produce zero findings for environments with a large number of matching resources.
- Corrected the underlying issue that could cause a path's hop count to differ between the Path Summary panel and the Attack Paths list.
- Resolved an issue where the Blast Radius panel's "reachable" and "protected" Crown Jewel counts could appear to contradict each other.
- Corrected a condition in the multi-rule attribution view where the selected rule's title displayed twice and long rule descriptions did not truncate.
- Resolved an issue where Blast Radius analysis did not traverse a specific AWS EKS connector-role edge type, producing incomplete results for some AWS Elastic Kubernetes Service paths.
- Fixed the display issue where AWS IAM policy-version and role-policy nodes could display a meaningless name (for example, "v1") in the Attack Path Explorer.
- Resolved an issue where a specific EASM detection rule bound its entry point to the vulnerability node instead of the internet-exposed service, causing the path to render backwards.
- Resolved an issue where a Crown Jewel could intermittently disappear from Blast Radius and other analyses that traverse it, despite its designation remaining intact.
Tanium Cloud Release Date: 19 June 2026
Initial release
- Tanium has added Tanium Attack Path Mapping (APM), a new Atlas-first solution that maps multi-hop attack paths from exposed assets to high-value targets across hybrid endpoint, cloud, and identity environments.
Features
- Added continuous attack path discovery via the Attack Path Explorer. APM continuously builds a graph of attack paths and surfaces each finding as an end-to-end traversal from entry condition to a terminal Crown Jewel.
- Added the Attack Path Explorer. Attack Path Explorer is the primary investigation surface for inspecting, filtering, and pivoting through attack-path findings.
- Added Blast Radius analysis. The blast radius analysis surfaces the downstream nodes reachable from a selected node so security teams can quantify the potential reach of any individual exposure.
- Added Choke Point analysis. The choke point analysis identifies single nodes whose remediation breaks the largest number of attack paths simultaneously, enabling high-leverage remediation decisions.
- Added native integration with Tanium Atlas. APM surfaces use Atlas's natural-language search, contextual navigation, and unified workbench.
- Added Crown Jewel targeting and designation from Tanium Atlas. You can define Crown Jewels by computer name, user name, directory role, cloud resources, directory roles, AWS KMS keys, and other node types.