Highlights
Micro-Segmentation Policy Planner & Enforcer
We introduced a dedicated Micro-Segmentation Policy Planner & Enforcer that lets you design, validate, and operationalize segmentation rules directly from Faddom.
The planner automatically builds policies from real application maps, tracks changes on existing rules, and enables direct enforcement in supported platforms
Automatically generate segmentation policies from Faddom’s live application topology.
Plan, compare, and track modifications across previously created rules.
Push planned policies directly to Nutanix Flow for immediate enforcement.
Coming soon: Enforcement for VMware NSX and Cloud Security Groups.
Third-Party Monitoring Integrations (Starting with Zabbix)
We’ve introduced a new integration framework that lets Faddom ingest alerts and events from external monitoring tools. The first out-of-the-box integration is with Zabbix, enabling customers to forward Zabbix alerts directly into Faddom for analysis and context.
Read more here
New capability to receive events from third-party monitoring systems into Faddom.
Official Zabbix integration using a prebuilt Media Type (Webhook) template.
Easy setup: import our JSON template into Zabbix and start sending events to Faddom.
Fully configurable on the customer’s Zabbix server (URL, method, JSON body, headers).
Automatic two-way synchronization with Zabbix to make sure nothing is missed.
Foundation for upcoming integrations with additional monitoring platforms.
Redesigned Application Dependencies View
We’ve delivered a complete redesign of the Application Dependencies view, making it faster, clearer, and easier to explore relationships across maps and folders.
Color-based grouping for folders and maps, providing instant visual clarity.
Arc-based structure that organizes folders, nested folders, and maps with clear separation lines.
Improved interactions: hover previews, connection highlighting, and click-to-focus behavior.
New Focus Mode: double-click any folder to isolate it, dim irrelevant data, and explore its maps and connections.
Find Free IP Addresses in Your Network
We’ve added a new network management capability that helps you quickly identify unused IP addresses within a selected subnet.
Faddom analyzes historical network traffic to pinpoint IPs that haven’t communicated in the past X days—making them safe candidates for new deployments.
Automatically find the first available IPs in any subnet based on real traffic history.
Add a comment/tag to reserve an IP, stored directly on the server’s custom tags once created.
Maintain a historical record of past IP assignments for auditing and tracking.
Search across all reserved IP notes and statuses.
Updated: Notifications vs. Operational Events
We’ve improved the Events & Notifications experience to make it easier to distinguish between Operational Events and general Notifications, helping teams focus on issues that may impact the stability of their environment.
Clear separation between Operational Events (items that can affect environment health or break functionality) and regular Notifications.
The bell icon screen now displays both categories with a clear visual distinction.
Operational Events are prioritized and shown by default, giving immediate visibility into issues that require attention.
Notifications retain a chronological, informational feed, while unread items are highlighted with improved badge indicators.
New Public API Documentation
New Public APIs with new endpoints for servers, connections, and external events, making it easier to integrate Faddom into automation workflows and monitoring ecosystems.
What’s now available
Connections: list connections with filters (source, target, port, tags) and retrieve full connection details.
Servers: list servers with advanced filtering and fetch complete server data including OS, tags, software, certificates, events, and relationships.
Events: create and update events in Faddom from monitoring tools using secure token-based authentication.
For full specifications, versioning details, and usage examples, visit our support portal.
API: Support Access Token Authentication (Replaces Basic Auth Option)
Our new API is using an access-token–based authentication model, enabling secure integrations. This enhancement aligns with our SAML implementation and modern security standards.
APIs can now be called using Bearer access tokens.
Removes dependency on Basic Auth for automated integrations.
Provides a more secure and compliant authentication method.
Additional Enhancements
Tag-Based Maps Now Show All Servers
Tag-based application maps now include all servers with the selected tag, even if they have no detected connections. This allows teams to visualize complete groups, track “floating” servers, and maintain tag-based organization without losing visibility.
Configure Active / Idle / Inactive Connection Timings
Faddom now allows customers to customize connection statuses: active, idle, or inactive. This makes connection state classification more flexible and better aligned with each environment’s behavior.
New settings under Global Parameters → Application Maps for configuring connection timing thresholds.
Adjust the durations for:
Active (default: recent activity)
Idle (default: >30 minutes)
Inactive (default: >1 hour)
Supports environments with longer-running tasks or unique activity patterns.
Provides more accurate dependency mapping based on real operational cycles.
New: Create Application Maps in Bulk Using Tags
We’ve added the ability to automatically create multiple application maps at once based on imported server tags. This streamlines onboarding for large environments and accelerates map creation during bulk data imports.
Highlights
Generate maps automatically for each unique value of a selected tag (e.g., “Application”).
Ideal for customers existing tagging of their servers.
Reduces manual work and ensures consistent map structure across large deployments.
New: Custom Tags with Dropdown/List Options
We’ve expanded the Custom Tags framework to support list-based (dropdown) fields, making it easier to standardize and control metadata across servers.
Automatic DNS Resolution for Servers Not in Maps
Faddom now periodically resolves DNS names for servers that are not part of any application map, ensuring broader and more accurate hostname coverage across the environment.
Weekly scheduled DNS resolution for all servers in the network topology that don’t already resolve automatically.
Automatically skips servers that repeatedly fail DNS resolution to avoid unnecessary load.
Applies only to servers without an existing VM name.
Collect Nutanix Categories
Faddom now automatically collects categories from Nutanix environments. This ensures that maps, planning features, and tag-based grouping stay aligned with the metadata defined in Nutanix.
Filter Application Maps Using Tags
We’ve added the ability to filter application maps based on server tags, making it easier to focus on specific groups, attributes, or classifications within a map.
Discover Multiple GCP Projects from a Single Service Account
We’ve expanded Faddom’s GCP discovery capabilities so customers can now use one Service Account to discover multiple GCP projects, instead of being limited to a single project per key.
Choose Which Credentials Are Used per Discovery Task
Software and CVE Discovery tasks can now run using only the credentials you select, rather than all credentials stored in Faddom. This gives teams tighter control, improves accuracy, and prevents unnecessary authentication attempts.
Select specific credentials for each discovery task via a simple checkbox UI.
Prevent account lockouts in environments with strict password policies.
Useful for mixed environments where some machines require local users while others use domain accounts.
Accurate Pricing for Windows VMs on 1- and 3-Year Reservations
We improved migration planning to correctly calculate Windows VM costs for 1-year and 3-year reserved contracts.
Adds missing Windows Server licensing cost for reserved instances.
Supports Azure Hybrid Benefit (AHB).
Provides accurate total pricing for Windows VM reservations.
Custom Scheduling for User Discovery
User Discovery can now run on a custom time interval, allowing customers to collect Active Directory data before logs are rotated or deleted.
Dismissed OS Events No Longer Re-Raised Daily
We resolved an issue where dismissed Operating System–related events (such as expired OS alerts) were being raised again on every discovery cycle.
Faddom now tracks dismissed OS events properly so they stay dismissed unless the user chooses otherwise.
Dismissed OS events are no longer re-generated on the next day’s discovery.
Prevents repetitive noise for known or intentionally ignored OS issues.
Filter Search Results by Port
You can now refine search results by filtering for specific ports directly within the Search view.
More Filters in Software Inventory
The Software Inventory view now supports additional filtering options, making it easier to locate and analyze software across large environments.
Filter by Vendor, Version, and Group.
Fixes & Updates
Database Upgrade: PostgreSQL 16
We are upgrading Faddom’s database from PostgreSQL 13 to PostgreSQL 16, ahead of PostgreSQL 13 reaching End of Life in November 2025. This ensures continued security, stability, and support for both new deployments and existing customer environments.
Platform Upgrade: Tomcat 10
We’ve upgraded Faddom’s application server to Tomcat 10, ensuring improved security, stability, and long-term support for future product enhancements.
Platform Update: Java 17
We are upgrading Faddom’s Java runtime from Java 11 to Java 17 to ensure compatibility with modern libraries and maintain long-term support.
Update: Clear MB (Bytes) Units in Connection Behavior Charts
We improved the Y-axis labeling in the Connection Behavior charts to clearly show MB (Bytes).
Fix: Correct Tier Classification for Servers and Ports
We improved how servers and ports are classified under tiers (e.g., Database, Web) so the view reflects only the traffic relevant to the selected tier.
Highlights
Only ports relevant to the tier are shown; all unrelated traffic is grouped under “Other ports.”
Prevents confusion caused by displaying all server ports in tier views.
Improved tier selection logic to choose the most relevant tier based on client activity.
Fix: Improved Stability for Software Discovery Tasks
We’ve addressed an issue where Software Discovery tasks could time out due to heavy thread usage during result processing.
Fix: Correct Column Headers in Inventory Data Source Export
We fixed an issue where the IP Address and Display Name columns in the inventory export were mislabeled, causing the data under each header to be swapped.
Fix: Missing Node Count for OpenShift Deployments
We resolved an issue where Kubernetes clusters deployed on Oracle OpenShift 4.16 showed correct services and pod data but reported a node count of 0 in Faddom.
Fix: Visio Export Colors Now Match the Faddom UI
We resolved inconsistencies between the colors shown in Faddom’s UI and those generated in Visio exports. Servers and connection lines now use the same color logic across both formats, ensuring accurate and predictable visuals.
Fix: Tag Values Not Displayed Correctly When Re-Editing Maps
We resolved an issue where tag-based maps showed incorrect or missing tag values when reopening Edit Map → Map Configuration.
Fix: Discovery Scope Changes Now Persist Correctly
We resolved an issue where excluded subnets were re-added to the discovery scope after running a new discovery cycle due to a stale cache in the SubnetManager.
Fix: Search UI No Longer Sends “undefined” to the API
We resolved an issue where at some cases, the Search UI sent an "undefined" value to the backend, causing API errors in certain environments.
Fix: Notifications Page Now Loads Reliably
We resolved an issue where the Notifications page failed to load due to a timing problem in the application list initialization.
Fix: Consistent Client Counts Between Map View and Tier View
We addressed discrepancies where the number of clients shown in Map View differed from the count shown in Tier View, causing confusion when expanding tiers.
Hostnames Containing “-” Now Searchable
We resolved an issue where servers with a dash (“-”) in their hostname were not indexed correctly, causing them to appear only when searching by IP.
DNS Responses No Longer Shown as Inbound External Traffic
We corrected an issue where DNS response packets (UDP) were incorrectly classified as inbound external connections.
UDP-based DNS/NTP responses are now filtered correctly.
External traffic view no longer displays DNS replies as inbound connections.
Clear Warning & Error Indicators for Data Sources
We improved the Data Sources screen to better show configuration status and surface issues immediately.