Skip to Content
Information
Important This documentation space contains information about the SaaS version of Automation Console. If you are using the on-premises version of Automation Console, see TrueSight Automation Console 24.3

Configuring the BMC Discovery connector

BMC Discovery connector establishes a connection with BMC Discovery to find all the assets and related services (Business Services, Technical Services, and Business Applications) in a network. BMC discovery obtains information about the assets even if they are not enrolled in the endpoint manager, TrueSight Server Automation. As an administrator, when you integrate BMC Helix Automation Console or TrueSight Automation Console with BMC Discovery, you can identify the assets in your environment that are not included in vulnerability scans. These are blind spots, and they represent potential security risks. The blind spot assets appear on the Discovered Assets page. This helps to ensure that the discovered assets are scanned for missing patches, compliances, and vulnerabilities.

Warning
Important
  • When you edit the connector configuration, ensure that the server belongs to the Load Balancer setup or the Disaster Recovery setup in the same environment as the existing connector host. If you specify a new server outside of the Load Balancer setup or the Disaster Recovery setup, the existing data is duplicated leading to confusion and mismanagement.
  • When you configure the BMC Discovery connector on BMC Helix Automation Console or on TrueSight Automation Console, ensure that the Discovery Cloud Connector and the On-Prem Discovery connector are not configured together. If you do, then the data is duplicated leading to confusion and mismanagement.

To configure the Discovery Cloud connector

To configure the connector, perform the following steps: 

  1. In BMC Helix Automation Console, click Configuration and then click Connectors.
  2. On the Manage Connectors page, click Add Connector.
  3. On the Add Connector page, select Discovery Cloud Connector.
  4. On the Add Connector page, provide the following details:
    Add Discovery cloud connector.png

    Section

    Field

    Value

    Connector Details

    Connector Name

    The connector name; for example, Discovery Cloud Connector.

    Collection Mode

     

    The data collection interval

    • Select On Demand to trigger data collection as required.
    • In the At Scheduled Intervals field, specify the number of days after which data collection must be triggered.
      The time interval is 60 minutes by default. The minimum acceptable is 5 minutes, and the maximum is 10080 minutes.

    Share with

     

    A list of security groups that can access the Discovered Assets page; for example, ITManagers and PatchingUser.

    Exclude IPs/Hosts/Range

     

    A list of hosts or IPs or a range (only IPv4) for which resources must not be fetched from BMC Helix Discovery. The list must be comma-separated and can consist of hosts, IPs, or IPv4 range combinations; for example, 192.168.1.100,abc.xyz.com,192.168.10.100-192.168.10.200).
    Note: If you provide similar IPv4 ranges, only the last range is considered. For example, if you enter 10.12.11.100-10.12.11.200,10.12.11.150-10.12.11.200, only the last range 10.12.11.150-10.12.11.200 is considered for exclusion.

  5. Click Create.

Where to go next?

Now that you have successfully configured the connector and added a service account, based on the data refresh cycle configured in the service account, the assets appear in Automation Console, under Assets > Discovered Assets page. To view discovered assets, see, Working-with-assets.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Helix Automation Console