Run Certificate Discovery via individual URL scans

  • Rversion finale: Australia
  • Mis à jour 12 mars 2026
  • 1 minute de lecture
  • To initiate certificate discovery through URL scans, you must manually include individual URLs and configure a new certificate Discovery schedule.

    Avant de commencer

    Role required: discovery_admin or admin

    Pourquoi et quand exécuter cette tâche

    Only the certificates that are available on the server during URL scans can be discovered. To confirm the available certificates, use the following command:

    openssl s_client -showcerts -connect <URL>:<PORT> </dev/null

    Procédure

    1. Navigate to All > Certificate Management > Certificate Discovery Source URLS.
    2. To add individual URLs to the table, select New.
      Ensure accurate results by entering URLs in the following format: scheme://host:port. The port is optional, and defaults are used if not provided. For example: https://www.servicenow.com or https://servicenow.com:443, ldaps://myldap.com or ldaps://myldap.com:636.
    3. Create a Discovery schedule with the following fields.
      For more information on setting up your Discovery schedules, see Schedule a horizontal discovery.
      1. Select Discovery: Certificates.
      2. Select Certificate Discovery Type: URL Certificate Discovery.

        Keep the batch size as is, unless there is a specific recommendation to change it.

    4. To add or delete other URLs, from the Certificate URLs tab, select Edit.
    5. Select Submit.
    6. Select the checkbox to include URLs from the HTTP(s) Endpoint [cmdb_ci_endpoint_http] table in the discovery process.

    Résultats

    When your Discovery schedule runs, it automatically scans for any certificates on the specified URLs and fetches all URLs from the cmdb_ci_endpoint_http table. It then creates a mapping between the URL and the schedule in the sn_disco_certmgmt_cert_url_sched_m2m.

    With Service Mapping enabled, by default, it creates a relationship between the HTTP endpoint and application when it creates an entry in cmdb_ci_endpoint_http. For example, the Amazon application is automatically connected to amazon.com.

    The relationship is: cmdb_ci_endpoint_http[parent] --> [Implement End Point To::Implement End Point From] --> cmdb_ci_appl[child].

    If the above relationship exists, the URL certificate discovery creates an additional relationship between the certificate and application. This relationship is: cmdb_ci_appl[parent] --> [Uses::Used by] --> cmdb_ci_certificate[child].

    Remarque :
    URL discovery schedules do not generate server configuration items (CIs).