Faddom is an agentless Application Dependency Mapping solution that works passively (and not based on active scanning) and in real time, leveraging existing network traffic protocols.

No, with Faddom, all of your data remains in your environment. Nothing needs to be sent out to the cloud.

To deploy Faddom, you can either use our Linux based virtual machine template, or install on a clean Windows server. For details, check out our getting started page here.

On average it takes less than an hour to download Faddom, deploy it, and configure the traffic to reach the sensor. Maps will begin to appear up to 5 minutes after complete set up.

A virtual appliance is a pre-packaged virtual machine including an operating system including all the software that is needed to run the solution.

Yes, Faddom can work completely offline.

NetFlow is a network protocol that was originally developed by Cisco to analyze network traffic. It analyzes packets that are sent over the network and groups them into “flows” which are more or less based on the protocol, access points, source and destination IP addresses, and ports.

Netflow is supported on many devices and platforms, for further information please check this link .

Version 5 and newer (including IPFIX)

Similar to the NetFlow protocol we discussed in the previous post, sFlow is also a method to get information on the traffic between servers without getting the full traffic information. Like NetFlow, sFlow also supports using sampling to limit collection to 1 out of every X packets.

Like Netflow, sFlow is a popular standard and is supported by many devices including switches, routers, firewalls, and other devices.

All your data is stored inside your environment. Faddom comes with a pre-installed database server that stores all of your data.

Faddom does not create any overhead on the environment as it runs completely passively, listening to network protocols without accessing any of your servers.

All the maps are updated in near-real time.