Documentation update

   

The service name is changed from BMC Helix Vulnerability Management to BMC Helix Automation Console.
You can find the latest documentation at BMC Helix Automation Console. Open link .

Configuring the BMC Discovery connector

BMC Discovery connector establishes connection with BMC Discovery (on-premises only) to find all the assets 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 which assets in your environment 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 and vulnerabilities.For BMC Helix Automation Console, you configure the connector from the UI using a Cloud Native User profile. This profile is created when you subscribe to the BMC Helix Automation Console service. For TrueSight Automation Console, as an administrator, you configure and enable the connector from the UI. 

Configuring the connector

To configure the connector, do these steps: 

  1. Go to BMC Helix Automation Console login page.
  2. Select the Login Profile as Cloud Native User and provide the credentials to login as a cloud user. 
  3. Go to the briefcase menu on the top right, and click Connectors > Add a Connector.
  4. From the on-premises connectors, select the BMC Discovery connector, and click Configure.
  5. On the Add a connector page, provide the following details:

    1. Enter the endpoint URL, in an FQDN format, with the port number where BMC Discovery is available.
    2. Select one of the authentication type: 
      • Token Based: Provide the token.
      • User Credential Based: Enter a username and password required to log on to BMC Discovery. 
        If using a user credential based approach, a service account is created for this integration.
        After entering the password, click Save.
    3. Select one of the Business Service Configuration option: 
      • Create Business Services for all Business Application Instances containing cloud resources
      • Create Business Service based on Subgroup name where manual Group name is: Provide a group name.
        At minimum, user should belong to the API access group.
    4. In the Collection Mode area, specify the data collection interval. 
      By default, the time interval is 60 minutes. Minimum acceptable is 5 minutes and maximum is 10080 minutes.

  6. Click Continue and download the connector zip file on a local host. 
  7. On the server where the connector file is downloaded and extracted, go to the connector location, and run the following command to install and start the connector: 
    • Windows: run.bat
    • Linux: run.sh

    The connector starts running successfully. You can view the connector status on the Connectors page. 

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.

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

Comments