AWS Discovery now goes beyond EC2 instances, giving you visibility into the managed cloud services modern AWS environments increasingly rely on.

We've expanded Kubernetes Discovery with new authentication and networking support, making it easier to map containerized environments end to end.

Faddom now uses DNS to identify the SaaS applications and domains behind your connections, adding useful context to application maps and external traffic.

Application maps now show DNS names for SaaS discovery, resolving connections to recognizable service names instead of raw IPs. Detected SaaS applications can be manually grouped and labeled.

External Traffic now includes DNS data as well. DNS names are shown for external connections when available, with ASN used as a fallback when a name can't be resolved. A new setting (off by default) lets you enable DNS identification for devices in your discovery scope, and you can now create policy rules directly from a DNS name.

Tier-Types now support additional criteria for assigning servers to tiers, such as ports, subnet, server name, and tags, and tier assignment logic has been extended to cover non-server assets like PaaS services. This gives more flexibility in how servers and services are automatically grouped into tiers, reducing the need for manual assignment.

Several improvements landed for Compass, Faddom's AI assistant, this release:

Following Zabbix integration, Faddom now supports Nagios as an out-of-the-box monitoring integration, letting you forward Nagios alerts directly into Faddom for analysis and context.

The Search view has been redesigned to match the look and feel of the tier-based servers design, for a more consistent experience across Faddom.

Operational events are now visible directly within Investigate charts, making it easier to correlate events with performance data.

Software Discovery now collects the domain of each server via WMI/SSH, adding useful context to inventory data.

You can now open the connection side panel directly from the Map List view.

When a device is removed from Faddom, its data is now retained in inventory along with the date of removal, instead of disappearing entirely.

Faddom's Public API now exposes inventory changes, extending the existing API suite for automation and integration use cases.

When editing a map with many elements, live updates could interrupt your work, refreshing mid-edit and forcing you to start over. You're now in control of when that happens. Pause live map refreshes while in edit mode, review pending changes via a banner showing the change count, and apply them on your own schedule with a "Refresh now" button. Available across all map types, including legacy maps.

Email notifications can now authenticate to Microsoft mail servers using OAuth, aligning with modern security requirements.

The Inventory view now supports customizable columns, so you can tailor the view to the data that matters most to you.

Azure Discovery now correctly ignores duplicate subscriptions defined multiple times under different credentials.

Export options for Subnet Dependencies have been improved for more complete and accurate reporting.

Migration planning now provides improved calculations and clearer indications for servers with missing pricing data.

A dedicated IP Groups page has been added to Inventory for easier management and visibility.

You can now save an advanced search directly as an application map.

VM creation date has been added to server properties and is now exposed via API.

Faddom can now be configured to define the LDAP user base at the root level, supporting a wider range of directory structures.

A hosts counter has been added to Inventory, and host information is now included in exports.

Search has been added to the dialog listing servers without detected software.

Application maps now show a clearer indication when filtering by port is active.

You can now search by text within the sensor deployment content library.

We resolved a mismatch between the server count shown in inventory and the server count listed under "My Account".

We resolved an issue affecting CVE Discovery when result sets were unusually large.

We fixed an issue where Active Directory credential validation used the local proxy instead of the proxy selected in configuration.

Faddom now clearly indicates when a Software Discovery task has no working credentials, instead of failing silently.

We resolved an issue causing duplicate entries to appear in User Inventory for the same account.

We fixed an issue where connection labels and their export option were missing in Tier View.

We fixed an issue preventing IP Groups from being assigned to server tiers.

We resolved an issue where Visio export failed for legacy maps without a saved layout.

We fixed an issue where User Discovery batches larger than 2MB failed to reach the server.

We resolved an issue where duplicate user entries were created on LDAP login and could not be deleted.

We fixed an issue where notification email links displayed a server's IP address instead of its configured hostname.

Failed connections are now more clearly shown in the Subnet Dependencies connection list.

We resolved an issue where the Update Map button stayed disabled after modifying a tag-based map's configuration.

We fixed an issue where the S3 session token failed to refresh while collecting flow logs from a shared folder.

We resolved an issue where data import failed due to CSV file size limits.

We fixed an issue where the Inventory search filter persisted incorrectly when switching screens.

We added a success confirmation when moving connections to tiers, which was previously missing.

We resolved an issue affecting LDAP domain and port modification in Access Control.

We resolved several inconsistencies in Advanced Search, including a Target filter that was incorrectly filtering by Source, filters not carrying over correctly between map and list views, and autocomplete not working when a dash was included in the search term.

We fixed an issue where the User Inventory table would repopulate with the full user count after counters finished loading, causing it to exceed its intended display limit of 500.
​