Ask anything. Get answers - instantly.
​

Compass AI is Faddom’s new assistant that lets you query your environment in natural language. No dashboards, no filters, no syntax. Just type your question.
​

Disclaimer: Faddom can see the typed query, but never accesses your database or the AI-generated results.
​

Now available for a limited time - 30 days free for existing customers.

Faddom’s new Lighthouse AI automatically detects unusual traffic behavior and security threats — from DoS attacks and rogue connections to performance issues like outages and packet loss.

Powered by a multi-layer ML model (including VAE), Lighthouse highlights what matters, learns your environment, and reduces noise over time.

🧠 Covers:

• DoS, MITM, DNS spoofing, port scanning, data theft

• Outages, packet loss, network & app performance issues and more.

🔒 All data sent to Lighthouse is obfuscated for enhanced privacy and security.

⚙️ Early Access Only:

Faddom's application maps just got a major upgrade. The new tier-based view organizes servers by logical layers like Web, App, and DB - giving you a clearer, more structured view of application dependencies.
​

This enhanced layout is now the preferred default, designed for better visibility, easier navigation, and faster decision-making in complex environments.

Need the old view? It’s still accessible via the "View" toggle - but we think you’ll like the upgrade.t.

We’ve introduced a dedicated view to spotlight the most at risk servers in your environment - powered by the new Faddom Risk Score.

This unique scoring mechanism goes beyond basic CVE data. It adjusts for exploitability, real-world impact, and actual risk exposure based on everything

Faddom knows - including live traffic analysis, user access, and system context.

Revamped the Shadow IT screen with a new look and enhanced context on potential exposure. This update helps teams prioritize overlooked assets that may introduce security risk.

Revamped the Shadow IT screen with a new look and enhanced context on potential exposure. This update helps teams prioritize overlooked assets that may introduce security risk.

Redesigned the Import Data screen in Settings to improve usability and accessibility:

This update ensures cleaner workflows and better visibility for admins working with external data enrichment and tagging.

LDAP can now be configured directly from the UI, simplifying setup and removing the need for manual config file edits. This integrates with FaddomAuthenticator and supports:

Replaced “Track Search” with clearer “Save this search as Map” wording, added distinct classifications for Application, Tag-Based, and Tracked Search maps, and removed the legacy “Track Search” tree node. All map types can now be added to folders.

Added support for authenticating to Linux servers using certificates (keystores), enabling credential-less software discovery across environments aligned with modern cloud security practices.

Faddom now collects CPU and memory usage metrics for Google Cloud VMs, just like we do for AWS and Azure. This enables performance visibility across all major cloud providers.

You can now filter migration targets by their custom status—making it easier to focus only on what matters most in your workflow.

When adding credentials, we now verify the password against Active Directory. If it doesn't match—an error will be shown.

You can now see when external and subnet traffic policies were created or edited—plus, sort them by timestamp for easier tracking.

Users with limited permissions (like VIEWER) can now change their own passwords from the UI—no admin needed. This was previously restricted to admins only.

We’ve added a CVSS column and moved the CVE trendline to the bottom of the screen. The “Secure” dashboard is now hidden from the main tree, as it’s available via custom dashboards.

Added a global toggle under Global Parameters to enable/disable “Service Dependency” filtering across all maps.

Update notifications logic to record and display the user who marked a notification as "close" for improved traceability.

Add export option to generate a list of servers filtered by specific software.

Includes:

New “Tracked Operational Events” option in map settings

Lets users pick which event types are shown on servers.

We now prioritize and unify OS information across all parts of the platform. Data is collected from multiple sources—network traffic, hypervisor APIs, and software discovery—and only the most reliable result is shown. A new update priority logic ensures we don’t overwrite better data with older or less accurate inputs. This logic also now applies when updating custom fields. The result: cleaner, more consistent OS details everywhere, including server properties and Shadow IT.

The migration wave export now includes an additional tab listing all software details (such as SQL and server versions) for each server in the wave-offering deeper insights and eliminating the need to export the software inventory separately.

When discovering Azure environments, users can now see which subscriptions were detected by the app registration. This helps confirm expected access and provides guidance if additional permissions are needed.

You can now select multiple servers and use Add to map after revealing connections via Show Incoming or Show Outgoing.

This improves efficiency when working with several connections at once.

The ‘Last Seen’ timestamp is now shown per SSL certificate directly in the UI.

This improvement makes it easier to verify certificate activity without querying the database.

Expanded disk free space collection to include all data sources - previously limited to VMware and Nutanix only.

A new Throughput column has been added to the subnet dependencies view, showing per-port traffic levels.

This helps you quickly spot incoming vs. outgoing traffic trends, especially between on-prem and cloud environments.

You can now filter outgoing traffic by port in the Secure > External Traffic Dashboard — just like with incoming traffic.
​

This enhancement helps manage large-scale environments where per-server port filters are not practical.

Tooltips have been added to the Connection Properties section to help users better understand the data presented.

You can now filter source and target servers in the Connections List using partial names—no need for exact matches.

This makes it easier to locate, select, and filter multiple related servers in one go.

The Related Servers field in the CVEs table now shows server names instead of IP addresses, making it easier to recognize and interpret affected systems at a glance.

The CVEs dashboard now includes a Software column.

If multiple software entries exist, we show the first one followed by “+X more” for a clean, concise view.

Resolved an issue where flow log reads failed due to concurrent writes, leading to HTTP header errors and potential failures.

The sensor deployment screen now clearly notifies users when their vCenter version is unsupported, with a helpful message and link to relevant guidance. Prevents confusing "undefined" UI messages.

To address slow performance with large datasets, the SSL Insights table now limits initial API and DB loads to 100 results. Full search and filtering remain functional across the entire dataset.

User details in the inventory now display non-English characters correctly. This resolves an issue where such characters previously appeared as gibberish, particularly under Active Directory integration scenarios.

The mismatch between asset counters in the Dashboard and My Account was caused by each pulling from a different source.

This has now been resolved and the values are aligned.

Fixed an issue where editing a custom tag properties failed in some instances.

When selecting a time range of 24 hours or less in Advanced Search, a timestamp is now displayed so users can easily confirm the data’s timeframe.

Improved the migration wave logic to gracefully handle cases where disk sizing data is unavailable.

Fixed an issue where commas in vendor names disrupted the CSV export format. Vendor names are now properly quoted to preserve row structure.

Audit logs now correctly redact passwords when using DES authentication for SNMP mapping. Parameters are fully covered by the exclusion list to ensure sensitive data is never exposed.

Resolved an issue where migration wave exports showed only one side of each connection. Both source and target systems now appear correctly in dependency exports.

Resolved an issue where sFlow hosts were incorrectly listed twice—once as VMs and once as hosts. They now appear only in their correct role.