We've introduced a native Jira JSM integration through an Atlassian Forge app, enabling two-way synchronization between Faddom and Jira for streamlined IT operations and change management workflows.

We've significantly enhanced Compass, Faddom's AI-powered assistant, with new data sharing capabilities, a contextual side panel, and automatic insight generation to help teams get answers faster.

Faddom can now suggest application maps based on user activity patterns to identify logical groupings and recommend map structures that reflect how your environment is actually used.

Faddom now supports flow log collection from Kubernetes environments via Cilium CNI , enabling deeper visibility into container-level network traffic and inter-service communication.

Faddom now tracks and monitors changes to user discovery data, making it easier to detect when Active Directory or user-related information has been modified across discovery cycles.

Servers that are manually added to Faddom can now be enriched with additional information and fully managed, including editing, updating, and organizing within maps and groups.

The Inventory view now includes storage information for servers, providing visibility into disk capacity and utilization alongside existing hardware and software data.

The Faddom event log forwarding service can be deployed on an AD server, and will forward any user login events to the Faddom server or proxy, in a secure manner.

Faddom now supports discovering Azure and AWS environments through a Faddom Proxy, enabling cloud discovery in environments where direct API access is restricted or needs to be routed through a controlled endpoint.

We've expanded Faddom's Public API with a new Applications endpoint, allowing teams to programmatically access application map data for automation and integration workflows - for more info check our guide - here

External traffic policies can now use subnets as a source or target, enabling broader and more flexible network segmentation rules.

You can now trigger CVE discovery on a single server on demand, without waiting for a full scheduled scan. This enables faster vulnerability assessment for specific machines.

Migration planning now supports custom infrastructure services, allowing teams to define and include organization-specific services in their cloud migration cost calculations.

Migration pricing configuration now includes the option to set a minimum CPU threshold for VM sizing, ensuring that right-sizing recommendations meet your organization's performance requirements.

We improved the Policy Violations dashboard card and its modification behavior for a more consistent experience.

Both subnet traffic policies and external traffic policies can now be exported to CSV, enabling offline analysis and reporting.

The User panel now supports exporting user data, enabling teams to extract user discovery information for reporting and compliance purposes.

Faddom now supports hourly-partitioned AWS Flow Logs, in addition to the existing daily partitions, improving compatibility with different AWS configurations.

We've enhanced the full disk notification to provide clearer and more actionable alerts when Faddom's disk space is running low, helping administrators respond before it impacts operations.

A new dashboard view shows when users last logged into Faddom, providing administrators with visibility into user activity and helping identify inactive accounts.

ServiceNow has been added to the Integrations section in Settings, making it easier to configure and manage the ServiceNow integration directly from Faddom's settings page.

The Getting Started wizard now includes a step for configuring webhooks connections, helping new users set up external event integrations during onboarding.

We've added group-level settings options, allowing administrators to configure settings that apply across groups of users or assets.

We resolved an issue where internal subnets were incorrectly classified as external traffic in the Tier View, causing confusion in network segmentation analysis.

We fixed an issue where nmap port scanning activity was triggering false positive host discovery and generating incorrect Free IP reporting data.

We resolved an issue where the proxy used for User Discovery was unable to resolve non-standard domain names, causing discovery failures in certain environments.

We fixed an issue where in some cases, Azure rightsizing recommendations displayed incorrect data, ensuring accurate optimization suggestions.

We resolved an issue where the application tag, at some cases, would not persist when saved in Application Maps configuration.

We fixed an issue where servers powered off in vCenter incorrectly showed a healthy sensor status in Faddom.

We resolved an issue that caused Citrix API Discovery tasks to fail in some cases.

We fixed an issue where refreshing from the Edit Map screen, at some cases, did not recalculate the map data, requiring users to exit and re-enter the map.

We improved the error message shown when entering incorrect credentials for Nutanix discovery. Previously, the message incorrectly advised discovering Prism Element instead of indicating invalid credentials.

We fixed an issue where tag-based maps displayed wrong values when editing tags that contained dashes in their names.

We resolved an issue where clicking on an IP group in Application Maps incorrectly redirected to the dashboard instead of the expected view.

We fixed issues with ASN (Autonomous System Number) filtering in the Discovery Filters, ensuring correct filtering behavior.

We resolved an issue where exporting a Map/Wave with a special character in the name produced files with incorrect extensions.

We fixed an issue where Software and CVE Discovery would show as module locked in certain scenarios.

We resolved an error that occurred when accessing the database during user configuration updates.

We fixed an issue where Connection Behavior charts displayed incorrect data in certain scenarios.

We resolved an issue where the customize columns modal in the Connection List did not clear properly when closed.

We added a link in the Properties Panel to guide users to tag configuration when no tags are defined.

We fixed an issue where the refresh button in Advanced Search did not update the search results.

We added a visual indication when Software Discovery tasks are still running, so users know when the process is in progress.

We resolved an unexpected error that occurred when loading Application Clients in certain conditions.

We added the fix version field to CVE exports, providing more complete vulnerability data in exported reports.

We added a size limit to the Tomcat access log to prevent excessive disk usage in high-traffic environments.

We fixed an issue where change summary timestamps in Maps showed "N/A" for newly detected changes.

We fixed an issue where the Notifications Summary Report showed a default value of -1 for the day parameter.

We fixed a logic issue in scheduled tasks that caused incorrect pluralization handling.

We improved validation for AWS credentials to properly handle cases where the Access Key ID field was left blank.

We corrected the CVE count displayed in Server Properties to accurately reflect the number of vulnerabilities.

We resolved an issue where the Compass server table displayed servers that were not part of the active server discovery scope.