Resources

Products

Certificate Autodiscovery

Modified on: Tue, 31 Mar, 2026 at 4:42 PM

Note: Available only for new signups after the 31 March, 2026 release. If you signed up earlier, refer to the existing ITAM documentation.


Certificate autodiscovery jobs scan specified network assets to identify SSL certificates and import their details. If a certificate is discovered on an IP address already associated with a device in the system, it is automatically linked to that device. For more information on managing certificates after they are discovered, see the Certificates management page. 

Add SSL certificate discovery job

To create a new certificate autodiscovery job, follow these steps:

  1. Go to Admin > Asset Management > Scan and discover > click the Discovery Jobs tab.

  2. Select SSL Certificate from the list of discovery jobs and click Add new.

  3. Enter a relevant name for the discovery job.

  4. Enter the target IP address or range of IP addresses.

  5. Specify the ports to be scanned.

  6. To identify supported encryption methods, enable Find cipher suites supported by the server.
    Note: Discovering cipher suites can significantly slow down the discovery process. If you encounter performance issues or wish to speed up regularly scheduled jobs, disable this toggle.

  7. Scroll down to the Discovery Schedule section and click + Add new to set the run times and days.

  8. Click Save.

NoteNewly created jobs do not run on the day they are created. This prevents an unintentionally large number of jobs from running simultaneously during initial setup. To run a job immediately after creation, click Run Now on the job details page or the 

After the scan completes, go to Applications > Certificates to inspect the discovered data.

Multitenancy considerations

Certificate discovery can fail if multitenancy is enabled and the discovery job targets a VRF group whose subnet does not exist in the system. If you encounter this behavior, perform one of the following actions:

  • Create the target subnet manually in the system.

  • Run a network discovery first to populate the necessary subnets, as recommended in autodiscovery best practices.