Faddom Help Center



The Certificates view presents discovered certificates (from network capture) along with their status.

A certificate is identified by its serial number and you can see the server name on which it resides, the port number, and the common name. For each certificate, its validity dates and last update date are displayed as well as when it was last seen in use by Faddom.

Red certificates: means the certificate is expired.

Yellow certificates: means the certificate is about to expire.

When a certificate is about to expire or has expired, a notification is generated and displayed on the Notifications screen.


Certificates actions:

  • Delete Selected
    Select certificates to remove from the list. Certificates may appear again if they are observed in the captured traffic.
    Deleting certificates does not hide them from now on, only removes the current observation results
  • Filter Selected
    Select certificates that should be hidden from the list. A certificate that is filtered will not appear again until the filter is deleted.
  • Advanced Filters
    Create Advanced certificate filters; the server will ignore any certificate that falls within the filter(s) range
  • Manage Filters
    View defined certificate filters

VMWare VMs and Hosts

Discover details on VMs managed by a Vcenter Server, including further information about the operating system, CPU, memory, disks, and network cards. 

VMware discovery requires credentials for the Vcenter Server. To access, go to the Discover/VMware screen.

VMware discovery is managed through the Discover/VMware screen. 

Click the Discover from vCenter button to extract VM details from a vCenter Server. It is possible to add multiple vCenter Servers. For each one, specify the credentials to access the VMware API and extract the details for each deployed VM.

When adding a vCenter Server, it is possible to save its credentials for updating the configuration later.  These credentials are used when executing the VMware discovery again.

To execute VMware discovery, select Discover from VCenter, and click on the “Run Discovery” button for each vCenter: mceclip0.png

VMware discovery is also run automatically once a day if credentials are saved for the vCenter server.



Discover details on Microsoft Hyper-V, including the hosts and which VMs are running on them. Hyper-V discovery is performed through sFlow traffic that can be generated by a plugin to the Hyper-V extensible switch. 

To enable Hyper-V discovery, click on “Discover from Hyper-V” and follow instructions.



Discover Kubernetes cluster resources. To activate the Kubernetes discovery click on the “Add Cluster” button and insert cluster details.

To get detailed dependencies on the traffic between services in a Kubernetes environment, it is recommended to get network traffic to Faddom from the nodes in the cluster. This can be done using a tool such as Host sFlow to generate sFlow to send to Faddom or by installing a Faddom Sensor on the nodes.


Amazon EC2

Presents discovered AWS EC2 instances and their details such as the instance type, region, etc.
For each instance, you have actions for additional info on it: search, properties, charts, alarms.


Azure VMs

Presents discovered Microsoft Azure VMs and their details such as the instance size, location, etc.
For each instance, you have actions for additional info on it: search, properties, charts, alarms.


IP Groups

Presents discovered IP groups and their members. IP groups are most commonly discovered from Load Balancers or from the VMware discovery process.

IP groups can be load balancers, servers with multiple IP addresses, or any other type of grouping of IP addresses. An IP group is defined globally and the servers in it will be grouped together in all maps.

For each IP group, you can view or edit its members.

To add an IP group by discovery from Load Balancer click on “Discover from Load Balancer” button.

To manually add an IP group click “New”.


Was this article helpful?
0 out of 0 found this helpful