# Identity Mesh — August 20, 2026 **Release Date**: August 20, 2026 **Release Type**: Mixed (New Features, Improvements, Bug Fixes) ------------------------------------------------------------------------ ## Overview This release joins the cryptographic, software, hardware, and identity views of your estate into a single traversable graph, adds progress reporting to re-correlation runs, and resolves three defects in settings, connector entity counts, and certificate answers. - **Asset relationship graph** — follow a cryptographic asset up through the software that uses it, the hardware that runs it, and on to the identity that owns it, then back down again. - **Re-correlation progress** — a live progress bar with labeled steps and an estimated completion time, plus audit log entries as each step starts and finishes. - **Three fixes** — the SBOM Dependency Graph setting is readable for every organization, the connector entity collection drawer no longer reports failures for entity types it cannot count, and questions about a certificate's expiration date now return the date. ------------------------------------------------------------------------ ## New features ### Asset relationship graph Cryptographic, software, and hardware assets and the identities that own them are now one connected graph you can traverse, instead of separate views that never meet. **What you get:** - Anchor the graph on a cryptographic asset, a software asset, or a machine and see its neighborhood as a graph rather than a list. - Typed relationships — what runs on what, what uses which cryptography, what is installed where, and who owns it — so an edge tells you why two assets are connected. - Anchor on an identity instead, and see the software, machines, and cryptographic assets that identity owns alongside its groups, roles, and resources. - Filter the view by kind, to narrow a dense graph to software, hardware, cryptographic assets, or owners. - A badge when a neighborhood is large enough to be truncated, so a partial view is never mistaken for a complete one. **Why it matters:** post-quantum readiness work begins with a cryptographic finding and ends with a person who has to act on it. Walking from an algorithm to the software that uses it, the machine it runs on, and the identity accountable for it turns a finding into an owner and a remediation path. **Known limitation:** the step from a cryptographic asset to the software that uses it relies on inventory data that not every data source supplies today. Where that data is absent, the software step is omitted and the graph connects the remaining relationships. ------------------------------------------------------------------------ ## Improvements ### Re-correlation progress and estimated completion time Re-correlating an organization's data now reports how far the run has progressed and roughly when it will finish. **What you get:** - A progress bar showing percentage complete, labeled with the step currently running. - An estimated time to completion, derived from the number of identities in the run and the rate observed so far. - Audit log entries as each step starts and completes, so the run leaves a durable record you can review afterwards. - The bar reaches 100% when re-correlation itself finishes. Identity reconciliation continues after that as a background sweep; its completion time depends on queue conditions and is therefore not estimated, so its start and finish are recorded in the audit log instead. **Why it matters:** re-correlation on a large organization runs long enough that "is it still working?" is a fair question. A percentage and an estimate answer it directly, and the audit log entries answer it after the fact. ------------------------------------------------------------------------ ## Bug fixes ### SBOM Dependency Graph setting could not be read Under **Settings → General**, the SBOM Dependency Graph switch reported that the current setting could not be read, and stayed disabled, for any organization that had never changed it. Because the switch was inert in that state, the setting could not be changed for the first time from the interface at all, and reloading the page did not clear the error. An unchanged setting now resolves to its default, which is enabled, and the switch is usable. ------------------------------------------------------------------------ ### Connector entity counts reported failures for entity types that cannot be counted Opening the entity collection drawer for a connector raised error notifications and a failure message, and the connector row showed a failed status, even though data collection was healthy. The drawer requested counts for two entity types that have no counted source, and each of those requests failed. The drawer now requests only entity types that can be counted; counts for those appear as before, on every connector. ------------------------------------------------------------------------ ### Certificate expiration dates were unavailable to the assistant Asking a widget's chat for a certificate's expiration date returned an explanation that the validity dates had not been received, rather than the date — including for certificates whose expiry was already visible in the certificate list. Certificate validity is now part of the certificate detail the assistant can read, and a question about one certificate in the expiring-certificates widget is answered from a per-certificate lookup rather than from the widget's summary counts.