Versions Compared

Old Version 30

changes.mady.by.user Gary Leicht

Saved on

compared with

New Version 31

changes.mady.by.user Gary Leicht

Saved on

Key

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

...

  1. 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 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.
  2. You must also configure the destinations to which you want Data Connector to send source data. For details, see Configuring Destinations.
  3. 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 Filters.
  4. 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.
  5. NIOS IPMeta configuration flow to BloxOne Destination requires at least 16 GB RAM size for hosts where ipmeta flows are configured. If there are more frequent DB object updates then the RAM size needs to be further increased based on the DB size. It can be doubled to the previous memory resource limit ( i.e 16 * 2 = 32 GB ).

Info

Known Limitations
● You can only assign one destination for every traffic flow you create (see sections “Adding Traffic Flows” and “Adding destinations” for more information on traffic flows and destinations).

...