Setting up the BMC Discovery connector

This topic describes the process for setting up a connector for BMC Discovery. This connector enables communication between TrueSight Vulnerability Management and an instance of BMC Discovery. 

After setting up the connector, you can use TrueSight Vulnerability Management and BMC Discovery to enable blind spot detection and filter vulnerability data on dashboards by application.

The following sections in this topic describe how to set up the BMC Discovery connector.   

The following video demonstrates how to use TrueSight Vulnerability Management to set up a connector for BMC Discovery.

https://youtu.be/pcsg3CnZ28c

Before you begin

To set up a connector for BMC Discovery, confirm that a system connector for TrueSight Server Automation has already been set up

Note

When setting up connectors, a single machine cannot host more than one connector of the same type. For example, if you have set up a connector for Discovery on a host, you cannot set up another Discovery connector on the same host.

To set up a BMC Discovery connector

  1. Log on to TrueSight Vulnerability Management as a TrueSight Server Automation administrator with your registered credentials.
  2. Click the External Connectors tab. 
  3. Click Add External Connector
    The Create External Connection page appears. It lets you choose the connectors that interact with TrueSight Vulnerability Management.
    Note that you cannot add an external connector such as BMC Discovery without first adding a system connector for an endpoint manager such as TrueSight Server Automation. 
  4. From Type, select Discovery.

  5. Provide the following information for the BMC Discovery connector.

    Tip

    If you have access to the TrueSight Server Automation Application Server, you can obtain most of the following information by going to Configuration > Configuration Object Dictionary. Select Server Objects and then select Atrium Discovery in the list at left. The content panel at right provides Discovery connection information.

    OptionDescription
    Connection String

    URL for the Discovery instance, such as http://clm-aus-014680/ or http://10.0.0.10/.

    PortPort number used to connect to the Discovery instance.
    Username

    Name of the Discovery user required to connect to the Discovery instance.

    Note: For BMC Discovery versions 11.1 and later, ensure that your Discovery user is added to the api-access group in BMC Discovery. For more information, see XML API in the BMC Discovery documentation.

    PasswordPassword required to connect to the Discovery instance.
    Exclude IPs/Hosts/Range

    Comma-separated list of devices for which data should be filtered out. You can exclude individual IP addresses or host names. You can also mix host names and IP addresses. Special characters are not permitted in this list.

    Example individual IP address : 192.168.1.100

    Example of mixed formats: 192.168.1.100,192.168.1.120,myserver1234.com

    Example of IP address range: 192.168.1.1-192.168.1.5

  6. Click Test Connection to confirm that the connection to Discovery is working correctly.
    A message confirms that the connection is valid. 

  7. Click Create External Connector

Where to go from here 

Learn more about using BMC Discovery to detect blind spots and filter dashboard data by application.

Was this page helpful? Yes No Submitting... Thank you

Comments