Versions Compared

Old Version 21

changes.mady.by.user Gary Leicht

Saved on

compared with

New Version 22

changes.mady.by.user Shirly Tsang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Review the prerequisites and requirements, then set up your environment and components. For details, see BloxOne Connectivity and Service Requirements.
  2. If you do not already have a join token, create one. For details, see Creating Join Tokens.
  3. Set up a Data Connector VM (virtual machine) by using either the Docker or OVA package (for container and VM) that Infoblox provides, and connect the virtual machine to the Cloud Services Portal using the join token. For information on all installer packages, including the installers for Docker or the OVA package, see Downloading BloxOne Apps. All installer packages are available at Administration > Downloads of the Cloud Services Portal. Within the Cloud Services Portal, all available installer packages are listed in the drop-down menu of the Hosts section of the page.
    Note that you deploy a Data Connector VM as a host running the Data Connector service in BloxOne DDI and or BloxOne Threat Defense Cloud. For details, see Deploying the Data Connector VMHosts.
  4. Log in to the Cloud Services Portal , locate the Data Connector VM, rename the host, and enable the Data Connector service on itthe configured host. For details, see Configuring Creating Services.
  5. Before you configure traffic flows for Data Connector, you must first set up the sources from which you want Data Connector to collect data. Note that BloxOne Threat Defense Cloud is preconfigured as the source and destination, and BloxOne DDI is preconfigured as the source. No configuration is required on your part. For details, see Configuring Sources.
  6. You must also configure the destinations to which you want Data Connector to send source data. For details, see Configuring Destinations.
  7. Optionally, you can add ETL (Extract, Transform, Load) filters to extract specific source data before Data Connector sends the data to the configured destinations.
    For details, see Configuring ETL filtersFilters.
  8. Once you have configured sources, destinations, and ETL filters, you can configure not only the traffic flows that define the types of source data that will be collected from the sources but also the destinations to which the data will be sent. For details, see Configuring Traffic Flows.